Still happens with Linux maryzen 6.8.0-136-generic #136~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 3 16:29:11 UTC x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2092703 Title: Ubuntu 22.04 fails to start after kernel update to 6.8.0-50 Status in linux package in Ubuntu: Confirmed Bug description: Hello, I've recently (2024-12-24) updated the kernel in my Ubuntu 22.04 from 6.8.0-49 to 6.8.0-50, but it doesn't work. I can still successfully boot 6.8.0-49 kernel. I'm using Lenovo Thinkpad L15 Gen 2 with AMD Ryzen 5850U. As far as I noticed in boot logs from previous boot (journalctl -b -1), there is some problem with X.org: gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) modesetting: Driver for Modesetting Kernel Drivers: kms gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) FBDEV: driver for framebuffer: fbdev gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) VESA: driver for VESA chipsets: vesa gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: xf86EnableIO: failed to enable I/O ports 0000-03ff (Operation not permitted) gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) open /dev/dri/card0: No such file or directory gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (WW) Falling back to old probe method for modesetting gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) open /dev/dri/card0: No such file or directory gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) Loading sub module "fbdevhw" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) LoadModule: "fbdevhw" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) Loading /usr/lib/xorg/modules/libfbdevhw.so gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) Module fbdevhw: vendor="X.Org Foundation" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: compiled for 1.21.1.4, module version = 0.0.2 gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: ABI class: X.Org Video Driver, version 25.2 gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Unable to find a valid framebuffer device gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (WW) Falling back to old probe method for fbdev gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) Loading sub module "fbdevhw" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) LoadModule: "fbdevhw" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) Loading /usr/lib/xorg/modules/libfbdevhw.so gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) Module fbdevhw: vendor="X.Org Foundation" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: compiled for 1.21.1.4, module version = 0.0.2 gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: ABI class: X.Org Video Driver, version 25.2 gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) open /dev/fb0: No such file or directory gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: vesa: Ignoring device with a bound kernel driver gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Screen 0 deleted because of no matching config section. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) UnloadModule: "modesetting" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Screen 0 deleted because of no matching config section. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) UnloadModule: "fbdev" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) UnloadSubModule: "fbdevhw" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) UnloadSubModule: "fbdevhw" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) UnloadSubModule: "fbdevhw" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Screen 0 deleted because of no matching config section. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (II) UnloadModule: "vesa" gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Device(s) detected, but none match those in the config file. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: Fatal server error: gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) no screens found(EE) gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: Please consult the The X.Org Foundation support gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: at http://wiki.x.org gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: for help. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1667]: (EE) Server terminated with error (1). Closing log file. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a /usr/libexec/gdm-x-session[1664]: Unable to run X server gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a gdm-launch-environment][1657]: pam_unix(gdm-launch-environment:session): session closed for user gdm gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a gdm3[1205]: Gdm: GdmDisplay: Session never registered, failing gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a gdm-launch-environment][1657]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a kernel: logitech-hidpp-device 0003:046D:4082.0004: HID++ 4.5 device connected. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a systemd[1]: session-c6.scope: Deactivated successfully. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a gdm3[1205]: Gdm: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a gdm3[1205]: Gdm: Child process -1664 was already dead. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a gdm3[1205]: Gdm: GdmDisplay: Session never registered, failing gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a systemd-logind[1049]: Session c6 logged out. Waiting for processes to exit. gru 30 07:00:40 adrian-ThinkPad-L15-Gen-2a systemd-logind[1049]: Removed session c6. When booting 6.8.0-49 (the one that works fine), I see it uses /dev/dri/card1 instead (extract from logs attached as kernel-6.8.0-49-journalctl-boot-logs-ok.txt). I'm also attaching: - cat /proc/version_signature > version.log (from the working kernel 6.8.0-49) - sudo lspci -vnvn > lspci-vnvn.log (from the working kernel 6.8.0-49) - apt-updated-packages.txt - a list of updated packages - kernel-6.8.0-50-journalctl-boot-logs-issue.txt - extract from logs from journalctl -b -1 (boot attempt using problematic kernel 6.8.0-50) - kernel-6.8.0-49-journalctl-boot-logs-ok.txt - extract from logs from journalctl -b -0 (booting working kernel 6.8.0-49) How can I make kernel 6.8.0-50 work? BR, Adrian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2092703/+subscriptions
воскресенье
[Bug 2163121] Re: [Regression] Laptop fails to power off completely when HDMI is connected in kernel 7.0.0-28
** Description changed: Issue Description: When shutting down the system with an external monitor connected via HDMI, the OS finishes the shutdown process normally, but the laptop hardware remains powered on (the power LED stays illuminated and the machine does not fully power off). If the HDMI cable is disconnected before the shutdown, the laptop powers off completely and correctly. Important note: Once the system enters this "stuck" state (black screen, power LED on), unplugging the HDMI cable does not recover the system or allow it to finish powering off. It remains completely frozen. The HDMI cable must be unplugged before initiating the shutdown sequence to avoid the hang. Regression Details: This is a regression introduced in kernel 7.0.0-28. I have tested previous kernels on the exact same hardware and they work perfectly (the system powers off completely even with the HDMI connected). - Fails in: Kernel 7.0.0-28 + Fails in: Kernel 7.0.0-28-generic Works in: Kernel 7.0.0-14-generic Works in: Kernel 6.x branch (tested on Linux Mint's default 6.x kernel) Steps to Reproduce: 1. Boot the laptop with kernel 7.0.0-28. 2, Connect an external monitor via the HDMI port. 3. Shut down the system from the GUI (or via sudo shutdown now). 4. Notice the OS halts, but the laptop's power LED remains on and the machine does not fully power down. 5. Unplugging the HDMI cable at this frozen stage does nothing; the machine remains stuck and must be forced off by holding the physical power button. System Information: OS: Linux Mint 22.3 Zena (Ubuntu 24.04 noble base) Hardware: LENOVO IdeaPad 5 15ALC05 CPU: AMD Ryzen 7 5700U with Radeon Graphics (Lucienne / Zen 2) GPU: AMD Lucienne (amdgpu driver) BIOS: H2CN33WW (08/30/2023) System: - Kernel: 7.0.0-14-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0 clocksource: tsc - Desktop: Cinnamon v: 6.6.9 tk: GTK v: 3.24.41 wm: Muffin v: 6.6.3 with: plank vt: 7 dm: LightDM - v: 1.30.0 Distro: Linux Mint 22.3 Zena base: Ubuntu 24.04 noble + Kernel: 7.0.0-28-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0 clocksource: tsc + Desktop: Cinnamon v: 6.6.9 tk: GTK v: 3.24.41 wm: Muffin v: 6.6.3 with: plank vt: 7 dm: LightDM + v: 1.30.0 Distro: Linux Mint 22.3 Zena base: Ubuntu 24.04 noble Machine: - Type: Laptop System: LENOVO product: 82LN v: IdeaPad 5 15ALC05 - Mobo: LENOVO model: LNVNB161216 UEFI: LENOVO v: H2CN33WW date: 08/30/2023 + Type: Laptop System: LENOVO product: 82LN v: IdeaPad 5 15ALC05 + Mobo: LENOVO model: LNVNB161216 UEFI: LENOVO v: H2CN33WW date: 08/30/2023 CPU: - Info: 8-core model: AMD Ryzen 7 5700U with Radeon Graphics bits: 64 type: MT MCP smt: enabled - arch: Zen 2 rev: 1 + Info: 8-core model: AMD Ryzen 7 5700U with Radeon Graphics bits: 64 type: MT MCP smt: enabled + arch: Zen 2 rev: 1 Graphics: - Device-1: AMD Lucienne vendor: Lenovo driver: amdgpu v: kernel arch: GCN-5 pcie: speed: 8 GT/s - lanes: 16 ports: active: eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:164c - class-ID: 0300 + Device-1: AMD Lucienne vendor: Lenovo driver: amdgpu v: kernel arch: GCN-5 pcie: speed: 8 GT/s + lanes: 16 ports: active: eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:164c + class-ID: 0300 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163121 Title: [Regression] Laptop fails to power off completely when HDMI is connected in kernel 7.0.0-28 Status in linux package in Ubuntu: New Bug description: Issue Description: When shutting down the system with an external monitor connected via HDMI, the OS finishes the shutdown process normally, but the laptop hardware remains powered on (the power LED stays illuminated and the machine does not fully power off). If the HDMI cable is disconnected before the shutdown, the laptop powers off completely and correctly. Important note: Once the system enters this "stuck" state (black screen, power LED on), unplugging the HDMI cable does not recover the system or allow it to finish powering off. It remains completely frozen. The HDMI cable must be unplugged before initiating the shutdown sequence to avoid the hang. Regression Details: This is a regression introduced in kernel 7.0.0-28. I have tested previous kernels on the exact same hardware and they work perfectly (the system powers off completely even with the HDMI connected). Fails in: Kernel 7.0.0-28-generic Works in: Kernel 7.0.0-14-generic Works in: Kernel 6.x branch (tested on Linux Mint's default 6.x kernel) Steps to Reproduce: 1. Boot the laptop with kernel 7.0.0-28. 2, Connect an external monitor via the HDMI port. 3. Shut down the system from the GUI (or via sudo shutdown now). 4. Notice the OS halts, but the laptop's power LED remains on and the machine does not fully power down. 5. Unplugging the HDMI cable at this frozen stage does nothing; the machine remains stuck and must be forced off by holding the physical power button. System Information: OS: Linux Mint 22.3 Zena (Ubuntu 24.04 noble base) Hardware: LENOVO IdeaPad 5 15ALC05 CPU: AMD Ryzen 7 5700U with Radeon Graphics (Lucienne / Zen 2) GPU: AMD Lucienne (amdgpu driver) BIOS: H2CN33WW (08/30/2023) System: Kernel: 7.0.0-28-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0 clocksource: tsc Desktop: Cinnamon v: 6.6.9 tk: GTK v: 3.24.41 wm: Muffin v: 6.6.3 with: plank vt: 7 dm: LightDM v: 1.30.0 Distro: Linux Mint 22.3 Zena base: Ubuntu 24.04 noble Machine: Type: Laptop System: LENOVO product: 82LN v: IdeaPad 5 15ALC05 Mobo: LENOVO model: LNVNB161216 UEFI: LENOVO v: H2CN33WW date: 08/30/2023 CPU: Info: 8-core model: AMD Ryzen 7 5700U with Radeon Graphics bits: 64 type: MT MCP smt: enabled arch: Zen 2 rev: 1 Graphics: Device-1: AMD Lucienne vendor: Lenovo driver: amdgpu v: kernel arch: GCN-5 pcie: speed: 8 GT/s lanes: 16 ports: active: eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:164c class-ID: 0300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163121/+subscriptions
[Bug 2131598] Re: Keyboard keys get stuck and repeat
Still happens with Linux maryzen 6.8.0-136-generic #136~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 3 16:29:11 UTC x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2131598 Title: Keyboard keys get stuck and repeat Status in linux package in Ubuntu: New Bug description: Once in a while, as I use my laptop (a Lenovo ThinkPad P16s Gen 2 AMD, running Ubuntu 22.04 and the proposed OEM kernel), as I am typing a key gets 'stuck', ie., it acts as if I never lifted the finger of the key. If I was typing an 'a' it starts writing 'aaaaaaaa' nonstop, if I was typing 'd' it will write 'dddddd', or, worse, if I was in vim an not in insert mode, it starts deleting all the file's lines, one by one. When this happens, nothing seems to make the input stop. It always happened to me while using vim inside a konsole. The only thing I have managed to do to make the input stop was to insert an USB keyboard on one of the USB slots - that made the input stop and the computer behave normally. After the fact I looked at dmesg but there was no indication whatsoever of something gone wrong. This happens to me infrequently (less than one per month), but it wasn't just once - and this can be perilous (in case the input being sent has a destructive action, like the 'delete' key on a file manager; or when there's no external keyboards around and the only choice is to force a shutdown by pressing the power key). Apparently I am not alone in this, for eg. you can see the same behavior on a Lenovo ThinkPad L14 Gen 2 running 20.04 reported in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/124406/comments/385 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2131598/+subscriptions
[Bug 2163121] [NEW] [Regression] Laptop fails to power off completely when HDMI is connected in kernel 7.0.0-28
Public bug reported: Issue Description: When shutting down the system with an external monitor connected via HDMI, the OS finishes the shutdown process normally, but the laptop hardware remains powered on (the power LED stays illuminated and the machine does not fully power off). If the HDMI cable is disconnected before the shutdown, the laptop powers off completely and correctly. Important note: Once the system enters this "stuck" state (black screen, power LED on), unplugging the HDMI cable does not recover the system or allow it to finish powering off. It remains completely frozen. The HDMI cable must be unplugged before initiating the shutdown sequence to avoid the hang. Regression Details: This is a regression introduced in kernel 7.0.0-28. I have tested previous kernels on the exact same hardware and they work perfectly (the system powers off completely even with the HDMI connected). Fails in: Kernel 7.0.0-28 Works in: Kernel 7.0.0-14-generic Works in: Kernel 6.x branch (tested on Linux Mint's default 6.x kernel) Steps to Reproduce: 1. Boot the laptop with kernel 7.0.0-28. 2, Connect an external monitor via the HDMI port. 3. Shut down the system from the GUI (or via sudo shutdown now). 4. Notice the OS halts, but the laptop's power LED remains on and the machine does not fully power down. 5. Unplugging the HDMI cable at this frozen stage does nothing; the machine remains stuck and must be forced off by holding the physical power button. System Information: OS: Linux Mint 22.3 Zena (Ubuntu 24.04 noble base) Hardware: LENOVO IdeaPad 5 15ALC05 CPU: AMD Ryzen 7 5700U with Radeon Graphics (Lucienne / Zen 2) GPU: AMD Lucienne (amdgpu driver) BIOS: H2CN33WW (08/30/2023) System: Kernel: 7.0.0-14-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0 clocksource: tsc Desktop: Cinnamon v: 6.6.9 tk: GTK v: 3.24.41 wm: Muffin v: 6.6.3 with: plank vt: 7 dm: LightDM v: 1.30.0 Distro: Linux Mint 22.3 Zena base: Ubuntu 24.04 noble Machine: Type: Laptop System: LENOVO product: 82LN v: IdeaPad 5 15ALC05 Mobo: LENOVO model: LNVNB161216 UEFI: LENOVO v: H2CN33WW date: 08/30/2023 CPU: Info: 8-core model: AMD Ryzen 7 5700U with Radeon Graphics bits: 64 type: MT MCP smt: enabled arch: Zen 2 rev: 1 Graphics: Device-1: AMD Lucienne vendor: Lenovo driver: amdgpu v: kernel arch: GCN-5 pcie: speed: 8 GT/s lanes: 16 ports: active: eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:164c class-ID: 0300 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amdgpu hdmi lenovo regression shutdown ** Attachment added: "System logs, lspci and dmesg for kernel 7.0.0-28" https://bugs.launchpad.net/bugs/2163121/+attachment/5990834/+files/logs_kernel_7.0.0-28.zip -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163121 Title: [Regression] Laptop fails to power off completely when HDMI is connected in kernel 7.0.0-28 Status in linux package in Ubuntu: New Bug description: Issue Description: When shutting down the system with an external monitor connected via HDMI, the OS finishes the shutdown process normally, but the laptop hardware remains powered on (the power LED stays illuminated and the machine does not fully power off). If the HDMI cable is disconnected before the shutdown, the laptop powers off completely and correctly. Important note: Once the system enters this "stuck" state (black screen, power LED on), unplugging the HDMI cable does not recover the system or allow it to finish powering off. It remains completely frozen. The HDMI cable must be unplugged before initiating the shutdown sequence to avoid the hang. Regression Details: This is a regression introduced in kernel 7.0.0-28. I have tested previous kernels on the exact same hardware and they work perfectly (the system powers off completely even with the HDMI connected). Fails in: Kernel 7.0.0-28 Works in: Kernel 7.0.0-14-generic Works in: Kernel 6.x branch (tested on Linux Mint's default 6.x kernel) Steps to Reproduce: 1. Boot the laptop with kernel 7.0.0-28. 2, Connect an external monitor via the HDMI port. 3. Shut down the system from the GUI (or via sudo shutdown now). 4. Notice the OS halts, but the laptop's power LED remains on and the machine does not fully power down. 5. Unplugging the HDMI cable at this frozen stage does nothing; the machine remains stuck and must be forced off by holding the physical power button. System Information: OS: Linux Mint 22.3 Zena (Ubuntu 24.04 noble base) Hardware: LENOVO IdeaPad 5 15ALC05 CPU: AMD Ryzen 7 5700U with Radeon Graphics (Lucienne / Zen 2) GPU: AMD Lucienne (amdgpu driver) BIOS: H2CN33WW (08/30/2023) System: Kernel: 7.0.0-14-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0 clocksource: tsc Desktop: Cinnamon v: 6.6.9 tk: GTK v: 3.24.41 wm: Muffin v: 6.6.3 with: plank vt: 7 dm: LightDM v: 1.30.0 Distro: Linux Mint 22.3 Zena base: Ubuntu 24.04 noble Machine: Type: Laptop System: LENOVO product: 82LN v: IdeaPad 5 15ALC05 Mobo: LENOVO model: LNVNB161216 UEFI: LENOVO v: H2CN33WW date: 08/30/2023 CPU: Info: 8-core model: AMD Ryzen 7 5700U with Radeon Graphics bits: 64 type: MT MCP smt: enabled arch: Zen 2 rev: 1 Graphics: Device-1: AMD Lucienne vendor: Lenovo driver: amdgpu v: kernel arch: GCN-5 pcie: speed: 8 GT/s lanes: 16 ports: active: eDP-1 empty: DP-1,HDMI-A-1 bus-ID: 03:00.0 chip-ID: 1002:164c class-ID: 0300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163121/+subscriptions
[Bug 2163015] Re: System fails to power off / hangs on shutdown-reboot after upgrade to Kubuntu 26.04 (kernel 7.0)
Update: Issue resolved by updating ASUS ProArt X870E-CREATOR WIFI BIOS from version 1715 (2025-09-19) to version 2402 (2026-07-15). The updated AGESA ComboAM5 PI 1.3.0.1b Patch A appears to fix the ACPI shutdown/reboot hang. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163015 Title: System fails to power off / hangs on shutdown-reboot after upgrade to Kubuntu 26.04 (kernel 7.0) Status in linux package in Ubuntu: New Bug description: ## Summary On an HP ProBook 445 14" G11 (AMD Ryzen, Rembrandt/YELLOW_CARP APU, model 0x1002:0x1681), the system intermittently fails to fully power off or reboot after upgrading from Kubuntu 25.10 (kernel 6.17.x) to Kubuntu 26.04 LTS (kernel 7.0.x). The OS-level shutdown/reboot sequence completes cleanly according to systemd/journald logs, but the hardware does not fully cut power afterward (fan keeps running, power LED stays lit, screen goes black but the machine never truly turns off or restarts). This did not occur before the 25.10 → 26.04 upgrade. BIOS/EC firmware is already at the latest available version, ruling out a firmware fix as the immediate solution. ## Environment - **Hardware**: HP ProBook 445 14 inch G11 Notebook PC - **CPU/APU**: AMD Ryzen (Rembrandt, codename YELLOW_CARP, PCI ID 1002:1681, subsystem 103C:8C79) - **BIOS/EC**: 01.08.03 Rev.A (confirmed latest available via HP support site) - **OS**: Kubuntu 26.04 LTS "Resolute Raccoon" (upgraded from Kubuntu 25.10 "Questing Quokka") - **Kernel**: 7.0.0-29-generic (also reproduced on 7.0.0-28-generic; 7.0.0-22-generic available for further testing) - **Desktop**: KDE Plasma, Wayland session (SDDM) - **Secure Boot**: Enabled - **Disk encryption**: LUKS (root on NVMe, cryptsetup) ## Regression Context - Kubuntu 25.10 shipped with kernel 6.17.x and shutdown/reboot worked reliably. - Kubuntu 26.04 LTS ships with kernel 7.0.x (upstream renumbering from 6.x, not a from-scratch rewrite, but a full kernel major bump with all associated driver updates). - The 6.17.x kernel packages are no longer installed on this system, so a direct old-kernel bisect is not currently possible; only kernel points within the 7.0.x series (7.0.0-22, -28, -29) remain available. - The issue is **intermittent**, not deterministic: some shutdowns/reboots complete correctly (confirmed via journal: `systemd-poweroff.service` finishes and `poweroff.target` is reached cleanly), while others leave the hardware in a half-powered state. - The issue has also been observed on a plain `reboot` (not just `poweroff`), ruling out an S5-specific ACPI quirk. ## Steps Already Taken (no effect) 1. Verified BIOS/EC firmware is already the latest version (01.08.03 Rev.A) via `fwupdmgr` and HP's support site — no update available. 2. Added `acpi_osi=Linux` to `GRUB_CMDLINE_LINUX_DEFAULT` and ran `update-grub` — the very next reboot after applying this still hung, so this had no beneficial effect (parameter has since been reverted). 3. Confirmed via `journalctl -b -3 -e` that a "good" shutdown completes normally end-to-end at the systemd/journald level: ``` systemd-logind[1744]: The system will power off now! systemd-logind[1744]: System is powering down. ... systemd[1]: Finished systemd-poweroff.service - System Power Off. systemd[1]: Reached target poweroff.target - System Power Off. ``` No errors, no hung units, no failed unmounts in this particular boot's shutdown sequence. 4. Ruled out a misconfigured shutdown-vs-reboot action (checked `systemd-logind` logs directly; confirmed the correct target — `poweroff.target` or `reboot.target` — was requested and reached in each case examined). 5. Checked GPU runtime power management as a possible blocker: ``` cat /sys/bus/pci/devices/0000:04:00.0/power/runtime_status -> active cat /sys/bus/pci/devices/0000:04:00.0/power/control -> on ``` This reflects that amdgpu runtime autosuspend is disabled (consistent with kernel log message `amdgpu 0000:04:00.0: Runtime PM not available`), but this should not affect the forced power-down sequence during full system shutdown, so it is likely not the root cause (included here for completeness/future reference). 6. Reviewed `/var/log/apt/history.log*` and confirmed the kernel series transitioned 6.17.0-22 → 6.17.0-23 → 6.17.0-29 (Kubuntu 25.10) → 7.0.0-15 → 7.0.0-22 → 7.0.0-27 → 7.0.0-28 → 7.0.0-29 (Kubuntu 26.04), alongside routine `linux-firmware-amd-graphics` package bumps in the same window. ## Relevant Kernel Log Excerpts From `journalctl -k -b -1 | grep -iE "amd_pmc|amdgpu|pmc|acpi.*power"` (a normal boot after a failed shutdown, for reference — not the failure itself, since journald is terminated before the actual hang occurs during shutdown): ``` ACPI: \_SB_.PCI0.GP31: Overriding _PRW sleep state (S4) by S0 from power resources ACPI: \_SB_.PCI0.GP41: Overriding _PRW sleep state (S4) by S0 from power resources ACPI: \_SB_.PCI0.BUSC.NHI0: Overriding _PRW sleep state (S4) by S0 from power resources ACPI: \_SB_.PCI0.BUSC.NHI1: Overriding _PRW sleep state (S4) by S0 from power resources x86/amd: Previous system reset reason [0x00200800]: ACPI power state transition occurred amdgpu 0000:04:00.0: initializing kernel modesetting (YELLOW_CARP 0x1002:0x1681 0x103C:0x8C79 0x0D). amdgpu 0000:04:00.0: Runtime PM not available amdgpu 0000:04:00.0: [drm] *ERROR* lttpr_caps phy_repeater_cnt is 0x0, forcing it to 0x80. amdgpu 0000:04:00.0: [drm] *ERROR* LTTPR count is nonzero but invalid lane count reported. Assuming no LTTPR present. ``` Note: the `_PRW` overrides on the USB4/Thunderbolt controllers (GP31/GP41/NHI0/NHI1) stand out, as these are exactly the kind of power resources involved in a full S5/S4 ACPI transition, and USB4/Thunderbolt controllers are a documented source of similar shutdown/resume hangs on other Ryzen Rembrandt/Phoenix laptops. The `x86/amd: Previous system reset reason [0x00200800]: ACPI power state transition occurred` line confirms the EC did register an ACPI power transition attempt from the prior (failed) shutdown — i.e., the transition was initiated but did not fully complete in a way that cut power to the whole platform. ## Suspected Cause Given that: - BIOS/EC is already current, - the OS-level shutdown sequence completes without any logged error, - the failure occurs strictly after journald terminates (i.e., during the kernel's final ACPI S5/S4 handoff to firmware), - the regression coincides with the 25.10→26.04 (kernel 6.17→7.0) upgrade, the most likely root cause is a regression in kernel 7.0.x's handling of the ACPI power-off/reboot path for this specific AMD Rembrandt platform — possibly related to USB4/Thunderbolt (NHI0/NHI1) power resource handling, `amd_pmc`, or general ACPI S5 transition changes introduced between 6.17 and 7.0. This matches a broader, currently- being-worked-on class of issues where AMD's Linux team is actively patching S5 power-transition robustness on Ryzen platforms. ## Requested Investigation - Confirm whether other HP ProBook 445 G11 (or other Rembrandt/Phoenix AMD laptop) users on Kubuntu/Ubuntu 26.04 (kernel 7.0.x) see the same intermittent power-off/reboot hang that was not present on 25.10 (kernel 6.17.x). - Bisect kernel 7.0.x commits related to `amd_pmc`, ACPI S5/S4 transition, and USB4/Thunderbolt (`thunderbolt`/`nhi`) power management between the 6.17 and 7.0 kernel branches. - If a specific commit is identified, consider backporting a fix or reverting the offending change for the 26.04 LTS kernel. ## Attachments to Include When Filing - Output of `ubuntu-bug linux` (auto-collects `lspci`, `dmesg`, `/proc/version_signature`, apport hardware info, etc.) - `journalctl -b -3 -e --no-pager` (clean shutdown, for baseline comparison) - `journalctl -k -b -1 | grep -iE "amd_pmc|amdgpu|pmc|acpi.*power"` (post-hang boot kernel log) - `sudo dmidecode -t bios` (confirms BIOS version 01.08.03 Rev.A) - `cat /proc/cmdline` 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 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: steffen 2580 F.... wireplumber /dev/snd/controlC0: steffen 2580 F.... wireplumber /dev/snd/seq: steffen 2535 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Aug 7 09:19:33 2026 InstallationDate: Installed on 2025-11-03 (277 days ago) InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) MachineType: HP HP ProBook 445 14 inch G11 Notebook PC ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=UUID=0277168a-b564-41b9-a91d-79407262c34a ro rd.luks.uuid=9d5c36a9-3dc3-4fdf-a1f9-b3f2aa284b34 acpi_osi=Linux 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-05-17 (82 days ago) dmi.bios.date: 05/19/2026 dmi.bios.release: 8.3 dmi.bios.vendor: HP dmi.bios.version: W78 Ver. 01.08.03 dmi.board.name: 8C79 dmi.board.vendor: HP dmi.board.version: KBC Version 06.33.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 6.51 dmi.modalias: dmi:bvnHP:bvrW78Ver.01.08.03:bd05/19/2026:br8.3:efr6.51:svnHP:pnHPProBook44514inchG11NotebookPC:pvrSBKPFV3:rvnHP:rn8C79:rvrKBCVersion06.33.00:cvnHP:ct10:cvr:sku9Y7J4ET#ABD:pfa103C_5336ANHPProBook: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 445 14 inch G11 Notebook PC dmi.product.sku: 9Y7J4ET#ABD dmi.product.version: SBKPFV3 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163015/+subscriptions
[Bug 2150732] Re: Screen stays black after resuming from sleep
** Attachment added: "Slightly redacted output from journalctl -b -1 -p warning..alert" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150732/+attachment/5990831/+files/1558_filtered_w_crash.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150732 Title: Screen stays black after resuming from sleep Status in linux package in Ubuntu: Confirmed Status in linux-hwe-7.0 package in Ubuntu: Confirmed Bug description: After a "long" sleep (let's say more than 10 mins, but this is not clearly defined yet) when waking up, the screen stays black. I can confirm the system is responsive, the fingerprint sensor activates, it connects to the WiFi properly, it's really just the graphics part. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic 7.0.0-14.14 ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: a.dubois 5856 F.... pipewire a.dubois 5867 F.... wireplumber /dev/snd/seq: a.dubois 5856 F.... pipewire CasperMD5CheckMismatches: ./boot/grub/i386-pc/eltorito.img CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 12:07:57 2026 InstallationDate: Installed on 2026-02-27 (62 days ago) InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) MachineType: LENOVO 21KWS15400 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-14-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: Upgraded to resolute on 2026-04-24 (6 days ago) dmi.bios.date: 03/02/2026 dmi.bios.release: 1.20 dmi.bios.vendor: LENOVO dmi.bios.version: N48ET33W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 21KWS15400 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrN48ET33W(1.20):bd03/02/2026:br1.20:efr1.15:svnLENOVO:pn21KWS15400:pvrThinkPadP1Gen7:rvnLENOVO:rn21KWS15400:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21KW_BU_Think_FM_ThinkPadP1Gen7:pfaThinkPadP1Gen7: dmi.product.family: ThinkPad P1 Gen 7 dmi.product.name: 21KWS15400 dmi.product.sku: LENOVO_MT_21KW_BU_Think_FM_ThinkPad P1 Gen 7 dmi.product.version: ThinkPad P1 Gen 7 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150732/+subscriptions
[Bug 2150732] Re: Screen stays black after resuming from sleep
I just recently upgraded my laptop from 24.04 to 26.04. I believe I have the same underlying i915/Intel Meteor Lake resume bug, but in my case it manifests as a complete machine/display hang when logging out after a suspend/resume cycle. Hardware: * Lenovo ThinkPad P1 Gen 7 * DMI: LENOVO 21KVCTO1WW * BIOS: N48ET33W (1.20), 2026-03-02 * Intel Meteor Lake integrated graphics, i915 * External monitor connected via Thunderbolt 4 (the monitor also provides the external keyboard connection) * Ubuntu 26.04 LTS * Kernel: 7.0.0-29-generic The failure is highly reproducible: 1. Log in normally. 2. Without suspending, log out: logout works correctly. 3. Suspend the machine. 4. Resume it; the desktop appears to work normally. 5. Log out. 6. GNOME Shell hangs during logout and the machine eventually becomes effectively unusable. Ctrl+Alt+Del can sometimes still trigger a clean reboot/shutdown, otherwise a hard power-off is required. The important part of the journal from the failing logout is: ``` i915 0000:00:02.0: [drm] *ERROR* Failed to bring PHY A to idle. i915 0000:00:02.0: [drm] *ERROR* PHY A Read 0c70 failed after 3 retries. i915 0000:00:02.0: [drm] *ERROR* PHY A Write 0c70 failed after 3 retries. i915 0000:00:02.0: [drm] *ERROR* Timeout waiting for DDI BUF A to get active i915 0000:00:02.0: [drm] *ERROR* Timed out waiting for DP idle patterns ``` followed by: ``` org.gnome.Shell@ubuntu.service: State 'stop-sigterm' timed out. Killing. ``` and subsequently: ``` i915 ... [drm] *ERROR* flip_done timed out i915 ... [drm] *ERROR* [CRTC:150:pipe A] mismatch in pixel_rate i915 ... [drm] *ERROR* [CRTC:150:pipe A] mismatch in dpll_hw_state i915 ... [drm] *ERROR* pipe state doesn't match! i915 ... [drm] *ERROR* DPLL 0: pll hw state mismatch i915 ... [drm] *ERROR* flip_done timed out i915 ... [drm] *ERROR* [CRTC:150:pipe A] commit wait timed out i915 ... [drm] *ERROR* [CONNECTOR:507:eDP-1] commit wait timed out i915 ... [drm] *ERROR* [PLANE:34:plane 1A] commit wait timed out i915 ... [drm] *ERROR* vblank wait timed out on crtc 0 i915 ... [drm] *ERROR* PHY A failed to change powerdown state ``` The kernel warning occurs in i915 display modesetting code, with the relevant call trace including: ``` intel_modeset_verify_crtc intel_atomic_commit_tail drm_atomic_commit drm_client_modeset_commit drm_fbdev_client_restore ``` There is an extremely close Fedora report: RHBZ #2463170, "Kernel 7.0.x: i915 driver causes lock screen freeze and complete display deadlock with Meteor Lake + docking station on Wayland": https://bugzilla.redhat.com/show_bug.cgi?id=2463170 That report identifies three i915 patches which make the problem disappear in Fedora: * drm/i915/dp_tunnel: Don't update tunnel state during system resume * drm/i915/cx0: Clear response ready & error bit * drm/i915/pps: Enable panel power earlier The first is particularly relevant to my configuration because the external display is connected through a Thunderbolt/DisplayPort tunnel. The Fedora report states that kernels containing these fixes are working, whereas the corresponding unpatched kernel reproduces the failure. Could the Ubuntu kernel team kindly investigate whether these three i915 fixes can be backported to the 26.04 kernel? I would also be interested to know whether there is an Ubuntu kernel build containing these patches that I could test. I use ZFS, so changing kernel stacks is considerably more complicated for me than for a vanilla deployment, making a targeted Ubuntu kernel build preferable to a generic kernel downgrade. I am attaching the complete journal from a failed logout. Happy to provide any additional diagnostic information required. (credit where credit is due: ChatGPT helped me debug this issue and write this report!) -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150732 Title: Screen stays black after resuming from sleep Status in linux package in Ubuntu: Confirmed Status in linux-hwe-7.0 package in Ubuntu: Confirmed Bug description: After a "long" sleep (let's say more than 10 mins, but this is not clearly defined yet) when waking up, the screen stays black. I can confirm the system is responsive, the fingerprint sensor activates, it connects to the WiFi properly, it's really just the graphics part. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic 7.0.0-14.14 ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: a.dubois 5856 F.... pipewire a.dubois 5867 F.... wireplumber /dev/snd/seq: a.dubois 5856 F.... pipewire CasperMD5CheckMismatches: ./boot/grub/i386-pc/eltorito.img CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 12:07:57 2026 InstallationDate: Installed on 2026-02-27 (62 days ago) InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) MachineType: LENOVO 21KWS15400 ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-14-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: Upgraded to resolute on 2026-04-24 (6 days ago) dmi.bios.date: 03/02/2026 dmi.bios.release: 1.20 dmi.bios.vendor: LENOVO dmi.bios.version: N48ET33W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 21KWS15400 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76530 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.15 dmi.modalias: dmi:bvnLENOVO:bvrN48ET33W(1.20):bd03/02/2026:br1.20:efr1.15:svnLENOVO:pn21KWS15400:pvrThinkPadP1Gen7:rvnLENOVO:rn21KWS15400:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21KW_BU_Think_FM_ThinkPadP1Gen7:pfaThinkPadP1Gen7: dmi.product.family: ThinkPad P1 Gen 7 dmi.product.name: 21KWS15400 dmi.product.sku: LENOVO_MT_21KW_BU_Think_FM_ThinkPad P1 Gen 7 dmi.product.version: ThinkPad P1 Gen 7 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150732/+subscriptions
[Bug 2163062] Re: idxd: crash-kernel NULL-pointer Oops in `destroy_workqueue()` breaks kdump on Intel DSA/IAA systems
Patch submitted to KTML: [SRU][R][PATCH 0/2] dmaengine: idxd: fix kdump crash kernel NULL deref / double-free in idxd release path -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163062 Title: idxd: crash-kernel NULL-pointer Oops in `destroy_workqueue()` breaks kdump on Intel DSA/IAA systems Status in linux package in Ubuntu: New Status in linux source package in Resolute: New Bug description: [Impact] On systems with Intel DSA/IAA accelerators (the `idxd` driver), the **kdump crash kernel Oopses with a NULL-pointer dereference in `destroy_workqueue()`**. In the crash kernel the DSA/IAA devices are HALTED (inherited from the panicked kernel), so idxd probe fails at device reset before its workqueue is allocated, and `idxd_conf_device_release()` then calls `destroy_workqueue(NULL)`. The Oops — in a udev worker that exits with IRQs disabled, on the `nr_cpus=1` crash kernel — wedges the crash kernel: it can no longer finish the vmcore or reboot, so the host hangs and needs a manual BMC power reset. **Net effect: kdump/vmcore capture is broken on idxd-equipped hardware.** Regressing commit (mainline): `3d33de353b1f ("dmaengine: idxd: Fix not releasing workqueue on .release()")`, which added an unconditional `destroy_workqueue(idxd->wq)` to `idxd_conf_device_release()`. Backtrace (full: `idxd-oops.txt`): idxd 0000:6a:02.0: Intel(R) IDXD DMA Engine init failed BUG: kernel NULL pointer dereference, address: 00000000000000b8 Oops: 0000 [#1] SMP NOPTI CPU: 0 ... Comm: (udev-worker) ... 7.0.0-1010-nvidia Hardware name: NVIDIA DGXH200/DGXH200, BIOS 1.7.8 12/05/2025 RIP: 0010:destroy_workqueue+0x17/0x390 RDI: 0000000000000000 CR2: 00000000000000b8 Call Trace: idxd_conf_device_release+0x19/0xa0 [idxd] put_device+0x13/0x30 idxd_pci_probe_alloc+0x285/0x460 [idxd] idxd_pci_probe+0x16/0x30 [idxd] ... idxd_init_module+0xd3/0xff0 [idxd] note: (udev-worker)[1002] exited with irqs disabled `RDI=0` / `CR2=0xb8` confirm `destroy_workqueue(NULL)`. Reproducer: On a system with `idxd` (Intel DSA/IAA) devices and kdump enabled: echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger Without the fix: crash kernel Oopses in `destroy_workqueue()`, hangs, no reboot (BMC reset required). With the fix: no Oops, full vmcore saved, host reboots. Affected kernels: Any Ubuntu 7.0 `-generic` / `-nvidia` kernel carrying `3d33de353b1f` (observed on `linux-nvidia` 7.0, resolute/26.04; `-generic` has the same idxd code). [Fix] Two patches from Steve Wahl (HPE), on `dmaengine@vger.kernel.org`, **Acked-by: Vinicius Costa Gomes** (author of the regression). **Not yet in mainline/linux-next as of July 2026.** 1. **dmaengine: idxd: Do not call destroy_workqueue with null idxd->wq** — `Fixes: 3d33de353b1f` — https://lore.kernel.org/all/20260522203414.336549-1-steve.wahl@hpe.com/ (adds `if (idxd->wq) destroy_workqueue(idxd->wq);`) 2. **dmaengine: idxd: fix duplicate memory frees on initialization error path** — patch 2/2 of the same series (removes a latent double-free on the `idxd_alloc()`/`idxd_free()` error unwind). [Test Plan] Compile and boot tested. [Where problems could occur] Low, confined to idxd probe/error paths: patch 1 only NULL-checks before `destroy_workqueue()` (no change when the workqueue exists); patch 2 removes double frees already handled by the release callback. No effect on the normal (non-error) path. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163062/+subscriptions
[Bug 2163015] Re: System fails to power off / hangs on shutdown-reboot after upgrade to Kubuntu 26.04 (kernel 7.0)
Same problem here on my system: ## System Configuration | Component | Details | |---|---| | **CPU** | AMD Ryzen 9 9950X3D (16 cores, 32 threads) | | **Mainboard** | ASUS ProArt X870E-CREATOR WIFI (AMD X870E chipset) | | **RAM** | 64 GB DDR5-6000 | | **GPU** | ASUS Radeon RX 6600 Dual (AMD RDNA 2, open-source Mesa/amdgpu driver) | | **Storage** | WD Black SN850X 2 TB NVMe (system), WD Black SN850X 4 TB NVMe (data) | | **OS** | Ubuntu 26.04 LTS "Resolute Raccoon" | | **Affected kernel** | 7.0.0-29-generic | ## Problem Description After upgrading to kernel **7.0.0-29-generic**, both `shutdown` and `reboot` hang after the systemd shutdown sequence completes successfully. The monitors turn off, but the system remains powered on indefinitely and must be hard-powered off. ## Symptoms - `sudo systemctl poweroff` → systemd shutdown completes, monitors turn off, machine stays on - `sudo systemctl reboot` → same behaviour, machine does not reboot - `sudo systemctl poweroff --force` → same behaviour - Hard power-off and restart required in all cases ## Kernel Parameters Tested (No Effect) The following kernel parameters were added to `GRUB_CMDLINE_LINUX_DEFAULT` individually and in combination — none resolved the issue: - `acpi=force` - `reboot=acpi` - `noapic` ## Shutdown Log (last entries before hang) The systemd shutdown sequence completes without errors. The last recorded log entries are: ``` systemd[1]: Reached target poweroff.target - System Power Off. systemd[1]: Shutting down. systemd-shutdown[1]: Syncing filesystems and block devices. systemd-shutdown[1]: Sending SIGTERM to remaining processes... systemd-journald[1391]: Received SIGTERM from PID 1 (systemd-shutdow). systemd-udevd[1440]: Failed to remove file descriptor "config-serialization" from the store, ignoring: Connection refused dnsmasq[5318]: exiting on receipt of SIGTERM systemd-journald[1391]: Journal stopped ``` After `Journal stopped`, the system hangs indefinitely. ## ACPI Wakeup Sources All wakeup sources are enabled on S4 (excerpt): ``` GPP3 S4 *enabled pci:0000:00:01.4 GP17 S4 *enabled pci:0000:00:08.1 XHC0 S4 *enabled pci:0000:7c:00.3 XHC1 S4 *enabled pci:0000:7c:00.4 XHC2 S4 *enabled pci:0000:7d:00.0 GPP0 S4 *enabled pci:0000:00:01.1 SWUS S4 *enabled pci:0000:01:00.0 SWDS S4 *enabled pci:0000:02:00.0 ... ``` ## Network - Wake-on-LAN was enabled (`Wake-on: g`) on `enp13s0` — disabled as part of troubleshooting, no effect on the issue ## Workaround (not fully 100% safe) Boot permanently with kernel 7.0.0-28-generic by setting in `/etc/default/grub`: ``` GRUB_DEFAULT="Advanced options for Ubuntu>Ubuntu, with Linux 7.0.0-28-generic" ``` Then run `sudo update-grub`. Sometimes it works, sometimes not. :-( -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163015 Title: System fails to power off / hangs on shutdown-reboot after upgrade to Kubuntu 26.04 (kernel 7.0) Status in linux package in Ubuntu: New Bug description: ## Summary On an HP ProBook 445 14" G11 (AMD Ryzen, Rembrandt/YELLOW_CARP APU, model 0x1002:0x1681), the system intermittently fails to fully power off or reboot after upgrading from Kubuntu 25.10 (kernel 6.17.x) to Kubuntu 26.04 LTS (kernel 7.0.x). The OS-level shutdown/reboot sequence completes cleanly according to systemd/journald logs, but the hardware does not fully cut power afterward (fan keeps running, power LED stays lit, screen goes black but the machine never truly turns off or restarts). This did not occur before the 25.10 → 26.04 upgrade. BIOS/EC firmware is already at the latest available version, ruling out a firmware fix as the immediate solution. ## Environment - **Hardware**: HP ProBook 445 14 inch G11 Notebook PC - **CPU/APU**: AMD Ryzen (Rembrandt, codename YELLOW_CARP, PCI ID 1002:1681, subsystem 103C:8C79) - **BIOS/EC**: 01.08.03 Rev.A (confirmed latest available via HP support site) - **OS**: Kubuntu 26.04 LTS "Resolute Raccoon" (upgraded from Kubuntu 25.10 "Questing Quokka") - **Kernel**: 7.0.0-29-generic (also reproduced on 7.0.0-28-generic; 7.0.0-22-generic available for further testing) - **Desktop**: KDE Plasma, Wayland session (SDDM) - **Secure Boot**: Enabled - **Disk encryption**: LUKS (root on NVMe, cryptsetup) ## Regression Context - Kubuntu 25.10 shipped with kernel 6.17.x and shutdown/reboot worked reliably. - Kubuntu 26.04 LTS ships with kernel 7.0.x (upstream renumbering from 6.x, not a from-scratch rewrite, but a full kernel major bump with all associated driver updates). - The 6.17.x kernel packages are no longer installed on this system, so a direct old-kernel bisect is not currently possible; only kernel points within the 7.0.x series (7.0.0-22, -28, -29) remain available. - The issue is **intermittent**, not deterministic: some shutdowns/reboots complete correctly (confirmed via journal: `systemd-poweroff.service` finishes and `poweroff.target` is reached cleanly), while others leave the hardware in a half-powered state. - The issue has also been observed on a plain `reboot` (not just `poweroff`), ruling out an S5-specific ACPI quirk. ## Steps Already Taken (no effect) 1. Verified BIOS/EC firmware is already the latest version (01.08.03 Rev.A) via `fwupdmgr` and HP's support site — no update available. 2. Added `acpi_osi=Linux` to `GRUB_CMDLINE_LINUX_DEFAULT` and ran `update-grub` — the very next reboot after applying this still hung, so this had no beneficial effect (parameter has since been reverted). 3. Confirmed via `journalctl -b -3 -e` that a "good" shutdown completes normally end-to-end at the systemd/journald level: ``` systemd-logind[1744]: The system will power off now! systemd-logind[1744]: System is powering down. ... systemd[1]: Finished systemd-poweroff.service - System Power Off. systemd[1]: Reached target poweroff.target - System Power Off. ``` No errors, no hung units, no failed unmounts in this particular boot's shutdown sequence. 4. Ruled out a misconfigured shutdown-vs-reboot action (checked `systemd-logind` logs directly; confirmed the correct target — `poweroff.target` or `reboot.target` — was requested and reached in each case examined). 5. Checked GPU runtime power management as a possible blocker: ``` cat /sys/bus/pci/devices/0000:04:00.0/power/runtime_status -> active cat /sys/bus/pci/devices/0000:04:00.0/power/control -> on ``` This reflects that amdgpu runtime autosuspend is disabled (consistent with kernel log message `amdgpu 0000:04:00.0: Runtime PM not available`), but this should not affect the forced power-down sequence during full system shutdown, so it is likely not the root cause (included here for completeness/future reference). 6. Reviewed `/var/log/apt/history.log*` and confirmed the kernel series transitioned 6.17.0-22 → 6.17.0-23 → 6.17.0-29 (Kubuntu 25.10) → 7.0.0-15 → 7.0.0-22 → 7.0.0-27 → 7.0.0-28 → 7.0.0-29 (Kubuntu 26.04), alongside routine `linux-firmware-amd-graphics` package bumps in the same window. ## Relevant Kernel Log Excerpts From `journalctl -k -b -1 | grep -iE "amd_pmc|amdgpu|pmc|acpi.*power"` (a normal boot after a failed shutdown, for reference — not the failure itself, since journald is terminated before the actual hang occurs during shutdown): ``` ACPI: \_SB_.PCI0.GP31: Overriding _PRW sleep state (S4) by S0 from power resources ACPI: \_SB_.PCI0.GP41: Overriding _PRW sleep state (S4) by S0 from power resources ACPI: \_SB_.PCI0.BUSC.NHI0: Overriding _PRW sleep state (S4) by S0 from power resources ACPI: \_SB_.PCI0.BUSC.NHI1: Overriding _PRW sleep state (S4) by S0 from power resources x86/amd: Previous system reset reason [0x00200800]: ACPI power state transition occurred amdgpu 0000:04:00.0: initializing kernel modesetting (YELLOW_CARP 0x1002:0x1681 0x103C:0x8C79 0x0D). amdgpu 0000:04:00.0: Runtime PM not available amdgpu 0000:04:00.0: [drm] *ERROR* lttpr_caps phy_repeater_cnt is 0x0, forcing it to 0x80. amdgpu 0000:04:00.0: [drm] *ERROR* LTTPR count is nonzero but invalid lane count reported. Assuming no LTTPR present. ``` Note: the `_PRW` overrides on the USB4/Thunderbolt controllers (GP31/GP41/NHI0/NHI1) stand out, as these are exactly the kind of power resources involved in a full S5/S4 ACPI transition, and USB4/Thunderbolt controllers are a documented source of similar shutdown/resume hangs on other Ryzen Rembrandt/Phoenix laptops. The `x86/amd: Previous system reset reason [0x00200800]: ACPI power state transition occurred` line confirms the EC did register an ACPI power transition attempt from the prior (failed) shutdown — i.e., the transition was initiated but did not fully complete in a way that cut power to the whole platform. ## Suspected Cause Given that: - BIOS/EC is already current, - the OS-level shutdown sequence completes without any logged error, - the failure occurs strictly after journald terminates (i.e., during the kernel's final ACPI S5/S4 handoff to firmware), - the regression coincides with the 25.10→26.04 (kernel 6.17→7.0) upgrade, the most likely root cause is a regression in kernel 7.0.x's handling of the ACPI power-off/reboot path for this specific AMD Rembrandt platform — possibly related to USB4/Thunderbolt (NHI0/NHI1) power resource handling, `amd_pmc`, or general ACPI S5 transition changes introduced between 6.17 and 7.0. This matches a broader, currently- being-worked-on class of issues where AMD's Linux team is actively patching S5 power-transition robustness on Ryzen platforms. ## Requested Investigation - Confirm whether other HP ProBook 445 G11 (or other Rembrandt/Phoenix AMD laptop) users on Kubuntu/Ubuntu 26.04 (kernel 7.0.x) see the same intermittent power-off/reboot hang that was not present on 25.10 (kernel 6.17.x). - Bisect kernel 7.0.x commits related to `amd_pmc`, ACPI S5/S4 transition, and USB4/Thunderbolt (`thunderbolt`/`nhi`) power management between the 6.17 and 7.0 kernel branches. - If a specific commit is identified, consider backporting a fix or reverting the offending change for the 26.04 LTS kernel. ## Attachments to Include When Filing - Output of `ubuntu-bug linux` (auto-collects `lspci`, `dmesg`, `/proc/version_signature`, apport hardware info, etc.) - `journalctl -b -3 -e --no-pager` (clean shutdown, for baseline comparison) - `journalctl -k -b -1 | grep -iE "amd_pmc|amdgpu|pmc|acpi.*power"` (post-hang boot kernel log) - `sudo dmidecode -t bios` (confirms BIOS version 01.08.03 Rev.A) - `cat /proc/cmdline` 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 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: steffen 2580 F.... wireplumber /dev/snd/controlC0: steffen 2580 F.... wireplumber /dev/snd/seq: steffen 2535 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Aug 7 09:19:33 2026 InstallationDate: Installed on 2025-11-03 (277 days ago) InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) MachineType: HP HP ProBook 445 14 inch G11 Notebook PC ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-29-generic root=UUID=0277168a-b564-41b9-a91d-79407262c34a ro rd.luks.uuid=9d5c36a9-3dc3-4fdf-a1f9-b3f2aa284b34 acpi_osi=Linux 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-05-17 (82 days ago) dmi.bios.date: 05/19/2026 dmi.bios.release: 8.3 dmi.bios.vendor: HP dmi.bios.version: W78 Ver. 01.08.03 dmi.board.name: 8C79 dmi.board.vendor: HP dmi.board.version: KBC Version 06.33.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 6.51 dmi.modalias: dmi:bvnHP:bvrW78Ver.01.08.03:bd05/19/2026:br8.3:efr6.51:svnHP:pnHPProBook44514inchG11NotebookPC:pvrSBKPFV3:rvnHP:rn8C79:rvrKBCVersion06.33.00:cvnHP:ct10:cvr:sku9Y7J4ET#ABD:pfa103C_5336ANHPProBook: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 445 14 inch G11 Notebook PC dmi.product.sku: 9Y7J4ET#ABD dmi.product.version: SBKPFV3 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163015/+subscriptions
суббота
[Bug 2163075] Re: Max screen brightness is capped at 50% during boot/KMS load despite slider being at 100% (After updates on Ubuntu 24 & 26)
** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163075 Title: Max screen brightness is capped at 50% during boot/KMS load despite slider being at 100% (After updates on Ubuntu 24 & 26) Status in linux package in Ubuntu: New Bug description: Hello Ubuntu Team, I am reporting a specific screen brightness issue that triggers only after system updates (It happened previously on Ubuntu 24, and now again after a recent update on Ubuntu 26). Crucial Symptoms: Slider works but brightness is capped: The brightness UI slider still works and can be adjusted. However, when the slider is at 100% (maximum), the actual physical brightness of the screen is only about 50% of what it normally was before the update. Trigger point during boot: When I power on the laptop, the BIOS/POST screen is at full, normal brightness. But the exact moment the Ubuntu loading screen appears (when the kernel/graphics driver loads), the screen dims significantly, even though the OS slider is set to max. Failed Workarounds: I have already exhaustively tested all common GRUB parameters (acpi_backlight=vendor, native, video, none) back when I was on Ubuntu 24, and absolutely none of them resolved the issue. This strongly suggests an issue with Kernel Mode Setting (KMS) or the display driver improperly limiting the maximum backlight value after recent updates. Apport hardware and system logs are attached automatically (ubuntu-bug linux). Please let me know what specific command outputs you need to trace this regression. Thank you. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-28-generic (not installed) ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: ahmed-elsherbiny 5083 F.... pipewire ahmed-elsherbiny 5102 F.... wireplumber /dev/snd/pcmC0D0p: ahmed-elsherbiny 5083 F...m pipewire /dev/snd/seq: ahmed-elsherbiny 5083 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 05:16:05 2026 MachineType: Dell Inc. Latitude 7430 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: snapd_recovery_mode=run console=ttyS0,115200n8 console=tty1 panic=-1 quiet splash snapd.xkb="us,pc105,,grp_led:scroll" SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2026 dmi.bios.release: 1.41 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.41.0 dmi.board.name: 00N39X dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnDellInc.:bvr1.41.0:bd05/26/2026:br1.41:efr1.21:svnDellInc.:pnLatitude7430:pvr:rvnDellInc.:rn00N39X:rvrA01:cvnDellInc.:ct10:cvr:sku0B0B:pfaLatitude: dmi.product.family: Latitude dmi.product.name: Latitude 7430 dmi.product.sku: 0B0B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163075/+subscriptions
[Bug 2163094] Re: ASUS Vivobook S16 M3607GA: internal audio missing with AMD ACP7.x / RT721 SoundWire
** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163094 Title: ASUS Vivobook S16 M3607GA: internal audio missing with AMD ACP7.x / RT721 SoundWire Status in linux package in Ubuntu: New Bug description: Kubuntu 26.04 LTS on ASUS Vivobook S16 M3607GA has no internal speakers or microphone. Only Radeon HDMI audio outputs are available. Kernel: 7.0.0-29-generic ALSA aplay -l only shows the Radeon HDMI devices. No internal ALSA sound card is created. The AMD Audio Coprocessor is detected: 03:00.5 Multimedia controller: AMD Audio Coprocessor [1022:15e2] Kernel driver in use: snd_pci_ps The Realtek RT721 SoundWire device is successfully enumerated: sdw:0:1:025d:0721:01 The relevant modules including soundwire_amd, snd_pci_ps and snd_soc_rt721_sdca are loaded, but the internal sound card is not created. There appears to be an upstream kernel fix for this exact standalone RT721 topology: ASoC: amd: acp70: add standalone RT721 SoundWire machine Upstream commit: d2dcd85f9e09 Could this fix please be considered for backporting to the Ubuntu 26.04 (Resolute) 7.0 kernel? Expected result: an amd-soundwire ALSA card providing the internal speakers/microphone. Actual result: only Radeon HDMI audio devices are available. 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 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: rosta 1771 F.... wireplumber /dev/snd/seq: rosta 1767 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Aug 8 20:30:58 2026 InstallationDate: Installed on 2026-08-08 (0 days ago) InstallationMedia: Kubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423) MachineType: ASUS Vivobook S16 M3607GA ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=3fbd7ae3-9f83-45f4-9e79-8b0f9350bd78 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2025 dmi.bios.release: 5.35 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: M3607GA.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M3607GA 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.3 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrM3607GA.302:bd12/12/2025:br5.35:efr3.3:svnASUS:pnVivobookS16M3607GA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM3607GA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaVivobookS16: dmi.product.family: Vivobook S16 dmi.product.name: Vivobook S16 M3607GA dmi.product.version: 1.0 dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163094/+subscriptions
[Bug 2163095] Re: New kernel breaks usb wifi adapters
It would help to upload logs from the boot of 7.0.0-29 and include results from terminal for dkms status -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2163095 Title: New kernel breaks usb wifi adapters Status in linux package in Ubuntu: New Bug description: I have a laptop with a defective wifi adapter that runs with iwlwifi and I was able to use a usb adapter with kernel 7.0.0-28-generic. When 26.04 updated to 7.0.0-29-generic, my brostrend adapter no longer worked and a panda pau0b adapter could not load its driver either. Reverting to 7.0.0-28-generic allows me to use the usb adapter. Something in 7.0.0-29-generic is preventing these drivers from being loaded. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: chris 3709 F.... pipewire chris 3716 F.... wireplumber /dev/snd/seq: chris 3709 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Aug 8 14:49:04 2026 InstallationDate: Installed on 2024-04-21 (840 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2) MachineType: Default string Default string 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=/boot/vmlinuz-7.0.0-28-generic root=UUID=ee005047-cb0a-447e-841b-b02ec9a2ca60 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-07-07 (33 days ago) dmi.bios.date: 11/01/2023 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GM118C_V33.1180.01 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 140.15 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGM118C_V33.1180.01:bd11/01/2023:br5.13:efr140.15:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuDefaultstring:pfaDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163095/+subscriptions
[Bug 2132118] Re: regression - Audio not available on Acer Aspire 4820TG after update to 24.04 (was working on 22.04)
The patch proposed for the bug on bugzilla.kernel.org ^^^ Also, there is a workaround: echo 1 | sudo tee /sys/bus/pci/devices/0000:00:1b.0/remove echo 1 | sudo tee /sys/bus/pci/rescan No reboot required -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2132118 Title: regression - Audio not available on Acer Aspire 4820TG after update to 24.04 (was working on 22.04) Status in linux package in Ubuntu: New Bug description: After updating to 24.04, the audio is not working anymore In the setting, only a "dummy output" is available cat /proc/version_signature Ubuntu 6.8.0-87.88-generic 6.8.12 sudo dmesg | grep audio [ 7.319883] usbcore: registered new interface driver snd-usb-audio [ 12.122298] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 12.124478] snd_hda_intel 0000:01:00.1: Handle vga_switcheroo audio client [ 12.164371] snd_hda_intel 0000:01:00.1: bound 0000:01:00.0 (ops radeon_audio_component_bind_ops [radeon]) [ 12.228368] hdaudio hdaudioC0D0: no AFG or MFG node found [ 12.228388] hdaudio hdaudioC0D1: no AFG or MFG node found [ 12.228402] hdaudio hdaudioC0D2: no AFG or MFG node found [ 12.228416] hdaudio hdaudioC0D3: no AFG or MFG node found lspci | grep Audio 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) 01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2132118/+subscriptions