sorry here is the log. ** Attachment added: "ath9k_htc_crash.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2175503/+attachment/6020049/+files/ath9k_htc_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/2175503 Title: [Regression] Kernel panic/crash on USB hotplug with Netgear WNA1100 (ath9k_htc, 0846:9030) in 7.0.0-43-generic Status in linux package in Ubuntu: New Bug description: After upgrading from linux-image-7.0.0-42-generic to 7.0.0-43-generic (on Zorin OS, using the Ubuntu 24.04 HWE kernel), my Netgear WNA1100 Wireless-N 150 USB Wi-Fi adapter (ID 0846:9030, Atheros AR9271 / ath9k_htc driver) stops working and causes a kernel panic when replugged. Steps to Reproduce: 1. Boot with adapter plugged in: The system boots and ath9k_htc initializes the interface, but there is no internet connectivity. 2. Unplug and replug the adapter: Unplugging the USB dongle and plugging it back in immediately triggers a hard kernel panic / system freeze (before journald can flush a stack trace to disk). System & Hardware Details: • Last working kernel: 7.0.0-42-generic (#42~24.04.1-Ubuntu) • Broken kernel: 7.0.0-43-generic (#43~24.04.1-Ubuntu) • Hardware: Bus 002 Device 004: ID 0846:9030 NetGear, Inc. WNA1100 Wireless-N 150 [Atheros AR9271] • Driver & Firmware: ath9k_htc (ath9k_htc/htc_9271-1.4.0.fw) • Kernel Parameters: usbcore.autosuspend=-1 is already enabled. Booting back into 7.0.0-42-generic completely resolves both the lack of internet connectivity and the hot-replug kernel panic. Attached is ath9k_htc_crash.txt containing uname -a, lsusb, working initialization logs from 7.0.0-42-generic, and the frozen 7.0.0-43-generic kernel log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2175503/+subscriptions
[РЕШЕНО] Ошибка № ...
Ошибки в Программах и Способы их Исправления
суббота
[Bug 2175496] [NEW] Realtek RTL8125BG Ethernet unavailable on Ubuntu 7.0.0-44.44, works on 7.0.0-43.43
Public bug reported: On Ubuntu 26.04.1 LTS (amd64), the onboard Realtek RTL8125BG Ethernet controller (10ec:8125) on an ASRock B850M Pro RS WiFi White was unavailable after booting 7.0.0-44-generic (7.0.0-44.44). When the PCIe device later appeared, the kernel reported can't assign; no space for the upstream bridge window and the controller's BARs. The r8125 driver then reported region #1 not an MMIO resource, aborting. Booting 7.0.0-43-generic (7.0.0-43.43) restored enp6s0 and a working 2.5 Gbps link. Both kernels have r8125-dkms version 9.016.01-1 installed. Please investigate the PCIe enumeration and resource allocation differences between these builds. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2175496 Title: Realtek RTL8125BG Ethernet unavailable on Ubuntu 7.0.0-44.44, works on 7.0.0-43.43 Status in linux package in Ubuntu: New Bug description: On Ubuntu 26.04.1 LTS (amd64), the onboard Realtek RTL8125BG Ethernet controller (10ec:8125) on an ASRock B850M Pro RS WiFi White was unavailable after booting 7.0.0-44-generic (7.0.0-44.44). When the PCIe device later appeared, the kernel reported can't assign; no space for the upstream bridge window and the controller's BARs. The r8125 driver then reported region #1 not an MMIO resource, aborting. Booting 7.0.0-43-generic (7.0.0-43.43) restored enp6s0 and a working 2.5 Gbps link. Both kernels have r8125-dkms version 9.016.01-1 installed. Please investigate the PCIe enumeration and resource allocation differences between these builds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2175496/+subscriptions
[Bug 2175475] Re: Possible performance regression in Ubuntu kernel 7.0.0-43 compared with 7.0.0-42 on ASUS VivoBook X1704ZA
** 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/2175475 Title: Possible performance regression in Ubuntu kernel 7.0.0-43 compared with 7.0.0-42 on ASUS VivoBook X1704ZA Status in linux package in Ubuntu: New Bug description: Description: I am reporting a suspected kernel performance regression affecting my ASUS VivoBook X1704ZA/F1704ZA running Linux Mint 22.3 (Ubuntu 24.04 base), with KDE Plasma 5 on X11. Observed behavior with kernel 7.0.0-43-generic: The desktop developed intermittent freezes and noticeable delays during normal use. Even opening Konsole sometimes took several seconds. The system had ample available RAM and low CPU pressure. No failed systemd services or obvious NVMe I/O errors were found. I/O pressure was observed, including approximately 6.49% full I/O pressure averaged over five minutes. One boot took approximately 59.7 seconds, including 44.6 seconds attributed to firmware initialization. ACPI firmware errors involving missing thermal sensor symbols (AE_NOT_FOUND) were logged. Comparison with kernel 7.0.0-42-generic: I temporarily booted the same installation using kernel 7.0.0-42-generic without changing my installed applications or removing the newer kernel. The system appeared noticeably more responsive, and the intermittent freezes have not recurred during the initial observation period. A secondary-monitor wallpaper issue occurred after booting, but restarting KDE Plasma restored the wallpaper. Hardware: Laptop: ASUS VivoBook X1704ZA/F1704ZA BIOS: X1704ZA.312 Graphics: Intel integrated graphics Storage: NVMe SSD RAM: Approximately 38 GiB Display configuration: Internal display plus external HDMI monitor Expected behavior: Kernel updates should preserve normal desktop responsiveness, without introducing multi-second application launch delays or intermittent freezes. Request: Please investigate whether kernel 7.0.0-43 introduces a regression affecting I/O latency, graphics responsiveness, power management, or firmware interaction on this ASUS model. The regression is suspected, not yet conclusively isolated. I can provide boot logs and additional diagnostic information if needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2175475/+subscriptions
[Bug 2175492] Re: Kernel panic / NULL pointer dereference in CFS scheduler (task_h_load, update_load_avg, sched_balance_update_blocked_averages) since 7.0.0-34; 7.0.0-31 was stable
** 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/2175492 Title: Kernel panic / NULL pointer dereference in CFS scheduler (task_h_load, update_load_avg, sched_balance_update_blocked_averages) since 7.0.0-34; 7.0.0-31 was stable Status in linux package in Ubuntu: New Bug description: Hardware: Lenovo IdeaPad 3 15ADA05 (81W1), AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx, 8 GB DDR4 (4 GB soldered + 4 GB SODIMM), BIOS E8CN34WW (04/28/2022), WD SN530 NVMe, Qualcomm QCA6174 Wi-Fi (ath10k). Regression: - The machine ran stable for five years, including kernels 7.0.0-28, -30 and -31 (installed 2026-07-18, 2026-08-22, 2026-09-05, on Ubuntu 24.04 HWE). - 7.0.0-34 was installed on 2026-09-27. The first crash occurred on 2026-10-06. Since then the system crashes repeatedly, also with 7.0.0-42 and 7.0.0-43 (now on Ubuntu 26.04.1 LTS). Symptoms: - Hard crash / kernel panic ("Fatal exception in interrupt"), several times per week. - Triggers: typically a few minutes after resume from suspend (S3/deep), but also shortly after a cold boot (7 seconds and about 2 minutes after boot in two cases). Suspend has now been disabled as a workaround; crashes after cold boot remain possible. Crash signatures (from pstore, files attached): - 2026-10-06, 7.0.0-34: "BUG: kernel NULL pointer dereference, address: 0000000000000121", RIP task_h_load+0x99, call trace wake_affine -> select_task_rq_fair -> select_task_rq -> try_to_wake_up (Comm: gnome-shell); followed by page faults in update_load_avg / enqueue_entity on other CPUs. (This October dump is no longer available; signature taken from my notes.) - 2026-11-09, 7.0.0-42: page faults, RIP desc_read_finalized_seq, kernel_fpu_begin_mask / irq_fpu_usable (Comm: apt-cache), "Fatal exception in interrupt". - 2026-11-13, 7.0.0-43: oops 7 s after boot; the preserved part of the call trace runs through drm_ioctl (only part of the dump was saved). - 2026-11-18, 7.0.0-43: "unable to handle page fault", RIP __sched_balance_update_blocked_averages+0x531/0x690 and +0x31b/0x690, then "kernel NULL pointer dereference, address: 0000000000000121" (Comm: swapper/1, cpuidle path), ~110 s after boot. The NULL dereference at offset 0x121 in task_h_load / the load- tracking path resembles the h_load_next use-after-free that was addressed upstream by "sched/fair: Clear ->h_load_next when unregistering a cgroup" (tip sched/urgent, December 2025). It may be worth checking whether this fix (or a related one) is missing or was regressed between 7.0.0-31 and 7.0.0-34. Hardware checks: - Memtest86+ 8.00: 15 full passes (~8 h), 0 errors. The system did not crash during this 8 h full-load test. - NVMe SMART: healthy (3 % used, 0 media errors). - Secure Boot disabled. I can test kernels or provide further logs if needed. --- ProblemType: Bug ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: sepehr 3108 F.... wireplumber /dev/snd/controlC0: sepehr 3108 F.... wireplumber /dev/snd/seq: sepehr 3103 F.... pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 26.04 InstallationDate: Installed on 2025-03-18 (613 days ago) InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) MachineType: LENOVO 81W1 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-43-generic root=UUID=c70ead31-d268-4264-bc86-8fdcba92c2d3 ro quiet splash ProcVersionSignature: Ubuntu 7.0.0-43.43-generic 7.0.14 Tags: resolute wayland-session Uname: Linux 7.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 04/28/2022 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: E8CN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ADA05 dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrE8CN34WW:bd04/28/2022:br1.34:efr1.34:svnLENOVO:pn81W1:pvrIdeaPad315ADA05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad315ADA05:skuLENOVO_MT_81W1_BU_idea_FM_IdeaPad315ADA05:pfaIdeaPad315ADA05: dmi.product.family: IdeaPad 3 15ADA05 dmi.product.name: 81W1 dmi.product.sku: LENOVO_MT_81W1_BU_idea_FM_IdeaPad 3 15ADA05 dmi.product.version: IdeaPad 3 15ADA05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2175492/+subscriptions
[Bug 2096804] Re: Kernel crashes several times a week; no diagnostic information available
Update: this bug turned out to be CVE-2025-38253, which was fixed in 6.8.0-98. ** CVE added: https://cve.org/CVERecord?id=CVE-2025-38253 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2096804 Title: Kernel crashes several times a week; no diagnostic information available Status in linux package in Ubuntu: New Bug description: After upgrading to Ubuntu 24.04, I frequently get a complete kernel stoppage. In the middle of doing any random task, the entire laptop freezes: no mouse movements, no Ctrl-Alt-F1, no Ctrl-Alt-Backspace, nothing. Whatever the last content of the screen was just remains there as a static image. Logs: There is nothing reported in /var/log/kern.log just prior to the crash; the system simply seems to stop in its tracks. There are no relevant messages in desg or syslog either. To reproduce: It doesn't seem to be triggered by what I am doing at the time, i.e., it occurs at random times. I assume the bug is in the kernel itself (linux- image-6.8.0-51-generic), or perhaps in a module, as nothing in userspace should create a complete shutdown. I realize this report doesn't do much to pinpoint the location of the bug; please advise on what I should do to collect more information. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2096804/+subscriptions
[Bug 2175492] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2175492/+attachment/6020007/+files/Lspci-vt.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2175492 Title: Kernel panic / NULL pointer dereference in CFS scheduler (task_h_load, update_load_avg, sched_balance_update_blocked_averages) since 7.0.0-34; 7.0.0-31 was stable Status in linux package in Ubuntu: New Bug description: Hardware: Lenovo IdeaPad 3 15ADA05 (81W1), AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx, 8 GB DDR4 (4 GB soldered + 4 GB SODIMM), BIOS E8CN34WW (04/28/2022), WD SN530 NVMe, Qualcomm QCA6174 Wi-Fi (ath10k). Regression: - The machine ran stable for five years, including kernels 7.0.0-28, -30 and -31 (installed 2026-07-18, 2026-08-22, 2026-09-05, on Ubuntu 24.04 HWE). - 7.0.0-34 was installed on 2026-09-27. The first crash occurred on 2026-10-06. Since then the system crashes repeatedly, also with 7.0.0-42 and 7.0.0-43 (now on Ubuntu 26.04.1 LTS). Symptoms: - Hard crash / kernel panic ("Fatal exception in interrupt"), several times per week. - Triggers: typically a few minutes after resume from suspend (S3/deep), but also shortly after a cold boot (7 seconds and about 2 minutes after boot in two cases). Suspend has now been disabled as a workaround; crashes after cold boot remain possible. Crash signatures (from pstore, files attached): - 2026-10-06, 7.0.0-34: "BUG: kernel NULL pointer dereference, address: 0000000000000121", RIP task_h_load+0x99, call trace wake_affine -> select_task_rq_fair -> select_task_rq -> try_to_wake_up (Comm: gnome-shell); followed by page faults in update_load_avg / enqueue_entity on other CPUs. (This October dump is no longer available; signature taken from my notes.) - 2026-11-09, 7.0.0-42: page faults, RIP desc_read_finalized_seq, kernel_fpu_begin_mask / irq_fpu_usable (Comm: apt-cache), "Fatal exception in interrupt". - 2026-11-13, 7.0.0-43: oops 7 s after boot; the preserved part of the call trace runs through drm_ioctl (only part of the dump was saved). - 2026-11-18, 7.0.0-43: "unable to handle page fault", RIP __sched_balance_update_blocked_averages+0x531/0x690 and +0x31b/0x690, then "kernel NULL pointer dereference, address: 0000000000000121" (Comm: swapper/1, cpuidle path), ~110 s after boot. The NULL dereference at offset 0x121 in task_h_load / the load- tracking path resembles the h_load_next use-after-free that was addressed upstream by "sched/fair: Clear ->h_load_next when unregistering a cgroup" (tip sched/urgent, December 2025). It may be worth checking whether this fix (or a related one) is missing or was regressed between 7.0.0-31 and 7.0.0-34. Hardware checks: - Memtest86+ 8.00: 15 full passes (~8 h), 0 errors. The system did not crash during this 8 h full-load test. - NVMe SMART: healthy (3 % used, 0 media errors). - Secure Boot disabled. I can test kernels or provide further logs if needed. --- ProblemType: Bug ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: sepehr 3108 F.... wireplumber /dev/snd/controlC0: sepehr 3108 F.... wireplumber /dev/snd/seq: sepehr 3103 F.... pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 26.04 InstallationDate: Installed on 2025-03-18 (613 days ago) InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) MachineType: LENOVO 81W1 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-43-generic root=UUID=c70ead31-d268-4264-bc86-8fdcba92c2d3 ro quiet splash ProcVersionSignature: Ubuntu 7.0.0-43.43-generic 7.0.14 Tags: resolute wayland-session Uname: Linux 7.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 04/28/2022 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: E8CN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ADA05 dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrE8CN34WW:bd04/28/2022:br1.34:efr1.34:svnLENOVO:pn81W1:pvrIdeaPad315ADA05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad315ADA05:skuLENOVO_MT_81W1_BU_idea_FM_IdeaPad315ADA05:pfaIdeaPad315ADA05: dmi.product.family: IdeaPad 3 15ADA05 dmi.product.name: 81W1 dmi.product.sku: LENOVO_MT_81W1_BU_idea_FM_IdeaPad 3 15ADA05 dmi.product.version: IdeaPad 3 15ADA05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2175492/+subscriptions
[Bug 2175492] Re: Kernel panic / NULL pointer dereference in CFS scheduler (task_h_load, update_load_avg, sched_balance_update_blocked_averages) since 7.0.0-34; 7.0.0-31 was stable
apport information ** Tags added: apport-collected resolute wayland-session ** Description changed: Hardware: Lenovo IdeaPad 3 15ADA05 (81W1), AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx, 8 GB DDR4 (4 GB soldered + 4 GB SODIMM), BIOS E8CN34WW (04/28/2022), WD SN530 NVMe, Qualcomm QCA6174 Wi-Fi (ath10k). Regression: - The machine ran stable for five years, including kernels 7.0.0-28, -30 and -31 (installed 2026-07-18, 2026-08-22, 2026-09-05, on Ubuntu 24.04 HWE). - 7.0.0-34 was installed on 2026-09-27. The first crash occurred on 2026-10-06. Since then the system crashes repeatedly, also with 7.0.0-42 and 7.0.0-43 (now on Ubuntu 26.04.1 LTS). Symptoms: - Hard crash / kernel panic ("Fatal exception in interrupt"), several times per week. - Triggers: typically a few minutes after resume from suspend (S3/deep), but also shortly after a cold boot (7 seconds and about 2 minutes after boot in two cases). Suspend has now been disabled as a workaround; crashes after cold boot remain possible. Crash signatures (from pstore, files attached): - 2026-10-06, 7.0.0-34: "BUG: kernel NULL pointer dereference, address: 0000000000000121", RIP task_h_load+0x99, call trace wake_affine -> select_task_rq_fair -> select_task_rq -> try_to_wake_up (Comm: gnome-shell); followed by page faults in update_load_avg / enqueue_entity on other CPUs. (This October dump is no longer available; signature taken from my notes.) - 2026-11-09, 7.0.0-42: page faults, RIP desc_read_finalized_seq, kernel_fpu_begin_mask / irq_fpu_usable (Comm: apt-cache), "Fatal exception in interrupt". - 2026-11-13, 7.0.0-43: oops 7 s after boot; the preserved part of the call trace runs through drm_ioctl (only part of the dump was saved). - 2026-11-18, 7.0.0-43: "unable to handle page fault", RIP __sched_balance_update_blocked_averages+0x531/0x690 and +0x31b/0x690, then "kernel NULL pointer dereference, address: 0000000000000121" (Comm: swapper/1, cpuidle path), ~110 s after boot. The NULL dereference at offset 0x121 in task_h_load / the load-tracking path resembles the h_load_next use-after-free that was addressed upstream by "sched/fair: Clear ->h_load_next when unregistering a cgroup" (tip sched/urgent, December 2025). It may be worth checking whether this fix (or a related one) is missing or was regressed between 7.0.0-31 and 7.0.0-34. Hardware checks: - Memtest86+ 8.00: 15 full passes (~8 h), 0 errors. The system did not crash during this 8 h full-load test. - NVMe SMART: healthy (3 % used, 0 media errors). - Secure Boot disabled. I can test kernels or provide further logs if needed. + --- + ProblemType: Bug + ApportVersion: 2.34.1-0ubuntu0.1 + Architecture: amd64 + AudioDevicesInUse: + USER PID ACCESS COMMAND + /dev/snd/controlC1: sepehr 3108 F.... wireplumber + /dev/snd/controlC0: sepehr 3108 F.... wireplumber + /dev/snd/seq: sepehr 3103 F.... pipewire + CRDA: N/A + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 26.04 + InstallationDate: Installed on 2025-03-18 (613 days ago) + InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) + MachineType: LENOVO 81W1 + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-43-generic root=UUID=c70ead31-d268-4264-bc86-8fdcba92c2d3 ro quiet splash + ProcVersionSignature: Ubuntu 7.0.0-43.43-generic 7.0.14 + Tags: resolute wayland-session + Uname: Linux 7.0.0-43-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip kvm lpadmin plugdev sudo users + _MarkForUpload: True + dmi.bios.date: 04/28/2022 + dmi.bios.release: 1.34 + dmi.bios.vendor: LENOVO + dmi.bios.version: E8CN34WW + dmi.board.asset.tag: No Asset Tag + dmi.board.name: LNVNB161216 + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40700WIN + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: IdeaPad 3 15ADA05 + dmi.ec.firmware.release: 1.34 + dmi.modalias: dmi:bvnLENOVO:bvrE8CN34WW:bd04/28/2022:br1.34:efr1.34:svnLENOVO:pn81W1:pvrIdeaPad315ADA05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad315ADA05:skuLENOVO_MT_81W1_BU_idea_FM_IdeaPad315ADA05:pfaIdeaPad315ADA05: + dmi.product.family: IdeaPad 3 15ADA05 + dmi.product.name: 81W1 + dmi.product.sku: LENOVO_MT_81W1_BU_idea_FM_IdeaPad 3 15ADA05 + dmi.product.version: IdeaPad 3 15ADA05 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2175492/+attachment/6020003/+files/AlsaInfo.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2175492 Title: Kernel panic / NULL pointer dereference in CFS scheduler (task_h_load, update_load_avg, sched_balance_update_blocked_averages) since 7.0.0-34; 7.0.0-31 was stable Status in linux package in Ubuntu: New Bug description: Hardware: Lenovo IdeaPad 3 15ADA05 (81W1), AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx, 8 GB DDR4 (4 GB soldered + 4 GB SODIMM), BIOS E8CN34WW (04/28/2022), WD SN530 NVMe, Qualcomm QCA6174 Wi-Fi (ath10k). Regression: - The machine ran stable for five years, including kernels 7.0.0-28, -30 and -31 (installed 2026-07-18, 2026-08-22, 2026-09-05, on Ubuntu 24.04 HWE). - 7.0.0-34 was installed on 2026-09-27. The first crash occurred on 2026-10-06. Since then the system crashes repeatedly, also with 7.0.0-42 and 7.0.0-43 (now on Ubuntu 26.04.1 LTS). Symptoms: - Hard crash / kernel panic ("Fatal exception in interrupt"), several times per week. - Triggers: typically a few minutes after resume from suspend (S3/deep), but also shortly after a cold boot (7 seconds and about 2 minutes after boot in two cases). Suspend has now been disabled as a workaround; crashes after cold boot remain possible. Crash signatures (from pstore, files attached): - 2026-10-06, 7.0.0-34: "BUG: kernel NULL pointer dereference, address: 0000000000000121", RIP task_h_load+0x99, call trace wake_affine -> select_task_rq_fair -> select_task_rq -> try_to_wake_up (Comm: gnome-shell); followed by page faults in update_load_avg / enqueue_entity on other CPUs. (This October dump is no longer available; signature taken from my notes.) - 2026-11-09, 7.0.0-42: page faults, RIP desc_read_finalized_seq, kernel_fpu_begin_mask / irq_fpu_usable (Comm: apt-cache), "Fatal exception in interrupt". - 2026-11-13, 7.0.0-43: oops 7 s after boot; the preserved part of the call trace runs through drm_ioctl (only part of the dump was saved). - 2026-11-18, 7.0.0-43: "unable to handle page fault", RIP __sched_balance_update_blocked_averages+0x531/0x690 and +0x31b/0x690, then "kernel NULL pointer dereference, address: 0000000000000121" (Comm: swapper/1, cpuidle path), ~110 s after boot. The NULL dereference at offset 0x121 in task_h_load / the load- tracking path resembles the h_load_next use-after-free that was addressed upstream by "sched/fair: Clear ->h_load_next when unregistering a cgroup" (tip sched/urgent, December 2025). It may be worth checking whether this fix (or a related one) is missing or was regressed between 7.0.0-31 and 7.0.0-34. Hardware checks: - Memtest86+ 8.00: 15 full passes (~8 h), 0 errors. The system did not crash during this 8 h full-load test. - NVMe SMART: healthy (3 % used, 0 media errors). - Secure Boot disabled. I can test kernels or provide further logs if needed. --- ProblemType: Bug ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: sepehr 3108 F.... wireplumber /dev/snd/controlC0: sepehr 3108 F.... wireplumber /dev/snd/seq: sepehr 3103 F.... pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 26.04 InstallationDate: Installed on 2025-03-18 (613 days ago) InstallationMedia: Ubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) MachineType: LENOVO 81W1 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-43-generic root=UUID=c70ead31-d268-4264-bc86-8fdcba92c2d3 ro quiet splash ProcVersionSignature: Ubuntu 7.0.0-43.43-generic 7.0.14 Tags: resolute wayland-session Uname: Linux 7.0.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm lpadmin plugdev sudo users _MarkForUpload: True dmi.bios.date: 04/28/2022 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: E8CN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15ADA05 dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrE8CN34WW:bd04/28/2022:br1.34:efr1.34:svnLENOVO:pn81W1:pvrIdeaPad315ADA05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad315ADA05:skuLENOVO_MT_81W1_BU_idea_FM_IdeaPad315ADA05:pfaIdeaPad315ADA05: dmi.product.family: IdeaPad 3 15ADA05 dmi.product.name: 81W1 dmi.product.sku: LENOVO_MT_81W1_BU_idea_FM_IdeaPad 3 15ADA05 dmi.product.version: IdeaPad 3 15ADA05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2175492/+subscriptions
пятница
[Bug 2175435] Re: amd_pstate fails to load on Zen 2 (Ryzen 5 4600G, shared-memory CPPC): "failed to set auto_sel, ret: -95", falls back to acpi-cpufreq
** 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/2175435 Title: amd_pstate fails to load on Zen 2 (Ryzen 5 4600G, shared-memory CPPC): "failed to set auto_sel, ret: -95", falls back to acpi-cpufreq Status in linux package in Ubuntu: New Bug description: Summary ------- On Ubuntu 26.04.1 with kernel 7.0.0-43-generic, the amd_pstate driver fails to initialize on every CPU of a Ryzen 5 4600G (Renoir, Zen 2, shared-memory CPPC). The kernel falls back to acpi-cpufreq. As a result power-profiles-daemon has no CPU driver ("PlatformDriver: placeholder") and the GNOME "Performance" power mode is missing. CPPC is enabled in the BIOS (AMD CBS -> NBIO Common Options -> SMU Common Options -> CPPC = Enabled), and the ACPI _CPC data is visible to the OS (/sys/devices/system/cpu/cpu0/acpi_cppc/ is populated, see below). Hardware / software ------------------- - CPU: AMD Ryzen 5 4600G with Radeon Graphics (family 23 / 0x17, model 96 / 0x60, stepping 1), microcode 0x860010f - Board: ASUS PRIME A320I-K, BIOS 6254 (2026-01-23) - OS: Ubuntu 26.04.1 LTS - Kernel: Ubuntu 7.0.0-43.43-generic 7.0.14 (CONFIG_X86_AMD_PSTATE=y, CONFIG_X86_AMD_PSTATE_DEFAULT_MODE=3) - Kernel cmdline includes: amd_pstate=active Steps to reproduce ------------------ 1. Enable CPPC in BIOS. 2. Boot 7.0.0-43-generic with amd_pstate=active (the kernel's default mode is also active). 3. cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver Expected: amd-pstate-epp Actual: acpi-cpufreq; /sys/devices/system/cpu/amd_pstate/ does not exist Kernel log (identical on every boot) ------------------------------------ amd_pstate: The CPPC feature is supported but currently disabled by the BIOS. Please enable it if your BIOS has the CPPC option. amd_pstate: failed to set auto_sel, ret: -95 amd_pstate: Failed to initialize CPU 0: -95 amd_pstate: failed to set auto_sel, ret: -95 amd_pstate: Failed to initialize CPU 1: -95 ... (same for CPUs 2-11) amd_pstate: failed to register with return -19 ACPI CPPC values exposed by firmware (cpu0) ------------------------------------------- highest_perf=255 nominal_perf=219 reference_perf=219 lowest_nonlinear_perf=141 lowest_perf=24 guaranteed_perf=0 nominal_freq=3701 lowest_freq=400 feedback_ctrs present (counters increasing) Analysis -------- - The "CPPC ... disabled by the BIOS" warning appears to be a heuristic for this CPU model when X86_FEATURE_CPPC (MSR CPPC) is absent; Renoir uses the shared-memory (ACPI _CPC) path, and _CPC is present. - The actual failure is cppc_set_auto_sel() returning -EOPNOTSUPP (-95), which suggests the firmware's _CPC package does not implement the Autonomous Selection Enable register. The driver treats this as fatal for each CPU instead of continuing without auto_sel. - Expected behaviour: if auto_sel is not supported, the driver should log a warning and continue (or fall back to a mode that does not require it), rather than failing registration entirely. References ---------- - Same error on Proxmox kernel 6.17 with Ryzen 4650G (also Renoir) and other AM4 systems; reported working on kernel 6.8: https://forum.proxmox.com/threads/cant-get-amd-pstate-to-work-it-used-to-be-fine.177103 - Related upstream patch "Fix EPP initialization for shared memory systems" (June 2026), which calls cppc_set_auto_sel() but only warns on failure: https://patchew.org/linux/20260605103131.88711-1-scardracs@disroot.org/mbox I am happy to test a proposed fix or a mainline kernel. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-43-generic 7.0.0-43.43 ProcVersionSignature: Ubuntu 7.0.0-43.43-generic 7.0.14 Uname: Linux 7.0.0-43-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Nov 20 21:40:29 2026 InstallationDate: Installed on 2024-07-18 (855 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) MachineType: System manufacturer System Product Name ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-43-generic root=/dev/mapper/main-root ro quiet splash amd_pstate=active 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. RfKill: SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-07-18 (125 days ago) dmi.bios.date: 01/05/2026 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6254 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320I-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6254:bd01/05/2026:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320I-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2175435/+subscriptions
[Bug 2175126] Re: [SRU] drm/i915/bios: Support VBT #57 vswing/pre-emphasis override
** 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/2175126 Title: [SRU] drm/i915/bios: Support VBT #57 vswing/pre-emphasis override Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-7.0 package in Ubuntu: In Progress Status in linux-oem-7.3 package in Ubuntu: In Progress Status in linux source package in Resolute: In Progress Status in linux-oem-7.0 source package in Resolute: In Progress Status in linux-oem-7.3 source package in Resolute: In Progress Status in linux source package in Stonking: In Progress Status in linux-oem-7.0 source package in Stonking: Invalid Status in linux-oem-7.3 source package in Stonking: Invalid Bug description: SRU Justification: [ Impact ] On Intel Panther Lake laptops whose Video BIOS Table (VBT) requests per-port voltage swing / pre-emphasis overrides (use_vbt_vswing=1), boot triggers a kernel drm_WARN in intel_bios_init() ("Port D asks to use VBT vswing/preemph tables") and the display driver ignores the OEM-provided VBT Block #57 PHY signal-tuning tables. [ Fix ] Backport the VBT Block #57 Vswing / Pre-emphasis Override (VS/PE-O) series from Linux 7.4-rc1 (plus prerequisite wrapper commit 07095bb7ea730 from Linux 7.2-rc1 for 7.0 kernels): - 07095bb7ea730 ("drm/i915/ddi: add wrapper for calling ->get_buf_trans() hook") [7.0 only] - 3018008dc1c3c ("drm/i915/bios: search for VBT #57 by default") - c76c03dab8287 ("drm/i915/bios: store VBT #57's metadata in intel_vbt_data") - 1b15117625045 ("drm/i915/bios: print VS/PE-O port info") - a138a81d7805a ("drm/i915/bios: de/allocate VS/PE-O buffers for each port") - e084812de907c ("drm/i915/buf_trans: add vfunc for VS/PE-O") - e8fe5008ae3da ("drm/i915: override Snps's VS/PE when requested") - 7fdf86e530c7f ("drm/i915: override Combo's VS/PE when requested") - 4bda5543b3c66 ("drm/i915/bios: remove VS/PE-O warning") [ Test Plan ] 1. Boot an affected Intel Panther Lake laptop with VBT Block #57 vswing/pre-emphasis override enabled in BIOS. 2. Check dmesg during boot and verify no drm_WARN occurs in intel_bios_init() and drm.debug logs "Port D requests vswing/pre-emphasis override". 3. Connect an external DisplayPort monitor on the affected port and verify link training and display output work properly. [ Where problems could occur ] Changes are scoped to Intel i915/xe VBT parsing and DDI buffer translation selection. Systems whose VBT does not set use_vbt_vswing continue using the existing predefined PHY tables unchanged. Any regression would affect DisplayPort/eDP link training on systems with VBT Block #57 overrides enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2175126/+subscriptions
[Bug 2172110] Re: Lenovo IdeaPad Slim 3 17IWC11 (83VS): internal PS/2 keyboard dead after boot unless i8042.dumbkbd is set
Same issue on another model of the family, plus the root cause and a patch. New affected machine - LENOVO 83RQ / IdeaPad Slim 3 14IWC11, BIOS U2CN31WW (09/30/2026), EC 1.24 - Ubuntu 26.10, kernel 7.3.0-11.12-generic - Same symptoms as the 83VS: keyboard works in firmware/GRUB, dead in Linux, IRQ 1 frozen, only the Fn keys work. - Additional data point: i8042.dumbkbd=1 fixes input but kills the Caps Lock, Num Lock and Scroll Lock LEDs (atkbd no longer exposes EV_LED, /sys/class/leds/input3::capslock disappears). Root cause atkbd_probe() calls atkbd_deactivate(), which sends ATKBD_CMD_RESET_DIS (0xF5). This EC ACKs the command but never sends scancodes again, even after ATKBD_CMD_ENABLE (0xF4). Upstream already has the atkbd_deactivate_fixup DMI quirk for 83RR (commit 3bf8d603fd45) and for 83QK, but current mainline has no entry for 83RQ or 83VS. Request Please add a SAUCE/DMI quirk for 83RQ (and ideally for the whole IWC11 family). Attached is the 8-line patch for 83RQ, identical to the merged 83RR entry; I checked that it applies to current mainline. The original upstream submission for 83RQ exists but was not merged: https://patchew.org/linux/20260911182328.9267-1-iustinivan2002@gmail.com ** Patch added: "DMI quirk for 83RQ (same as merged 83RR entry). 83VS needs its own entry." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172110/+attachment/6019824/+files/0001-Input-atkbd-skip-deactivate-for-Lenovo-IdeaPad-Slim-3-14IWC11.patch -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2172110 Title: Lenovo IdeaPad Slim 3 17IWC11 (83VS): internal PS/2 keyboard dead after boot unless i8042.dumbkbd is set Status in linux package in Ubuntu: Confirmed Bug description: Summary The built-in keyboard of the Lenovo IdeaPad Slim 3 17IWC11 (type 83VS) works in the firmware setup, boot menu and GRUB, but produces no input once Linux is running. It works only with the kernel parameter i8042.dumbkbd. External USB and Bluetooth keyboards work normally. Environment - Machine: Lenovo IdeaPad Slim 3 17IWC11, machine type 83VS (sold without OS) - BIOS: U2CN23WW (fwupd/LVFS reports no firmware update available) - Ubuntu 26.10, kernel 7.3.0-9-generic - Also observed in the Ubuntu 26.04 installer/live session (keyboard unusable there too) Observed behaviour (without i8042.dumbkbd) - Keyboard works in BIOS setup (F2), boot menu (F12) and GRUB. - After the kernel starts, no key press reaches the system (installer, login screen, desktop). - dmesg shows the controller and keyboard being registered with no error: i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1 i8042: PNP: PS/2 appears to have AUX port disabled serio: i8042 KBD port at 0x60,0x64 irq 1 input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3 - /proc/interrupts: IRQ 1 (IR-IO-APIC 1-edge i8042) stays at 28 and does not increase while typing on the built-in keyboard. - /sys/class/input/input3/inhibited = 0. - No atkbd error messages in dmesg. - ideapad_acpi logs: "VPC2004:00: Unknown keyboard type: 1" and "Keyboard backlight control not available". - The touchpad works (handled through i2c_hid_acpi / hid_multitouch). Parameters tried - No effect: i8042.nopnp; i8042.reset i8042.nomux; i8042.kbdreset; acpi_osi="Windows 2022"; i8042.noloop. - irqpoll: broke the graphical login (login loop) and was removed. - i8042.dumbkbd: keyboard works. Made persistent with a drop-in file in /etc/default/grub.d/. Behaviour with i8042.dumbkbd - Typing works; Fn+F11 and Fn+F12 work; Fn+PrintScreen works. - PrintScreen alone has no visible effect. - F9 (settings icon) and Fn+F9 send a signal , but trigger no default action in GNOME. Expected behaviour The internal keyboard should work without any kernel parameter. Additional information Similar symptoms have been reported on other IdeaPad Slim 3 models (keyboard fine in firmware/GRUB, dead in Linux). I can provide further logs or test patches/parameters on request. ProblemType: Bug DistroRelease: Ubuntu 26.10 Package: linux-image-7.3.0-9-generic 7.3.0-9.9 ProcVersionSignature: Ubuntu 7.3.0-9.9-generic 7.3.0-rc6 Uname: Linux 7.3.0-9-generic x86_64 ApportVersion: 2.36.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: bri 35227 F.... pipewire bri 35233 F.... wireplumber /dev/snd/seq: bri 35227 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: Error executing command as another user: Request dismissed Date: Sat Oct 24 11:53:53 2026 InstallationDate: Installed on 2026-10-22 (2 days ago) InstallationMedia: Ubuntu 26.10 "Stonking Stingray" - Official amd64 (20261013) MachineType: LENOVO 83VS ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.3.0-9-generic root=UUID=3d214042-ff4e-4890-9756-244565d888d3 ro quiet splash i8042.dumbkbd 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) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 06/04/2026 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: U2CN23WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Slim 3 17IWC11 dmi.ec.firmware.release: 1.21 dmi.modalias: dmi:bvnLENOVO:bvrU2CN23WW:bd06/04/2026:br1.23:efr1.21:svnLENOVO:pn83VS:pvrIdeaPadSlim317IWC11:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPadSlim317IWC11:skuLENOVO_MT_83VS_BU_idea_FM_IdeaPadSlim317IWC11:pfaIdeaPadSlim317IWC11: dmi.product.family: IdeaPad Slim 3 17IWC11 dmi.product.name: 83VS dmi.product.sku: LENOVO_MT_83VS_BU_idea_FM_IdeaPad Slim 3 17IWC11 dmi.product.version: IdeaPad Slim 3 17IWC11 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172110/+subscriptions
[Bug 2167288] Re: No internal speaker or 3.5mm headphone audio on ASUS ExpertBook PM3606CHA - Realtek ALC256 subsystem 1043:3501
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2167288 Title: No internal speaker or 3.5mm headphone audio on ASUS ExpertBook PM3606CHA - Realtek ALC256 subsystem 1043:3501 Status in linux package in Ubuntu: Confirmed Bug description: ASUS ExpertBook P3 PM3606CHA Ubuntu 26.04 Kernel: 7.0.0-31-generic Audio codec: Realtek ALC256 Vendor ID: 0x10ec0256 Subsystem ID: 0x10433501 Symptoms: - Internal speakers produce no sound. - 3.5 mm headphones also produce no sound. - PipeWire detects Ryzen HD Audio Controller Speaker normally. - ALSA exposes ALC256 Analog playback device. - speaker-test runs normally but produces no audible sound. - Headphone jack detection does not work: pin 0x21 GET_PIN_SENSE returns 0x0 both unplugged and plugged. - Speaker pin 0x14 has PIN_WIDGET_CONTROL=0x40. - EAPD on pin 0x14 is already 0x02. - Manually enabling codec GPIO2 (mask/direction/data = 0x04) does not restore speaker audio. - No CS35L41/TAS2781/etc external amplifier is detected by ACPI. dmesg: ALC256: picked fixup (pin match) autoconfig for ALC256: line_outs=1 (0x14) type:speaker hp_outs=1 (0x21) ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-31-generic 7.0.0-31.31 ProcVersionSignature: Ubuntu 7.0.0-31.31-generic 7.0.14 Uname: Linux 7.0.0-31-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 15 09:46:56 2026 InstallationDate: Installed on 2026-09-14 (0 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: ASUS ASUS EXPERTBOOK PM3606CHA ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-31-generic root=UUID=7b60115e-0170-41c8-8f2f-181cb8f8c35d 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: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2026 dmi.bios.release: 3.4 dmi.bios.vendor: ASUSTeK COMPUTER INC. (Licensed by AMI, LLC.) dmi.bios.version: PM3606CHA.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: PM3606CHA 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.21 dmi.modalias: dmi:bvnASUSTeKCOMPUTERINC.(LicensedbyAMI,LLC.):bvrPM3606CHA.304:bd03/20/2026:br3.4:efr3.21:svnASUS:pnASUSEXPERTBOOKPM3606CHA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnPM3606CHA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSEXPERTBOOK: dmi.product.family: ASUS EXPERTBOOK dmi.product.name: ASUS EXPERTBOOK PM3606CHA 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/2167288/+subscriptions
[Bug 2173944] Re: noble selftests:net:tls test compile error due to selftests: tls: add rekey tests
This bug is awaiting verification that the linux-ibm-gt- tdx/6.8.0-1068.74+tdx1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-ibm-gt-tdx' to 'verification-done-noble-linux-ibm-gt-tdx'. If the problem still exists, change the tag 'verification-needed-noble-linux-ibm-gt-tdx' to 'verification-failed-noble-linux-ibm-gt-tdx'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-ibm-gt-tdx-v2 verification-needed-noble-linux-ibm-gt-tdx -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2173944 Title: noble selftests:net:tls test compile error due to selftests: tls: add rekey tests Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Noble: Fix Committed Bug description: ubuntu_kselftests_net fails to compile due to tls test case for 6.8.0-150.150: tls.c: In function ‘tls_basic_recvmsg_nopad_retry_iov’: tls.c:1621:9: error: too many arguments to function ‘tls_crypto_info_init’ 1621 | tls_crypto_info_init(TLS_1_3_VERSION, TLS_CIPHER_AES_GCM_128, | ^~~~~~~~~~~~~~~~~~~~ tls.c:46:13: note: declared here 46 | static void tls_crypto_info_init(uint16_t tls_version, uint16_t cipher_type, | ^~~~~~~~~~~~~~~~~~~~ tls.c: In function ‘tls_basic_rekey_rx’: tls.c:1684:9: error: too many arguments to function ‘tls_crypto_info_init’ 1684 | tls_crypto_info_init(TLS_1_3_VERSION, TLS_CIPHER_AES_GCM_128, | ^~~~~~~~~~~~~~~~~~~~ tls.c:46:13: note: declared here 46 | static void tls_crypto_info_init(uint16_t tls_version, uint16_t cipher_type, | ^~~~~~~~~~~~~~~~~~~~ tls.c:1686:9: error: too many arguments to function ‘tls_crypto_info_init’ 1686 | tls_crypto_info_init(TLS_1_3_VERSION, TLS_CIPHER_AES_GCM_128, | ^~~~~~~~~~~~~~~~~~~~ tls.c:46:13: note: declared here 46 | static void tls_crypto_info_init(uint16_t tls_version, uint16_t cipher_type, | ^~~~~~~~~~~~~~~~~~~~ tls.c: In function ‘tls_basic_rekey_tx’: tls.c:1715:9: error: too many arguments to function ‘tls_crypto_info_init’ 1715 | tls_crypto_info_init(TLS_1_3_VERSION, TLS_CIPHER_AES_GCM_128, | ^~~~~~~~~~~~~~~~~~~~ The following commit which was applied to 6.8.0-150.150: selftests: tls: add rekey tests [ Upstream commit 555f0edb9ff043196655a5b7cc65f67dfd05b530 ] lacks 2 dependency commits: selftests: tls: add a selftest for wrapping rec_seq [ Upstream commit 81bc949f640f78b507c7523de7c750bcc87c1bb8 ] selftests: tls: add key_generation argument to tls_crypto_info_init [ Upstream commit b2e584aa3c710802600b690f34a56fb526aebf2f ] Applying dependency commit resolves ubuntu_kselftests_net compilation issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2173944/+subscriptions
[Bug 2174483] Re: [resolute] .NET processes crash with general protection fault in libc since linux 7.0.0-42 (7.0.0-38 OK)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2174483 Title: [resolute] .NET processes crash with general protection fault in libc since linux 7.0.0-42 (7.0.0-38 OK) Status in linux package in Ubuntu: Confirmed Bug description: == Summary == After upgrading Ubuntu 26.04 (resolute) amd64 hosts from linux 7.0.0-38 to 7.0.0-42 / 7.0.0-43, .NET processes running in containers crash randomly with SIGSEGV (exit code 139). The kernel logs a general protection fault on .NET runtime threads ("TP Worker" thread pool, "BGC" background GC) inside the container's libc. Rebooting the same VM into an older kernel makes the crashes stop completely. The kernel is the only thing that changes. == Affected / not affected kernels (same VMs, same container images) == linux-image-7.0.0-31-generic 7.0.0-31.31 OK (0 faults in ~2 months of CI use; 0 faults after rollback) linux-image-7.0.0-38-generic 7.0.0-38.38 OK (host running 9 .NET services, 0 faults) linux-image-7.0.0-42-generic 7.0.0-42.42 BROKEN linux-image-7.0.0-43-generic 7.0.0-43.43 BROKEN (resolute-updates) linux-image-7.0.0-44-generic 7.0.0-44.44 BROKEN (resolute-proposed, signed, tested 2026-11-14) The regression was introduced somewhere between 7.0.0-38.38 and 7.0.0-42.42. == System info == lsb_release -rd: Ubuntu 26.04 LTS / Release 26.04 /proc/version_signature (current, rolled back): Ubuntu 7.0.0-31.31-generic 7.0.14 lspci: no PCI devices listed (Hyper-V Generation 2 VM, synthetic VMBus devices only) == Environment == - Ubuntu 26.04 LTS amd64, Hyper-V Generation 2 VMs (UEFI, Secure Boot enabled), 8 vCPU, 16 GB RAM - CPU: Intel(R) Xeon(R) Platinum 8276 CPU @ 2.20GHz (flags include avx2 avx512f avx512vl erms xsaves) - Container runtimes: containerd 2.1.5 (RKE2 Kubernetes v1.34.4) and Docker 29.6.0. Both are affected. - .NET: SDK 9.0.320 / runtime 9.0.22, ASP.NET Core 9 runtime images, and .NET 10 SDK. All are affected. - Container libc: affected with both Ubuntu 24.04 glibc 2.39-0ubuntu8.9 (mcr.microsoft.com/dotnet/sdk:9.0-noble, 10.0-noble) and Debian 12 glibc 2.36-9+deb12u14 (ASP.NET 9 runtime image). This is not specific to one libc build. == Kernel log (examples) == Ubuntu 24.04 glibc 2.39 in the container (host kernel 7.0.0-43, and the same with 7.0.0-44): traps: .NET BGC[39263] general protection fault ip:754c651919a2 sp:75441e735a20 error:0 in libc.so.6[289a2,754c65191000+189000] traps: .NET TP Worker[213956] general protection fault ip:76786d3879a2 sp:7676caffbe60 error:0 in libc.so.6[289a2,76786d387000+189000] traps: .NET TP Worker[12529] general protection fault ip:7a6d09bee9a2 sp:7a68aac9be50 error:0 (7.0.0-44) Debian 12 glibc 2.36 in the container (host kernel 7.0.0-42): traps: .NET TP Worker[940249] general protection fault ip:70ce23ea950f sp:70cc4900ea10 error:0 in libc.so.6[2650f,70ce23ea9000+156000] traps: .NET BGC[946081] general protection fault ip:71f63264a50f sp:71f44cff8a30 error:0 in libc.so.6[2650f,71f63264a000+156000] On each host the faulting offset is always identical (0x289a2 in one libc build, 0x2650f in the other). == Analysis of the faulting IP == In both libc builds the reported IP is NOT on an instruction boundary: - glibc 2.39-0ubuntu8.9 (build-id a4a7992a8e66555c8141ab2a08a8465ff6e0ea65): the text segment is mapped from file offset 0x28000, so the IP is at file address 0x509a2. That is 1 byte into the instruction "mov %r11,-0x448(%rbp)" at 0x509a1. - glibc 2.36-9+deb12u14 (build-id 93ac61ec5a8eb1396f9fbd350e3169a558528a40): the text segment is mapped from 0x26000, so the IP is at file address 0x4c50f. That is the last byte of the padding "nopl" between wcstombs and the next function, 1 byte before "push %rbx" at 0x4c510 and 2 bytes before the next instruction at 0x4c511. A user RIP that lands off an instruction boundary in two unrelated libc builds suggests that the user-mode instruction pointer is corrupted by the kernel, for example on signal delivery or return, or by syscall-restart IP adjustment. It does not look like a libc or .NET bug. The .NET runtime uses signals heavily on these threads (thread suspension for GC, activation injection) and also uses membarrier. == Reproduction == - The most reliable reproducer is a real CI job running "dotnet sonarscanner begin" followed by "dotnet restore" on a mid-size solution, in a container limited to 4 CPUs / 4 GiB. It failed 3/3 on 7.0.0-43 and 1/1 on 7.0.0-44, and passed every time on 7.0.0-31 and 7.0.0-38. - A long-running ASP.NET Core 9 service (HTTP client + EF Core / Npgsql) crashed 3 times in about 1 hour on 7.0.0-42. - A synthetic loop of "dotnet new webapi && dotnet build" reproduces rarely (1 fault in about 80 builds), so the trigger seems to depend on load or timing. Fault frequency on an affected CI host: 17 faults in 8 hours. == Workaround == Pin GRUB_DEFAULT to 7.0.0-38 (or 7.0.0-31) and hold linux-generic / linux-image-generic / linux-headers-generic. == Notes == - I can test candidate kernels or bisect between 7.0.0-38.38 and 7.0.0-42.42 if packages are provided. The intermediate ABIs 7.0.0-39/-40/-41 were not published to resolute-updates. - Production nodes were rolled back, so apport data from an affected boot is not attached. I can boot a test node into 7.0.0-43 to collect it on request. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174483/+subscriptions