see also another report which is about the same thing -
https://www.dedoimedo.com/computers/ubuntu-kernel-6-8-100-buggy-network.html
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142510
Title:
Regression: ip route get intermittently returns broadcast …
<local,brd> for public IPs on 6.8.0-100 (breaks outbound TCP/Docker
pulls)
Status in linux package in Ubuntu:
New
Bug description:
Summary / Regression
This is a regression between Ubuntu kernels on an Ubuntu VM (Proxmox/QEMU/KVM, bridged networking, DHCP reservation). With 6.8.0-100-generic, ip -details route get <public-ip> intermittently returns an invalid cached result marking public IPs as broadcast/local (cache <local,brd>). When it enters this state, outbound TCP fails with "Network is unreachable" and Docker/Portainer pulls fail. Booting 6.8.0-90-generic on the same VM fixes it (route lookups remain unicast).
Environment
Ubuntu VM on Proxmox VE (QEMU/KVM), bridge vmbr0, DHCP reservation.
Reproduced across configuration changes: virtio/e1000 NIC, cpu
host/kvm64, cloud-init disabled; persists specifically with 6.8.0-100
and disappears with 6.8.0-90.
Evidence (6.8.0-100-generic)
Running repeatedly:
ip -details route get 1.1.1.1
shows flapping between correct unicast and incorrect broadcast classification:
unicast 1.1.1.1 via 192.168.1.1 dev ens18 table main src 192.168.1.72
cache
broadcast 1.1.1.1 via 192.168.1.1 dev ens18 table main src 192.168.1.72
cache <local,brd>
broadcast 1.1.1.1 via 192.168.1.1 dev ens18 table main src 192.168.1.72
cache <local,brd>
When the broadcast … <local,brd> state appears, outbound TCP
connections to public IPs fail ("Network is unreachable"), and ubuntu-
bug linux upload also sometimes fails with urlopen error [Errno 101]
Network is unreachable.
Expected
Public IPs should never be classified as broadcast … <local,brd> in route lookup; outbound TCP should stay stable.
Workaround
Boot kernel 6.8.0-90-generic (issue disappears). Flushing caches (ip route flush cache and ip neigh flush dev ens18) temporarily restores correct behavior on 6.8.0-100.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-100-generic 6.8.0-100.100
ProcVersionSignature: Ubuntu 6.8.0-100.100-generic 6.8.12
Uname: Linux 6.8.0-100-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
Date: Mon Feb 23 19:39:48 2026
InstallationDate: Installed on 2025-03-13 (347 days ago)
InstallationMedia: Ubuntu-Server 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm
ProcFB: 0 bochs-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-100-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro usbcore.autosuspend=-1
RelatedPackageVersions:
linux-restricted-modules-6.8.0-100-generic N/A
linux-backports-modules-6.8.0-100-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.22
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-9.2
dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-9.2:cvnQEMU:ct1:cvrpc-i440fx-9.2:sku:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-9.2
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142510/+subscriptions
понедельник
[Bug 2125250] Re: UBSAN: array-index-out-of-bounds in /build/linux-1ylo5V/linux-6.8.0/drivers/input/mouse/focaltech.c:221:17
Hi, All.
I've faced exactly with the same behaviour.
And hardware is Asus as well.
uname -a
Linux E402MA 6.8.0-100-generic #100-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 13 16:40:06 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux
2026-02-23T21:46:56.583079+02:00 E402MA kernel: ------------[ cut here ]------------
2026-02-23T21:46:56.583086+02:00 E402MA kernel: UBSAN: array-index-out-of-bounds in /build/linux-ylyFjh/linux-6.8.0/drivers/input/mouse/focaltech.c:222:17
2026-02-23T21:46:56.583093+02:00 E402MA kernel: index -1 is out of range for type 'focaltech_finger_state [5]'
2026-02-23T21:46:56.583502+02:00 E402MA kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.8.0-100-generic #100-Ubuntu
2026-02-23T21:46:56.583519+02:00 E402MA kernel: Hardware name: ASUSTeK COMPUTER INC. E402MA/E402MA, BIOS E402MA.207 01/28/2016
2026-02-23T21:46:56.583528+02:00 E402MA kernel: Call Trace:
2026-02-23T21:46:56.583535+02:00 E402MA kernel: <IRQ>
2026-02-23T21:46:56.583543+02:00 E402MA kernel: dump_stack_lvl+0x76/0xa0
2026-02-23T21:46:56.583551+02:00 E402MA kernel: dump_stack+0x10/0x20
2026-02-23T21:46:56.583559+02:00 E402MA kernel: __ubsan_handle_out_of_bounds+0xc6/0x110
2026-02-23T21:46:56.583568+02:00 E402MA kernel: focaltech_process_packet+0x3f8/0x400 [psmouse]
2026-02-23T21:46:56.583575+02:00 E402MA kernel: focaltech_process_byte+0x23/0x30 [psmouse]
2026-02-23T21:46:56.583636+02:00 E402MA kernel: psmouse_handle_byte+0x19/0x130 [psmouse]
2026-02-23T21:46:56.583650+02:00 E402MA kernel: psmouse_receive_byte+0x91/0x300 [psmouse]
2026-02-23T21:46:56.583659+02:00 E402MA kernel: ps2_interrupt+0xb7/0x1b0
2026-02-23T21:46:56.583667+02:00 E402MA kernel: serio_interrupt+0x4c/0xa0
2026-02-23T21:46:56.583675+02:00 E402MA kernel: i8042_interrupt+0x196/0x4c0
2026-02-23T21:46:56.583682+02:00 E402MA kernel: __handle_irq_event_percpu+0x4f/0x1b0
2026-02-23T21:46:56.583690+02:00 E402MA kernel: handle_irq_event+0x39/0x80
2026-02-23T21:46:56.583697+02:00 E402MA kernel: handle_edge_irq+0x8c/0x250
2026-02-23T21:46:56.583705+02:00 E402MA kernel: __common_interrupt+0x51/0xf0
2026-02-23T21:46:56.583712+02:00 E402MA kernel: common_interrupt+0x9f/0xb0
2026-02-23T21:46:56.583720+02:00 E402MA kernel: </IRQ>
2026-02-23T21:46:56.583727+02:00 E402MA kernel: <TASK>
2026-02-23T21:46:56.583734+02:00 E402MA kernel: asm_common_interrupt+0x27/0x40
2026-02-23T21:46:56.583741+02:00 E402MA kernel: RIP: 0010:cpuidle_enter_state+0xda/0x730
2026-02-23T21:46:56.583749+02:00 E402MA kernel: Code: b5 f4 fe e8 38 ef ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 46 44 f3 fe 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0
f 88 f7 01 00 00 4d 63 ee 49 83 fd 0a 0f 83 17 05 00 00
2026-02-23T21
...
Now I've disabled internal pointing device in BIOS. Working via x2x.
Regards,
Max
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2125250
Title:
UBSAN: array-index-out-of-bounds in
/build/linux-1ylo5V/linux-6.8.0/drivers/input/mouse/focaltech.c:221:17
Status in linux package in Ubuntu:
New
Bug description:
I'm facing this error in the journal.
It likely still happens in a recent kernel since I haven't seen any
change in the problematic piece of code
drivers/input/mouse/focaltech.c
This is on noble (6.8.0-83-generic #83-Ubuntu)
sept. 19 14:35:03 Albert2 kernel: ------------[ cut here ]------------
sept. 19 14:35:03 Albert2 kernel: UBSAN: array-index-out-of-bounds in /build/linux-1ylo5V/linux-6.8.0/drivers/input/mouse/focaltech.c:221:17
sept. 19 14:35:03 Albert2 kernel: index -1 is out of range for type 'focaltech_finger_state [5]'
sept. 19 14:35:03 Albert2 kernel: CPU: 2 PID: 0 Comm: swapper/2 Not tainted 6.8.0-83-generic #83-Ubuntu
sept. 19 14:35:03 Albert2 kernel: Hardware name: ASUSTeK COMPUTER INC. UX303LNB/UX303LNB, BIOS UX303LNB.206 01/22/2015
sept. 19 14:35:03 Albert2 kernel: Call Trace:
sept. 19 14:35:03 Albert2 kernel: <IRQ>
sept. 19 14:35:03 Albert2 kernel: dump_stack_lvl+0x76/0xa0
sept. 19 14:35:03 Albert2 kernel: dump_stack+0x10/0x20
sept. 19 14:35:03 Albert2 kernel: __ubsan_handle_out_of_bounds+0xc6/0x110
sept. 19 14:35:03 Albert2 kernel: focaltech_process_packet+0x3d0/0x400 [psmouse]
sept. 19 14:35:03 Albert2 kernel: focaltech_process_byte+0x23/0x30 [psmouse]
sept. 19 14:35:03 Albert2 kernel: psmouse_handle_byte+0x19/0x130 [psmouse]
sept. 19 14:35:03 Albert2 kernel: psmouse_receive_byte+0x91/0x300 [psmouse]
sept. 19 14:35:03 Albert2 kernel: ps2_interrupt+0xb7/0x1b0
sept. 19 14:35:03 Albert2 kernel: serio_interrupt+0x4c/0xa0
sept. 19 14:35:03 Albert2 kernel: i8042_interrupt+0x196/0x4c0
sept. 19 14:35:03 Albert2 kernel: __handle_irq_event_percpu+0x4f/0x1b0
sept. 19 14:35:03 Albert2 kernel: handle_irq_event+0x39/0x80
sept. 19 14:35:03 Albert2 kernel: handle_edge_irq+0x8c/0x250
sept. 19 14:35:03 Albert2 kernel: __common_interrupt+0x51/0xf0
sept. 19 14:35:03 Albert2 kernel: common_interrupt+0x9f/0xb0
sept. 19 14:35:03 Albert2 kernel: </IRQ>
sept. 19 14:35:03 Albert2 kernel: <TASK>
sept. 19 14:35:03 Albert2 kernel: asm_common_interrupt+0x27/0x40
sept. 19 14:35:03 Albert2 kernel: RIP: 0010:cpuidle_enter_state+0xda/0x730
sept. 19 14:35:03 Albert2 kernel: Code: 05 f5 fe e8 38 ee ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 36 94 f3 fe 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 f7 01 00 00 4d 63 ee 49 83 fd 0a 0f 83 17 05 00 00
sept. 19 14:35:03 Albert2 kernel: RSP: 0018:ffffbf28c00f3e18 EFLAGS: 00000246
sept. 19 14:35:03 Albert2 kernel: RAX: 0000000000000000 RBX: ffff97dce6d55a60 RCX: 0000000000000000
sept. 19 14:35:03 Albert2 kernel: RDX: 0000000000000002 RSI: 0000000000000000 RDI: 0000000000000000
sept. 19 14:35:03 Albert2 kernel: RBP: ffffbf28c00f3e68 R08: 0000000000000000 R09: 0000000000000000
sept. 19 14:35:03 Albert2 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff928e68a0
sept. 19 14:35:03 Albert2 kernel: R13: 0000000000000008 R14: 0000000000000008 R15: 0000001f22eb3ce7
sept. 19 14:35:03 Albert2 kernel: ? cpuidle_enter_state+0xca/0x730
sept. 19 14:35:03 Albert2 kernel: cpuidle_enter+0x2e/0x50
sept. 19 14:35:03 Albert2 kernel: call_cpuidle+0x23/0x60
sept. 19 14:35:03 Albert2 kernel: cpuidle_idle_call+0x11d/0x190
sept. 19 14:35:03 Albert2 kernel: do_idle+0x87/0xf0
sept. 19 14:35:03 Albert2 kernel: cpu_startup_entry+0x2a/0x30
sept. 19 14:35:03 Albert2 kernel: start_secondary+0x129/0x160
sept. 19 14:35:03 Albert2 kernel: secondary_startup_64_no_verify+0x184/0x18b
sept. 19 14:35:03 Albert2 kernel: </TASK>
sept. 19 14:35:03 Albert2 kernel: ---[ end trace ]---
Note that I had the same error on jammy (5.15.0-153-generic
#163-Ubuntu)
sept. 19 13:09:38 Albert2 kernel: ================================================================================
sept. 19 13:09:38 Albert2 kernel: UBSAN: array-index-out-of-bounds in /build/linux-s9dSph/linux-5.15.0/drivers/input/mouse/focaltech.c:222:29
sept. 19 13:09:38 Albert2 kernel: index -1 is out of range for type 'focaltech_finger_state [5]'
sept. 19 13:09:38 Albert2 kernel: CPU: 2 PID: 0 Comm: swapper/2 Tainted: P OE 5.15.0-153-generic #163-Ubuntu
sept. 19 13:09:38 Albert2 kernel: Hardware name: ASUSTeK COMPUTER INC. UX303LNB/UX303LNB, BIOS UX303LNB.206 01/22/2015
sept. 19 13:09:38 Albert2 kernel: Call Trace:
sept. 19 13:09:38 Albert2 kernel: <IRQ>
sept. 19 13:09:38 Albert2 kernel: show_stack+0x52/0x5c
sept. 19 13:09:38 Albert2 kernel: dump_stack_lvl+0x4a/0x63
sept. 19 13:09:38 Albert2 kernel: dump_stack+0x10/0x16
sept. 19 13:09:38 Albert2 kernel: ubsan_epilogue+0x9/0x36
sept. 19 13:09:38 Albert2 kernel: __ubsan_handle_out_of_bounds.cold+0x44/0x49
sept. 19 13:09:38 Albert2 kernel: focaltech_process_packet+0x366/0x3a0 [psmouse]
sept. 19 13:09:38 Albert2 kernel: focaltech_process_byte+0x21/0x30 [psmouse]
sept. 19 13:09:38 Albert2 kernel: psmouse_handle_byte+0x19/0x70 [psmouse]
sept. 19 13:09:38 Albert2 kernel: psmouse_interrupt+0xd8/0x410 [psmouse]
sept. 19 13:09:38 Albert2 kernel: serio_interrupt+0x4d/0xa0
sept. 19 13:09:38 Albert2 kernel: i8042_interrupt+0x1b4/0x370
sept. 19 13:09:38 Albert2 kernel: __handle_irq_event_percpu+0x42/0x170
sept. 19 13:09:38 Albert2 kernel: handle_irq_event+0x59/0xb0
sept. 19 13:09:38 Albert2 kernel: handle_edge_irq+0x8c/0x230
sept. 19 13:09:38 Albert2 kernel: __common_interrupt+0x52/0xe0
sept. 19 13:09:38 Albert2 kernel: common_interrupt+0x89/0xa0
sept. 19 13:09:38 Albert2 kernel: </IRQ>
sept. 19 13:09:38 Albert2 kernel: <TASK>
sept. 19 13:09:38 Albert2 kernel: asm_common_interrupt+0x27/0x40
sept. 19 13:09:38 Albert2 kernel: RIP: 0010:cpuidle_enter_state+0xd9/0x620
sept. 19 13:09:38 Albert2 kernel: Code: 3d cc 60 37 4a e8 d7 b6 66 ff 49 89 c7 0f 1f 44 00 00 31 ff e8 28 c4 66 ff 80 7d d0 00 0f 85 61 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 f6 0f 88 6d 01 00 00 4d 63 ee 49 83 fd 09 0f 87 e7 03 00 00
sept. 19 13:09:38 Albert2 kernel: RSP: 0018:ffffb400800e3e28 EFLAGS: 00000246
sept. 19 13:09:38 Albert2 kernel: RAX: ffff901566d320c0 RBX: ffffd4007fd00000 RCX: 0000000000000000
sept. 19 13:09:38 Albert2 kernel: RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
sept. 19 13:09:38 Albert2 kernel: RBP: ffffb400800e3e78 R08: 0000001ea069a684 R09: 00000000001b7740
sept. 19 13:09:38 Albert2 kernel: R10: 0000000000000009 R11: 071c71c71c71c71c R12: ffffffffb72d6fa0
sept. 19 13:09:38 Albert2 kernel: R13: 0000000000000006 R14: 0000000000000006 R15: 0000001ea069a684
sept. 19 13:09:38 Albert2 kernel: ? cpuidle_enter_state+0xc8/0x620
sept. 19 13:09:38 Albert2 kernel: cpuidle_enter+0x2e/0x50
sept. 19 13:09:38 Albert2 kernel: cpuidle_idle_call+0x142/0x1e0
sept. 19 13:09:38 Albert2 kernel: do_idle+0x83/0xf0
sept. 19 13:09:38 Albert2 kernel: cpu_startup_entry+0x20/0x30
sept. 19 13:09:38 Albert2 kernel: start_secondary+0x12a/0x180
sept. 19 13:09:38 Albert2 kernel: secondary_startup_64_no_verify+0xc2/0xcb
sept. 19 13:09:38 Albert2 kernel: </TASK>
sept. 19 13:09:38 Albert2 kernel: ================================================================================
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.10
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: fabien 5742 F.... pulseaudio
/dev/snd/controlC1: fabien 5742 F.... pulseaudio
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
HibernationDevice: RESUME=UUID=70d9afbb-2d9a-4b6e-88f0-68d461d2b003
InstallationDate: Installed on 2015-07-13 (3721 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
Lsusb:
Bus 002 Device 002: ID 0bda:9210 Realtek Semiconductor Corp. RTL9210 M.2 NVME Adapter
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX303LNB
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-153-generic root=UUID=d0293d5f-398e-4356-b7fd-055cfc3abb3a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-153.163-generic 5.15.185
RelatedPackageVersions:
linux-restricted-modules-5.15.0-153-generic N/A
linux-backports-modules-5.15.0-153-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.39
Tags: jammy
Uname: Linux 5.15.0-153-generic x86_64
UpgradeStatus: Upgraded to jammy on 2025-06-07 (104 days ago)
UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/22/2015
dmi.bios.release: 5.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX303LNB.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX303LNB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LNB.206:bd01/22/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnUX303LNB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LNB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
dmi.product.family: UX
dmi.product.name: UX303LNB
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: fabien 2378 F.... wireplumber
/dev/snd/controlC0: fabien 2378 F.... wireplumber
/dev/snd/seq: fabien 2371 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 24.04
HibernationDevice: RESUME=UUID=70d9afbb-2d9a-4b6e-88f0-68d461d2b003
InstallationDate: Installed on 2015-07-13 (3722 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 0bda:9210 Realtek Semiconductor Corp. RTL9210 M.2 NVME Adapter
MachineType: ASUSTeK COMPUTER INC. UX303LNB
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-83-generic root=UUID=9737a659-57d0-4b16-857c-df68048312a7 ro quiet splash resume=UUID=70d9afbb-2d9a-4b6e-88f0-68d461d2b003 vt.handoff=7
ProcVersionSignature: Ubuntu 6.8.0-83.83-generic 6.8.12
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.8.0-83-generic N/A
linux-backports-modules-6.8.0-83-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.17
Tags: noble
Uname: Linux 6.8.0-83-generic x86_64
UpgradeStatus: Upgraded to noble on 2025-09-19 (1 days ago)
UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/22/2015
dmi.bios.release: 5.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX303LNB.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX303LNB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LNB.206:bd01/22/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnUX303LNB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LNB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
dmi.product.family: UX
dmi.product.name: UX303LNB
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
In attachment you'll find first the ones for jammy (kernel 5.15), then the ones for noble (kernel 6.8) and finally the kernel log of the previous boot which has the error. The current boot showed the error only later. So there also an additional dmesg output.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2125250/+subscriptions
I've faced exactly with the same behaviour.
And hardware is Asus as well.
uname -a
Linux E402MA 6.8.0-100-generic #100-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 13 16:40:06 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux
2026-02-23T21:46:56.583079+02:00 E402MA kernel: ------------[ cut here ]------------
2026-02-23T21:46:56.583086+02:00 E402MA kernel: UBSAN: array-index-out-of-bounds in /build/linux-ylyFjh/linux-6.8.0/drivers/input/mouse/focaltech.c:222:17
2026-02-23T21:46:56.583093+02:00 E402MA kernel: index -1 is out of range for type 'focaltech_finger_state [5]'
2026-02-23T21:46:56.583502+02:00 E402MA kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.8.0-100-generic #100-Ubuntu
2026-02-23T21:46:56.583519+02:00 E402MA kernel: Hardware name: ASUSTeK COMPUTER INC. E402MA/E402MA, BIOS E402MA.207 01/28/2016
2026-02-23T21:46:56.583528+02:00 E402MA kernel: Call Trace:
2026-02-23T21:46:56.583535+02:00 E402MA kernel: <IRQ>
2026-02-23T21:46:56.583543+02:00 E402MA kernel: dump_stack_lvl+0x76/0xa0
2026-02-23T21:46:56.583551+02:00 E402MA kernel: dump_stack+0x10/0x20
2026-02-23T21:46:56.583559+02:00 E402MA kernel: __ubsan_handle_out_of_bounds+0xc6/0x110
2026-02-23T21:46:56.583568+02:00 E402MA kernel: focaltech_process_packet+0x3f8/0x400 [psmouse]
2026-02-23T21:46:56.583575+02:00 E402MA kernel: focaltech_process_byte+0x23/0x30 [psmouse]
2026-02-23T21:46:56.583636+02:00 E402MA kernel: psmouse_handle_byte+0x19/0x130 [psmouse]
2026-02-23T21:46:56.583650+02:00 E402MA kernel: psmouse_receive_byte+0x91/0x300 [psmouse]
2026-02-23T21:46:56.583659+02:00 E402MA kernel: ps2_interrupt+0xb7/0x1b0
2026-02-23T21:46:56.583667+02:00 E402MA kernel: serio_interrupt+0x4c/0xa0
2026-02-23T21:46:56.583675+02:00 E402MA kernel: i8042_interrupt+0x196/0x4c0
2026-02-23T21:46:56.583682+02:00 E402MA kernel: __handle_irq_event_percpu+0x4f/0x1b0
2026-02-23T21:46:56.583690+02:00 E402MA kernel: handle_irq_event+0x39/0x80
2026-02-23T21:46:56.583697+02:00 E402MA kernel: handle_edge_irq+0x8c/0x250
2026-02-23T21:46:56.583705+02:00 E402MA kernel: __common_interrupt+0x51/0xf0
2026-02-23T21:46:56.583712+02:00 E402MA kernel: common_interrupt+0x9f/0xb0
2026-02-23T21:46:56.583720+02:00 E402MA kernel: </IRQ>
2026-02-23T21:46:56.583727+02:00 E402MA kernel: <TASK>
2026-02-23T21:46:56.583734+02:00 E402MA kernel: asm_common_interrupt+0x27/0x40
2026-02-23T21:46:56.583741+02:00 E402MA kernel: RIP: 0010:cpuidle_enter_state+0xda/0x730
2026-02-23T21:46:56.583749+02:00 E402MA kernel: Code: b5 f4 fe e8 38 ef ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 46 44 f3 fe 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0
f 88 f7 01 00 00 4d 63 ee 49 83 fd 0a 0f 83 17 05 00 00
2026-02-23T21
...
Now I've disabled internal pointing device in BIOS. Working via x2x.
Regards,
Max
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2125250
Title:
UBSAN: array-index-out-of-bounds in
/build/linux-1ylo5V/linux-6.8.0/drivers/input/mouse/focaltech.c:221:17
Status in linux package in Ubuntu:
New
Bug description:
I'm facing this error in the journal.
It likely still happens in a recent kernel since I haven't seen any
change in the problematic piece of code
drivers/input/mouse/focaltech.c
This is on noble (6.8.0-83-generic #83-Ubuntu)
sept. 19 14:35:03 Albert2 kernel: ------------[ cut here ]------------
sept. 19 14:35:03 Albert2 kernel: UBSAN: array-index-out-of-bounds in /build/linux-1ylo5V/linux-6.8.0/drivers/input/mouse/focaltech.c:221:17
sept. 19 14:35:03 Albert2 kernel: index -1 is out of range for type 'focaltech_finger_state [5]'
sept. 19 14:35:03 Albert2 kernel: CPU: 2 PID: 0 Comm: swapper/2 Not tainted 6.8.0-83-generic #83-Ubuntu
sept. 19 14:35:03 Albert2 kernel: Hardware name: ASUSTeK COMPUTER INC. UX303LNB/UX303LNB, BIOS UX303LNB.206 01/22/2015
sept. 19 14:35:03 Albert2 kernel: Call Trace:
sept. 19 14:35:03 Albert2 kernel: <IRQ>
sept. 19 14:35:03 Albert2 kernel: dump_stack_lvl+0x76/0xa0
sept. 19 14:35:03 Albert2 kernel: dump_stack+0x10/0x20
sept. 19 14:35:03 Albert2 kernel: __ubsan_handle_out_of_bounds+0xc6/0x110
sept. 19 14:35:03 Albert2 kernel: focaltech_process_packet+0x3d0/0x400 [psmouse]
sept. 19 14:35:03 Albert2 kernel: focaltech_process_byte+0x23/0x30 [psmouse]
sept. 19 14:35:03 Albert2 kernel: psmouse_handle_byte+0x19/0x130 [psmouse]
sept. 19 14:35:03 Albert2 kernel: psmouse_receive_byte+0x91/0x300 [psmouse]
sept. 19 14:35:03 Albert2 kernel: ps2_interrupt+0xb7/0x1b0
sept. 19 14:35:03 Albert2 kernel: serio_interrupt+0x4c/0xa0
sept. 19 14:35:03 Albert2 kernel: i8042_interrupt+0x196/0x4c0
sept. 19 14:35:03 Albert2 kernel: __handle_irq_event_percpu+0x4f/0x1b0
sept. 19 14:35:03 Albert2 kernel: handle_irq_event+0x39/0x80
sept. 19 14:35:03 Albert2 kernel: handle_edge_irq+0x8c/0x250
sept. 19 14:35:03 Albert2 kernel: __common_interrupt+0x51/0xf0
sept. 19 14:35:03 Albert2 kernel: common_interrupt+0x9f/0xb0
sept. 19 14:35:03 Albert2 kernel: </IRQ>
sept. 19 14:35:03 Albert2 kernel: <TASK>
sept. 19 14:35:03 Albert2 kernel: asm_common_interrupt+0x27/0x40
sept. 19 14:35:03 Albert2 kernel: RIP: 0010:cpuidle_enter_state+0xda/0x730
sept. 19 14:35:03 Albert2 kernel: Code: 05 f5 fe e8 38 ee ff ff 8b 53 04 49 89 c7 0f 1f 44 00 00 31 ff e8 36 94 f3 fe 80 7d d0 00 0f 85 61 02 00 00 fb 0f 1f 44 00 00 <45> 85 f6 0f 88 f7 01 00 00 4d 63 ee 49 83 fd 0a 0f 83 17 05 00 00
sept. 19 14:35:03 Albert2 kernel: RSP: 0018:ffffbf28c00f3e18 EFLAGS: 00000246
sept. 19 14:35:03 Albert2 kernel: RAX: 0000000000000000 RBX: ffff97dce6d55a60 RCX: 0000000000000000
sept. 19 14:35:03 Albert2 kernel: RDX: 0000000000000002 RSI: 0000000000000000 RDI: 0000000000000000
sept. 19 14:35:03 Albert2 kernel: RBP: ffffbf28c00f3e68 R08: 0000000000000000 R09: 0000000000000000
sept. 19 14:35:03 Albert2 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff928e68a0
sept. 19 14:35:03 Albert2 kernel: R13: 0000000000000008 R14: 0000000000000008 R15: 0000001f22eb3ce7
sept. 19 14:35:03 Albert2 kernel: ? cpuidle_enter_state+0xca/0x730
sept. 19 14:35:03 Albert2 kernel: cpuidle_enter+0x2e/0x50
sept. 19 14:35:03 Albert2 kernel: call_cpuidle+0x23/0x60
sept. 19 14:35:03 Albert2 kernel: cpuidle_idle_call+0x11d/0x190
sept. 19 14:35:03 Albert2 kernel: do_idle+0x87/0xf0
sept. 19 14:35:03 Albert2 kernel: cpu_startup_entry+0x2a/0x30
sept. 19 14:35:03 Albert2 kernel: start_secondary+0x129/0x160
sept. 19 14:35:03 Albert2 kernel: secondary_startup_64_no_verify+0x184/0x18b
sept. 19 14:35:03 Albert2 kernel: </TASK>
sept. 19 14:35:03 Albert2 kernel: ---[ end trace ]---
Note that I had the same error on jammy (5.15.0-153-generic
#163-Ubuntu)
sept. 19 13:09:38 Albert2 kernel: ================================================================================
sept. 19 13:09:38 Albert2 kernel: UBSAN: array-index-out-of-bounds in /build/linux-s9dSph/linux-5.15.0/drivers/input/mouse/focaltech.c:222:29
sept. 19 13:09:38 Albert2 kernel: index -1 is out of range for type 'focaltech_finger_state [5]'
sept. 19 13:09:38 Albert2 kernel: CPU: 2 PID: 0 Comm: swapper/2 Tainted: P OE 5.15.0-153-generic #163-Ubuntu
sept. 19 13:09:38 Albert2 kernel: Hardware name: ASUSTeK COMPUTER INC. UX303LNB/UX303LNB, BIOS UX303LNB.206 01/22/2015
sept. 19 13:09:38 Albert2 kernel: Call Trace:
sept. 19 13:09:38 Albert2 kernel: <IRQ>
sept. 19 13:09:38 Albert2 kernel: show_stack+0x52/0x5c
sept. 19 13:09:38 Albert2 kernel: dump_stack_lvl+0x4a/0x63
sept. 19 13:09:38 Albert2 kernel: dump_stack+0x10/0x16
sept. 19 13:09:38 Albert2 kernel: ubsan_epilogue+0x9/0x36
sept. 19 13:09:38 Albert2 kernel: __ubsan_handle_out_of_bounds.cold+0x44/0x49
sept. 19 13:09:38 Albert2 kernel: focaltech_process_packet+0x366/0x3a0 [psmouse]
sept. 19 13:09:38 Albert2 kernel: focaltech_process_byte+0x21/0x30 [psmouse]
sept. 19 13:09:38 Albert2 kernel: psmouse_handle_byte+0x19/0x70 [psmouse]
sept. 19 13:09:38 Albert2 kernel: psmouse_interrupt+0xd8/0x410 [psmouse]
sept. 19 13:09:38 Albert2 kernel: serio_interrupt+0x4d/0xa0
sept. 19 13:09:38 Albert2 kernel: i8042_interrupt+0x1b4/0x370
sept. 19 13:09:38 Albert2 kernel: __handle_irq_event_percpu+0x42/0x170
sept. 19 13:09:38 Albert2 kernel: handle_irq_event+0x59/0xb0
sept. 19 13:09:38 Albert2 kernel: handle_edge_irq+0x8c/0x230
sept. 19 13:09:38 Albert2 kernel: __common_interrupt+0x52/0xe0
sept. 19 13:09:38 Albert2 kernel: common_interrupt+0x89/0xa0
sept. 19 13:09:38 Albert2 kernel: </IRQ>
sept. 19 13:09:38 Albert2 kernel: <TASK>
sept. 19 13:09:38 Albert2 kernel: asm_common_interrupt+0x27/0x40
sept. 19 13:09:38 Albert2 kernel: RIP: 0010:cpuidle_enter_state+0xd9/0x620
sept. 19 13:09:38 Albert2 kernel: Code: 3d cc 60 37 4a e8 d7 b6 66 ff 49 89 c7 0f 1f 44 00 00 31 ff e8 28 c4 66 ff 80 7d d0 00 0f 85 61 01 00 00 fb 66 0f 1f 44 00 00 <45> 85 f6 0f 88 6d 01 00 00 4d 63 ee 49 83 fd 09 0f 87 e7 03 00 00
sept. 19 13:09:38 Albert2 kernel: RSP: 0018:ffffb400800e3e28 EFLAGS: 00000246
sept. 19 13:09:38 Albert2 kernel: RAX: ffff901566d320c0 RBX: ffffd4007fd00000 RCX: 0000000000000000
sept. 19 13:09:38 Albert2 kernel: RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000000
sept. 19 13:09:38 Albert2 kernel: RBP: ffffb400800e3e78 R08: 0000001ea069a684 R09: 00000000001b7740
sept. 19 13:09:38 Albert2 kernel: R10: 0000000000000009 R11: 071c71c71c71c71c R12: ffffffffb72d6fa0
sept. 19 13:09:38 Albert2 kernel: R13: 0000000000000006 R14: 0000000000000006 R15: 0000001ea069a684
sept. 19 13:09:38 Albert2 kernel: ? cpuidle_enter_state+0xc8/0x620
sept. 19 13:09:38 Albert2 kernel: cpuidle_enter+0x2e/0x50
sept. 19 13:09:38 Albert2 kernel: cpuidle_idle_call+0x142/0x1e0
sept. 19 13:09:38 Albert2 kernel: do_idle+0x83/0xf0
sept. 19 13:09:38 Albert2 kernel: cpu_startup_entry+0x20/0x30
sept. 19 13:09:38 Albert2 kernel: start_secondary+0x12a/0x180
sept. 19 13:09:38 Albert2 kernel: secondary_startup_64_no_verify+0xc2/0xcb
sept. 19 13:09:38 Albert2 kernel: </TASK>
sept. 19 13:09:38 Albert2 kernel: ================================================================================
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.10
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: fabien 5742 F.... pulseaudio
/dev/snd/controlC1: fabien 5742 F.... pulseaudio
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
HibernationDevice: RESUME=UUID=70d9afbb-2d9a-4b6e-88f0-68d461d2b003
InstallationDate: Installed on 2015-07-13 (3721 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
Lsusb:
Bus 002 Device 002: ID 0bda:9210 Realtek Semiconductor Corp. RTL9210 M.2 NVME Adapter
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX303LNB
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-153-generic root=UUID=d0293d5f-398e-4356-b7fd-055cfc3abb3a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-153.163-generic 5.15.185
RelatedPackageVersions:
linux-restricted-modules-5.15.0-153-generic N/A
linux-backports-modules-5.15.0-153-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.39
Tags: jammy
Uname: Linux 5.15.0-153-generic x86_64
UpgradeStatus: Upgraded to jammy on 2025-06-07 (104 days ago)
UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/22/2015
dmi.bios.release: 5.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX303LNB.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX303LNB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LNB.206:bd01/22/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnUX303LNB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LNB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
dmi.product.family: UX
dmi.product.name: UX303LNB
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: fabien 2378 F.... wireplumber
/dev/snd/controlC0: fabien 2378 F.... wireplumber
/dev/snd/seq: fabien 2371 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 24.04
HibernationDevice: RESUME=UUID=70d9afbb-2d9a-4b6e-88f0-68d461d2b003
InstallationDate: Installed on 2015-07-13 (3722 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 0bda:9210 Realtek Semiconductor Corp. RTL9210 M.2 NVME Adapter
MachineType: ASUSTeK COMPUTER INC. UX303LNB
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
LANG=fr_FR.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-83-generic root=UUID=9737a659-57d0-4b16-857c-df68048312a7 ro quiet splash resume=UUID=70d9afbb-2d9a-4b6e-88f0-68d461d2b003 vt.handoff=7
ProcVersionSignature: Ubuntu 6.8.0-83.83-generic 6.8.12
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.8.0-83-generic N/A
linux-backports-modules-6.8.0-83-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.17
Tags: noble
Uname: Linux 6.8.0-83-generic x86_64
UpgradeStatus: Upgraded to noble on 2025-09-19 (1 days ago)
UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/22/2015
dmi.bios.release: 5.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX303LNB.206
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX303LNB
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX303LNB.206:bd01/22/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnUX303LNB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX303LNB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
dmi.product.family: UX
dmi.product.name: UX303LNB
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
In attachment you'll find first the ones for jammy (kernel 5.15), then the ones for noble (kernel 6.8) and finally the kernel log of the previous boot which has the error. The current boot showed the error only later. So there also an additional dmesg output.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2125250/+subscriptions
[Bug 2139667] Re: [NEEDS PACKAGING] [mlnx5 hardware not supported] NVIDIA doca-ofed-25.10-dkms DKMS suite
> as this is an extra package to be manually installed by a customer
This isn't an acceptable justification for waving away regression risk
when adding something to the Ubuntu main archive. Any user may install
packages we publish into the main archive whether they are customers or
not, and all users expect us not to regress them.
Please perform a regression analysis again, but this time consider all
users, not just customers.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2139667
Title:
[NEEDS PACKAGING] [mlnx5 hardware not supported] NVIDIA doca-
ofed-25.10-dkms DKMS suite
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Noble:
In Progress
Bug description:
Support for ConnectX hardware through doca-ofed-25.10 DKMS in Ubuntu
Noble
[ SRU Justification ]
This is an effort to repackage the DKMS portion of the doca-ofed upstream package distributed by NVIDIA through a public HTTP source (e.g. https://linux.mellanox.com/public/repo/doca/).
NVIDIA distributes this as a set of deb packages in a tarball at the following address: https://developer.nvidia.com/doca-downloads; this package is for the 3.2.1 version of the upstream NVIDIA package.
Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX/DGX
platform: this is needed as customers using NVIDIA hardware can take
advantage of custom, high performance drivers directly through
Canonical apt system, without the need of downloading an external
tarball to be manually installed on the target machines.
This helps as well any automated installation flow as, by just
specifying the need for this package as an apt dependency, avoids the
automation issue of finding the HTTP address of the latest version of
the doca-ofed package distributed by NVIDIA and the relative scripting
to manually install them.
This package adds a set of kernel modules related to the NVIDIA mlnx5
hardware family (e.g. IB-capable ConnectX devices).
This package is related to the https://launchpad.net/ubuntu/+source/mofed-modules-24.10/ package already accepted last year. This is the newer LTS version distributed by NVIDIA.
There are no modification in repackaging, apart from a more coherent name with NVIDIA naming scheme, has been applied to the repackaging.
Another difference from the 24.10 version, is a smaller list of .ko files that will be built on the target machine, following what invoking the doca-ofed target on the original package installs.
[ Current Test Plan ]
* Hardware tested on:
* Noble-nvidia-tegra noble-derivative kernel 6.8.0-1013.13 -> 6.8.0-1016.16
- Tested on IGX Developer tool - ARM64
* Noble GA kernel 6.8.0-101-generic
- Tested on DGX B200 (amd64) and IGX GH200 (arm64)
* Compile and module insertion test on:
* Noble GA 6.8.0-71-generic, -88-generic, -90-generic and -100-generic
* Noble HWE-6.14.0-37-generic
* Noble HWE-6.17.0-14-generic
* Questing 6.17.0-7-generic and 6.17.0-8-generic
* Before uploading to Ubuntu an update version of the repackaged
kernel modules, a local test to the affected kernels must be executed.
At the moment, the main target kernel is the noble:linux-nvidia-tegra
one, so the tests will be thoroughly executed on the specific hardware
running said kernel. If the modules load correctly, the package is
considered sane and can be uploaded to the wider public. The
compilation test is executed as well on the latest version of Noble GA
and HWE.
* Another test suite run on each new spin of the module, is a smoke test running on DGX B200 (amd64) and GH200 (arm64) machines; those machines contains the hardware this set of kernel modules target.
The suite is able to test for the produced modules to be able to run IB interactions, fully load all the built modules and interactions between kernel-space modules/user-space applications.
A full test run can be found on the ARGOS-1951 Jira ticket.
Test-plan can be found at https://github.com/canonical/mofed-userspace-integration/tree/main/testcases
Test machines are freely available in Testflinger.
* The produced modules has been tested by an Nvidia team that has
given us the green light for the release.
[ Where problems could occur ]
* No issues are expected, as this is an extra package to be manually
installed by a customer and, without the necessary hardware, no driver
is automatically loaded in memory.
[ Other Info ]
* The repackaging code is contained in the repository at the
following address:
https://kernel.ubuntu.com/forgejo/alessiofaina/nvidia-doca-ofed-dkms
* Examples of the repackaged DKMS can be found at the following
personal PPA:
https://launchpad.net/~alessiofaina/+archive/ubuntu/mofed-autoupload-
test/+packages
* All the modules as GPL-2 or Dual BSD/GPL licensed, no closed source
binaries are redistributed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2139667/+subscriptions
This isn't an acceptable justification for waving away regression risk
when adding something to the Ubuntu main archive. Any user may install
packages we publish into the main archive whether they are customers or
not, and all users expect us not to regress them.
Please perform a regression analysis again, but this time consider all
users, not just customers.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2139667
Title:
[NEEDS PACKAGING] [mlnx5 hardware not supported] NVIDIA doca-
ofed-25.10-dkms DKMS suite
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Noble:
In Progress
Bug description:
Support for ConnectX hardware through doca-ofed-25.10 DKMS in Ubuntu
Noble
[ SRU Justification ]
This is an effort to repackage the DKMS portion of the doca-ofed upstream package distributed by NVIDIA through a public HTTP source (e.g. https://linux.mellanox.com/public/repo/doca/).
NVIDIA distributes this as a set of deb packages in a tarball at the following address: https://developer.nvidia.com/doca-downloads; this package is for the 3.2.1 version of the upstream NVIDIA package.
Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX/DGX
platform: this is needed as customers using NVIDIA hardware can take
advantage of custom, high performance drivers directly through
Canonical apt system, without the need of downloading an external
tarball to be manually installed on the target machines.
This helps as well any automated installation flow as, by just
specifying the need for this package as an apt dependency, avoids the
automation issue of finding the HTTP address of the latest version of
the doca-ofed package distributed by NVIDIA and the relative scripting
to manually install them.
This package adds a set of kernel modules related to the NVIDIA mlnx5
hardware family (e.g. IB-capable ConnectX devices).
This package is related to the https://launchpad.net/ubuntu/+source/mofed-modules-24.10/ package already accepted last year. This is the newer LTS version distributed by NVIDIA.
There are no modification in repackaging, apart from a more coherent name with NVIDIA naming scheme, has been applied to the repackaging.
Another difference from the 24.10 version, is a smaller list of .ko files that will be built on the target machine, following what invoking the doca-ofed target on the original package installs.
[ Current Test Plan ]
* Hardware tested on:
* Noble-nvidia-tegra noble-derivative kernel 6.8.0-1013.13 -> 6.8.0-1016.16
- Tested on IGX Developer tool - ARM64
* Noble GA kernel 6.8.0-101-generic
- Tested on DGX B200 (amd64) and IGX GH200 (arm64)
* Compile and module insertion test on:
* Noble GA 6.8.0-71-generic, -88-generic, -90-generic and -100-generic
* Noble HWE-6.14.0-37-generic
* Noble HWE-6.17.0-14-generic
* Questing 6.17.0-7-generic and 6.17.0-8-generic
* Before uploading to Ubuntu an update version of the repackaged
kernel modules, a local test to the affected kernels must be executed.
At the moment, the main target kernel is the noble:linux-nvidia-tegra
one, so the tests will be thoroughly executed on the specific hardware
running said kernel. If the modules load correctly, the package is
considered sane and can be uploaded to the wider public. The
compilation test is executed as well on the latest version of Noble GA
and HWE.
* Another test suite run on each new spin of the module, is a smoke test running on DGX B200 (amd64) and GH200 (arm64) machines; those machines contains the hardware this set of kernel modules target.
The suite is able to test for the produced modules to be able to run IB interactions, fully load all the built modules and interactions between kernel-space modules/user-space applications.
A full test run can be found on the ARGOS-1951 Jira ticket.
Test-plan can be found at https://github.com/canonical/mofed-userspace-integration/tree/main/testcases
Test machines are freely available in Testflinger.
* The produced modules has been tested by an Nvidia team that has
given us the green light for the release.
[ Where problems could occur ]
* No issues are expected, as this is an extra package to be manually
installed by a customer and, without the necessary hardware, no driver
is automatically loaded in memory.
[ Other Info ]
* The repackaging code is contained in the repository at the
following address:
https://kernel.ubuntu.com/forgejo/alessiofaina/nvidia-doca-ofed-dkms
* Examples of the repackaged DKMS can be found at the following
personal PPA:
https://launchpad.net/~alessiofaina/+archive/ubuntu/mofed-autoupload-
test/+packages
* All the modules as GPL-2 or Dual BSD/GPL licensed, no closed source
binaries are redistributed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2139667/+subscriptions
[Bug 2142510] [NEW] Regression: ip route get intermittently returns broadcast … for public IPs on 6.8.0-100 (breaks outbound TCP/Docker pulls)
Public bug reported:
Summary / Regression
This is a regression between Ubuntu kernels on an Ubuntu VM (Proxmox/QEMU/KVM, bridged networking, DHCP reservation). With 6.8.0-100-generic, ip -details route get <public-ip> intermittently returns an invalid cached result marking public IPs as broadcast/local (cache <local,brd>). When it enters this state, outbound TCP fails with "Network is unreachable" and Docker/Portainer pulls fail. Booting 6.8.0-90-generic on the same VM fixes it (route lookups remain unicast).
Environment
Ubuntu VM on Proxmox VE (QEMU/KVM), bridge vmbr0, DHCP reservation.
Reproduced across configuration changes: virtio/e1000 NIC, cpu
host/kvm64, cloud-init disabled; persists specifically with 6.8.0-100
and disappears with 6.8.0-90.
Evidence (6.8.0-100-generic)
Running repeatedly:
ip -details route get 1.1.1.1
shows flapping between correct unicast and incorrect broadcast classification:
unicast 1.1.1.1 via 192.168.1.1 dev ens18 table main src 192.168.1.72
cache
broadcast 1.1.1.1 via 192.168.1.1 dev ens18 table main src 192.168.1.72
cache <local,brd>
broadcast 1.1.1.1 via 192.168.1.1 dev ens18 table main src 192.168.1.72
cache <local,brd>
When the broadcast … <local,brd> state appears, outbound TCP connections
to public IPs fail ("Network is unreachable"), and ubuntu-bug linux
upload also sometimes fails with urlopen error [Errno 101] Network is
unreachable.
Expected
Public IPs should never be classified as broadcast … <local,brd> in route lookup; outbound TCP should stay stable.
Workaround
Boot kernel 6.8.0-90-generic (issue disappears). Flushing caches (ip route flush cache and ip neigh flush dev ens18) temporarily restores correct behavior on 6.8.0-100.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-100-generic 6.8.0-100.100
ProcVersionSignature: Ubuntu 6.8.0-100.100-generic 6.8.12
Uname: Linux 6.8.0-100-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
Date: Mon Feb 23 19:39:48 2026
InstallationDate: Installed on 2025-03-13 (347 days ago)
InstallationMedia: Ubuntu-Server 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm
ProcFB: 0 bochs-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-100-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro usbcore.autosuspend=-1
RelatedPackageVersions:
linux-restricted-modules-6.8.0-100-generic N/A
linux-backports-modules-6.8.0-100-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.22
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-9.2
dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-9.2:cvnQEMU:ct1:cvrpc-i440fx-9.2:sku:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-9.2
dmi.sys.vendor: QEMU
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142510
Title:
Regression: ip route get intermittently returns broadcast …
<local,brd> for public IPs on 6.8.0-100 (breaks outbound TCP/Docker
pulls)
Status in linux package in Ubuntu:
New
Bug description:
Summary / Regression
This is a regression between Ubuntu kernels on an Ubuntu VM (Proxmox/QEMU/KVM, bridged networking, DHCP reservation). With 6.8.0-100-generic, ip -details route get <public-ip> intermittently returns an invalid cached result marking public IPs as broadcast/local (cache <local,brd>). When it enters this state, outbound TCP fails with "Network is unreachable" and Docker/Portainer pulls fail. Booting 6.8.0-90-generic on the same VM fixes it (route lookups remain unicast).
Environment
Ubuntu VM on Proxmox VE (QEMU/KVM), bridge vmbr0, DHCP reservation.
Reproduced across configuration changes: virtio/e1000 NIC, cpu
host/kvm64, cloud-init disabled; persists specifically with 6.8.0-100
and disappears with 6.8.0-90.
Evidence (6.8.0-100-generic)
Running repeatedly:
ip -details route get 1.1.1.1
shows flapping between correct unicast and incorrect broadcast classification:
unicast 1.1.1.1 via 192.168.1.1 dev ens18 table main src 192.168.1.72
cache
broadcast 1.1.1.1 via 192.168.1.1 dev ens18 table main src 192.168.1.72
cache <local,brd>
broadcast 1.1.1.1 via 192.168.1.1 dev ens18 table main src 192.168.1.72
cache <local,brd>
When the broadcast … <local,brd> state appears, outbound TCP
connections to public IPs fail ("Network is unreachable"), and ubuntu-
bug linux upload also sometimes fails with urlopen error [Errno 101]
Network is unreachable.
Expected
Public IPs should never be classified as broadcast … <local,brd> in route lookup; outbound TCP should stay stable.
Workaround
Boot kernel 6.8.0-90-generic (issue disappears). Flushing caches (ip route flush cache and ip neigh flush dev ens18) temporarily restores correct behavior on 6.8.0-100.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-100-generic 6.8.0-100.100
ProcVersionSignature: Ubuntu 6.8.0-100.100-generic 6.8.12
Uname: Linux 6.8.0-100-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
Date: Mon Feb 23 19:39:48 2026
InstallationDate: Installed on 2025-03-13 (347 days ago)
InstallationMedia: Ubuntu-Server 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm
ProcFB: 0 bochs-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-100-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro usbcore.autosuspend=-1
RelatedPackageVersions:
linux-restricted-modules-6.8.0-100-generic N/A
linux-backports-modules-6.8.0-100-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.22
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-9.2
dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-9.2:cvnQEMU:ct1:cvrpc-i440fx-9.2:sku:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-9.2
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142510/+subscriptions
Summary / Regression
This is a regression between Ubuntu kernels on an Ubuntu VM (Proxmox/QEMU/KVM, bridged networking, DHCP reservation). With 6.8.0-100-generic, ip -details route get <public-ip> intermittently returns an invalid cached result marking public IPs as broadcast/local (cache <local,brd>). When it enters this state, outbound TCP fails with "Network is unreachable" and Docker/Portainer pulls fail. Booting 6.8.0-90-generic on the same VM fixes it (route lookups remain unicast).
Environment
Ubuntu VM on Proxmox VE (QEMU/KVM), bridge vmbr0, DHCP reservation.
Reproduced across configuration changes: virtio/e1000 NIC, cpu
host/kvm64, cloud-init disabled; persists specifically with 6.8.0-100
and disappears with 6.8.0-90.
Evidence (6.8.0-100-generic)
Running repeatedly:
ip -details route get 1.1.1.1
shows flapping between correct unicast and incorrect broadcast classification:
unicast 1.1.1.1 via 192.168.1.1 dev ens18 table main src 192.168.1.72
cache
broadcast 1.1.1.1 via 192.168.1.1 dev ens18 table main src 192.168.1.72
cache <local,brd>
broadcast 1.1.1.1 via 192.168.1.1 dev ens18 table main src 192.168.1.72
cache <local,brd>
When the broadcast … <local,brd> state appears, outbound TCP connections
to public IPs fail ("Network is unreachable"), and ubuntu-bug linux
upload also sometimes fails with urlopen error [Errno 101] Network is
unreachable.
Expected
Public IPs should never be classified as broadcast … <local,brd> in route lookup; outbound TCP should stay stable.
Workaround
Boot kernel 6.8.0-90-generic (issue disappears). Flushing caches (ip route flush cache and ip neigh flush dev ens18) temporarily restores correct behavior on 6.8.0-100.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-100-generic 6.8.0-100.100
ProcVersionSignature: Ubuntu 6.8.0-100.100-generic 6.8.12
Uname: Linux 6.8.0-100-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
Date: Mon Feb 23 19:39:48 2026
InstallationDate: Installed on 2025-03-13 (347 days ago)
InstallationMedia: Ubuntu-Server 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm
ProcFB: 0 bochs-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-100-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro usbcore.autosuspend=-1
RelatedPackageVersions:
linux-restricted-modules-6.8.0-100-generic N/A
linux-backports-modules-6.8.0-100-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.22
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-9.2
dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-9.2:cvnQEMU:ct1:cvrpc-i440fx-9.2:sku:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-9.2
dmi.sys.vendor: QEMU
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug noble
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142510
Title:
Regression: ip route get intermittently returns broadcast …
<local,brd> for public IPs on 6.8.0-100 (breaks outbound TCP/Docker
pulls)
Status in linux package in Ubuntu:
New
Bug description:
Summary / Regression
This is a regression between Ubuntu kernels on an Ubuntu VM (Proxmox/QEMU/KVM, bridged networking, DHCP reservation). With 6.8.0-100-generic, ip -details route get <public-ip> intermittently returns an invalid cached result marking public IPs as broadcast/local (cache <local,brd>). When it enters this state, outbound TCP fails with "Network is unreachable" and Docker/Portainer pulls fail. Booting 6.8.0-90-generic on the same VM fixes it (route lookups remain unicast).
Environment
Ubuntu VM on Proxmox VE (QEMU/KVM), bridge vmbr0, DHCP reservation.
Reproduced across configuration changes: virtio/e1000 NIC, cpu
host/kvm64, cloud-init disabled; persists specifically with 6.8.0-100
and disappears with 6.8.0-90.
Evidence (6.8.0-100-generic)
Running repeatedly:
ip -details route get 1.1.1.1
shows flapping between correct unicast and incorrect broadcast classification:
unicast 1.1.1.1 via 192.168.1.1 dev ens18 table main src 192.168.1.72
cache
broadcast 1.1.1.1 via 192.168.1.1 dev ens18 table main src 192.168.1.72
cache <local,brd>
broadcast 1.1.1.1 via 192.168.1.1 dev ens18 table main src 192.168.1.72
cache <local,brd>
When the broadcast … <local,brd> state appears, outbound TCP
connections to public IPs fail ("Network is unreachable"), and ubuntu-
bug linux upload also sometimes fails with urlopen error [Errno 101]
Network is unreachable.
Expected
Public IPs should never be classified as broadcast … <local,brd> in route lookup; outbound TCP should stay stable.
Workaround
Boot kernel 6.8.0-90-generic (issue disappears). Flushing caches (ip route flush cache and ip neigh flush dev ens18) temporarily restores correct behavior on 6.8.0-100.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-100-generic 6.8.0-100.100
ProcVersionSignature: Ubuntu 6.8.0-100.100-generic 6.8.12
Uname: Linux 6.8.0-100-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
Date: Mon Feb 23 19:39:48 2026
InstallationDate: Installed on 2025-03-13 (347 days ago)
InstallationMedia: Ubuntu-Server 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm
ProcFB: 0 bochs-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-100-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro usbcore.autosuspend=-1
RelatedPackageVersions:
linux-restricted-modules-6.8.0-100-generic N/A
linux-backports-modules-6.8.0-100-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.22
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-9.2
dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-9.2:cvnQEMU:ct1:cvrpc-i440fx-9.2:sku:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-9.2
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142510/+subscriptions
[Bug 2132317] Re: [UBUNTU 24.04] KVM: s390: improve interrupt cpu for wakeup
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin2404
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2132317
Title:
[UBUNTU 24.04] KVM: s390: improve interrupt cpu for wakeup
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux source package in Plucky:
Won't Fix
Status in linux source package in Questing:
Fix Released
Status in linux source package in Resolute:
Fix Released
Bug description:
[ Impact ]
Commit 352ccf890a3e (KVM: s390: improve interrupt cpu for wakeup)
addresses a performance optimization in the KVM subsystem
for the s390 architecture, specifically concerning the selection
of target virtual CPUs (vCPUs) for floating interrupt delivery.
The modification changes the heuristic algorithm used to determine
which vCPU should be awakened when a floating interrupt arrives,
shifting from an idle-CPU-preference strategy to a
last-sleep-CPU-preference strategy.
This algorithmic change yields significant performance improvements
by reducing inter-processor interrupt overhead
and improving cache locality.
[ Fix ]
Backport 352ccf890a3e (KVM: s390: improve interrupt cpu for wakeup)
from mainline.
[ Test Plan ]
To test the patch it is possible to run I/O-intensive workloads
(fio, uperf) with varying vCPU configurations, on a s390x machine,
to ensure interrupt delivery remains correct without errors,
timeouts, or kernel warnings. Moreover, during I/O-intensive workloads
a performance improvement should be visible.
[ Regression Potential]
The patch modifies interrupt delivery heuristics within s390 KVM
but does not change core interrupt handling logic
or data structures significantly.
The primary risk is suboptimal vCPU selection in workload patterns
that differ from the tested scenarios (fio, uperf), potentially
causing performance regressions rather than functional failures.
---
352ccf890a3e91f58bc32503f9afdc161bc2c34a
-------------------------
KVM: s390: improve interrupt cpu for wakeup
Turns out that picking an idle CPU for floating interrupts has some
negative side effects. The guest will keep the IO workload on its CPU
and rather use an IPI from the interrupt CPU instead of moving workload.
For example a guest with 2 vCPUs and 1 fio process might run that fio on
vcpu1. If after diag500 both vCPUs are idle then vcpu0 is woken up. The
guest will then do an IPI from vcpu0 to vcpu1.
So lets change the heuristics and prefer the last CPU that went to
sleep. This one is likely still in halt polling and can be woken up
quickly.
This patch shows significant improvements in terms of bandwidth or
cpu consumption for fio and uperf workloads and seems to be a net
win.
Link: https://lore.kernel.org/linux-s390/20250904113927.119306-1-borntraeger@linux.ibm.com/
Reviewed-by: Christoph Schlameu? <schlameuss@de.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@linux.ibm.com>
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2132317/+subscriptions
** Tags added: targetmilestone-inin2404
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2132317
Title:
[UBUNTU 24.04] KVM: s390: improve interrupt cpu for wakeup
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux source package in Plucky:
Won't Fix
Status in linux source package in Questing:
Fix Released
Status in linux source package in Resolute:
Fix Released
Bug description:
[ Impact ]
Commit 352ccf890a3e (KVM: s390: improve interrupt cpu for wakeup)
addresses a performance optimization in the KVM subsystem
for the s390 architecture, specifically concerning the selection
of target virtual CPUs (vCPUs) for floating interrupt delivery.
The modification changes the heuristic algorithm used to determine
which vCPU should be awakened when a floating interrupt arrives,
shifting from an idle-CPU-preference strategy to a
last-sleep-CPU-preference strategy.
This algorithmic change yields significant performance improvements
by reducing inter-processor interrupt overhead
and improving cache locality.
[ Fix ]
Backport 352ccf890a3e (KVM: s390: improve interrupt cpu for wakeup)
from mainline.
[ Test Plan ]
To test the patch it is possible to run I/O-intensive workloads
(fio, uperf) with varying vCPU configurations, on a s390x machine,
to ensure interrupt delivery remains correct without errors,
timeouts, or kernel warnings. Moreover, during I/O-intensive workloads
a performance improvement should be visible.
[ Regression Potential]
The patch modifies interrupt delivery heuristics within s390 KVM
but does not change core interrupt handling logic
or data structures significantly.
The primary risk is suboptimal vCPU selection in workload patterns
that differ from the tested scenarios (fio, uperf), potentially
causing performance regressions rather than functional failures.
---
352ccf890a3e91f58bc32503f9afdc161bc2c34a
-------------------------
KVM: s390: improve interrupt cpu for wakeup
Turns out that picking an idle CPU for floating interrupts has some
negative side effects. The guest will keep the IO workload on its CPU
and rather use an IPI from the interrupt CPU instead of moving workload.
For example a guest with 2 vCPUs and 1 fio process might run that fio on
vcpu1. If after diag500 both vCPUs are idle then vcpu0 is woken up. The
guest will then do an IPI from vcpu0 to vcpu1.
So lets change the heuristics and prefer the last CPU that went to
sleep. This one is likely still in halt polling and can be woken up
quickly.
This patch shows significant improvements in terms of bandwidth or
cpu consumption for fio and uperf workloads and seems to be a net
win.
Link: https://lore.kernel.org/linux-s390/20250904113927.119306-1-borntraeger@linux.ibm.com/
Reviewed-by: Christoph Schlameu? <schlameuss@de.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@linux.ibm.com>
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2132317/+subscriptions
[Bug 2141715] Re: FAN bridges broken inside containers on Noble HWE kernels
It's interesting to note that the `IFLA_VXLAN_FAN_MAP` mismatch is also
the root cause for https://github.com/actions/runner-images/issues/13669
** Bug watch added: github.com/actions/runner-images/issues #13669
https://github.com/actions/runner-images/issues/13669
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141715
Title:
FAN bridges broken inside containers on Noble HWE kernels
Status in linux package in Ubuntu:
New
Bug description:
It seems the `sysctl` used when creating FAN bridges are not visible
inside containers. This bug might be related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141703.
In the 24.04 host:
```
# uname -a
Linux v4 6.14.0-1017-azure #17~24.04.1-Ubuntu SMP Mon Dec 1 20:10:50 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
# lxc network create lxdfan0 bridge.mode=fan
Network lxdfan0 created
# lxc network delete lxdfan0
Network lxdfan0 deleted
# sysctl net.fan.IFLA_VXLAN_FAN_MAP net.fan.vxlan
net.fan.IFLA_VXLAN_FAN_MAP = 34
net.fan.vxlan = 4
```
In a 24.04 container on that host:
```
# lxc exec m1 -- lxc network create lxdfan0 bridge.mode=fan
Error: Failed starting network: Failed adding link: Failed to run: ip link add name lxdfan0-fan type vxlan id 15728640 dev eth0 local 10.176.231.58 dstport 0 fan-map 240.0.0.0/8:10.176.231.0/24: exit status 2 (info: Using default fan map value (33)
Error: binary attribute size out of range.)
# lxc exec m1 -- sysctl net.fan.IFLA_VXLAN_FAN_MAP net.fan.vxlan
sysctl: cannot stat /proc/sys/net/fan/IFLA_VXLAN_FAN_MAP: No such file or directory
sysctl: cannot stat /proc/sys/net/fan/vxlan: No such file or directory
```
So IFLA_VXLAN_FAN_MAP seems to have the following values based on the
kernel version:
* 6.8: 33
* 6.11: 33
* 6.14: 34
* 6.17: 35
It looks as if when that sysctl key is not readable, `iproute2`
assumes the value of 33 causing this problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141715/+subscriptions
the root cause for https://github.com/actions/runner-images/issues/13669
** Bug watch added: github.com/actions/runner-images/issues #13669
https://github.com/actions/runner-images/issues/13669
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141715
Title:
FAN bridges broken inside containers on Noble HWE kernels
Status in linux package in Ubuntu:
New
Bug description:
It seems the `sysctl` used when creating FAN bridges are not visible
inside containers. This bug might be related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141703.
In the 24.04 host:
```
# uname -a
Linux v4 6.14.0-1017-azure #17~24.04.1-Ubuntu SMP Mon Dec 1 20:10:50 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux
# lxc network create lxdfan0 bridge.mode=fan
Network lxdfan0 created
# lxc network delete lxdfan0
Network lxdfan0 deleted
# sysctl net.fan.IFLA_VXLAN_FAN_MAP net.fan.vxlan
net.fan.IFLA_VXLAN_FAN_MAP = 34
net.fan.vxlan = 4
```
In a 24.04 container on that host:
```
# lxc exec m1 -- lxc network create lxdfan0 bridge.mode=fan
Error: Failed starting network: Failed adding link: Failed to run: ip link add name lxdfan0-fan type vxlan id 15728640 dev eth0 local 10.176.231.58 dstport 0 fan-map 240.0.0.0/8:10.176.231.0/24: exit status 2 (info: Using default fan map value (33)
Error: binary attribute size out of range.)
# lxc exec m1 -- sysctl net.fan.IFLA_VXLAN_FAN_MAP net.fan.vxlan
sysctl: cannot stat /proc/sys/net/fan/IFLA_VXLAN_FAN_MAP: No such file or directory
sysctl: cannot stat /proc/sys/net/fan/vxlan: No such file or directory
```
So IFLA_VXLAN_FAN_MAP seems to have the following values based on the
kernel version:
* 6.8: 33
* 6.11: 33
* 6.14: 34
* 6.17: 35
It looks as if when that sysctl key is not readable, `iproute2`
assumes the value of 33 causing this problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141715/+subscriptions
[Bug 2139667] Re: [NEEDS PACKAGING] [mlnx5 hardware not supported] NVIDIA doca-ofed-25.10-dkms DKMS suite
** Description changed:
- Support for doca-ofed-25.10 DKMS in Ubuntu Noble
+ Support for ConnectX hardware through doca-ofed-25.10 DKMS in Ubuntu
+ Noble
[ SRU Justification ]
This is an effort to repackage the DKMS portion of the doca-ofed upstream package distributed by NVIDIA through a public HTTP source (e.g. https://linux.mellanox.com/public/repo/doca/).
NVIDIA distributes this as a set of deb packages in a tarball at the following address: https://developer.nvidia.com/doca-downloads; this package is for the 3.2.1 version of the upstream NVIDIA package.
Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX
platform: this is needed as customers using NVIDIA hardware can take
advantage of custom, high performance drivers directly through Canonical
apt system, without the need of downloading an external tarball to be
manually installed on the target machines.
This helps as well any automated installation flow as, by just
specifying the need for this package as an apt dependency, avoids the
automation issue of finding the HTTP address of the latest version of
the doca-ofed package distributed by NVIDIA and the relative scripting
to manually install them.
This package adds a set of kernel modules related to the NVIDIA mlnx5
hardware family (e.g. IB-capable ConnectX devices).
This package is related to the https://launchpad.net/ubuntu/+source/mofed-modules-24.10/ package already accepted last year. This is the newer LTS version distributed by NVIDIA.
There are no modification in repackaging, apart from a more coherent name with NVIDIA naming scheme, has been applied to the repackaging.
Another difference from the 24.10 version, is a smaller list of .ko files that will be built on the target machine, following what invoking the doca-ofed target on the original package installs.
[ Current Test Plan ]
- * Tested on
- * Noble-nvidia-tegra derivative kernel 6.8.0-1013.13 / 6.8.0-1014.14
- * Noble 6.8.0-71-generic, 6.8.0-88-generic and 6.8.0-90-generic
+ * Hardware tested on:
+ * Noble-nvidia-tegra noble-derivative kernel 6.8.0-1013.13 -> 6.8.0-1016.16
+ - Tested on IGX Developer tool - ARM64
+ * Noble GA kernel 6.8.0-101-generic
+ - Tested on DGX B200 (amd64) and IGX GH200 (arm64)
+
+ * Compile and module insertion test on:
+ * Noble GA 6.8.0-71-generic, -88-generic, -90-generic and -100-generic
+ * Noble HWE-6.14.0-37-generic
+ * Noble HWE-6.17.0-14-generic
* Questing 6.17.0-7-generic and 6.17.0-8-generic
* Before uploading to Ubuntu an update version of the repackaged kernel
modules, a local test to the affected kernels must be executed. At the
moment, the main target kernel is the noble:linux-nvidia-tegra one, so
the tests will be thoroughly executed on the specific hardware running
said kernel. If the modules load correctly, the package is considered
sane and can be uploaded to the wider public.
- * Another test suite that is run on each new spin of the module, is a smoke test running on DGX B200 (amd64) and GH200 (arm64) machines; those machines contains the hardware this set of kernel modules targets.
- The suite is able to test for the produced modules to be able to run IB interactions, fully load all the built modules and interactions between kernel-space modules and user-space applications.
+ * Another test suite run on each new spin of the module, is a smoke test running on DGX B200 (amd64) and GH200 (arm64) machines; those machines contains the hardware this set of kernel modules target.
+ The suite is able to test for the produced modules to be able to run IB interactions, fully load all the built modules and interactions between kernel-space modules/user-space applications.
A full test run can be found on the ARGOS-1951 Jira ticket.
+ Test-plan can be found at https://github.com/canonical/mofed-userspace-integration/tree/main/testcases
* The produced modules has been tested by an Nvidia team that has given
us the green light for the release.
[ Where problems could occur ]
* No issues are expected, as this is an extra package to be manually
installed by a customer and, without the necessary hardware, no driver
is automatically loaded in memory.
[ Other Info ]
* The repackaging code is contained in the repository at the following
address: https://kernel.ubuntu.com/forgejo/alessiofaina/nvidia-doca-
ofed-dkms
* Examples of the repackaged DKMS can be found at the following
personal PPA: https://launchpad.net/~alessiofaina/+archive/ubuntu/mofed-
autoupload-test/+packages
* All the modules as GPL-2 or Dual BSD/GPL licensed, no closed source
binaries are redistributed.
** Description changed:
Support for ConnectX hardware through doca-ofed-25.10 DKMS in Ubuntu
Noble
[ SRU Justification ]
This is an effort to repackage the DKMS portion of the doca-ofed upstream package distributed by NVIDIA through a public HTTP source (e.g. https://linux.mellanox.com/public/repo/doca/).
NVIDIA distributes this as a set of deb packages in a tarball at the following address: https://developer.nvidia.com/doca-downloads; this package is for the 3.2.1 version of the upstream NVIDIA package.
- Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX
+ Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX/DGX
platform: this is needed as customers using NVIDIA hardware can take
advantage of custom, high performance drivers directly through Canonical
apt system, without the need of downloading an external tarball to be
manually installed on the target machines.
This helps as well any automated installation flow as, by just
specifying the need for this package as an apt dependency, avoids the
automation issue of finding the HTTP address of the latest version of
the doca-ofed package distributed by NVIDIA and the relative scripting
to manually install them.
This package adds a set of kernel modules related to the NVIDIA mlnx5
hardware family (e.g. IB-capable ConnectX devices).
This package is related to the https://launchpad.net/ubuntu/+source/mofed-modules-24.10/ package already accepted last year. This is the newer LTS version distributed by NVIDIA.
There are no modification in repackaging, apart from a more coherent name with NVIDIA naming scheme, has been applied to the repackaging.
Another difference from the 24.10 version, is a smaller list of .ko files that will be built on the target machine, following what invoking the doca-ofed target on the original package installs.
[ Current Test Plan ]
* Hardware tested on:
* Noble-nvidia-tegra noble-derivative kernel 6.8.0-1013.13 -> 6.8.0-1016.16
- - Tested on IGX Developer tool - ARM64
- * Noble GA kernel 6.8.0-101-generic
- - Tested on DGX B200 (amd64) and IGX GH200 (arm64)
+ - Tested on IGX Developer tool - ARM64
+ * Noble GA kernel 6.8.0-101-generic
+ - Tested on DGX B200 (amd64) and IGX GH200 (arm64)
- * Compile and module insertion test on:
+ * Compile and module insertion test on:
* Noble GA 6.8.0-71-generic, -88-generic, -90-generic and -100-generic
- * Noble HWE-6.14.0-37-generic
- * Noble HWE-6.17.0-14-generic
+ * Noble HWE-6.14.0-37-generic
+ * Noble HWE-6.17.0-14-generic
* Questing 6.17.0-7-generic and 6.17.0-8-generic
* Before uploading to Ubuntu an update version of the repackaged kernel
modules, a local test to the affected kernels must be executed. At the
moment, the main target kernel is the noble:linux-nvidia-tegra one, so
the tests will be thoroughly executed on the specific hardware running
said kernel. If the modules load correctly, the package is considered
sane and can be uploaded to the wider public.
* Another test suite run on each new spin of the module, is a smoke test running on DGX B200 (amd64) and GH200 (arm64) machines; those machines contains the hardware this set of kernel modules target.
The suite is able to test for the produced modules to be able to run IB interactions, fully load all the built modules and interactions between kernel-space modules/user-space applications.
A full test run can be found on the ARGOS-1951 Jira ticket.
Test-plan can be found at https://github.com/canonical/mofed-userspace-integration/tree/main/testcases
* The produced modules has been tested by an Nvidia team that has given
us the green light for the release.
[ Where problems could occur ]
* No issues are expected, as this is an extra package to be manually
installed by a customer and, without the necessary hardware, no driver
is automatically loaded in memory.
[ Other Info ]
* The repackaging code is contained in the repository at the following
address: https://kernel.ubuntu.com/forgejo/alessiofaina/nvidia-doca-
ofed-dkms
* Examples of the repackaged DKMS can be found at the following
personal PPA: https://launchpad.net/~alessiofaina/+archive/ubuntu/mofed-
autoupload-test/+packages
* All the modules as GPL-2 or Dual BSD/GPL licensed, no closed source
binaries are redistributed.
** Description changed:
Support for ConnectX hardware through doca-ofed-25.10 DKMS in Ubuntu
Noble
[ SRU Justification ]
This is an effort to repackage the DKMS portion of the doca-ofed upstream package distributed by NVIDIA through a public HTTP source (e.g. https://linux.mellanox.com/public/repo/doca/).
NVIDIA distributes this as a set of deb packages in a tarball at the following address: https://developer.nvidia.com/doca-downloads; this package is for the 3.2.1 version of the upstream NVIDIA package.
Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX/DGX
platform: this is needed as customers using NVIDIA hardware can take
advantage of custom, high performance drivers directly through Canonical
apt system, without the need of downloading an external tarball to be
manually installed on the target machines.
This helps as well any automated installation flow as, by just
specifying the need for this package as an apt dependency, avoids the
automation issue of finding the HTTP address of the latest version of
the doca-ofed package distributed by NVIDIA and the relative scripting
to manually install them.
This package adds a set of kernel modules related to the NVIDIA mlnx5
hardware family (e.g. IB-capable ConnectX devices).
This package is related to the https://launchpad.net/ubuntu/+source/mofed-modules-24.10/ package already accepted last year. This is the newer LTS version distributed by NVIDIA.
There are no modification in repackaging, apart from a more coherent name with NVIDIA naming scheme, has been applied to the repackaging.
Another difference from the 24.10 version, is a smaller list of .ko files that will be built on the target machine, following what invoking the doca-ofed target on the original package installs.
[ Current Test Plan ]
* Hardware tested on:
* Noble-nvidia-tegra noble-derivative kernel 6.8.0-1013.13 -> 6.8.0-1016.16
- Tested on IGX Developer tool - ARM64
* Noble GA kernel 6.8.0-101-generic
- Tested on DGX B200 (amd64) and IGX GH200 (arm64)
* Compile and module insertion test on:
* Noble GA 6.8.0-71-generic, -88-generic, -90-generic and -100-generic
* Noble HWE-6.14.0-37-generic
* Noble HWE-6.17.0-14-generic
* Questing 6.17.0-7-generic and 6.17.0-8-generic
* Before uploading to Ubuntu an update version of the repackaged kernel
modules, a local test to the affected kernels must be executed. At the
moment, the main target kernel is the noble:linux-nvidia-tegra one, so
the tests will be thoroughly executed on the specific hardware running
said kernel. If the modules load correctly, the package is considered
sane and can be uploaded to the wider public.
* Another test suite run on each new spin of the module, is a smoke test running on DGX B200 (amd64) and GH200 (arm64) machines; those machines contains the hardware this set of kernel modules target.
The suite is able to test for the produced modules to be able to run IB interactions, fully load all the built modules and interactions between kernel-space modules/user-space applications.
A full test run can be found on the ARGOS-1951 Jira ticket.
Test-plan can be found at https://github.com/canonical/mofed-userspace-integration/tree/main/testcases
+ Test machines are freely available in Testflinger.
* The produced modules has been tested by an Nvidia team that has given
us the green light for the release.
[ Where problems could occur ]
* No issues are expected, as this is an extra package to be manually
installed by a customer and, without the necessary hardware, no driver
is automatically loaded in memory.
[ Other Info ]
* The repackaging code is contained in the repository at the following
address: https://kernel.ubuntu.com/forgejo/alessiofaina/nvidia-doca-
ofed-dkms
* Examples of the repackaged DKMS can be found at the following
personal PPA: https://launchpad.net/~alessiofaina/+archive/ubuntu/mofed-
autoupload-test/+packages
* All the modules as GPL-2 or Dual BSD/GPL licensed, no closed source
binaries are redistributed.
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Noble)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
** Changed in: linux (Ubuntu Noble)
Assignee: (unassigned) => Alessio Faina (alessiofaina)
** Description changed:
Support for ConnectX hardware through doca-ofed-25.10 DKMS in Ubuntu
Noble
[ SRU Justification ]
This is an effort to repackage the DKMS portion of the doca-ofed upstream package distributed by NVIDIA through a public HTTP source (e.g. https://linux.mellanox.com/public/repo/doca/).
NVIDIA distributes this as a set of deb packages in a tarball at the following address: https://developer.nvidia.com/doca-downloads; this package is for the 3.2.1 version of the upstream NVIDIA package.
Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX/DGX
platform: this is needed as customers using NVIDIA hardware can take
advantage of custom, high performance drivers directly through Canonical
apt system, without the need of downloading an external tarball to be
manually installed on the target machines.
This helps as well any automated installation flow as, by just
specifying the need for this package as an apt dependency, avoids the
automation issue of finding the HTTP address of the latest version of
the doca-ofed package distributed by NVIDIA and the relative scripting
to manually install them.
This package adds a set of kernel modules related to the NVIDIA mlnx5
hardware family (e.g. IB-capable ConnectX devices).
This package is related to the https://launchpad.net/ubuntu/+source/mofed-modules-24.10/ package already accepted last year. This is the newer LTS version distributed by NVIDIA.
There are no modification in repackaging, apart from a more coherent name with NVIDIA naming scheme, has been applied to the repackaging.
Another difference from the 24.10 version, is a smaller list of .ko files that will be built on the target machine, following what invoking the doca-ofed target on the original package installs.
[ Current Test Plan ]
* Hardware tested on:
* Noble-nvidia-tegra noble-derivative kernel 6.8.0-1013.13 -> 6.8.0-1016.16
- Tested on IGX Developer tool - ARM64
* Noble GA kernel 6.8.0-101-generic
- Tested on DGX B200 (amd64) and IGX GH200 (arm64)
* Compile and module insertion test on:
* Noble GA 6.8.0-71-generic, -88-generic, -90-generic and -100-generic
* Noble HWE-6.14.0-37-generic
* Noble HWE-6.17.0-14-generic
* Questing 6.17.0-7-generic and 6.17.0-8-generic
* Before uploading to Ubuntu an update version of the repackaged kernel
modules, a local test to the affected kernels must be executed. At the
moment, the main target kernel is the noble:linux-nvidia-tegra one, so
the tests will be thoroughly executed on the specific hardware running
said kernel. If the modules load correctly, the package is considered
- sane and can be uploaded to the wider public.
+ sane and can be uploaded to the wider public. The compilation test is
+ executed as well on the latest version of Noble GA and HWE.
* Another test suite run on each new spin of the module, is a smoke test running on DGX B200 (amd64) and GH200 (arm64) machines; those machines contains the hardware this set of kernel modules target.
The suite is able to test for the produced modules to be able to run IB interactions, fully load all the built modules and interactions between kernel-space modules/user-space applications.
A full test run can be found on the ARGOS-1951 Jira ticket.
Test-plan can be found at https://github.com/canonical/mofed-userspace-integration/tree/main/testcases
Test machines are freely available in Testflinger.
* The produced modules has been tested by an Nvidia team that has given
us the green light for the release.
[ Where problems could occur ]
* No issues are expected, as this is an extra package to be manually
installed by a customer and, without the necessary hardware, no driver
is automatically loaded in memory.
[ Other Info ]
* The repackaging code is contained in the repository at the following
address: https://kernel.ubuntu.com/forgejo/alessiofaina/nvidia-doca-
ofed-dkms
* Examples of the repackaged DKMS can be found at the following
personal PPA: https://launchpad.net/~alessiofaina/+archive/ubuntu/mofed-
autoupload-test/+packages
* All the modules as GPL-2 or Dual BSD/GPL licensed, no closed source
binaries are redistributed.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2139667
Title:
[NEEDS PACKAGING] [mlnx5 hardware not supported] NVIDIA doca-
ofed-25.10-dkms DKMS suite
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Noble:
In Progress
Bug description:
Support for ConnectX hardware through doca-ofed-25.10 DKMS in Ubuntu
Noble
[ SRU Justification ]
This is an effort to repackage the DKMS portion of the doca-ofed upstream package distributed by NVIDIA through a public HTTP source (e.g. https://linux.mellanox.com/public/repo/doca/).
NVIDIA distributes this as a set of deb packages in a tarball at the following address: https://developer.nvidia.com/doca-downloads; this package is for the 3.2.1 version of the upstream NVIDIA package.
Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX/DGX
platform: this is needed as customers using NVIDIA hardware can take
advantage of custom, high performance drivers directly through
Canonical apt system, without the need of downloading an external
tarball to be manually installed on the target machines.
This helps as well any automated installation flow as, by just
specifying the need for this package as an apt dependency, avoids the
automation issue of finding the HTTP address of the latest version of
the doca-ofed package distributed by NVIDIA and the relative scripting
to manually install them.
This package adds a set of kernel modules related to the NVIDIA mlnx5
hardware family (e.g. IB-capable ConnectX devices).
This package is related to the https://launchpad.net/ubuntu/+source/mofed-modules-24.10/ package already accepted last year. This is the newer LTS version distributed by NVIDIA.
There are no modification in repackaging, apart from a more coherent name with NVIDIA naming scheme, has been applied to the repackaging.
Another difference from the 24.10 version, is a smaller list of .ko files that will be built on the target machine, following what invoking the doca-ofed target on the original package installs.
[ Current Test Plan ]
* Hardware tested on:
* Noble-nvidia-tegra noble-derivative kernel 6.8.0-1013.13 -> 6.8.0-1016.16
- Tested on IGX Developer tool - ARM64
* Noble GA kernel 6.8.0-101-generic
- Tested on DGX B200 (amd64) and IGX GH200 (arm64)
* Compile and module insertion test on:
* Noble GA 6.8.0-71-generic, -88-generic, -90-generic and -100-generic
* Noble HWE-6.14.0-37-generic
* Noble HWE-6.17.0-14-generic
* Questing 6.17.0-7-generic and 6.17.0-8-generic
* Before uploading to Ubuntu an update version of the repackaged
kernel modules, a local test to the affected kernels must be executed.
At the moment, the main target kernel is the noble:linux-nvidia-tegra
one, so the tests will be thoroughly executed on the specific hardware
running said kernel. If the modules load correctly, the package is
considered sane and can be uploaded to the wider public. The
compilation test is executed as well on the latest version of Noble GA
and HWE.
* Another test suite run on each new spin of the module, is a smoke test running on DGX B200 (amd64) and GH200 (arm64) machines; those machines contains the hardware this set of kernel modules target.
The suite is able to test for the produced modules to be able to run IB interactions, fully load all the built modules and interactions between kernel-space modules/user-space applications.
A full test run can be found on the ARGOS-1951 Jira ticket.
Test-plan can be found at https://github.com/canonical/mofed-userspace-integration/tree/main/testcases
Test machines are freely available in Testflinger.
* The produced modules has been tested by an Nvidia team that has
given us the green light for the release.
[ Where problems could occur ]
* No issues are expected, as this is an extra package to be manually
installed by a customer and, without the necessary hardware, no driver
is automatically loaded in memory.
[ Other Info ]
* The repackaging code is contained in the repository at the
following address:
https://kernel.ubuntu.com/forgejo/alessiofaina/nvidia-doca-ofed-dkms
* Examples of the repackaged DKMS can be found at the following
personal PPA:
https://launchpad.net/~alessiofaina/+archive/ubuntu/mofed-autoupload-
test/+packages
* All the modules as GPL-2 or Dual BSD/GPL licensed, no closed source
binaries are redistributed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2139667/+subscriptions
- Support for doca-ofed-25.10 DKMS in Ubuntu Noble
+ Support for ConnectX hardware through doca-ofed-25.10 DKMS in Ubuntu
+ Noble
[ SRU Justification ]
This is an effort to repackage the DKMS portion of the doca-ofed upstream package distributed by NVIDIA through a public HTTP source (e.g. https://linux.mellanox.com/public/repo/doca/).
NVIDIA distributes this as a set of deb packages in a tarball at the following address: https://developer.nvidia.com/doca-downloads; this package is for the 3.2.1 version of the upstream NVIDIA package.
Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX
platform: this is needed as customers using NVIDIA hardware can take
advantage of custom, high performance drivers directly through Canonical
apt system, without the need of downloading an external tarball to be
manually installed on the target machines.
This helps as well any automated installation flow as, by just
specifying the need for this package as an apt dependency, avoids the
automation issue of finding the HTTP address of the latest version of
the doca-ofed package distributed by NVIDIA and the relative scripting
to manually install them.
This package adds a set of kernel modules related to the NVIDIA mlnx5
hardware family (e.g. IB-capable ConnectX devices).
This package is related to the https://launchpad.net/ubuntu/+source/mofed-modules-24.10/ package already accepted last year. This is the newer LTS version distributed by NVIDIA.
There are no modification in repackaging, apart from a more coherent name with NVIDIA naming scheme, has been applied to the repackaging.
Another difference from the 24.10 version, is a smaller list of .ko files that will be built on the target machine, following what invoking the doca-ofed target on the original package installs.
[ Current Test Plan ]
- * Tested on
- * Noble-nvidia-tegra derivative kernel 6.8.0-1013.13 / 6.8.0-1014.14
- * Noble 6.8.0-71-generic, 6.8.0-88-generic and 6.8.0-90-generic
+ * Hardware tested on:
+ * Noble-nvidia-tegra noble-derivative kernel 6.8.0-1013.13 -> 6.8.0-1016.16
+ - Tested on IGX Developer tool - ARM64
+ * Noble GA kernel 6.8.0-101-generic
+ - Tested on DGX B200 (amd64) and IGX GH200 (arm64)
+
+ * Compile and module insertion test on:
+ * Noble GA 6.8.0-71-generic, -88-generic, -90-generic and -100-generic
+ * Noble HWE-6.14.0-37-generic
+ * Noble HWE-6.17.0-14-generic
* Questing 6.17.0-7-generic and 6.17.0-8-generic
* Before uploading to Ubuntu an update version of the repackaged kernel
modules, a local test to the affected kernels must be executed. At the
moment, the main target kernel is the noble:linux-nvidia-tegra one, so
the tests will be thoroughly executed on the specific hardware running
said kernel. If the modules load correctly, the package is considered
sane and can be uploaded to the wider public.
- * Another test suite that is run on each new spin of the module, is a smoke test running on DGX B200 (amd64) and GH200 (arm64) machines; those machines contains the hardware this set of kernel modules targets.
- The suite is able to test for the produced modules to be able to run IB interactions, fully load all the built modules and interactions between kernel-space modules and user-space applications.
+ * Another test suite run on each new spin of the module, is a smoke test running on DGX B200 (amd64) and GH200 (arm64) machines; those machines contains the hardware this set of kernel modules target.
+ The suite is able to test for the produced modules to be able to run IB interactions, fully load all the built modules and interactions between kernel-space modules/user-space applications.
A full test run can be found on the ARGOS-1951 Jira ticket.
+ Test-plan can be found at https://github.com/canonical/mofed-userspace-integration/tree/main/testcases
* The produced modules has been tested by an Nvidia team that has given
us the green light for the release.
[ Where problems could occur ]
* No issues are expected, as this is an extra package to be manually
installed by a customer and, without the necessary hardware, no driver
is automatically loaded in memory.
[ Other Info ]
* The repackaging code is contained in the repository at the following
address: https://kernel.ubuntu.com/forgejo/alessiofaina/nvidia-doca-
ofed-dkms
* Examples of the repackaged DKMS can be found at the following
personal PPA: https://launchpad.net/~alessiofaina/+archive/ubuntu/mofed-
autoupload-test/+packages
* All the modules as GPL-2 or Dual BSD/GPL licensed, no closed source
binaries are redistributed.
** Description changed:
Support for ConnectX hardware through doca-ofed-25.10 DKMS in Ubuntu
Noble
[ SRU Justification ]
This is an effort to repackage the DKMS portion of the doca-ofed upstream package distributed by NVIDIA through a public HTTP source (e.g. https://linux.mellanox.com/public/repo/doca/).
NVIDIA distributes this as a set of deb packages in a tarball at the following address: https://developer.nvidia.com/doca-downloads; this package is for the 3.2.1 version of the upstream NVIDIA package.
- Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX
+ Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX/DGX
platform: this is needed as customers using NVIDIA hardware can take
advantage of custom, high performance drivers directly through Canonical
apt system, without the need of downloading an external tarball to be
manually installed on the target machines.
This helps as well any automated installation flow as, by just
specifying the need for this package as an apt dependency, avoids the
automation issue of finding the HTTP address of the latest version of
the doca-ofed package distributed by NVIDIA and the relative scripting
to manually install them.
This package adds a set of kernel modules related to the NVIDIA mlnx5
hardware family (e.g. IB-capable ConnectX devices).
This package is related to the https://launchpad.net/ubuntu/+source/mofed-modules-24.10/ package already accepted last year. This is the newer LTS version distributed by NVIDIA.
There are no modification in repackaging, apart from a more coherent name with NVIDIA naming scheme, has been applied to the repackaging.
Another difference from the 24.10 version, is a smaller list of .ko files that will be built on the target machine, following what invoking the doca-ofed target on the original package installs.
[ Current Test Plan ]
* Hardware tested on:
* Noble-nvidia-tegra noble-derivative kernel 6.8.0-1013.13 -> 6.8.0-1016.16
- - Tested on IGX Developer tool - ARM64
- * Noble GA kernel 6.8.0-101-generic
- - Tested on DGX B200 (amd64) and IGX GH200 (arm64)
+ - Tested on IGX Developer tool - ARM64
+ * Noble GA kernel 6.8.0-101-generic
+ - Tested on DGX B200 (amd64) and IGX GH200 (arm64)
- * Compile and module insertion test on:
+ * Compile and module insertion test on:
* Noble GA 6.8.0-71-generic, -88-generic, -90-generic and -100-generic
- * Noble HWE-6.14.0-37-generic
- * Noble HWE-6.17.0-14-generic
+ * Noble HWE-6.14.0-37-generic
+ * Noble HWE-6.17.0-14-generic
* Questing 6.17.0-7-generic and 6.17.0-8-generic
* Before uploading to Ubuntu an update version of the repackaged kernel
modules, a local test to the affected kernels must be executed. At the
moment, the main target kernel is the noble:linux-nvidia-tegra one, so
the tests will be thoroughly executed on the specific hardware running
said kernel. If the modules load correctly, the package is considered
sane and can be uploaded to the wider public.
* Another test suite run on each new spin of the module, is a smoke test running on DGX B200 (amd64) and GH200 (arm64) machines; those machines contains the hardware this set of kernel modules target.
The suite is able to test for the produced modules to be able to run IB interactions, fully load all the built modules and interactions between kernel-space modules/user-space applications.
A full test run can be found on the ARGOS-1951 Jira ticket.
Test-plan can be found at https://github.com/canonical/mofed-userspace-integration/tree/main/testcases
* The produced modules has been tested by an Nvidia team that has given
us the green light for the release.
[ Where problems could occur ]
* No issues are expected, as this is an extra package to be manually
installed by a customer and, without the necessary hardware, no driver
is automatically loaded in memory.
[ Other Info ]
* The repackaging code is contained in the repository at the following
address: https://kernel.ubuntu.com/forgejo/alessiofaina/nvidia-doca-
ofed-dkms
* Examples of the repackaged DKMS can be found at the following
personal PPA: https://launchpad.net/~alessiofaina/+archive/ubuntu/mofed-
autoupload-test/+packages
* All the modules as GPL-2 or Dual BSD/GPL licensed, no closed source
binaries are redistributed.
** Description changed:
Support for ConnectX hardware through doca-ofed-25.10 DKMS in Ubuntu
Noble
[ SRU Justification ]
This is an effort to repackage the DKMS portion of the doca-ofed upstream package distributed by NVIDIA through a public HTTP source (e.g. https://linux.mellanox.com/public/repo/doca/).
NVIDIA distributes this as a set of deb packages in a tarball at the following address: https://developer.nvidia.com/doca-downloads; this package is for the 3.2.1 version of the upstream NVIDIA package.
Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX/DGX
platform: this is needed as customers using NVIDIA hardware can take
advantage of custom, high performance drivers directly through Canonical
apt system, without the need of downloading an external tarball to be
manually installed on the target machines.
This helps as well any automated installation flow as, by just
specifying the need for this package as an apt dependency, avoids the
automation issue of finding the HTTP address of the latest version of
the doca-ofed package distributed by NVIDIA and the relative scripting
to manually install them.
This package adds a set of kernel modules related to the NVIDIA mlnx5
hardware family (e.g. IB-capable ConnectX devices).
This package is related to the https://launchpad.net/ubuntu/+source/mofed-modules-24.10/ package already accepted last year. This is the newer LTS version distributed by NVIDIA.
There are no modification in repackaging, apart from a more coherent name with NVIDIA naming scheme, has been applied to the repackaging.
Another difference from the 24.10 version, is a smaller list of .ko files that will be built on the target machine, following what invoking the doca-ofed target on the original package installs.
[ Current Test Plan ]
* Hardware tested on:
* Noble-nvidia-tegra noble-derivative kernel 6.8.0-1013.13 -> 6.8.0-1016.16
- Tested on IGX Developer tool - ARM64
* Noble GA kernel 6.8.0-101-generic
- Tested on DGX B200 (amd64) and IGX GH200 (arm64)
* Compile and module insertion test on:
* Noble GA 6.8.0-71-generic, -88-generic, -90-generic and -100-generic
* Noble HWE-6.14.0-37-generic
* Noble HWE-6.17.0-14-generic
* Questing 6.17.0-7-generic and 6.17.0-8-generic
* Before uploading to Ubuntu an update version of the repackaged kernel
modules, a local test to the affected kernels must be executed. At the
moment, the main target kernel is the noble:linux-nvidia-tegra one, so
the tests will be thoroughly executed on the specific hardware running
said kernel. If the modules load correctly, the package is considered
sane and can be uploaded to the wider public.
* Another test suite run on each new spin of the module, is a smoke test running on DGX B200 (amd64) and GH200 (arm64) machines; those machines contains the hardware this set of kernel modules target.
The suite is able to test for the produced modules to be able to run IB interactions, fully load all the built modules and interactions between kernel-space modules/user-space applications.
A full test run can be found on the ARGOS-1951 Jira ticket.
Test-plan can be found at https://github.com/canonical/mofed-userspace-integration/tree/main/testcases
+ Test machines are freely available in Testflinger.
* The produced modules has been tested by an Nvidia team that has given
us the green light for the release.
[ Where problems could occur ]
* No issues are expected, as this is an extra package to be manually
installed by a customer and, without the necessary hardware, no driver
is automatically loaded in memory.
[ Other Info ]
* The repackaging code is contained in the repository at the following
address: https://kernel.ubuntu.com/forgejo/alessiofaina/nvidia-doca-
ofed-dkms
* Examples of the repackaged DKMS can be found at the following
personal PPA: https://launchpad.net/~alessiofaina/+archive/ubuntu/mofed-
autoupload-test/+packages
* All the modules as GPL-2 or Dual BSD/GPL licensed, no closed source
binaries are redistributed.
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Noble)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
** Changed in: linux (Ubuntu Noble)
Assignee: (unassigned) => Alessio Faina (alessiofaina)
** Description changed:
Support for ConnectX hardware through doca-ofed-25.10 DKMS in Ubuntu
Noble
[ SRU Justification ]
This is an effort to repackage the DKMS portion of the doca-ofed upstream package distributed by NVIDIA through a public HTTP source (e.g. https://linux.mellanox.com/public/repo/doca/).
NVIDIA distributes this as a set of deb packages in a tarball at the following address: https://developer.nvidia.com/doca-downloads; this package is for the 3.2.1 version of the upstream NVIDIA package.
Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX/DGX
platform: this is needed as customers using NVIDIA hardware can take
advantage of custom, high performance drivers directly through Canonical
apt system, without the need of downloading an external tarball to be
manually installed on the target machines.
This helps as well any automated installation flow as, by just
specifying the need for this package as an apt dependency, avoids the
automation issue of finding the HTTP address of the latest version of
the doca-ofed package distributed by NVIDIA and the relative scripting
to manually install them.
This package adds a set of kernel modules related to the NVIDIA mlnx5
hardware family (e.g. IB-capable ConnectX devices).
This package is related to the https://launchpad.net/ubuntu/+source/mofed-modules-24.10/ package already accepted last year. This is the newer LTS version distributed by NVIDIA.
There are no modification in repackaging, apart from a more coherent name with NVIDIA naming scheme, has been applied to the repackaging.
Another difference from the 24.10 version, is a smaller list of .ko files that will be built on the target machine, following what invoking the doca-ofed target on the original package installs.
[ Current Test Plan ]
* Hardware tested on:
* Noble-nvidia-tegra noble-derivative kernel 6.8.0-1013.13 -> 6.8.0-1016.16
- Tested on IGX Developer tool - ARM64
* Noble GA kernel 6.8.0-101-generic
- Tested on DGX B200 (amd64) and IGX GH200 (arm64)
* Compile and module insertion test on:
* Noble GA 6.8.0-71-generic, -88-generic, -90-generic and -100-generic
* Noble HWE-6.14.0-37-generic
* Noble HWE-6.17.0-14-generic
* Questing 6.17.0-7-generic and 6.17.0-8-generic
* Before uploading to Ubuntu an update version of the repackaged kernel
modules, a local test to the affected kernels must be executed. At the
moment, the main target kernel is the noble:linux-nvidia-tegra one, so
the tests will be thoroughly executed on the specific hardware running
said kernel. If the modules load correctly, the package is considered
- sane and can be uploaded to the wider public.
+ sane and can be uploaded to the wider public. The compilation test is
+ executed as well on the latest version of Noble GA and HWE.
* Another test suite run on each new spin of the module, is a smoke test running on DGX B200 (amd64) and GH200 (arm64) machines; those machines contains the hardware this set of kernel modules target.
The suite is able to test for the produced modules to be able to run IB interactions, fully load all the built modules and interactions between kernel-space modules/user-space applications.
A full test run can be found on the ARGOS-1951 Jira ticket.
Test-plan can be found at https://github.com/canonical/mofed-userspace-integration/tree/main/testcases
Test machines are freely available in Testflinger.
* The produced modules has been tested by an Nvidia team that has given
us the green light for the release.
[ Where problems could occur ]
* No issues are expected, as this is an extra package to be manually
installed by a customer and, without the necessary hardware, no driver
is automatically loaded in memory.
[ Other Info ]
* The repackaging code is contained in the repository at the following
address: https://kernel.ubuntu.com/forgejo/alessiofaina/nvidia-doca-
ofed-dkms
* Examples of the repackaged DKMS can be found at the following
personal PPA: https://launchpad.net/~alessiofaina/+archive/ubuntu/mofed-
autoupload-test/+packages
* All the modules as GPL-2 or Dual BSD/GPL licensed, no closed source
binaries are redistributed.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2139667
Title:
[NEEDS PACKAGING] [mlnx5 hardware not supported] NVIDIA doca-
ofed-25.10-dkms DKMS suite
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Noble:
In Progress
Bug description:
Support for ConnectX hardware through doca-ofed-25.10 DKMS in Ubuntu
Noble
[ SRU Justification ]
This is an effort to repackage the DKMS portion of the doca-ofed upstream package distributed by NVIDIA through a public HTTP source (e.g. https://linux.mellanox.com/public/repo/doca/).
NVIDIA distributes this as a set of deb packages in a tarball at the following address: https://developer.nvidia.com/doca-downloads; this package is for the 3.2.1 version of the upstream NVIDIA package.
Current Ubuntu packaging lacks support for NVIDIA Bluefield/IGX/DGX
platform: this is needed as customers using NVIDIA hardware can take
advantage of custom, high performance drivers directly through
Canonical apt system, without the need of downloading an external
tarball to be manually installed on the target machines.
This helps as well any automated installation flow as, by just
specifying the need for this package as an apt dependency, avoids the
automation issue of finding the HTTP address of the latest version of
the doca-ofed package distributed by NVIDIA and the relative scripting
to manually install them.
This package adds a set of kernel modules related to the NVIDIA mlnx5
hardware family (e.g. IB-capable ConnectX devices).
This package is related to the https://launchpad.net/ubuntu/+source/mofed-modules-24.10/ package already accepted last year. This is the newer LTS version distributed by NVIDIA.
There are no modification in repackaging, apart from a more coherent name with NVIDIA naming scheme, has been applied to the repackaging.
Another difference from the 24.10 version, is a smaller list of .ko files that will be built on the target machine, following what invoking the doca-ofed target on the original package installs.
[ Current Test Plan ]
* Hardware tested on:
* Noble-nvidia-tegra noble-derivative kernel 6.8.0-1013.13 -> 6.8.0-1016.16
- Tested on IGX Developer tool - ARM64
* Noble GA kernel 6.8.0-101-generic
- Tested on DGX B200 (amd64) and IGX GH200 (arm64)
* Compile and module insertion test on:
* Noble GA 6.8.0-71-generic, -88-generic, -90-generic and -100-generic
* Noble HWE-6.14.0-37-generic
* Noble HWE-6.17.0-14-generic
* Questing 6.17.0-7-generic and 6.17.0-8-generic
* Before uploading to Ubuntu an update version of the repackaged
kernel modules, a local test to the affected kernels must be executed.
At the moment, the main target kernel is the noble:linux-nvidia-tegra
one, so the tests will be thoroughly executed on the specific hardware
running said kernel. If the modules load correctly, the package is
considered sane and can be uploaded to the wider public. The
compilation test is executed as well on the latest version of Noble GA
and HWE.
* Another test suite run on each new spin of the module, is a smoke test running on DGX B200 (amd64) and GH200 (arm64) machines; those machines contains the hardware this set of kernel modules target.
The suite is able to test for the produced modules to be able to run IB interactions, fully load all the built modules and interactions between kernel-space modules/user-space applications.
A full test run can be found on the ARGOS-1951 Jira ticket.
Test-plan can be found at https://github.com/canonical/mofed-userspace-integration/tree/main/testcases
Test machines are freely available in Testflinger.
* The produced modules has been tested by an Nvidia team that has
given us the green light for the release.
[ Where problems could occur ]
* No issues are expected, as this is an extra package to be manually
installed by a customer and, without the necessary hardware, no driver
is automatically loaded in memory.
[ Other Info ]
* The repackaging code is contained in the repository at the
following address:
https://kernel.ubuntu.com/forgejo/alessiofaina/nvidia-doca-ofed-dkms
* Examples of the repackaged DKMS can be found at the following
personal PPA:
https://launchpad.net/~alessiofaina/+archive/ubuntu/mofed-autoupload-
test/+packages
* All the modules as GPL-2 or Dual BSD/GPL licensed, no closed source
binaries are redistributed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2139667/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-meta-lowlatency-hwe-6.8/6.8.0-104.104.1~22.04.1)
All autopkgtests for the newly accepted linux-meta-lowlatency-hwe-6.8 (6.8.0-104.104.1~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
glibc/unknown (amd64)
systemd/unknown (amd64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-lowlatency-hwe-6.8
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
The following regressions have been reported in tests triggered by the package:
glibc/unknown (amd64)
systemd/unknown (amd64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-lowlatency-hwe-6.8
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-meta-oracle/6.17.0-1008.8)
All autopkgtests for the newly accepted linux-meta-oracle (6.17.0-1008.8) for questing have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/257.9-0ubuntu2.1 (amd64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/questing/update_excuses.html#linux-meta-oracle
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
The following regressions have been reported in tests triggered by the package:
systemd/257.9-0ubuntu2.1 (amd64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/questing/update_excuses.html#linux-meta-oracle
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
[Bug 2142384] Re: ELAN2514:00 (04F3:4428) stylus report rate extremely low (~10–25 Hz) on Ubuntu 24.04 kernel 6.17
Agree with: "I wanna add that sometimes, touch stops working after using
the stylus."
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142384
Title:
ELAN2514:00 (04F3:4428) stylus report rate extremely low (~10–25 Hz)
on Ubuntu 24.04 kernel 6.17
Status in linux package in Ubuntu:
Confirmed
Bug description:
The active stylus on my HP OmniBook x Flip Ultra 14 reports at
extremely low frequency (~10–25 Hz) under Ubuntu 24.04.4 LTS with
kernel 6.17.0-14-generic. The pen input is choppy and unusable, while
touch input works normally.
The pen is a HP MPP tilt pen 2.0
Steps to Reproduce:
Boot Ubuntu 24.04.4 LTS on HP OmniBook x Flip Ultra 14.
Ensure kernel 6.17.0-14-generic is in use.
Run:
sudo libinput debug-events
And then i move the pen and compare the input events with touch on my
screen. The timestamps of the pen are 40-100 ms apart, which makes it
unusable.
I think this is the stylus in libinput:
Device: ELAN2514:00 04F3:4428 Stylus
Kernel: /dev/input/event7
Group: 5
Seat: seat0, default
Size: 300x188mm
Capabilities: tablet
Accel profiles: none
Other relevant info:
lsmod | grep hid
hid_sensor_prox 20480 0
hid_sensor_trigger 20480 3 hid_sensor_prox
hid_sensor_iio_common 24576 2 hid_sensor_trigger,hid_sensor_prox
industrialio 139264 4 industrialio_triggered_buffer,hid_sensor_trigger,hid_sensor_prox,kfifo_buf
intel_hid 32768 0
sparse_keymap 12288 2 hp_wmi,intel_hid
mac_hid 12288 0
hid_sensor_hub 28672 3 hid_sensor_trigger,hid_sensor_iio_common,hid_sensor_prox
usbhid 77824 0
hid_multitouch 36864 0
hid_generic 12288 0
i2c_hid_acpi 12288 0
i2c_hid 40960 1 i2c_hid_acpi
hid 262144 6 i2c_hid,usbhid,hid_multitouch,hid_sensor_hub,snd_soc_sdca,hid_generic
cat /sys/bus/i2c/devices/i2c-ELAN2514:00/power/control
on
Ubuntu 24.04.4 LTS
Kernel: 6.17.0-14-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142384/+subscriptions
the stylus."
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142384
Title:
ELAN2514:00 (04F3:4428) stylus report rate extremely low (~10–25 Hz)
on Ubuntu 24.04 kernel 6.17
Status in linux package in Ubuntu:
Confirmed
Bug description:
The active stylus on my HP OmniBook x Flip Ultra 14 reports at
extremely low frequency (~10–25 Hz) under Ubuntu 24.04.4 LTS with
kernel 6.17.0-14-generic. The pen input is choppy and unusable, while
touch input works normally.
The pen is a HP MPP tilt pen 2.0
Steps to Reproduce:
Boot Ubuntu 24.04.4 LTS on HP OmniBook x Flip Ultra 14.
Ensure kernel 6.17.0-14-generic is in use.
Run:
sudo libinput debug-events
And then i move the pen and compare the input events with touch on my
screen. The timestamps of the pen are 40-100 ms apart, which makes it
unusable.
I think this is the stylus in libinput:
Device: ELAN2514:00 04F3:4428 Stylus
Kernel: /dev/input/event7
Group: 5
Seat: seat0, default
Size: 300x188mm
Capabilities: tablet
Accel profiles: none
Other relevant info:
lsmod | grep hid
hid_sensor_prox 20480 0
hid_sensor_trigger 20480 3 hid_sensor_prox
hid_sensor_iio_common 24576 2 hid_sensor_trigger,hid_sensor_prox
industrialio 139264 4 industrialio_triggered_buffer,hid_sensor_trigger,hid_sensor_prox,kfifo_buf
intel_hid 32768 0
sparse_keymap 12288 2 hp_wmi,intel_hid
mac_hid 12288 0
hid_sensor_hub 28672 3 hid_sensor_trigger,hid_sensor_iio_common,hid_sensor_prox
usbhid 77824 0
hid_multitouch 36864 0
hid_generic 12288 0
i2c_hid_acpi 12288 0
i2c_hid 40960 1 i2c_hid_acpi
hid 262144 6 i2c_hid,usbhid,hid_multitouch,hid_sensor_hub,snd_soc_sdca,hid_generic
cat /sys/bus/i2c/devices/i2c-ELAN2514:00/power/control
on
Ubuntu 24.04.4 LTS
Kernel: 6.17.0-14-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142384/+subscriptions
[Bug 2142464] Re: Ubuntu 22.04 jammy Machine: Kernel update USB stick dead
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Please execute the following command only once, as it will automatically
gather debugging information, in a terminal:
apport-collect 2142464
When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.
Please note: `ubuntu-bug`, `apport` & bug reporting tools are provided
with Ubuntu by default, many require manual addition for some releases
of downstream OSes based on Ubuntu (eg. Linux Mint). You should check
with your distribution first.
Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://discourse.ubuntu.com/t/welcome-to-support-and-help/49951, or for
more support options please look at
https://discourse.ubuntu.com/t/community-support/709
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142464
Title:
Ubuntu 22.04 jammy Machine: Kernel update USB stick dead
Status in linux package in Ubuntu:
Incomplete
Bug description:
`Recent Kernel auto updated on 10 motherboards all fail to mount several past working Kingston USB sticks
formated W95 bootable and some USB sticks start cycling and re copy USB stick header and some USB sticks displat no header not visible in Disks... Start up with a USB stick installeed corrupts the mother board BIOS display smearing the video.. start up with no USB inserted is working inserting USB stick after startup either no USB found in terminal or OS Disk menu and Bluetooth mouse freeze and or USB stick starts reload mount cycling...
The kernel update to Ubuntu 21 to 22 has corrupted dedicated memory
locations on ten stand alone not shared on a network isolated
motherboards that was USB stick maintained serviced now destroyed
Ubuntu 22.04 jammy
Machine:System:
Kernel: 5.15.0-170-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 6.0.4
tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy
Machine:
Type: Desktop Mobo: ASRock model: FM2A58M-HD+ serial: <superuser required>
UEFI: American Megatrends v: P1.60 date: 08/01/2014
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: <filter>
charge: 55% (should be ignored) status: Discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard serial: <filter>
charge: 50% (should be ignored) status: N/A
CPU:
Info: quad core model: AMD A8-6600K APU with Radeon HD Graphics bits: 64 type: MT MCP
arch: Piledriver rev: 1 cache: L1: 192 KiB L2: 4 MiB
Speed (MHz): avg: 1896 min/max: 1900/3900 boost: enabled cores: 1: 1896 2: 1896 3: 1896
4: 1896 bogomips: 31141
Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: AMD Richland [Radeon HD 8570D] vendor: ASRock driver: radeon v: kernel ports:
active: HDMI-A-1 empty: HDMI-A-2,VGA-1 bus-ID: 00:01.0 chip-ID: 1002:990e
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: ati,radeon
unloaded: fbdev,modesetting,vesa gpu: radeon display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96
Monitor-1: HDMI-0 mapped: HDMI-A-1 model: Beyond TV res: 1920x1080 dpi: 82
diag: 1387mm (54.6")
OpenGL: renderer: AMD ARUBA (DRM 2.50.0 / 5.15.0-170-generic LLVM 15.0.7)
v: 4.5 Mesa 23.2.1-1ubuntu3.1~22.04.3 direct render: Yes
Audio:
Device-1: AMD Trinity HDMI Audio vendor: ASRock driver: snd_hda_intel v: kernel bus-ID: 00:01.1
chip-ID: 1002:9902
Device-2: AMD FCH Azalia vendor: ASRock driver: snd_hda_intel v: kernel bus-ID: 00:14.2
chip-ID: 1022:780d
Sound Server-1: ALSA v: k5.15.0-170-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock driver: r8169
v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 01:00.0 chip-ID: 10ec:8168
IF: enp1s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: lxcbr0 state: down mac: <filter>
Drives:
Local Storage: total: 670.71 GiB used: 568.67 GiB (84.8%)
ID-1: /dev/sda vendor: Kingston model: SA400S37480G size: 447.13 GiB speed: 3.0 Gb/s
serial: <filter>
ID-2: /dev/sdb vendor: Western Digital model: WDS240G2G0A-00JH30 size: 223.58 GiB
speed: 3.0 Gb/s serial: <filter>
Partition:
ID-1: / size: 116.28 GiB used: 107.35 GiB (92.3%) fs: ext4 dev: /dev/sda2
ID-2: /boot/efi size: 511 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/sda1
Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
System Temperatures: cpu: 4.2 C mobo: N/A gpu: radeon temp: 4.0 C
Fan Speeds (RPM): N/A
Repos:
Packages: 2786 note: see --pkg apt: 2756 flatpak: 30
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/caprine.list
1: deb [trusted=yes] https: //apt.fury.io/lefterisgar/ * *
Active apt repos in: /etc/apt/sources.list.d/obsproject-obs-studio-jammy.list
1: deb [signed-by=/etc/apt/keyrings/obsproject-obs-studio-jammy.gpg] https: //ppa.launchpadcontent.net/obsproject/obs-studio/ubuntu jammy main
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http: //packages.linuxmint.com virginia main upstream import backport
2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Active apt repos in: /etc/apt/sources.list.d/waydroid.list
1: deb [signed-by=/usr/share/keyrings/waydroid.gpg] https: //repo.waydro.id/ jammy main
Active zypp repos in: /etc/zypp/repos.d/packman.repo
1: packman ~ http: //packman.inode.at/suse/openSUSE_12.1
Info:
Processes: 241 Uptime: 31m Memory: 13.57 GiB used: 2.17 GiB (16.0%) Init: systemd v: 249
runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Unknown python3.10 client inxi: 3.3.13
Stuck with USB stick backup s no longer available... Tried USB sticks
on a Windows 10 system all files are visible no problems mounting USB
stick on Windows...
Please advise solutions to reset kernels back to a working USB
system... Tried USB camera is working only USB sticks that are good in
a Windows system are corrupted in 10 Ubuntu systems
Please advise solutions
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142464/+subscriptions
Ubuntu better.
Please execute the following command only once, as it will automatically
gather debugging information, in a terminal:
apport-collect 2142464
When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.
Please note: `ubuntu-bug`, `apport` & bug reporting tools are provided
with Ubuntu by default, many require manual addition for some releases
of downstream OSes based on Ubuntu (eg. Linux Mint). You should check
with your distribution first.
Bug reporting is about finding & fixing problems thus preventing future
users from hitting the same bug.
I suspect a Support site would be more appropriate, eg.
https://answers.launchpad.net/ubuntu. You can also find help with your
problem in the support forum of your local Ubuntu community
http://loco.ubuntu.com/ or asking at https://askubuntu.com or
https://discourse.ubuntu.com/t/welcome-to-support-and-help/49951, or for
more support options please look at
https://discourse.ubuntu.com/t/community-support/709
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142464
Title:
Ubuntu 22.04 jammy Machine: Kernel update USB stick dead
Status in linux package in Ubuntu:
Incomplete
Bug description:
`Recent Kernel auto updated on 10 motherboards all fail to mount several past working Kingston USB sticks
formated W95 bootable and some USB sticks start cycling and re copy USB stick header and some USB sticks displat no header not visible in Disks... Start up with a USB stick installeed corrupts the mother board BIOS display smearing the video.. start up with no USB inserted is working inserting USB stick after startup either no USB found in terminal or OS Disk menu and Bluetooth mouse freeze and or USB stick starts reload mount cycling...
The kernel update to Ubuntu 21 to 22 has corrupted dedicated memory
locations on ten stand alone not shared on a network isolated
motherboards that was USB stick maintained serviced now destroyed
Ubuntu 22.04 jammy
Machine:System:
Kernel: 5.15.0-170-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 6.0.4
tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy
Machine:
Type: Desktop Mobo: ASRock model: FM2A58M-HD+ serial: <superuser required>
UEFI: American Megatrends v: P1.60 date: 08/01/2014
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: <filter>
charge: 55% (should be ignored) status: Discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard serial: <filter>
charge: 50% (should be ignored) status: N/A
CPU:
Info: quad core model: AMD A8-6600K APU with Radeon HD Graphics bits: 64 type: MT MCP
arch: Piledriver rev: 1 cache: L1: 192 KiB L2: 4 MiB
Speed (MHz): avg: 1896 min/max: 1900/3900 boost: enabled cores: 1: 1896 2: 1896 3: 1896
4: 1896 bogomips: 31141
Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: AMD Richland [Radeon HD 8570D] vendor: ASRock driver: radeon v: kernel ports:
active: HDMI-A-1 empty: HDMI-A-2,VGA-1 bus-ID: 00:01.0 chip-ID: 1002:990e
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: ati,radeon
unloaded: fbdev,modesetting,vesa gpu: radeon display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96
Monitor-1: HDMI-0 mapped: HDMI-A-1 model: Beyond TV res: 1920x1080 dpi: 82
diag: 1387mm (54.6")
OpenGL: renderer: AMD ARUBA (DRM 2.50.0 / 5.15.0-170-generic LLVM 15.0.7)
v: 4.5 Mesa 23.2.1-1ubuntu3.1~22.04.3 direct render: Yes
Audio:
Device-1: AMD Trinity HDMI Audio vendor: ASRock driver: snd_hda_intel v: kernel bus-ID: 00:01.1
chip-ID: 1002:9902
Device-2: AMD FCH Azalia vendor: ASRock driver: snd_hda_intel v: kernel bus-ID: 00:14.2
chip-ID: 1022:780d
Sound Server-1: ALSA v: k5.15.0-170-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock driver: r8169
v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 01:00.0 chip-ID: 10ec:8168
IF: enp1s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: lxcbr0 state: down mac: <filter>
Drives:
Local Storage: total: 670.71 GiB used: 568.67 GiB (84.8%)
ID-1: /dev/sda vendor: Kingston model: SA400S37480G size: 447.13 GiB speed: 3.0 Gb/s
serial: <filter>
ID-2: /dev/sdb vendor: Western Digital model: WDS240G2G0A-00JH30 size: 223.58 GiB
speed: 3.0 Gb/s serial: <filter>
Partition:
ID-1: / size: 116.28 GiB used: 107.35 GiB (92.3%) fs: ext4 dev: /dev/sda2
ID-2: /boot/efi size: 511 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/sda1
Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
System Temperatures: cpu: 4.2 C mobo: N/A gpu: radeon temp: 4.0 C
Fan Speeds (RPM): N/A
Repos:
Packages: 2786 note: see --pkg apt: 2756 flatpak: 30
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/caprine.list
1: deb [trusted=yes] https: //apt.fury.io/lefterisgar/ * *
Active apt repos in: /etc/apt/sources.list.d/obsproject-obs-studio-jammy.list
1: deb [signed-by=/etc/apt/keyrings/obsproject-obs-studio-jammy.gpg] https: //ppa.launchpadcontent.net/obsproject/obs-studio/ubuntu jammy main
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http: //packages.linuxmint.com virginia main upstream import backport
2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Active apt repos in: /etc/apt/sources.list.d/waydroid.list
1: deb [signed-by=/usr/share/keyrings/waydroid.gpg] https: //repo.waydro.id/ jammy main
Active zypp repos in: /etc/zypp/repos.d/packman.repo
1: packman ~ http: //packman.inode.at/suse/openSUSE_12.1
Info:
Processes: 241 Uptime: 31m Memory: 13.57 GiB used: 2.17 GiB (16.0%) Init: systemd v: 249
runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Unknown python3.10 client inxi: 3.3.13
Stuck with USB stick backup s no longer available... Tried USB sticks
on a Windows 10 system all files are visible no problems mounting USB
stick on Windows...
Please advise solutions to reset kernels back to a working USB
system... Tried USB camera is working only USB sticks that are good in
a Windows system are corrupted in 10 Ubuntu systems
Please advise solutions
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142464/+subscriptions
[Bug 2142464] [NEW] Ubuntu 22.04 jammy Machine: Kernel update USB stick dead
You have been subscribed to a public bug:
`Recent Kernel auto updated on 10 motherboards all fail to mount several past working Kingston USB sticks
formated W95 bootable and some USB sticks start cycling and re copy USB stick header and some USB sticks displat no header not visible in Disks... Start up with a USB stick installeed corrupts the mother board BIOS display smearing the video.. start up with no USB inserted is working inserting USB stick after startup either no USB found in terminal or OS Disk menu and Bluetooth mouse freeze and or USB stick starts reload mount cycling...
The kernel update to Ubuntu 21 to 22 has corrupted dedicated memory
locations on ten stand alone not shared on a network isolated
motherboards that was USB stick maintained serviced now destroyed
Ubuntu 22.04 jammy
Machine:System:
Kernel: 5.15.0-170-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 6.0.4
tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy
Machine:
Type: Desktop Mobo: ASRock model: FM2A58M-HD+ serial: <superuser required>
UEFI: American Megatrends v: P1.60 date: 08/01/2014
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: <filter>
charge: 55% (should be ignored) status: Discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard serial: <filter>
charge: 50% (should be ignored) status: N/A
CPU:
Info: quad core model: AMD A8-6600K APU with Radeon HD Graphics bits: 64 type: MT MCP
arch: Piledriver rev: 1 cache: L1: 192 KiB L2: 4 MiB
Speed (MHz): avg: 1896 min/max: 1900/3900 boost: enabled cores: 1: 1896 2: 1896 3: 1896
4: 1896 bogomips: 31141
Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: AMD Richland [Radeon HD 8570D] vendor: ASRock driver: radeon v: kernel ports:
active: HDMI-A-1 empty: HDMI-A-2,VGA-1 bus-ID: 00:01.0 chip-ID: 1002:990e
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: ati,radeon
unloaded: fbdev,modesetting,vesa gpu: radeon display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96
Monitor-1: HDMI-0 mapped: HDMI-A-1 model: Beyond TV res: 1920x1080 dpi: 82
diag: 1387mm (54.6")
OpenGL: renderer: AMD ARUBA (DRM 2.50.0 / 5.15.0-170-generic LLVM 15.0.7)
v: 4.5 Mesa 23.2.1-1ubuntu3.1~22.04.3 direct render: Yes
Audio:
Device-1: AMD Trinity HDMI Audio vendor: ASRock driver: snd_hda_intel v: kernel bus-ID: 00:01.1
chip-ID: 1002:9902
Device-2: AMD FCH Azalia vendor: ASRock driver: snd_hda_intel v: kernel bus-ID: 00:14.2
chip-ID: 1022:780d
Sound Server-1: ALSA v: k5.15.0-170-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock driver: r8169
v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 01:00.0 chip-ID: 10ec:8168
IF: enp1s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: lxcbr0 state: down mac: <filter>
Drives:
Local Storage: total: 670.71 GiB used: 568.67 GiB (84.8%)
ID-1: /dev/sda vendor: Kingston model: SA400S37480G size: 447.13 GiB speed: 3.0 Gb/s
serial: <filter>
ID-2: /dev/sdb vendor: Western Digital model: WDS240G2G0A-00JH30 size: 223.58 GiB
speed: 3.0 Gb/s serial: <filter>
Partition:
ID-1: / size: 116.28 GiB used: 107.35 GiB (92.3%) fs: ext4 dev: /dev/sda2
ID-2: /boot/efi size: 511 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/sda1
Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
System Temperatures: cpu: 4.2 C mobo: N/A gpu: radeon temp: 4.0 C
Fan Speeds (RPM): N/A
Repos:
Packages: 2786 note: see --pkg apt: 2756 flatpak: 30
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/caprine.list
1: deb [trusted=yes] https: //apt.fury.io/lefterisgar/ * *
Active apt repos in: /etc/apt/sources.list.d/obsproject-obs-studio-jammy.list
1: deb [signed-by=/etc/apt/keyrings/obsproject-obs-studio-jammy.gpg] https: //ppa.launchpadcontent.net/obsproject/obs-studio/ubuntu jammy main
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http: //packages.linuxmint.com virginia main upstream import backport
2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Active apt repos in: /etc/apt/sources.list.d/waydroid.list
1: deb [signed-by=/usr/share/keyrings/waydroid.gpg] https: //repo.waydro.id/ jammy main
Active zypp repos in: /etc/zypp/repos.d/packman.repo
1: packman ~ http: //packman.inode.at/suse/openSUSE_12.1
Info:
Processes: 241 Uptime: 31m Memory: 13.57 GiB used: 2.17 GiB (16.0%) Init: systemd v: 249
runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Unknown python3.10 client inxi: 3.3.13
Stuck with USB stick backup s no longer available... Tried USB sticks on
a Windows 10 system all files are visible no problems mounting USB
stick on Windows...
Please advise solutions to reset kernels back to a working USB
system... Tried USB camera is working only USB sticks that are good in a
Windows system are corrupted in 10 Ubuntu systems
Please advise solutions
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
Ubuntu 22.04 jammy Machine: Kernel update USB stick dead
https://bugs.launchpad.net/bugs/2142464
You received this bug notification because you are subscribed to linux in Ubuntu.
`Recent Kernel auto updated on 10 motherboards all fail to mount several past working Kingston USB sticks
formated W95 bootable and some USB sticks start cycling and re copy USB stick header and some USB sticks displat no header not visible in Disks... Start up with a USB stick installeed corrupts the mother board BIOS display smearing the video.. start up with no USB inserted is working inserting USB stick after startup either no USB found in terminal or OS Disk menu and Bluetooth mouse freeze and or USB stick starts reload mount cycling...
The kernel update to Ubuntu 21 to 22 has corrupted dedicated memory
locations on ten stand alone not shared on a network isolated
motherboards that was USB stick maintained serviced now destroyed
Ubuntu 22.04 jammy
Machine:System:
Kernel: 5.15.0-170-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 6.0.4
tk: GTK 3.24.33 wm: muffin dm: LightDM Distro: Linux Mint 21.3 Virginia base: Ubuntu 22.04 jammy
Machine:
Type: Desktop Mobo: ASRock model: FM2A58M-HD+ serial: <superuser required>
UEFI: American Megatrends v: P1.60 date: 08/01/2014
Battery:
Device-1: hidpp_battery_0 model: Logitech Wireless Mouse serial: <filter>
charge: 55% (should be ignored) status: Discharging
Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard serial: <filter>
charge: 50% (should be ignored) status: N/A
CPU:
Info: quad core model: AMD A8-6600K APU with Radeon HD Graphics bits: 64 type: MT MCP
arch: Piledriver rev: 1 cache: L1: 192 KiB L2: 4 MiB
Speed (MHz): avg: 1896 min/max: 1900/3900 boost: enabled cores: 1: 1896 2: 1896 3: 1896
4: 1896 bogomips: 31141
Flags: avx ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: AMD Richland [Radeon HD 8570D] vendor: ASRock driver: radeon v: kernel ports:
active: HDMI-A-1 empty: HDMI-A-2,VGA-1 bus-ID: 00:01.0 chip-ID: 1002:990e
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: ati,radeon
unloaded: fbdev,modesetting,vesa gpu: radeon display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96
Monitor-1: HDMI-0 mapped: HDMI-A-1 model: Beyond TV res: 1920x1080 dpi: 82
diag: 1387mm (54.6")
OpenGL: renderer: AMD ARUBA (DRM 2.50.0 / 5.15.0-170-generic LLVM 15.0.7)
v: 4.5 Mesa 23.2.1-1ubuntu3.1~22.04.3 direct render: Yes
Audio:
Device-1: AMD Trinity HDMI Audio vendor: ASRock driver: snd_hda_intel v: kernel bus-ID: 00:01.1
chip-ID: 1002:9902
Device-2: AMD FCH Azalia vendor: ASRock driver: snd_hda_intel v: kernel bus-ID: 00:14.2
chip-ID: 1022:780d
Sound Server-1: ALSA v: k5.15.0-170-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock driver: r8169
v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 01:00.0 chip-ID: 10ec:8168
IF: enp1s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IF-ID-1: lxcbr0 state: down mac: <filter>
Drives:
Local Storage: total: 670.71 GiB used: 568.67 GiB (84.8%)
ID-1: /dev/sda vendor: Kingston model: SA400S37480G size: 447.13 GiB speed: 3.0 Gb/s
serial: <filter>
ID-2: /dev/sdb vendor: Western Digital model: WDS240G2G0A-00JH30 size: 223.58 GiB
speed: 3.0 Gb/s serial: <filter>
Partition:
ID-1: / size: 116.28 GiB used: 107.35 GiB (92.3%) fs: ext4 dev: /dev/sda2
ID-2: /boot/efi size: 511 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/sda1
Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors:
System Temperatures: cpu: 4.2 C mobo: N/A gpu: radeon temp: 4.0 C
Fan Speeds (RPM): N/A
Repos:
Packages: 2786 note: see --pkg apt: 2756 flatpak: 30
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/caprine.list
1: deb [trusted=yes] https: //apt.fury.io/lefterisgar/ * *
Active apt repos in: /etc/apt/sources.list.d/obsproject-obs-studio-jammy.list
1: deb [signed-by=/etc/apt/keyrings/obsproject-obs-studio-jammy.gpg] https: //ppa.launchpadcontent.net/obsproject/obs-studio/ubuntu jammy main
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http: //packages.linuxmint.com virginia main upstream import backport
2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Active apt repos in: /etc/apt/sources.list.d/waydroid.list
1: deb [signed-by=/usr/share/keyrings/waydroid.gpg] https: //repo.waydro.id/ jammy main
Active zypp repos in: /etc/zypp/repos.d/packman.repo
1: packman ~ http: //packman.inode.at/suse/openSUSE_12.1
Info:
Processes: 241 Uptime: 31m Memory: 13.57 GiB used: 2.17 GiB (16.0%) Init: systemd v: 249
runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Unknown python3.10 client inxi: 3.3.13
Stuck with USB stick backup s no longer available... Tried USB sticks on
a Windows 10 system all files are visible no problems mounting USB
stick on Windows...
Please advise solutions to reset kernels back to a working USB
system... Tried USB camera is working only USB sticks that are good in a
Windows system are corrupted in 10 Ubuntu systems
Please advise solutions
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
Ubuntu 22.04 jammy Machine: Kernel update USB stick dead
https://bugs.launchpad.net/bugs/2142464
You received this bug notification because you are subscribed to linux in Ubuntu.
Подписаться на:
Комментарии (Atom)