Hello Marc, thanks for submitting a bug report. May I ask if this is a new regression? Did it work before, but start misbehaving after a kernel update? Has it ever worked? Thanks. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Benjamin Wheeler (benjaminwheeler) ** 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/2166226 Title: [amdgpu][Navi 23/RX 6600] system-wide stalls followed by SDMA1 reset hang in sdma_v5_2_stop_queue on 7.0.0-30 Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu: 26.04.1 LTS Kernel: 7.0.0-30-generic, package 7.0.0-30.30 GPU: AMD Navi 23 / RX 6600 [1002:73ff], subsystem [1849:5217] Mesa: 26.0.8-1ubuntu0.3 linux-firmware: 20260319.git217ca6e4.1ubuntu The desktop first began stuttering and later stopped responding. At 16:41:37, amdgpu began reporting "Fence fallback timer expired". SysRq/NMI stack dumps repeatedly caught CPU 7 in amdgpu_device_rreg() from the display/vblank IRQ handler, while other CPUs were waiting in smp_call_function_many_cond(). AMDGPU later reported: ring sdma1 timeout, signaled seq=72398, emitted seq=72398 Starting sdma1 ring reset The reset did not complete. Repeated stack dumps for over three minutes showed the amdgpu-reset-dev worker in: amdgpu_device_rreg sdma_v5_2_stop_queue amdgpu_sdma_reset_engine sdma_v5_2_reset_queue amdgpu_job_timedout drm_sched_job_timedout Four seconds before the first amdgpu warning, an ASMedia ASM4242 USB4 bridge at 17:00.0 reported that it could not transition from D3cold to D0. This is on a different PCIe root port, so its relationship is unknown. The kernel is tainted P/O because this is a ZFS-root system using the ZFS DKMS module. The amdgpu module itself is the stock Ubuntu kernel module. Frequency: Happens pretty reliably within 24 hours of boot Recovery required: Requires hard reset USB4 activity at the time: None ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-30-generic 7.0.0-30.30 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Sep 2 17:11:37 2026 IwDevWlp16s0Link: Not connected. MachineType: Micro-Star International Co., Ltd. MS-7E70 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_5ck8oa@/vmlinuz-7.0.0-30-generic root=ZFS=rpool/ROOT/ubuntu_5ck8oa ro init_on_alloc=0 nmi_watchdog=1 softlockup_panic=1 hardlockup_panic=1 crashkernel=1G crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-07-05 (59 days ago) dmi.bios.date: 09/24/2025 dmi.bios.release: 5.35 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.A31 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: PRO X870E-P WIFI (MS-7E70) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.A31:bd09/24/2025:br5.35:svnMicro-StarInternationalCo.,Ltd.:pnMS-7E70:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROX870E-PWIFI(MS-7E70):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuTobefilledbyO.E.M.:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7E70 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166226/+subscriptions
пятница
[Bug 2166167] Re: typec_ucsi: WARNING in typec_altmode_update_active after suspend/resume on Thinkpad AMD HawkPoint
Hello Gerard, thanks for submitting a bug report. May I ask if this is a new regression? Did the display work before, but started misbehaving after a kernel update? Has it ever worked? Additionally, there is a new kernel available. Could you try running updates to see if the issue persists? Thanks! ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Benjamin Wheeler (benjaminwheeler) ** 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/2166167 Title: typec_ucsi: WARNING in typec_altmode_update_active after suspend/resume on Thinkpad AMD HawkPoint Status in linux package in Ubuntu: Incomplete Bug description: After resuming from suspend, USB-C DisplayPort Alt Mode stops working. The external monitor briefly wakes up on cable plug/unplug but reports "no signal". All DP connectors show "disconnected" in /sys/class/drm/. The following warning repeats in dmesg on each cable plug: WARNING: drivers/usb/typec/class.c:311 typec_altmode_update_active+0x101/0x110 [typec] ucsi_altmode_update_active+0x116/0x1b0 [typec_ucsi] ucsi_check_altmodes+0x92/0xd0 [typec_ucsi] Hardware: Thinkpad with AMD HawkPoint (Ryzen AI / 8000 series) Kernel: 7.0.0-30-generic (Ubuntu 26.04) Connector: USB-C to DisplayPort cable Workaround: none found (module reload crashes the system) ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Wed Sep 2 11:39:23 2026 InstallationDate: Installed on 2025-07-01 (428 days ago) InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3) MachineType: LENOVO 21ME000RFR ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-06-09 (85 days ago) dmi.bios.date: 05/21/2026 dmi.bios.release: 1.22 dmi.bios.vendor: LENOVO dmi.bios.version: R2LET41W (1.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 21ME000RFR dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrR2LET41W(1.22):bd05/21/2026:br1.22:efr1.13:svnLENOVO:pn21ME000RFR:pvrThinkPadP14sGen5AMD:rvnLENOVO:rn21ME000RFR:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21ME_BU_Think_FM_ThinkPadP14sGen5AMD:pfaThinkPadP14sGen5AMD: dmi.product.family: ThinkPad P14s Gen 5 AMD dmi.product.name: 21ME000RFR dmi.product.sku: LENOVO_MT_21ME_BU_Think_FM_ThinkPad P14s Gen 5 AMD dmi.product.version: ThinkPad P14s Gen 5 AMD dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166167/+subscriptions
[Bug 2166520] Re: Dell XPS 13 9340: intel_backlight values change but Sharp C71M1 panel brightness does not
Probably a duplicate of bug 2161309 Please try kernel 7.0.0-31, which should be available on your repo mirror soon if it is not already. ** 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/2166520 Title: Dell XPS 13 9340: intel_backlight values change but Sharp C71M1 panel brightness does not Status in linux package in Ubuntu: Incomplete Bug description: Hardware: * Dell XPS 13 9340 * BIOS/firmware version: 1.24.0 * GPU: Intel Meteor Lake-P [Intel Arc Graphics], PCI ID 8086:7d55 * Kernel driver: i915 * Internal display: Sharp SHP 5519, Dell C71M1, 2560×1600 QHD+ LED-backlit LCD * 64 GiB RAM Software: * Ubuntu 26.04.1 LTS, 64-bit * GNOME 50 * Wayland * Kernel 7.0.0-30-generic Expected behaviour: Changing brightness with the keyboard brightness keys or GNOME brightness slider should change the physical brightness of the internal display. Actual behaviour: The brightness OSD appears and its slider changes, but the physical brightness of the display remains completely unchanged. Additional tests: 1. /sys/class/backlight/intel_backlight exists. 2. The interface reports max_brightness=1023 and type=raw. 3. Writing a value directly to /sys/class/backlight/intel_backlight/brightness changes both brightness and actual_brightness, but the physical display brightness remains unchanged. 4. For example, after writing 300, both brightness and actual_brightness reported 300, while the display remained visually identical. 5. Brightness adjustment works correctly inside the Dell BIOS, so the panel and backlight hardware are functional. 6. The issue also occurs with kernel 7.0.0-29-generic. 7. The following i915 DPCD backlight modes were tested without success: * i915.enable_dpcd_backlight=1 * i915.enable_dpcd_backlight=2 * i915.enable_dpcd_backlight=3 8. The original boot configuration has been restored to i915.enable_dpcd_backlight=1. The issue therefore appears to be in the i915 backlight control for this specific Sharp/Dell panel: the sysfs values change, but the corresponding hardware brightness command is not applied. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-30-generic 7.0.0-30.30 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: armando 6199 F.... pipewire armando 6209 F.... wireplumber /dev/snd/seq: armando 6199 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 4 18:43:49 2026 InstallationDate: Installed on 2026-06-05 (91 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: Dell Inc. XPS 13 9340 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-30-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash xe.force_probe=7d14 i915.force_probe=!7d14 xe.fastboot=1 i915.enable_dpcd_backlight=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/27/2026 dmi.bios.release: 1.24 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.24.0 dmi.board.name: 08214J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnDellInc.:bvr1.24.0:bd01/27/2026:br1.24:efr1.21:svnDellInc.:pnXPS139340:pvr:rvnDellInc.:rn08214J:rvrA00:cvnDellInc.:ct10:cvr:sku0C87:pfaXPS: dmi.product.family: XPS dmi.product.name: XPS 13 9340 dmi.product.sku: 0C87 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166520/+subscriptions
[Bug 2166119] Re: QCA9377 Bluetooth not detected on Ubuntu 26.04; USB enumeration fails with errors -110 and -71
Hey Leonardo, Thanks for submitting a bug report, and I'm glad to hear you were able to find a workaround. Has the USB bus been functioning normally since you did the Cold boot? For now I will mark this bug as Invalid, but if you find that the issue persists, please feel free to reopen it by setting the bug to "New" or "Confirmed". Thanks! ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Benjamin Wheeler (benjaminwheeler) ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166119 Title: QCA9377 Bluetooth not detected on Ubuntu 26.04; USB enumeration fails with errors -110 and -71 Status in linux package in Ubuntu: Invalid Bug description: Bluetooth worked normally on Ubuntu 24.04 LTS on this same laptop and hardware. After upgrading to Ubuntu 26.04 LTS, Bluetooth is no longer detected or available. Hardware: * ASUS VivoBook X512FB * Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter * PCI ID: 168c:0042 * Subsystem: Lite-On Communications Inc. 11ad:0836 * BIOS: X512FB.304 (08/26/2019) The Wi-Fi functionality of the QCA9377 continues to work normally. The Bluetooth controller is not detected: * `bluetoothctl list` returns no controller. * `lsusb` does not show a Bluetooth device. * No HCI device is present under `/sys/class/bluetooth`. * `rfkill` shows Bluetooth as unblocked. * `btusb` can be loaded successfully with `modprobe`, but no Bluetooth controller appears. The kernel log shows repeated USB enumeration failures on internal USB port 1-10: `usb 1-10: device descriptor read/64, error -110` followed by: `xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command` `usb 1-10: Device not responding to setup address.` `usb 1-10: device not accepting address 6, error -71` and finally: `usb usb1-port10: unable to enumerate USB device` The Bluetooth core and `btusb` driver are loaded, but no HCI controller is created because the underlying USB device fails to enumerate. The same laptop and QCA9377 hardware worked normally under Ubuntu 24.04 LTS. The Bluetooth problem appeared after upgrading to Ubuntu 26.04 LTS. This may be a kernel/USB/driver regression, as the same hardware worked normally on Ubuntu 24.04 LTS. However, I cannot confirm whether the issue is specifically a kernel regression yet. Expected behavior: The internal QCA9377 Bluetooth controller should be detected and available through `bluetoothctl`. Actual behavior: The Bluetooth controller fails USB enumeration with errors -110 and -71, no HCI controller is created, and Bluetooth is unavailable. Wi-Fi continues to work normally on the same QCA9377 adapter. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-30-generic 7.0.0-30.30 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: leonardo 3444 F.... wireplumber /dev/snd/seq: leonardo 3433 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 1 19:26:53 2026 InstallationDate: Installed on 2026-08-28 (4 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 13d3:56d3 IMC Networks USB2.0 HD UVC WebCam Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Lsusb-t: /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 006: Dev 003, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 006: Dev 003, If 1, Class=Video, Driver=uvcvideo, 480M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 10000M MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512FB_X512FB ProcEnviron: LANG=pt_BR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-30-generic root=UUID=810b2ac5-8f88-4cc7-9814-dc3780fab91a ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512FB.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512FB 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.:bvrX512FB.304:bd08/26/2019:br5.13:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512FB_X512FB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512FB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaVivoBook: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512FB_X512FB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166119/+subscriptions
[Bug 2165962] Re: Apple Trackpad not usable in Ubunty Desktop but works on laptop
Hey Salvador, thanks for submitting a bug report. Can you please verify the kernel version on your laptop? In a terminal window, type "uname -a" and paste the result. I am curious if the laptop (where the device works) is running a different version than the desktop. Also, did the trackpad work previously on the desktop? Or has it never worked? Thanks for your help. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Benjamin Wheeler (benjaminwheeler) ** 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/2165962 Title: Apple Trackpad not usable in Ubunty Desktop but works on laptop Status in linux package in Ubuntu: Incomplete Bug description: * Both Desktop and laptop have the same version of Ubuntu: 'Ubuntu 26.04.1 LTS' * Both show similar info when using lsusb: chava@desktop:~$ lsusb | grep -i apple Bus 005 Device 006: ID 05ac:0265 Apple, Inc. - When connecting to the desktop the USB trackpad does not work at all. - When connecting to the laptop the USB trackpad works like a charm. Multitouch, gestures, and all. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-30-generic 7.0.0-30.30 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Aug 31 21:39:58 2026 InstallationDate: Installed on 2026-09-01 (0 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO WIFI ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-30-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F30 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS PRO WIFI dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF30:bd09/15/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPROWIFI:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPROWIFI:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaX570MB: dmi.product.family: X570 MB dmi.product.name: X570 AORUS PRO WIFI dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2165962/+subscriptions
[Bug 2166071] Re: Regression in 6.8.0-138-generic: Docker embedded DNS 127.0.0.11 times out, works with 6.8.0-137-generic
Thanks for submitting the bug report, and I'm glad the kernel update seems to have restored behavior back too normal. For now we can leave the bug as Invalid, but if others encounter a similar issue in the future, they can reference this bug or perhaps open a new report. 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/2166071 Title: Regression in 6.8.0-138-generic: Docker embedded DNS 127.0.0.11 times out, works with 6.8.0-137-generic Status in linux package in Ubuntu: Invalid Bug description: Ubuntu 24.04.4 LTS There appears to be a kernel networking/DNS regression between 6.8.0-137-generic and 6.8.0-138-generic affecting Docker containers. After upgrading and booting kernel 6.8.0-138-generic, multiple unrelated Docker containers fail DNS resolution through Docker's embedded DNS resolver 127.0.0.11. Examples: CrowdSec: lookup version.crowdsec.net on 127.0.0.11:53: read udp ... ->127.0.0.11:53: i/o timeout NetBird: lookup pkgs.netbird.io on 127.0.0.11:53: read udp ... ->127.0.0.11:53: i/o timeout Watchtower: lookup index.docker.io on 127.0.0.11:53: read udp ... ->127.0.0.11:53: i/o timeout The problem appeared immediately after upgrading to and booting 6.8.0-138-generic. To verify the regression, I rebooted the same host using the previously installed kernel 6.8.0-137-generic. Without making any changes to Docker, the Docker networks, DNS configuration or the affected containers, DNS resolution immediately started working again. Affected kernel: 6.8.0-138-generic linux-image-6.8.0-138-generic 6.8.0-138.138 Working kernel: 6.8.0-137-generic linux-image-6.8.0-137-generic 6.8.0-137.137 Affected kernel uname: Linux dkr02 6.8.0-138-generic #138-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 31 22:41:49 UTC 2026 x86_64 GNU/Linux Steps to reproduce: 1. Boot the host with 6.8.0-138-generic. 2. Start the existing Docker containers. 3. DNS requests through Docker's embedded resolver 127.0.0.11 time out. 4. Reboot the identical host with 6.8.0-137-generic. 5. DNS resolution from the same Docker containers works again. Expected result: Docker container DNS resolution should continue to work after upgrading from kernel 6.8.0-137 to 6.8.0-138. Actual result: With 6.8.0-138, DNS requests from multiple Docker containers time out at Docker's 127.0.0.11 resolver. The issue is reproducible by changing only the booted kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166071/+subscriptions
четверг
Re: [Bug 2165927] Re: Hibernation resume fails with nv_pmops_freeze returns -5 on kernel 7.0.0-30-generic (regression from 7.0.0-28-generic)
Hello Benjamin, Thank you for your response and for taking the time to look into the report. I understand that, since the issue was reproduced on Linux Mint, it cannot be investigated further through the Ubuntu kernel bug tracker. I will report it to the Linux Mint team as suggested. For completeness, I also tested the newly released kernel 7.0.0-31-generic on the same machine, with the same NVIDIA 595.84 driver and the same configuration. The hibernation/resume problem is now completely fixed. My regression testing is therefore: - 7.0.0-28-generic: hibernation/resume works correctly - 7.0.0-30-generic: resume fails with nv_pmops_freeze [nvidia] returns -5 - 7.0.0-31-generic: hibernation/resume works correctly again, with the complete desktop session restored This strongly suggests that the regression introduced in 7.0.0-30 was fixed in 7.0.0-31. Thank you again for your assistance and for pointing me toward the appropriate channel for the Linux Mint-specific report. Best regards, Seghir On Thu, 3 Sept 2026 at 19:25, Benjamin Wheeler <2165927@bugs.launchpad.net> wrote: > Hello, thanks for the information. Unfortunately, since you are using > Linux Mint, you will need to open a bug report with the Linux Mint team, > or reproduce the issue on Ubuntu (https://ubuntu.com/download). I > believe you can start here > https://forums.linuxmint.com/viewforum.php?f=49 > > Thank you and good luck! > > ** Changed in: linux (Ubuntu) > Status: Confirmed => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2165927 > > Title: > Hibernation resume fails with nv_pmops_freeze returns -5 on kernel > 7.0.0-30-generic (regression from 7.0.0-28-generic) > > Status in linux package in Ubuntu: > Invalid > > Bug description: > Ubuntu 26.04 LTS (Resolute Raccoon), kernel 7.0.0-30-generic (Ubuntu > 7.0.0-30.30-generic / upstream 7.0.12) — running as Linux Mint 22.3. > > System information: > - Distro: Linux Mint 22.3, based on Ubuntu 24.04 LTS (Noble Numbat), > kernel 7.0.0-30-generic (Ubuntu 7.0.0-30.30~24.04.1-generic). > - Host: ASUS TUF Dash F15 FX517ZE (Optimus hybrid graphics) > - CPU: Intel 12th Gen i7-12650H > - GPU: NVIDIA GeForce RTX 3050 Ti Mobile + Intel Alder Lake-P UHD > Graphics > - NVIDIA driver: 595.84 (Open Kernel Module) > - PRIME mode: on-demand > - Affected kernel: 7.0.0-30-generic (working: 7.0.0-28-generic, same > driver) > > Description: > > Hibernation worked reliably until approximately three weeks ago. After > a kernel upgrade from 7.0.0-28-generic to 7.0.0-30-generic, > hibernation resume consistently fails. > > The hibernation image is written successfully. On the next boot, the > kernel correctly detects and loads the saved image (100% progress, > "Image successfully loaded"), but immediately afterward the NVIDIA > driver fails to freeze the PCI device during the atomic restore step: > > nvidia 0000:01:00.0: PM: pci_pm_freeze(): nv_pmops_freeze [nvidia] > returns -5 > nvidia 0000:01:00.0: PM: dpm_run_callback(): pci_pm_freeze returns -5 > nvidia 0000:01:00.0: PM: failed to quiesce async: error -5 > PM: hibernation: Failed to load image, recovering. > PM: hibernation: resume failed (-5) > > The kernel then aborts the restore and boots fresh, discarding the > saved session entirely (all open applications are lost). > > Steps to reproduce: > 1. Open several applications (tested with ParaView, browser, terminal) > 2. sudo systemctl hibernate > 3. Power the machine back on > 4. Observe: fresh boot instead of restored session; dmesg shows the > error above > > Regression testing performed: > - Kernel 7.0.0-28-generic + driver 595.84 -> hibernation/resume works > perfectly, all windows restored > - Kernel 7.0.0-30-generic + driver 595.84 -> fails every time with the > error above > > Additional tests performed (none resolved the issue on kernel 30): > - NVreg_PreserveVideoMemoryAllocations=1 already set by default (via > /lib/modprobe.d/nvidia-runtimepm.conf) -- no effect > - Disabling GPU firmware (NVreg_EnableGpuFirmware=0) -- no effect, > identical error > - nvidia-hibernate.service, nvidia-resume.service, > nvidia-suspend.service all confirmed enabled > > Related bug (different symptom, same kernel/driver pair): > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2164816 -- > describes a hibernation write/poweroff failure on the same kernel > 7.0.0-30-generic with a newer NVIDIA GPU (RTX 5060 Ti). My issue occurs > during resume/restore instead, which may indicate a broader PM regression > affecting the NVIDIA driver's PCI freeze/thaw callbacks introduced in this > kernel version. > > Full dmesg output attached showing the failure at the "nv_pmops_freeze" > line. > --- > ProblemType: Bug > ApportVersion: 2.28.3-0ubuntu0.1 > Architecture: amd64 > AudioDevicesInUse: > USER PID ACCESS COMMAND > /dev/snd/controlC2: seghir 1566 F.... wireplumber > /dev/snd/controlC0: seghir 1566 F.... wireplumber > /dev/snd/controlC1: seghir 1566 F.... wireplumber > /dev/snd/seq: seghir 1563 F.... pipewire > CRDA: N/A > CasperMD5CheckResult: unknown > CurrentDesktop: X-Cinnamon > DistroRelease: Linux Mint 22.3 > HibernationDevice: RESUME=UUID=3413547b-d881-4439-990b-994ec8807450 > MachineType: ASUSTeK COMPUTER INC. ASUS TUF Dash F15 FX517ZE_TUF517ZE > Package: linux (not installed) > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-30-generic > root=UUID=4b23724b-e789-4437-9b4e-ba97027762d7 ro quiet splash > resume=UUID=3413547b-d881-4439-990b-994ec8807450 > ProcVersionSignature: Ubuntu 7.0.0-30.30~24.04.1-generic 7.0.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-7.0.0-30-generic N/A > linux-backports-modules-7.0.0-30-generic N/A > linux-firmware > 20240318.git3b128b60-0ubuntu2.29 > Tags: zena > Uname: Linux 7.0.0-30-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users > _MarkForUpload: True > dmi.bios.date: 12/15/2023 > dmi.bios.release: 5.26 > dmi.bios.vendor: American Megatrends International, LLC. > dmi.bios.version: FX517ZE.319 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: FX517ZE > 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.ec.firmware.release: 3.10 > dmi.modalias: > dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFX517ZE.319:bd12/15/2023:br5.26:efr3.10:svnASUSTeKCOMPUTERINC.:pnASUSTUFDashF15FX517ZE_TUF517ZE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX517ZE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSTUFDashF15: > dmi.product.family: ASUS TUF Dash F15 > dmi.product.name: ASUS TUF Dash F15 FX517ZE_TUF517ZE > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2165927/+subscriptions > > -- Abdelghani SEGHIR *Research Laboratory of Applied Hydraulics and Environment (LRHAE), * *University of Bejaia, Algeria * blogue : a-seghir.blogspot.com/ tel : +213 667 98 47 08 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2165927 Title: Hibernation resume fails with nv_pmops_freeze returns -5 on kernel 7.0.0-30-generic (regression from 7.0.0-28-generic) Status in linux package in Ubuntu: Invalid Bug description: Ubuntu 26.04 LTS (Resolute Raccoon), kernel 7.0.0-30-generic (Ubuntu 7.0.0-30.30-generic / upstream 7.0.12) — running as Linux Mint 22.3. System information: - Distro: Linux Mint 22.3, based on Ubuntu 24.04 LTS (Noble Numbat), kernel 7.0.0-30-generic (Ubuntu 7.0.0-30.30~24.04.1-generic). - Host: ASUS TUF Dash F15 FX517ZE (Optimus hybrid graphics) - CPU: Intel 12th Gen i7-12650H - GPU: NVIDIA GeForce RTX 3050 Ti Mobile + Intel Alder Lake-P UHD Graphics - NVIDIA driver: 595.84 (Open Kernel Module) - PRIME mode: on-demand - Affected kernel: 7.0.0-30-generic (working: 7.0.0-28-generic, same driver) Description: Hibernation worked reliably until approximately three weeks ago. After a kernel upgrade from 7.0.0-28-generic to 7.0.0-30-generic, hibernation resume consistently fails. The hibernation image is written successfully. On the next boot, the kernel correctly detects and loads the saved image (100% progress, "Image successfully loaded"), but immediately afterward the NVIDIA driver fails to freeze the PCI device during the atomic restore step: nvidia 0000:01:00.0: PM: pci_pm_freeze(): nv_pmops_freeze [nvidia] returns -5 nvidia 0000:01:00.0: PM: dpm_run_callback(): pci_pm_freeze returns -5 nvidia 0000:01:00.0: PM: failed to quiesce async: error -5 PM: hibernation: Failed to load image, recovering. PM: hibernation: resume failed (-5) The kernel then aborts the restore and boots fresh, discarding the saved session entirely (all open applications are lost). Steps to reproduce: 1. Open several applications (tested with ParaView, browser, terminal) 2. sudo systemctl hibernate 3. Power the machine back on 4. Observe: fresh boot instead of restored session; dmesg shows the error above Regression testing performed: - Kernel 7.0.0-28-generic + driver 595.84 -> hibernation/resume works perfectly, all windows restored - Kernel 7.0.0-30-generic + driver 595.84 -> fails every time with the error above Additional tests performed (none resolved the issue on kernel 30): - NVreg_PreserveVideoMemoryAllocations=1 already set by default (via /lib/modprobe.d/nvidia-runtimepm.conf) -- no effect - Disabling GPU firmware (NVreg_EnableGpuFirmware=0) -- no effect, identical error - nvidia-hibernate.service, nvidia-resume.service, nvidia-suspend.service all confirmed enabled Related bug (different symptom, same kernel/driver pair): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2164816 -- describes a hibernation write/poweroff failure on the same kernel 7.0.0-30-generic with a newer NVIDIA GPU (RTX 5060 Ti). My issue occurs during resume/restore instead, which may indicate a broader PM regression affecting the NVIDIA driver's PCI freeze/thaw callbacks introduced in this kernel version. Full dmesg output attached showing the failure at the "nv_pmops_freeze" line. --- ProblemType: Bug ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: seghir 1566 F.... wireplumber /dev/snd/controlC0: seghir 1566 F.... wireplumber /dev/snd/controlC1: seghir 1566 F.... wireplumber /dev/snd/seq: seghir 1563 F.... pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 22.3 HibernationDevice: RESUME=UUID=3413547b-d881-4439-990b-994ec8807450 MachineType: ASUSTeK COMPUTER INC. ASUS TUF Dash F15 FX517ZE_TUF517ZE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-30-generic root=UUID=4b23724b-e789-4437-9b4e-ba97027762d7 ro quiet splash resume=UUID=3413547b-d881-4439-990b-994ec8807450 ProcVersionSignature: Ubuntu 7.0.0-30.30~24.04.1-generic 7.0.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-7.0.0-30-generic N/A linux-backports-modules-7.0.0-30-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.29 Tags: zena Uname: Linux 7.0.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 12/15/2023 dmi.bios.release: 5.26 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FX517ZE.319 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX517ZE 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.ec.firmware.release: 3.10 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFX517ZE.319:bd12/15/2023:br5.26:efr3.10:svnASUSTeKCOMPUTERINC.:pnASUSTUFDashF15FX517ZE_TUF517ZE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX517ZE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSTUFDashF15: dmi.product.family: ASUS TUF Dash F15 dmi.product.name: ASUS TUF Dash F15 FX517ZE_TUF517ZE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2165927/+subscriptions
[Bug 2164635] Re: System completely freezes immediately after automatic resume from suspend
I am attaching additional diagnostic data collected on 2026-09-03. The persistent journal contains six complete system hangs, each of which made the system entirely unresponsive and required a forced hardware restart. They have the same kernel signature. In each case, a `KMS thread` is blocked in uninterruptible `D` state on a semaphore likely held by `nvidia-modeset`; the stack trace repeatedly points to `nvWriteGpEntry [nvidia_modeset]`. The affected system is running Ubuntu 26.04, kernel `7.0.0-30-generic`, and `nvidia-driver-595-open` version `595.84-0ubuntu0.26.04.1` on an NVIDIA RTX 4050 Max-Q / AD107M GPU. The six incidents were recorded on 2026-08-10, 2026-08-11, 2026-08-12, 2026-08-25, 2026-09-01, and 2026-09-02. Each affected boot ended without a normal systemd shutdown sequence, consistent with requiring a forced restart. For the 2026-09-02 incident, the kernel continued reporting the blocked task for more than 1228 seconds; afterwards, several short presses of the physical power button were recorded, but systemd never began shutdown. I found no corresponding kernel panic, OOM event, NVMe/I/O failure, fatal PCIe error, or Machine Check Exception in the retained boots. The attached report contains the timestamps, representative kernel excerpt, and related NVIDIA ACPI/EDID warnings. ** Attachment added: "FEEDBACK.launchpad-2164635-nvidia-kms-hangs.md" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2164635/+attachment/5997276/+files/FEEDBACK.launchpad-2164635-nvidia-kms-hangs.md -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2164635 Title: System completely freezes immediately after automatic resume from suspend Status in linux package in Ubuntu: New Bug description: ## Summary The system completely freezes immediately after resuming from suspend. This has happened three times so far. In all observed cases, the machine had been suspended automatically due to inactivity for a long period. The machine resumed from suspend without user interaction. The lock screen was displayed normally, but the entire system was completely unresponsive. ## Expected behavior The system should resume from suspend and remain fully operational. ## Actual behavior Immediately after resume: * the lock screen is displayed normally; * mouse input does not work; * the built-in keyboard does not respond; * the graphical session does not respond; * the entire machine appears frozen. The only way to recover is a forced reboot using the physical power button. After rebooting, the system works normally again. ## Reproducibility Observed 3 times. Common pattern: 1. The machine remains inactive for a long period. 2. Ubuntu automatically enters suspend. 3. The machine remains suspended for more than about 30 minutes. 4. The machine resumes without user interaction. 5. Immediately after resume, the system is completely frozen. The problem has only been observed after long suspend periods. ## Environment * Ubuntu 26.04 LTS * GNOME * Wayland * Dell G15 5530 * Hybrid/balanced graphics mode * NVIDIA GPU * External HDMI monitor connected * External monitor configured as the primary display * Extended desktop * Laptop lid open * Connected to AC power * Bluetooth enabled ## Additional information No graphical corruption or rendering artifacts are visible. The lock screen looks normal despite the system being completely unresponsive. No other suspend/resume problem has been observed. Because the whole system freezes, it is not possible to collect diagnostic information while the problem is occurring. Diagnostic information from the boot affected by the freeze was collected immediately after the forced reboot and submitted through Apport. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-30-generic 7.0.0-30.30 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: diego 5360 F.... pipewire diego 5368 F.... wireplumber /dev/snd/controlC0: diego 5368 F.... wireplumber /dev/snd/seq: diego 5360 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 07:34:33 2026 InstallationDate: Installed on 2026-08-02 (17 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0bda:5522 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 187c:0551 Alienware Corporation AW-ELC Bus 001 Device 004: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Dell Inc. Dell G15 5530 ProcEnviron: LANG=pt_BR.UTF-8 PATH=(custom, user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb 1 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-30-generic root=UUID=466e9a49-1cb8-4f82-9f43-588d2422dbe0 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2026 dmi.bios.release: 1.33 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.33.0 dmi.board.name: 0KC8TC dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnDellInc.:bvr1.33.0:bd04/23/2026:br1.33:efr1.22:svnDellInc.:pnDellG155530:pvr:rvnDellInc.:rn0KC8TC:rvrA02:cvnDellInc.:ct10:cvr:sku0BF7:pfaGSeries: dmi.product.family: GSeries dmi.product.name: Dell G15 5530 dmi.product.sku: 0BF7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2164635/+subscriptions
[Bug 2166370] Re: [NetApp] get_iscsi_target_details() does not paginate iscsi-interface-get-iter, causing iSCSI LIFs to be silently dropped and volume attach failures with SLM
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: kernel-sru-workflow ** No longer affects: kernel-sru-workflow/abi-testing -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166370 Title: [NetApp] get_iscsi_target_details() does not paginate iscsi-interface- get-iter, causing iSCSI LIFs to be silently dropped and volume attach failures with SLM Status in linux package in Ubuntu: New Bug description: Summary A customer running a NetApp ONTAP backend and Selective LUN Mapping (SLM) enabled found that attaching a Cinder volume to a Nova instance consistently failed.the volume sat in "attaching" status for about 7 minutes, then reverted to "available". Investigation traced this to Client.get_iscsi_target_details() issuing a single iscsi-interface-get-iter ZAPI call without a max-records argument and without any pagination handling. When an ONTAP cluster has more iSCSI LIFs than fit in one default-sized ZAPI response page, the method silently returns only the first page of results. Because SLM restricted the affected LUN to specific reporting nodes whose LIFs fell outside that truncated first page, those LIFs were never returned to Nova/os-brick, the initiator never attempted iSCSI login/discovery against them, no working path was created, multipath -ll showed no device, and the attach ultimately timed out and rolled the instance back to available. Environment - OpenStack: Nova + Cinder (NetApp cDOT iSCSI driver), os-brick iSCSI connector - Backend: NetApp ONTAP cluster with 12 nodes, SLM (Selective LUN Mapping) enabled - Multiple nodes/LIFs in the cluster (>20 iSCSI interfaces total) Steps to reproduce / conditions 1. Configure an ONTAP cluster with enough nodes/iSCSI LIFs that the total LIF count exceeds ONTAP's default iscsi-interface-get-iter page size when max-records is not specified. 2. Provision a LUN whose SLM reporting-nodes are configured such that the serving LIFs are not in the first page of results returned by an unpaginated iscsi-interface-get-iter (in the customer's case, node 05/06 LIFs were excluded while nodes served by the LUN's home controller happened to fall outside the returned page). 3. Attach the corresponding Cinder volume to a Nova instance Observed behavior - nova-compute logs "Attaching volume ... to /dev/sdb", passes connection info (target_portals/target_iqns/target_luns) to os-brick. - os-brick's iSCSI connector logs in to the portals it was given and repeatedly scans for the device (Searching for a device in session ... yield: None) in a loop for ~7 minutes. - Packet capture confirms no iSCSI login/REPORT LUNS traffic is ever sent to the target IPs on the controller nodes (05/06) that SLM actually maps the LUN to - Manual LUN mapping test on a second compute node (comp138) confirmed the LUN is correctly reachable there because that host happened to already have a session on a portal within the returned page. - Attach ultimately fails: os_brick.exception.VolumeDeviceNotFound: Volume device not found, and the volume reverts from attaching to available. Root cause: get_iscsi_target_details() in client_cmode.py does not set max-records on the iscsi-interface-get-iter request and does not iterate using the next-tag element ONTAP returns when a result set is truncated. With enough total iSCSI LIFs across the cluster, the call returns only a partial (first-page) list of LIFs. When SLM restricts a given LUN to specific reporting nodes whose LIFs are not in that truncated first page, the Cinder driver never advertises those LIFs as target portals, so the initiator has no way to discover/log in to the correct path, and the volume attach fails. Impact: Any deployment with more iSCSI LIFs than one ZAPI page (commonly seen in larger/multi-node clusters) combined with SLM restricting a LUN to specific nodes can hit this - the driver may simply never learn about the LIFs it needs to advertise, causing intermittent, host/LUN-mapping-dependent attach failures that are difficult to diagnose without a packet capture, as seen here. [1] cinder/volume/drivers/netapp/dataontap/client/client_cmode.py -- swm properties -- built: route-entry: 1 reason: crank-failure: Stalled -- Package not identified from title ~~: tracker: last-message: '2026-09-03 14:45:14.345120+00:00' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166370/+subscriptions
[Bug 2163863] Re: New CVS firmware protocol 2.0 takes additional handshake command flag to disable HPD
Migrated to hwe-7.0 already. ** Changed in: linux-oem-6.17 (Ubuntu Noble) Status: In Progress => Won't Fix -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163863 Title: New CVS firmware protocol 2.0 takes additional handshake command flag to disable HPD Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.17 package in Ubuntu: Invalid Status in linux-oem-7.0 package in Ubuntu: Invalid Status in vision-drivers package in Ubuntu: Incomplete Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: Won't Fix Status in linux-oem-7.0 source package in Noble: Invalid Status in vision-drivers source package in Noble: Won't Fix Status in linux source package in Resolute: Triaged Status in linux-oem-6.17 source package in Resolute: Invalid Status in linux-oem-7.0 source package in Resolute: Triaged Status in vision-drivers source package in Resolute: Incomplete Status in linux source package in Stonking: Fix Released Status in linux-oem-6.17 source package in Stonking: Invalid Status in linux-oem-7.0 source package in Stonking: Invalid Status in vision-drivers source package in Stonking: Incomplete Bug description: From the CVS Driver perspective, camera ownership is already handled by the driver. When running with firmware that supports Protocol 2.0 or later, the driver sends a command to indicate that SENSING OFF is required. However, for firmware that only supports Protocol 1.0, there is no mechanism to notify the firmware of a SENSING OFF state. Historically, this was not an issue because Linux did not have any users of HPD (Human Presence Detection) functionality. ISH was not enabling or registering those sensors, so CVS would never receive HPD- related notifications. However, in the current scenario, it appears that the sensors are being registered and treated as HPD-capable devices under Linux, resulting in ISH sending HPD-related commands to CVS FW. This behavior is unexpected on Linux and is not part of the Linux POR. The CVS driver has no visibility into when ISH sends HPD notifications to CVS FW, nor does it have a mechanism to detect an unexpected HPD ownership transition and perform any blocking, recovery, or re- handshake. Even on Windows, these are independent communication paths operating in parallel. Affects: https://certification.canonical.com/hardware/202606-39025/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163863/+subscriptions
[Bug 2165806] Re: Ubuntu 26.04.1 Server ISO cannot install on MAXIO MAP1602 NVMe due to kernel 7.0.0-30 I/O regression; 7.0.0-31 works
Hello, and thanks for submitting the detailed bug report! I will pass this along to the kernel team to have a closer look. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Benjamin Wheeler (benjaminwheeler) ** Changed in: linux (Ubuntu) Assignee: Benjamin Wheeler (benjaminwheeler) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Status: New => Triaged -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2165806 Title: Ubuntu 26.04.1 Server ISO cannot install on MAXIO MAP1602 NVMe due to kernel 7.0.0-30 I/O regression; 7.0.0-31 works Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 26.04.1 Server cannot be installed on an ACEMAGIC M1A PRO+ with its factory HOGE H820 2 TB / MAXIO MAP1602 NVMe SSD. The Ubuntu 26.04.1 live-server ISO boots kernel 7.0.0-30. With this kernel, reproducible NVMe READ and WRITE failures occur during installation, and the installation eventually fails during grub-install. The same physical machine, SSD, M.2 slot, and SSD firmware operate normally with kernels 7.0.0-14, 6.8, 6.14, and 7.0.0-31. The regression is also independently reproducible on installed Ubuntu 24.04 and Ubuntu 26.04 systems by switching between 7.0.0-30 and 7.0.0-31. PRIMARY IMPACT The current Ubuntu 26.04.1 Server ISO cannot complete installation on this hardware. During installation, kernel 7.0.0-30 reports NVMe block I/O failures. The installer then eventually fails with: grub-install: error: cannot copy '/usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed' to '/boot/efi/EFI/ubuntu/grubx64.efi': Invalid argument. The grub-install failure occurs in the same installation in which the kernel is reporting NVMe READ/WRITE failures. I believe the storage regression is likely contributing to the grub-install failure, but I have not independently proven that the NVMe errors are the direct cause of the grub-install error. HARDWARE System: ACEMAGIC M1A PRO+ AMD Ryzen AI Max+ 395 AMD Radeon 8060S 128 GB memory, 8000 MT/s BIOS: American Megatrends Project version: P10_F11_20_IEC0008_BI0010_AMI_120W Build date: 2026-01-13 NVMe: Model: HOGE H820 2TB Firmware: H240313a PCI vendor ID: 0x1e4b PCI device/controller: 0x1602 Controller family: MAXIO MAP1602 NVMe SMART data observed during troubleshooting: critical_warning: 0 available_spare: 100% percentage_used: 0% media_errors: 0 num_err_log_entries: 0 temperature: approximately 39 C UBUNTU 26.04.1 SERVER INSTALL FAILURE Installation method: - Ubuntu 26.04.1 live-server ISO - ISO written directly to USB using dd - UEFI boot - Secure Boot disabled - entire NVMe disk - no LVM - ext4 root filesystem - 1 GiB FAT EFI System Partition The installer successfully partitions the disk, creates the filesystems, and mounts the target. During installation, kernel 7.0.0-30 begins producing NVMe block I/O failures. Examples of WRITE failures observed: invalid error, dev nvme0n1, sector 11896 op 0x1:(WRITE) ... invalid error, dev nvme0n1, sector 2080 op 0x1:(WRITE) ... followed by messages including: Buffer I/O error on dev nvme0n1p1, logical block 32, lost async page write Buffer I/O error on dev nvme0n1p1, logical block 33, lost async page write Buffer I/O error on dev nvme0n1p1, logical block 34, lost async page write READ failures were also observed, including: invalid error, dev nvme0n1, sector 3104 op 0x0:(READ) ... invalid error, dev nvme0n1, sector 3144 op 0x0:(READ) ... invalid error, dev nvme0n1, sector 3184 op 0x0:(READ) ... ... invalid error, dev nvme0n1, sector 3480 op 0x0:(READ) ... The failing READ requests repeatedly showed multi-segment I/O, including phys_seg 33. Installation ultimately fails at grub-install with: grub-install: error: cannot copy '/usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed' to '/boot/efi/EFI/ubuntu/grubx64.efi': Invalid argument. The Ubuntu installer offered to send an error report to Canonical after the failure, and I selected that option. Therefore an installer-side failure report from this machine should already exist in Canonical's error-reporting infrastructure, although I do not currently have an identifier for that report. REGRESSION TESTING All of the following tests used the same physical ACEMAGIC M1A PRO+, same HOGE H820 SSD, same M.2 slot, and same SSD firmware. Ubuntu 26.04 ------------ 1. Ubuntu 26.04 base installation, kernel 7.0.0-14 PASS Ubuntu 26.04 installs and boots successfully. No NVMe "invalid error", Buffer I/O errors, or related read/write failures are present. 2. Upgrade the installed Ubuntu 26.04 system to kernel 7.0.0-30 FAIL The same NVMe "invalid error" messages return. 3. Upgrade the same Ubuntu 26.04 installation from 7.0.0-30 to 7.0.0-31 from ppa:canonical-kernel-team/ppa PASS The NVMe errors disappear again. Ubuntu 26.04.1 live-server ISO ------------------------------ 4. Ubuntu 26.04.1 live-server ISO, kernel 7.0.0-30 FAIL The same NVMe READ/WRITE errors occur during installation. Unlike the Ubuntu 24.04.4 installer case below, the failures are severe enough here that grub-install fails and Ubuntu 26.04.1 Server cannot be installed. Ubuntu 24.04 ------------ 5. Ubuntu 24.04.4 installation using kernel 7.0.0-30 KERNEL REGRESSION PRESENT, BUT INSTALLATION COMPLETES Ubuntu 24.04.4 installs successfully. After boot, the same NVMe "invalid error" messages are present in the kernel logs. Thus the storage regression is present with 7.0.0-30 on Ubuntu 24.04 as well, even though that installer happens to complete. 6. Downgrade the same Ubuntu 24.04 system to kernel 6.8 PASS The NVMe errors disappear. Sustained fio testing completes without NVMe errors. The Radeon 8060S does not initialize correctly on this older kernel, which is unrelated to the NVMe regression. 7. Upgrade the same Ubuntu 24.04 system to kernel 6.14 PASS NVMe remains clean. Radeon 8060S / amdgpu initializes successfully. Sustained fio testing completes without NVMe errors. 8. Upgrade the same Ubuntu 24.04 system to kernel 7.0.0-31 from ppa:canonical-kernel-team/ppa PASS NVMe errors remain absent. A 10-minute mixed direct-I/O fio workload using libaio, iodepth=32, numjobs=4, and direct=1 completes without NVMe errors. SUMMARY Ubuntu 26.04 + 7.0.0-14 -> PASS Ubuntu 26.04 + 7.0.0-30 -> FAIL Ubuntu 26.04 + 7.0.0-31 -> PASS Ubuntu 26.04.1 ISO + -30 -> FAIL, installation cannot complete Ubuntu 24.04.4 + 7.0.0-30 -> regression present, install completes Ubuntu 24.04 + 6.8 -> PASS Ubuntu 24.04 + 6.14 -> PASS Ubuntu 24.04 + 7.0.0-31 -> PASS The -30 -> -31 comparison has been reproduced on both Ubuntu 24.04 and Ubuntu 26.04. This strongly isolates the problem to the kernel code present in 7.0.0-30 and absent/fixed in 7.0.0-31, rather than to the Ubuntu userspace release or SSD hardware. APST TESTING NVMe APST was tested as a possible cause. The Ubuntu 26.04.1 installer was booted with: nvme_core.default_ps_max_latency_us=0 The runtime value was verified as: /sys/module/nvme_core/parameters/default_ps_max_latency_us = 0 The same NVMe WRITE / Buffer I/O errors still occurred. Disabling NVMe APST therefore does not resolve the failure. STORAGE VALIDATION The SSD does not appear to contain defective media at the sector range where errors were reported. On a working kernel, a direct read spanning the affected region completed successfully: dd if=/dev/nvme0n1 of=/dev/null bs=512 skip=3000 count=600 iflag=direct 600+0 records in 600+0 records out No new NVMe errors were produced. The same SSD also completed substantial mixed read/write fio testing on working kernels without media errors or kernel block-I/O failures. This included sustained testing on: - 6.8 - 6.14 - 7.0.0-31 LIKELY UPSTREAM REGRESSION / FIX I have not performed a source-level git bisect, so the following is a suspected cause rather than independently proven. Linux 7.0.11 included: iommupt: Avoid rewalking during map upstream commit: d6c65b0fd6218bd21ed0be7a8d3218e8f6dc91de Linux 7.0.13 later included: iommu/dma: Do not try to iommu_map a 0 length region in swiotlb upstream commit: 6ec91df8aff77e2e8fe3179c1f3fc15b43a40ba3 The latter fix describes an IOMMU DMA mapping path in which an unaligned mapping can produce a zero-length middle region. iommu_map() then rejects the zero-length mapping as illegal. The upstream description explicitly notes NVMe as a frequent trigger because NVMe can issue unusually aligned buffers in some paths. Ubuntu kernel 7.0.0-31 contains the Linux 7.0.13 and 7.0.14 upstream stable updates, and 7.0.0-31 is the first tested Ubuntu 7.0 kernel in this environment where the problem disappears. Given the observed: 7.0.0-30 -> FAIL 7.0.0-31 -> PASS and the I/O errors being reported as "invalid error", this IOMMU/DMA fix appears to be a strong candidate for the fix. Please confirm whether this system is hitting that regression, or another change incorporated between Ubuntu 7.0.0-30 and 7.0.0-31. EXPECTED RESULT Ubuntu 26.04.1 Server should install successfully on this hardware. The HOGE H820 / MAXIO MAP1602 NVMe controller should operate without kernel block-I/O failures. IMPACT The practical issue is not merely log noise. The kernel shipped on the Ubuntu 26.04.1 Server ISO causes storage errors during installation and prevents the current 26.04.1 live-server image from completing installation on this system. The same regression can also be reproduced after installation by booting 7.0.0-30 on both Ubuntu 24.04 and Ubuntu 26.04. Kernel 7.0.0-31 from ppa:canonical-kernel-team/ppa does not reproduce the problem on either release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2165806/+subscriptions
[Bug 2165927] Re: Hibernation resume fails with nv_pmops_freeze returns -5 on kernel 7.0.0-30-generic (regression from 7.0.0-28-generic)
Hello, thanks for the information. Unfortunately, since you are using Linux Mint, you will need to open a bug report with the Linux Mint team, or reproduce the issue on Ubuntu (https://ubuntu.com/download). I believe you can start here https://forums.linuxmint.com/viewforum.php?f=49 Thank you and good luck! ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2165927 Title: Hibernation resume fails with nv_pmops_freeze returns -5 on kernel 7.0.0-30-generic (regression from 7.0.0-28-generic) Status in linux package in Ubuntu: Invalid Bug description: Ubuntu 26.04 LTS (Resolute Raccoon), kernel 7.0.0-30-generic (Ubuntu 7.0.0-30.30-generic / upstream 7.0.12) — running as Linux Mint 22.3. System information: - Distro: Linux Mint 22.3, based on Ubuntu 24.04 LTS (Noble Numbat), kernel 7.0.0-30-generic (Ubuntu 7.0.0-30.30~24.04.1-generic). - Host: ASUS TUF Dash F15 FX517ZE (Optimus hybrid graphics) - CPU: Intel 12th Gen i7-12650H - GPU: NVIDIA GeForce RTX 3050 Ti Mobile + Intel Alder Lake-P UHD Graphics - NVIDIA driver: 595.84 (Open Kernel Module) - PRIME mode: on-demand - Affected kernel: 7.0.0-30-generic (working: 7.0.0-28-generic, same driver) Description: Hibernation worked reliably until approximately three weeks ago. After a kernel upgrade from 7.0.0-28-generic to 7.0.0-30-generic, hibernation resume consistently fails. The hibernation image is written successfully. On the next boot, the kernel correctly detects and loads the saved image (100% progress, "Image successfully loaded"), but immediately afterward the NVIDIA driver fails to freeze the PCI device during the atomic restore step: nvidia 0000:01:00.0: PM: pci_pm_freeze(): nv_pmops_freeze [nvidia] returns -5 nvidia 0000:01:00.0: PM: dpm_run_callback(): pci_pm_freeze returns -5 nvidia 0000:01:00.0: PM: failed to quiesce async: error -5 PM: hibernation: Failed to load image, recovering. PM: hibernation: resume failed (-5) The kernel then aborts the restore and boots fresh, discarding the saved session entirely (all open applications are lost). Steps to reproduce: 1. Open several applications (tested with ParaView, browser, terminal) 2. sudo systemctl hibernate 3. Power the machine back on 4. Observe: fresh boot instead of restored session; dmesg shows the error above Regression testing performed: - Kernel 7.0.0-28-generic + driver 595.84 -> hibernation/resume works perfectly, all windows restored - Kernel 7.0.0-30-generic + driver 595.84 -> fails every time with the error above Additional tests performed (none resolved the issue on kernel 30): - NVreg_PreserveVideoMemoryAllocations=1 already set by default (via /lib/modprobe.d/nvidia-runtimepm.conf) -- no effect - Disabling GPU firmware (NVreg_EnableGpuFirmware=0) -- no effect, identical error - nvidia-hibernate.service, nvidia-resume.service, nvidia-suspend.service all confirmed enabled Related bug (different symptom, same kernel/driver pair): https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2164816 -- describes a hibernation write/poweroff failure on the same kernel 7.0.0-30-generic with a newer NVIDIA GPU (RTX 5060 Ti). My issue occurs during resume/restore instead, which may indicate a broader PM regression affecting the NVIDIA driver's PCI freeze/thaw callbacks introduced in this kernel version. Full dmesg output attached showing the failure at the "nv_pmops_freeze" line. --- ProblemType: Bug ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: seghir 1566 F.... wireplumber /dev/snd/controlC0: seghir 1566 F.... wireplumber /dev/snd/controlC1: seghir 1566 F.... wireplumber /dev/snd/seq: seghir 1563 F.... pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 22.3 HibernationDevice: RESUME=UUID=3413547b-d881-4439-990b-994ec8807450 MachineType: ASUSTeK COMPUTER INC. ASUS TUF Dash F15 FX517ZE_TUF517ZE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-30-generic root=UUID=4b23724b-e789-4437-9b4e-ba97027762d7 ro quiet splash resume=UUID=3413547b-d881-4439-990b-994ec8807450 ProcVersionSignature: Ubuntu 7.0.0-30.30~24.04.1-generic 7.0.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-7.0.0-30-generic N/A linux-backports-modules-7.0.0-30-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.29 Tags: zena Uname: Linux 7.0.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 12/15/2023 dmi.bios.release: 5.26 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FX517ZE.319 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX517ZE 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.ec.firmware.release: 3.10 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFX517ZE.319:bd12/15/2023:br5.26:efr3.10:svnASUSTeKCOMPUTERINC.:pnASUSTUFDashF15FX517ZE_TUF517ZE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX517ZE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSTUFDashF15: dmi.product.family: ASUS TUF Dash F15 dmi.product.name: ASUS TUF Dash F15 FX517ZE_TUF517ZE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2165927/+subscriptions
среда
[Bug 2163696] Re: Keyboard not working after Kernal upgrade
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163696 Title: Keyboard not working after Kernal upgrade Status in linux package in Ubuntu: New Bug description: I upgraded from 6.8.0-137-generic to 6.8.0-138 generic on Linux Mint. After the upgrade, my keyboard stopped working. (On 2 machines). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163696/+subscriptions