This bug is awaiting verification that the linux-oem-6.17/6.17.0-1030.30 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-oem-6.17' to 'verification-done- noble-linux-oem-6.17'. If the problem still exists, change the tag 'verification-needed-noble-linux-oem-6.17' to 'verification-failed- noble-linux-oem-6.17'. 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-oem-6.17-v2 verification-needed-noble-linux-oem-6.17 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160183 Title: Suspend resume time is too long on EliteBook 8 G1a 13 Status in linux package in Ubuntu: New Status in linux-oem-6.17 package in Ubuntu: New Status in linux source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: Fix Committed Status in linux source package in Resolute: New Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Summary] Suspend resume time is too long on EliteBook 8 G1a 13. Suspend time is normal at 0.616 seconds, but resume takes 20.888 seconds. I also found some suspicious log in journal log. Jul 09 01:52:28 localhost kernel: mhi mhi0: MHI did not load image over BHI, ret: -5 Jul 09 01:52:28 localhost kernel: ath12k_pci 0000:01:00.0: failed to set mhi state: POWER_ON(2) Jul 09 01:52:28 localhost kernel: ath12k_pci 0000:01:00.0: failed to start mhi: -110 Jul 09 01:52:28 localhost kernel: PM: suspend of devices complete after 107.286 msecs .. .. .. Jul 09 01:52:28 localhost kernel: PM: noirq resume of devices complete after 424.651 msecs Jul 09 01:52:28 localhost kernel: ath12k_pci 0000:01:00.0: failed to set mhi state INIT(0) in current mhi state (0x1) Jul 09 01:52:28 localhost kernel: ath12k_pci 0000:01:00.0: failed to set mhi state: INIT(0) Jul 09 01:52:28 localhost kernel: ath12k_pci 0000:01:00.0: failed to start mhi: -22 Jul 09 01:52:28 localhost kernel: ath12k_pci 0000:01:00.0: failed to power up hif during resume: -22 Jul 09 01:52:28 localhost kernel: ath12k_pci 0000:01:00.0: failed to early resume core: -22 Jul 09 01:52:28 localhost kernel: ath12k_pci 0000:01:00.0: PM: dpm_run_callback(): pci_pm_resume_early returns -22 Jul 09 01:52:28 localhost kernel: ath12k_pci 0000:01:00.0: PM: failed to resume async early: error -22 [Reproduce steps] Run the following command: sudo fwts s3 --s3-sleep-delay=30 --s3-device-check --s3-device-check-delay=45 Wait for the suspend/resume test to complete. Check the reported suspend and resume timing. Observe that resume takes 20.888 seconds. [Failure rate] 1/1 [Affected machines] https://certification.canonical.com/hardware/202503-36556/ ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.17.0-1029-oem 6.17.0-1029.29 ProcVersionSignature: Ubuntu 6.17.0-1029.29-oem 6.17.13 Uname: Linux 6.17.0-1029-oem x86_64 ApportVersion: 2.28.2-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1730 F.... wireplumber /dev/snd/controlC0: ubuntu 1730 F.... wireplumber /dev/snd/seq: ubuntu 1726 F.... pipewire CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.standard.hotfix.manifest ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Thu Jul 9 02:55:05 2026 DistributionChannelDescriptor: # This is the distribution channel descriptor for Ubuntu 24.04 for HP # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-noble-oem-24.04b-proposed-20250605-516 InstallationDate: Installed on 2026-07-06 (3 days ago) InstallationMedia: Ubuntu OEM 24.04.2 LTS "Noble Numbat" - Release amd64 (20250603) MachineType: HP HP EliteBook 8 G1a 13 inch Notebook AI PC ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-1029-oem root=UUID=776bf8ec-29ed-465b-8999-6df82c789332 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.17.0-1029-oem N/A linux-backports-modules-6.17.0-1029-oem N/A linux-firmware 20240318.git3b128b60-0ubuntu2.27 SourcePackage: linux-oem-6.17 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/23/2025 dmi.bios.release: 2.1 dmi.bios.vendor: HP dmi.bios.version: X81 Ver. 01.02.01 dmi.board.name: 8E14 dmi.board.vendor: HP dmi.board.version: KBC Version 54.24.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 84.36 dmi.modalias: dmi:bvnHP:bvrX81Ver.01.02.01:bd05/23/2025:br2.1:efr84.36:svnHP:pnHPEliteBook8G1a13inchNotebookAIPC:pvrSBKPF,SBKPFV2:rvnHP:rn8E14:rvrKBCVersion54.24.00:cvnHP:ct10:cvr:sku1234567#ABA: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 8 G1a 13 inch Notebook AI PC dmi.product.sku: 1234567#ABA dmi.product.version: SBKPF,SBKPFV2 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160183/+subscriptions
пятница
[Bug 2159608] Re: noble/linux-raspi FTBFS: bcmasp phylib managed-EEE backport missing prerequisites
This bug is awaiting verification that the linux-aws/6.8.0-1061.64 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-aws' to 'verification-done-noble- linux-aws'. If the problem still exists, change the tag 'verification- needed-noble-linux-aws' to 'verification-failed-noble-linux-aws'. 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-aws-v2 verification-needed-noble-linux-aws -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2159608 Title: noble/linux-raspi FTBFS: bcmasp phylib managed-EEE backport missing prerequisites Status in linux package in Ubuntu: Confirmed Bug description: [ Impact ] The noble/linux-raspi kernel fails to build from source (FTBFS noble- stable-2026-06-16). Rebasing onto Ubuntu-6.8.0-136.136 pulled in a broken stable backport whose defect is latent in the generic/master kernel — master does not compile the Broadcom ASP2 driver — but becomes a fatal compile error in linux-raspi, which enables it on arm64 (CONFIG_BCMASP: “Required for Pi (not in master)”). compiling drivers/net/ethernet/broadcom/asp2/bcmasp_intf.o: bcmasp_intf.c:675:37: error: 'struct phy_device' has no member named 'eee_cfg' bcmasp_intf.c:677:27: error: 'struct phy_device' has no member named 'enable_tx_lpi' bcmasp_intf.c:1081:23: error: 'struct phy_device' has no member named 'eee_cfg' bcmasp_intf.c:1364:41: error: 'struct phy_device' has no member named 'eee_cfg' bcmasp_intf.c:1416:53: error: 'struct phy_device' has no member named 'eee_cfg' Commit e57cfd7faf78 (“net: bcm: asp2: convert to phylib managed EEE”, upstream 21f56ad1b211) was pulled in only as Stable-dep-of: cbfa5be2bf64 (“net: bcmasp: fix double free of WoL irq”). The conversion makes the driver consume phylib managed-EEE fields (phydev->eee_cfg, phydev->enable_tx_lpi) whose infrastructure was never backported to Noble 6.8 — the managed-EEE consumer was dragged in without its infrastructure. The commit is present in master tags (132.x → 136.136) but master CI stays green because it does not build this driver. [ Fix ] Clean revert of the managed-EEE conversion. The three EEE commits sit beneath a stack (asp-v3.0, the WoL fix, asp-v2.0 removal, probe/clk fixes) that touches the same files, so a zero-hand-edit revert unwinds 10 commits newest-first down to the EEE base (d55c64e4ae98 .. cec1550ce9b3), restoring self-managed EEE. ASP 2.2 support (fa6cc48ea828) is outside the conflict path and is preserved. # Revert commit Reverts in-tree Subject 1 d55c64e4ae98 bfc6bba5abff net: bcmasp: Fix network filter wake for asp-3.0 2 fb1b8c9e8dd7 e307cd953e52 net: bcmasp: Restore programming of TX map vector register 3 0c01abc7dcc9 c2ed77c1f649 net: bcmasp: fix double disable of clk 4 9fcea88c77d8 605c2d7260f5 net: bcmasp: Add support for asp-v3.0 5 fe845d76a9fa 14fa5d8ff619 net: bcmasp: fix double free of WoL irq 6 2bab11107ddf 3f28a3564218 net: bcmasp: streamline early exit in probe 7 88d4b5fa1300 bcbbececeea4 net: bcmasp: Remove support for asp-v2.0 8 ff089f3a67cc e57cfd7faf78 * net: bcm: asp2: convert to phylib managed EEE 9 26f4ed96942e 8d2cc390d968 * net: bcm: asp2: remove tx_lpi_enabled 10 cec1550ce9b3 d1943caf8cd3 * net: bcm: asp2: fix LPI timer handling [ Test Plan ] Kernel should compile properly after patch application. Build noble/linux-raspi (arm64) with CONFIG_BCMASP=m [ Other Info ] Culprit commit: e57cfd7faf78 (bcmasp managed-EEE), in Ubuntu-6.8.0-136.136. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2159608/+subscriptions
[Bug 2158934] Re: Regression related to IOMMU grouping
I updated my regular PC to the new version and it works. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158934 Title: Regression related to IOMMU grouping Status in linux package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Bug description: Title: Regression: PCI commit 7a126c1b6cfa ("Enable ACS after configuring IOMMU for OF platforms") merges IOMMU groups on AMD x86, breaks VFIO passthrough — needs revert 817daf163312 backported Package: linux (Ubuntu) — noble, 6.8 kernel Is this a regression? Yes. Summary Upstream commit 7a126c1b6cfa ("PCI: Enable ACS after configuring IOMMU for OF platforms") was backported into Ubuntu's noble 6.8 kernel in 6.8.0-130.130 (as part of syncing to upstream stable v6.12.75; see changelog entry for LP: #2150809). This commit moves pci_enable_acs() into pci_dma_configure(), which runs on all platforms, not just OF/Device-Tree ones. On AMD x86 systems this changes ACS evaluation timing relative to IOMMU group assignment, causing devices that previously sat in isolated IOMMU groups to merge into one — breaking VFIO PCI passthrough. This is a known upstream regression, already fixed via revert commit 817daf163312 ("PCI: Revert 'Enable ACS after configuring IOMMU for OF platforms'"), bisected and confirmed on AMD-Vi hardware. See: https://forum.level1techs.com/t/iommu-group-regression-in-linux-kernel-6-12-75/247479 The revert is absent from Ubuntu's noble 6.8 changelogs from 6.8.0-130.130 through 6.8.0-134.134. Impact VFIO PCI passthrough fails with: vfio 0000:0b:00.0: group 2 is not viable Please ensure all devices within the iommu_group are bound to their vfio bus driver. Reproduction (my system) 6.8.0-124-generic (pre-regression): two AMD 1022:1453 GPP bridges, each with a downstream NVIDIA GP107 GPU, sit in separate IOMMU groups (16 and 17). 6.8.0-134-generic (regressed): the same two bridges and both GPUs merge into a single IOMMU group. Both kernels use identical cmdline (amd_iommu iommu=pt) and identical vfio-pci binding via /etc/modprobe.d/vfio.conf (subsystem-ID matched). System info CPU/chipset: AMD Family 17h (Zen), AMD 400-series chipset GPUs: 2x NVIDIA GP107 [GTX 1050 Ti] (10de:1c82) + audio functions (10de:0fb9) Working: 6.8.0-124-generic (6.8.0-124.124) Broken: 6.8.0-134-generic (6.8.0-134.134) Requested fix Backport 817daf163312 into the noble 6.8 stable branch. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-134-generic 6.8.0-134.134 ProcVersionSignature: Ubuntu 6.8.0-134.134-generic 6.8.12 Uname: Linux 6.8.0-134-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: macro 2576 F.... wireplumber /dev/snd/controlC0: macro 2576 F.... wireplumber /dev/snd/seq: macro 2574 F.... pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jul 1 17:29:33 2026 InstallationDate: Installed on 2018-10-20 (2811 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-134-generic root=UUID=6eb14018-7030-43e9-bfbd-634e324040e2 ro quiet splash amd_iommu=on iommu=pt vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-134-generic N/A linux-backports-modules-6.8.0-134-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.27 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1001 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VII HERO (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1001:bd09/27/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIIHERO(WI-FI):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: 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/2158934/+subscriptions
[Bug 2161093] Re: Black screen after boot with kernel 7.0.0-28-generic on AMD Radeon RX 580
Additional information: - The system boots successfully with kernel 6.17.0-40-generic. - The problem occurs only with kernel 7.0.0-28-generic. - Kernel command line: quiet splash amdgpu.dc=0 acpi_enforce_resources=lax The amdgpu driver appears to initialize successfully according to the previous boot journal, but the screen becomes black immediately after the boot splash. This issue is reproducible on every boot with kernel 7.0.0-28-generic. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161093 Title: Black screen after boot with kernel 7.0.0-28-generic on AMD Radeon RX 580 Status in linux package in Ubuntu: New Bug description: After installing the latest system updates on KDE neon, my system no longer boots into the graphical desktop when using kernel 7.0.0-28-generic. Hardware: - CPU: AMD Ryzen 5 1600 - GPU: AMD Radeon RX 580 8 GB (Polaris) Symptoms: - GRUB loads normally. - The boot logo is displayed. - After that the screen becomes completely black. - Ctrl+Alt+F1...F6 do not switch to a TTY. - Ctrl+Alt+Del reboots the computer. Booting the previous kernel (6.17.0-40-generic) on the same installation works normally. The issue started immediately after installing system updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161093/+subscriptions
[Bug 2161093] [NEW] Black screen after boot with kernel 7.0.0-28-generic on AMD Radeon RX 580
Public bug reported: After installing the latest system updates on KDE neon, my system no longer boots into the graphical desktop when using kernel 7.0.0-28-generic. Hardware: - CPU: AMD Ryzen 5 1600 - GPU: AMD Radeon RX 580 8 GB (Polaris) Symptoms: - GRUB loads normally. - The boot logo is displayed. - After that the screen becomes completely black. - Ctrl+Alt+F1...F6 do not switch to a TTY. - Ctrl+Alt+Del reboots the computer. Booting the previous kernel (6.17.0-40-generic) on the same installation works normally. The issue started immediately after installing system updates. ** 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/2161093 Title: Black screen after boot with kernel 7.0.0-28-generic on AMD Radeon RX 580 Status in linux package in Ubuntu: New Bug description: After installing the latest system updates on KDE neon, my system no longer boots into the graphical desktop when using kernel 7.0.0-28-generic. Hardware: - CPU: AMD Ryzen 5 1600 - GPU: AMD Radeon RX 580 8 GB (Polaris) Symptoms: - GRUB loads normally. - The boot logo is displayed. - After that the screen becomes completely black. - Ctrl+Alt+F1...F6 do not switch to a TTY. - Ctrl+Alt+Del reboots the computer. Booting the previous kernel (6.17.0-40-generic) on the same installation works normally. The issue started immediately after installing system updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161093/+subscriptions
[Bug 2161011] Re: MSI Prestige 14 H: ELAN I2C touchpad stops working after NVIDIA runtime suspend (nouveau)
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161011 Title: MSI Prestige 14 H: ELAN I2C touchpad stops working after NVIDIA runtime suspend (nouveau) Status in linux package in Ubuntu: New Bug description: Hardware Laptop: MSI Prestige 14 H B13UCX-632NEU Mainboard: MS-14F1 BIOS: E14F1IMS.513 2024-03-28 Operating System: Ubuntu 24.04 LTS Kernel: 6.8.0-134-generic Graphics: - Intel Raptor Lake-P UHD Graphics - NVIDIA GeForce RTX 2050 (GA107M) - nouveau driver Touchpad: ELAN0307:00 Vendor/Product ID: 04F3:3282 Driver: i2c_hid_acpi + hid_multitouch Problem The ELAN touchpad works normally immediately after boot. Approximately 10-20 seconds after the graphical session starts, the touchpad stops responding completely. The touchpad is still detected correctly by the kernel and by libinput, but it no longer generates any pointer events. An external USB mouse continues to work normally. Investigation The following was verified: - Touchpad hardware is functional. - The problem is reproducible after every reboot. - i2c_hid_acpi and hid_multitouch are loaded correctly. - libinput detects the touchpad normally. - Runtime power management for the touchpad itself is already disabled. - The problem is not caused by the USB mouse. The problem appears to be related to NVIDIA runtime power management. When the NVIDIA device 0000:01:00.0 enters runtime suspend, the touchpad stops generating events. The following command alone is NOT sufficient: echo on > /sys/bus/pci/devices/0000:01:00.0/power/control However, the following sequence restores the touchpad immediately and is reproducible every time: echo auto > /sys/bus/pci/devices/0000:01:00.0/power/control sleep 2 echo on > /sys/bus/pci/devices/0000:01:00.0/power/control Immediately after this transition the touchpad starts working again. A permanent workaround was implemented using a systemd service which performs this sequence approximately 10 seconds after the graphical session starts. After this workaround the touchpad works reliably. Expected behaviour Runtime power management of the NVIDIA GPU should not cause the ELAN I2C HID touchpad to stop generating input events. Additional observations This appears to be an interaction between: - nouveau runtime power management - NVIDIA PCI runtime suspend - MSI firmware / ACPI - Intel I2C controller - ELAN I2C HID touchpad rather than a failure of the touchpad driver itself. The issue is fully reproducible on every boot. If additional logs or testing are needed, I am willing to help reproduce the issue and test proposed fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161011/+subscriptions
[Bug 2160302] Re: Drop DEP-8 tests from kernel packages
** Changed in: linux (Ubuntu Stonking) Status: In Progress => Fix Committed -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2160302 Title: Drop DEP-8 tests from kernel packages Status in linux package in Ubuntu: Fix Committed Status in linux source package in Jammy: Triaged Status in linux source package in Noble: Triaged Status in linux source package in Resolute: Triaged Status in linux source package in Stonking: Fix Committed Bug description: == SRU Justification == Impact: We added DEP-8 tests to the kernel package when there was no other testing. Today we do much more thorough regression testing internally (RT is a superset of kernel ADT). Given that generally ADT is already struggling to cope and we literally get no added value from running the same tests in ADT and RT lets drop the tests from ADT. This does not change the fact that the tests of other packages with relations to the kernel get run in ADT for each new kernel (DKMS, snapd, systemd, glibc, ...). Fix: Delete debian/tests from the kernel source package. Testcase: The kernel package stops showing as separate test run on ADT. Other packages get still triggered for new kernel uploads. Regression Potential: Possibly the missing test gets flagged on the first modified upload and has to be accepted. Otherwise nothing should hard rely on those tests to be run in ADT. And they still run for RT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160302/+subscriptions
[Bug 2161036] Re: [SRU] Fix incorrect boot_display reporting on multi-GPU systems
** Changed in: hwe-next Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-oem-7.0 (Ubuntu Resolute) Status: New => In Progress ** Changed in: linux (Ubuntu Resolute) Importance: Undecided => Medium ** Changed in: linux-oem-6.17 (Ubuntu) Importance: Undecided => Medium ** Changed in: hwe-next Assignee: (unassigned) => AaronMa (mapengyu) ** Changed in: linux-oem-6.17 (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-oem-7.0 (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Noble) Status: New => Won't Fix ** Changed in: linux-oem-6.17 (Ubuntu Resolute) Importance: Undecided => Medium ** Changed in: linux-oem-7.0 (Ubuntu Resolute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Resolute) Status: New => In Progress ** Changed in: linux-oem-6.17 (Ubuntu Noble) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Stonking) Status: New => In Progress ** Changed in: linux-oem-7.0 (Ubuntu Noble) Importance: Undecided => Medium -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161036 Title: [SRU] Fix incorrect boot_display reporting on multi-GPU systems Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.17 package in Ubuntu: New Status in linux-oem-7.0 package in Ubuntu: New Status in linux source package in Noble: Won't Fix Status in linux-oem-6.17 source package in Noble: In Progress Status in linux-oem-7.0 source package in Noble: New Status in linux source package in Resolute: In Progress Status in linux-oem-6.17 source package in Resolute: New Status in linux-oem-7.0 source package in Resolute: In Progress Status in linux source package in Stonking: In Progress Status in linux-oem-6.17 source package in Stonking: New Status in linux-oem-7.0 source package in Stonking: New Bug description: [SRU Justification] [Impact] On multi-GPU systems, a VGA-compatible device that is not driving the display can incorrectly be reported as the primary graphics device through the boot_display sysfs attribute. [Fix] Apply upstream commit 596b3678326d3d1aed7c19423b6746f1ce09688a ("x86/video: Only fall back to vga_default_device() without screen info"). When framebuffer screen information is valid, use it exclusively to identify the primary device. Fall back to vga_default_device() only when no framebuffer has been set up. [Test Plan] Boot a multi-GPU system and verify that boot_display identifies only the GPU backing the framebuffer. Verify fallback behavior when no framebuffer has been initialized. [Where problems could occur] The change is limited to primary display-device detection in arch/x86/video/video-common.c. The main risk is incorrect identification of the primary GPU on systems with unusual or incomplete framebuffer information. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2161036/+subscriptions
[Bug 2161036] Re: [SRU] Fix incorrect boot_display reporting on multi-GPU systems
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu ** Also affects: linux-oem-6.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-7.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.17 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-7.0 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Resolute) Importance: Undecided Status: New ** Also affects: linux-oem-6.17 (Ubuntu Resolute) Importance: Undecided Status: New ** Also affects: linux-oem-7.0 (Ubuntu Resolute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Stonking) Importance: Undecided Status: New ** Also affects: linux-oem-6.17 (Ubuntu Stonking) Importance: Undecided Status: New ** Also affects: linux-oem-7.0 (Ubuntu Stonking) 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/2161036 Title: [SRU] Fix incorrect boot_display reporting on multi-GPU systems Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.17 package in Ubuntu: New Status in linux-oem-7.0 package in Ubuntu: New Status in linux source package in Noble: New Status in linux-oem-6.17 source package in Noble: New Status in linux-oem-7.0 source package in Noble: New Status in linux source package in Resolute: New Status in linux-oem-6.17 source package in Resolute: New Status in linux-oem-7.0 source package in Resolute: New Status in linux source package in Stonking: New Status in linux-oem-6.17 source package in Stonking: New Status in linux-oem-7.0 source package in Stonking: New Bug description: [SRU Justification] [Impact] On multi-GPU systems, a VGA-compatible device that is not driving the display can incorrectly be reported as the primary graphics device through the boot_display sysfs attribute. [Fix] Apply upstream commit 596b3678326d3d1aed7c19423b6746f1ce09688a ("x86/video: Only fall back to vga_default_device() without screen info"). When framebuffer screen information is valid, use it exclusively to identify the primary device. Fall back to vga_default_device() only when no framebuffer has been set up. [Test Plan] Boot a multi-GPU system and verify that boot_display identifies only the GPU backing the framebuffer. Verify fallback behavior when no framebuffer has been initialized. [Where problems could occur] The change is limited to primary display-device detection in arch/x86/video/video-common.c. The main risk is incorrect identification of the primary GPU on systems with unusual or incomplete framebuffer information. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2161036/+subscriptions
[Bug 2158934] Re: Regression related to IOMMU grouping
It actually should be released now (as of yesterday Jul-16) in Ubuntu-6.8.0-136.136 ** Changed in: linux (Ubuntu Noble) Status: Fix Committed => Fix Released -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158934 Title: Regression related to IOMMU grouping Status in linux package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Bug description: Title: Regression: PCI commit 7a126c1b6cfa ("Enable ACS after configuring IOMMU for OF platforms") merges IOMMU groups on AMD x86, breaks VFIO passthrough — needs revert 817daf163312 backported Package: linux (Ubuntu) — noble, 6.8 kernel Is this a regression? Yes. Summary Upstream commit 7a126c1b6cfa ("PCI: Enable ACS after configuring IOMMU for OF platforms") was backported into Ubuntu's noble 6.8 kernel in 6.8.0-130.130 (as part of syncing to upstream stable v6.12.75; see changelog entry for LP: #2150809). This commit moves pci_enable_acs() into pci_dma_configure(), which runs on all platforms, not just OF/Device-Tree ones. On AMD x86 systems this changes ACS evaluation timing relative to IOMMU group assignment, causing devices that previously sat in isolated IOMMU groups to merge into one — breaking VFIO PCI passthrough. This is a known upstream regression, already fixed via revert commit 817daf163312 ("PCI: Revert 'Enable ACS after configuring IOMMU for OF platforms'"), bisected and confirmed on AMD-Vi hardware. See: https://forum.level1techs.com/t/iommu-group-regression-in-linux-kernel-6-12-75/247479 The revert is absent from Ubuntu's noble 6.8 changelogs from 6.8.0-130.130 through 6.8.0-134.134. Impact VFIO PCI passthrough fails with: vfio 0000:0b:00.0: group 2 is not viable Please ensure all devices within the iommu_group are bound to their vfio bus driver. Reproduction (my system) 6.8.0-124-generic (pre-regression): two AMD 1022:1453 GPP bridges, each with a downstream NVIDIA GP107 GPU, sit in separate IOMMU groups (16 and 17). 6.8.0-134-generic (regressed): the same two bridges and both GPUs merge into a single IOMMU group. Both kernels use identical cmdline (amd_iommu iommu=pt) and identical vfio-pci binding via /etc/modprobe.d/vfio.conf (subsystem-ID matched). System info CPU/chipset: AMD Family 17h (Zen), AMD 400-series chipset GPUs: 2x NVIDIA GP107 [GTX 1050 Ti] (10de:1c82) + audio functions (10de:0fb9) Working: 6.8.0-124-generic (6.8.0-124.124) Broken: 6.8.0-134-generic (6.8.0-134.134) Requested fix Backport 817daf163312 into the noble 6.8 stable branch. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-134-generic 6.8.0-134.134 ProcVersionSignature: Ubuntu 6.8.0-134.134-generic 6.8.12 Uname: Linux 6.8.0-134-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: macro 2576 F.... wireplumber /dev/snd/controlC0: macro 2576 F.... wireplumber /dev/snd/seq: macro 2574 F.... pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Jul 1 17:29:33 2026 InstallationDate: Installed on 2018-10-20 (2811 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-134-generic root=UUID=6eb14018-7030-43e9-bfbd-634e324040e2 ro quiet splash amd_iommu=on iommu=pt vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-134-generic N/A linux-backports-modules-6.8.0-134-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.27 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/27/2018 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1001 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VII HERO (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1001:bd09/27/2018:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIIHERO(WI-FI):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: 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/2158934/+subscriptions
[Bug 2161053] [NEW] Backlight brightness control breaks in 7.0.0-28.28
Public bug reported: Kubuntu 26.04: With the recent 7.0.0-28.28 kernel, backlight brightness control completely breaks and causes the screen to go to max brightness. No user interaction in the GUI or via the brightness control keys on laptops is able to alter mentioned brightness setting. Steps to reproduce: On systems with screen brightness control, update to 7.0.0-28.28 and try to alter mentioned setting. Expected result: Brightness should change, either by using the GUI-based controls or the dedicated shortcuts on most laptops ("Fn-keys" and similar setups). Workaround: Booting into the previous 7.0.0-27 kernel solves the issue. Find the debug info regarding the test system attached. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Jul 17 08:59:40 2026 InstallationDate: Installed on 2025-12-13 (216 days ago) InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U749 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-28-generic root=UUID=xxxx ro i8042.nomux=1 i8042.reset 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-04-12 (96 days ago) dmi.bios.date: 03/28/2025 dmi.bios.release: 2.31 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 2.31 dmi.board.vendor: FUJITSU dmi.board.version: B4 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK U749 dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK U749 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session ** Description changed: Kubuntu 26.04: With the recent 7.0.0-28.28 kernel, backlight brightness control completely breaks and causes the screen to go to max brightness. No user interaction in the GUI or via the brightness control keys on laptops is able to alter mentioned brightness setting. Steps to reproduce: On systems with screen brightness control, update to 7.0.0-28.28 and try to alter mentioned setting. Expected result: Brightness should change, either by using the GUI-based controls or the dedicated shortcuts on most laptops ("Fn-keys" and similar setups). Workaround: Booting into the previous 7.0.0-27 kernel solves the issue. Find the debug info regarding the test system attached. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 - AudioDevicesInUse: - USER PID ACCESS COMMAND - /dev/snd/controlC0: pascal 1687 F.... wireplumber - /dev/snd/seq: pascal 1666 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Jul 17 08:59:40 2026 InstallationDate: Installed on 2025-12-13 (216 days ago) InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U749 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-28-generic root=UUID=cb8b7c20-c2e6-44cf-a885-f622cd70b94f ro i8042.nomux=1 i8042.reset 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-04-12 (96 days ago) dmi.bios.date: 03/28/2025 dmi.bios.release: 2.31 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 2.31 - dmi.board.name: FJNB2CB dmi.board.vendor: FUJITSU dmi.board.version: B4 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK U749 dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion2.31:bd03/28/2025:br2.31:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU749:pvr10601736746:rvnFUJITSU:rnFJNB2CB:rvrB4:cvnFUJITSU:ct10:cvrLIFEBOOKU749:skuSK01:pfaLIFEBOOK-FTS: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK U749 - dmi.product.sku: SK01 - dmi.product.version: 10601736746 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED ** Description changed: Kubuntu 26.04: With the recent 7.0.0-28.28 kernel, backlight brightness control completely breaks and causes the screen to go to max brightness. No user interaction in the GUI or via the brightness control keys on laptops is able to alter mentioned brightness setting. Steps to reproduce: On systems with screen brightness control, update to 7.0.0-28.28 and try to alter mentioned setting. Expected result: Brightness should change, either by using the GUI-based controls or the dedicated shortcuts on most laptops ("Fn-keys" and similar setups). Workaround: Booting into the previous 7.0.0-27 kernel solves the issue. Find the debug info regarding the test system attached. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Jul 17 08:59:40 2026 InstallationDate: Installed on 2025-12-13 (216 days ago) InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U749 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-28-generic root=UUID=cb8b7c20-c2e6-44cf-a885-f622cd70b94f ro i8042.nomux=1 i8042.reset 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-04-12 (96 days ago) dmi.bios.date: 03/28/2025 dmi.bios.release: 2.31 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 2.31 dmi.board.vendor: FUJITSU dmi.board.version: B4 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK U749 - dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion2.31:bd03/28/2025:br2.31:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU749:pvr10601736746:rvnFUJITSU:rnFJNB2CB:rvrB4:cvnFUJITSU:ct10:cvrLIFEBOOKU749:skuSK01:pfaLIFEBOOK-FTS: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK U749 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161053/+attachment/5982748/+files/WifiSyslog.txt ** Description changed: Kubuntu 26.04: With the recent 7.0.0-28.28 kernel, backlight brightness control completely breaks and causes the screen to go to max brightness. No user interaction in the GUI or via the brightness control keys on laptops is able to alter mentioned brightness setting. Steps to reproduce: On systems with screen brightness control, update to 7.0.0-28.28 and try to alter mentioned setting. Expected result: Brightness should change, either by using the GUI-based controls or the dedicated shortcuts on most laptops ("Fn-keys" and similar setups). Workaround: Booting into the previous 7.0.0-27 kernel solves the issue. Find the debug info regarding the test system attached. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Jul 17 08:59:40 2026 InstallationDate: Installed on 2025-12-13 (216 days ago) InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U749 ProcFB: 0 i915drmfb - ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-28-generic root=UUID=cb8b7c20-c2e6-44cf-a885-f622cd70b94f ro i8042.nomux=1 i8042.reset + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-28-generic root=UUID=xxxx ro i8042.nomux=1 i8042.reset 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-04-12 (96 days ago) dmi.bios.date: 03/28/2025 dmi.bios.release: 2.31 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 2.31 dmi.board.vendor: FUJITSU dmi.board.version: B4 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK U749 dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK U749 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161053/+attachment/5982729/+files/AlsaInfo.txt ** Attachment removed: "CRDA.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161053/+attachment/5982730/+files/CRDA.txt ** Attachment removed: "acpidump.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161053/+attachment/5982749/+files/acpidump.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161053/+attachment/5982747/+files/UdevDb.txt ** Attachment removed: "RfKill.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161053/+attachment/5982746/+files/RfKill.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161053/+attachment/5982745/+files/ProcModules.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161053/+attachment/5982744/+files/ProcInterrupts.txt ** Attachment removed: "ProcEnviron.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161053/+attachment/5982743/+files/ProcEnviron.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161053/+attachment/5982742/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161053/+attachment/5982731/+files/CurrentDmesg.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161053/+attachment/5982732/+files/Dependencies.txt ** Attachment removed: "DpkgList.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161053/+attachment/5982733/+files/DpkgList.txt ** Attachment removed: "IwDevWlp0s20f3Link.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161053/+attachment/5982734/+files/IwDevWlp0s20f3Link.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161053/+attachment/5982735/+files/Lspci.txt ** Attachment removed: "Lspci-vt.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161053/+attachment/5982736/+files/Lspci-vt.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161053/+attachment/5982741/+files/ProcCpuinfo.txt ** Attachment removed: "PaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161053/+attachment/5982740/+files/PaInfo.txt ** Attachment removed: "Lsusb-v.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161053/+attachment/5982739/+files/Lsusb-v.txt ** Attachment removed: "Lsusb-t.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161053/+attachment/5982738/+files/Lsusb-t.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161053/+attachment/5982737/+files/Lsusb.txt -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161053 Title: Backlight brightness control breaks in 7.0.0-28.28 Status in linux package in Ubuntu: New Bug description: Kubuntu 26.04: With the recent 7.0.0-28.28 kernel, backlight brightness control completely breaks and causes the screen to go to max brightness. No user interaction in the GUI or via the brightness control keys on laptops is able to alter mentioned brightness setting. Steps to reproduce: On systems with screen brightness control, update to 7.0.0-28.28 and try to alter mentioned setting. Expected result: Brightness should change, either by using the GUI-based controls or the dedicated shortcuts on most laptops ("Fn-keys" and similar setups). Workaround: Booting into the previous 7.0.0-27 kernel solves the issue. Find the debug info regarding the test system attached. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-generic 7.0.0-28.28 ProcVersionSignature: Ubuntu 7.0.0-28.28-generic 7.0.12 Uname: Linux 7.0.0-28-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Jul 17 08:59:40 2026 InstallationDate: Installed on 2025-12-13 (216 days ago) InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U749 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-28-generic root=UUID=xxxx ro i8042.nomux=1 i8042.reset 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-04-12 (96 days ago) dmi.bios.date: 03/28/2025 dmi.bios.release: 2.31 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 2.31 dmi.board.vendor: FUJITSU dmi.board.version: B4 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK U749 dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK U749 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161053/+subscriptions
четверг
[Bug 2160976] Re: dmidecode: DDR5 PMIC0/RCD Revision Number incorrectly reported as "Device Type: Not Installed" on Ubuntu Server 26.04
** 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/2160976 Title: dmidecode: DDR5 PMIC0/RCD Revision Number incorrectly reported as "Device Type: Not Installed" on Ubuntu Server 26.04 Status in linux package in Ubuntu: New Bug description: dmidecode shipped in Ubuntu Server 26.04 incorrectly parses SMBIOS Type 17 DDR5 PMIC0 and RCD Revision Number fields. It prints "Device Type: Not Installed" instead of the actual revision number. This is a dmidecode parsing bug. The same bug exists in the upstream dmidecode source (versions 3.6, 3.7, and current git master). STEPS TO REPRODUCE: 1. Boot a system with DDR5 RDIMMs and SMBIOS >= 3.7. (Tested on Dell PowerEdge, SMBIOS 3.8.0.) 2. Run: sudo dmidecode -t 17 | grep -E "PMIC0|RCD" ACTUAL OUTPUT: PMIC0 Manufacturer ID: Bank 1, Hex 0x97 PMIC0 Device Type: Not Installed RCD Manufacturer ID: Bank 7, Hex 0x32 RCD Device Type: Not Installed EXPECTED OUTPUT: PMIC0 Manufacturer ID: Bank 1, Hex 0x97 PMIC0 Revision Number: 0x0022 RCD Manufacturer ID: Bank 7, Hex 0x32 RCD Revision Number: 0x0011 SMBIOS v3.7.1 CR231 and v3.9 define SMBIOS Type 17 offsets 0x5E and 0x62 as 16-bit Revision Number WORDs for PMIC0 and RCD respectively. The function dmi_memory_revision() in dmidecode.c incorrectly splits the WORD into a high byte ("Device Type") and a low byte ("Device Revision"). The high byte is 0x00, so dmidecode prints "Not Installed". A patch has been submitted to the upstream dmidecode project on Savannah: https://savannah.nongnu.org/patch/?10586 The patch modifies dmi_memory_revision() in dmidecode.c to correctly print the full 16-bit WORD as a Revision Number for DDR5 (mem_type 0x22/0x23). The patch can be used into the Ubuntu dmidecode package and include the fix in the next Ubuntu 26.04 update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2160976/+subscriptions
[Bug 2158971] Re: amdgpu: ring gfx_0.1.0 timeout + page fault on gnome-shell (Rembrandt/YELLOW_CARP, GFX10.3, RTL8852BE notebook)
Confirmed: bug #2158614 matches my symptoms exactly. Same ring timeout pattern (gfx_0.1.0), same gnome-shell victim, same MODE2 reset. Hardware differs (Rembrandt/GFX10.3 vs Granite Ridge) but failure sequence is identical. Marked myself as affected on #2158614. Regarding the mainline kernel test: this is a production machine used for work and teaching; I prefer not to run an unsupported kernel. The coredump attached to this report should provide sufficient data for kernel team analysis. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2158971 Title: amdgpu: ring gfx_0.1.0 timeout + page fault on gnome-shell (Rembrandt/YELLOW_CARP, GFX10.3, RTL8852BE notebook) Status in linux package in Ubuntu: Incomplete Bug description: Hardware: Lenovo IdeaPad Slim 3 (AMD Rembrandt/YELLOW_CARP, 0x1681) Kernel: 6.17.0-35-generic (Ubuntu HWE 24.04) Mesa: 25.2.8-0ubuntu0.24.04.2 Driver: amdgpu (radeonsi, DRM 3.64) Session: GNOME Wayland Symptom: Recurring GPU reset (4 times in 10 days, increasing frequency). Screen freezes for ~2-3 seconds, recovers automatically via MODE2 reset. Process always involved: gnome-shell (cs0 thread). Kernel log pattern on every occurrence: - ring gfx_0.1.0 timeout - [gfxhub] page fault, PERMISSION_FAULTS, client UTCL2/SQC - Ring gfx_0.1.0 reset failed - GPU reset begin / MODE2 reset / GPU reset succeeded AMDGPU coredump attached (captured via udev rule immediately after fault). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2158971/+subscriptions