Public bug reported: Intel IPU7 ISYS drivers landed drivers/staging in v6.17-rc1 commit b7fe4c0019b12 ("media: staging/ipu7: add Intel IPU7 PCI device driver"), and IPU6 ISYS in v6.10-rc1 commit 25fedc021985a ("media: intel/ipu6: add Intel IPU6 PCI device driver"). Neither has any MODULE_FIRMWARE declarations. intel-ipu7 0000:00:05.0: firmware cpd file: intel/ipu/ipu7ptl_fw.bin intel-ipu7 0000:00:05.0: Direct firmware load for intel/ipu/ipu7ptl_fw.bin failed with error -2 intel-ipu7 0000:00:05.0: error -ENOENT: Requesting signed firmware intel/ipu/ipu7ptl_fw.bin failed intel-ipu7 0000:00:05.0: probe with driver intel-ipu7 failed with error -2 ** Affects: ipu6-drivers (Ubuntu) Importance: Undecided Status: New ** Affects: ipu7-drivers (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.17 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-7.0 (Ubuntu) Importance: Undecided Status: New ** Tags: jira-somerville-5231 ** Description changed: + Intel IPU7 ISYS drivers landed drivers/staging in v6.17-rc1 commit + b7fe4c0019b12 ("media: staging/ipu7: add Intel IPU7 PCI device driver"), + and IPU6 ISYS in v6.10-rc1 commit 25fedc021985a ("media: intel/ipu6: add + Intel IPU6 PCI device driver"). Neither has any MODULE_FIRMWARE + declarations. + intel-ipu7 0000:00:05.0: firmware cpd file: intel/ipu/ipu7ptl_fw.bin intel-ipu7 0000:00:05.0: Direct firmware load for intel/ipu/ipu7ptl_fw.bin failed with error -2 intel-ipu7 0000:00:05.0: error -ENOENT: Requesting signed firmware intel/ipu/ipu7ptl_fw.bin failed intel-ipu7 0000:00:05.0: probe with driver intel-ipu7 failed with error -2 ** Also affects: linux-oem-6.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-7.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: ipu7-drivers (Ubuntu) Importance: Undecided Status: New ** Also affects: ipu6-drivers (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/2164611 Title: ipu firmware not packed into initramfs automatically Status in ipu6-drivers package in Ubuntu: New Status in ipu7-drivers package in Ubuntu: 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 Bug description: Intel IPU7 ISYS drivers landed drivers/staging in v6.17-rc1 commit b7fe4c0019b12 ("media: staging/ipu7: add Intel IPU7 PCI device driver"), and IPU6 ISYS in v6.10-rc1 commit 25fedc021985a ("media: intel/ipu6: add Intel IPU6 PCI device driver"). Neither has any MODULE_FIRMWARE declarations. intel-ipu7 0000:00:05.0: firmware cpd file: intel/ipu/ipu7ptl_fw.bin intel-ipu7 0000:00:05.0: Direct firmware load for intel/ipu/ipu7ptl_fw.bin failed with error -2 intel-ipu7 0000:00:05.0: error -ENOENT: Requesting signed firmware intel/ipu/ipu7ptl_fw.bin failed intel-ipu7 0000:00:05.0: probe with driver intel-ipu7 failed with error -2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2164611/+subscriptions
среда
[Bug 2162959] Re: System hangs on shutdown/reboot ~50% of the time since kernel 7.0.0-28 (PCI/ASPM regression)
Additional data point: same regression on the Ubuntu 24.04 LTS HWE kernel, on a mobile AMD Phoenix platform with integrated graphics only, no discrete GPU and no PCIe switch. This may widen the scope beyond the reports so far. ## Hardware - Lenovo ThinkPad P16s Gen 2 AMD (21K90004CK) - GPU: AMD Phoenix1 [1002:15bf], integrated, amdgpu. No discrete GPU present. - BIOS: LENOVO R2FET61W (1.41), 2024-11-15; EC firmware 1.30 (fwupd/LVFS report both as latest available — no pending updates) - NVMe: KIOXIA KXG8AZNV2T04; root on LVM + ext4 - Secure Boot disabled ## Software - Ubuntu 24.04.4 LTS (noble), GNOME - BROKEN: 7.0.0-28-generic (#28~24.04.1, upstream 7.0.12) - BROKEN: 7.0.0-29-generic (#29~24.04.2) - GOOD: 6.17.0-40-generic (#40~24.04.1) — multiple consecutive clean poweroffs - 7.0.0-27 not tested; not offered in the noble HWE stream, so I cannot confirm the -27/-28 boundary reported here. ## Symptoms - Roughly 2 of 3 poweroff attempts hang. - Display goes dark; power LED and keyboard backlight stay lit; fan keeps running. - Never completes power-off; requires holding the power button. - Journal ends at exactly the same point reported in this bug: systemd[1]: Reached target poweroff.target - System Power Off. systemd[1]: Shutting down. systemd-shutdown[1]: Syncing filesystems and block devices. systemd-shutdown[1]: Sending SIGTERM to remaining processes... systemd-journald[456]: Received SIGTERM from PID 1 (systemd-shutdow). systemd-journald[456]: Journal stopped - Magic SysRq at the hang (Alt+SysRq+o) has no effect. ## Isolation already performed — all negative, problem persists - Reproduces from a bare TTY with no desktop session running. - Reproduces with rabbitmq-server, mssql-server and apache2 stopped. - Reproduces with every ACPI wake source disarmed (all entries in /proc/acpi/wakeup set to *disabled, plus mhi0 power/wakeup disabled). - Reproduces with no Thunderbolt dock and no external devices attached. - Reproduces after unloading VirtualBox out-of-tree modules (vboxdrv, vboxnetflt, vboxnetadp) and disabling vboxdrv.service. - Platform power profile (balanced vs power-saver) makes no difference. - Firmware is current; no BIOS or EC update available via LVFS. ## Reboot vs poweroff Initially 5/5 clean reboots on 7.0.0-29 while poweroff was failing ~2 in 3. A reboot hang was observed later, so reboot is affected too, but at a much lower rate than poweroff on this machine. This is consistent with the report here that both paths are affected. ## Firmware observation — possibly relevant to why some platforms hang hard I decompiled this machine's DSDT. `_PTS(5)` routes several SMM calls through a helper that polls a handshake flag in ACPI NVS with no timeout and no iteration bound: OperationRegion (SMI0, SystemIO, 0xB0, 0x02) Field (SMI0, ByteAcc, NoLock, Preserve) { APMC, 8, APMD, 8 } Method (SMI, 5, Serialized) { Acquire (MSMI, 0xFFFF) CMD = Arg0 ERR = 0x01 PAR0 = Arg1 ... PAR3 = Arg4 APMC = 0xF5 While ((ERR == 0x01)) // unbounded { Sleep (0x01) APMC = 0xF5 } Local0 = PAR0 Release (MSMI) Return (Local0) } `_PTS(5)` reaches this via `SCMS(0x0D)` (SMI 0x02) and `AWON(0x05)` (SMI 0x12). If the SMM response is delayed or dropped, the ACPI interpreter spins here indefinitely and the PM1_CNT SLP_TYP/SLP_EN write never happens — which matches the observed state (fully powered, EC alive, no OS). For contrast, Lenovo's own `SECM` method in SSDT1 on this same machine uses the identical polling idiom but bounds it: Local0 = 0x64 While (((\_SB.SCMD != 0x00) && (Local0 != 0x00))) { Sleep (0x01) Local0-- } So the unbounded loop looks like an omission rather than intent. This firmware defect predates the regression — the machine shipped in 2024 and powered off reliably for two years — but it may explain why affected platforms wedge completely instead of merely stalling. ## Not yet tested here - `pcie_aspm=off` (the workaround noted in this bug) - 7.0.0-27, to confirm the boundary Happy to test proposed kernels or collect further data on this platform. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2162959 Title: System hangs on shutdown/reboot ~50% of the time since kernel 7.0.0-28 (PCI/ASPM regression) Status in linux package in Ubuntu: Confirmed Bug description: ### Summary System intermittently hangs during shutdown and reboot on kernel 7.0.0-28-generic and 7.0.0-29-generic. The issue does not occur on 7.0.0-27-generic. ### Symptoms - ~50% of shutdown/reboot attempts result in a hang - Display turns off, but: USB peripherals remain powered (LEDs on keyboard/joystick), power LED on case stays lit, fans keep spinning - System never completes power-off; requires holding the physical power button - Affects both shutdown and reboot (not just power-off) - The issue is a race condition — not 100% reproducible but very frequent ### Reproduction 1. Boot with kernel 7.0.0-28-generic or 7.0.0-29-generic 2. Shut down or reboot the system 3. Approximately 50% of attempts will hang after journal stops (after `systemd-shutdown[1]: Sending SIGTERM to remaining processes...`) ### Bisect Results - **7.0.0-27-generic** (upstream v7.0.6): OK — no hangs - **7.0.0-28-generic** (upstream v7.0.12): BROKEN — hangs ~50% - **7.0.0-29-generic** (upstream v7.0.12 + CVE fixes): BROKEN — hangs ~50% ### Workaround Adding pcie_aspm=off to kernel boot parameters seems to reduce the frequency of the issue but does not fully eliminate it ### Suspected Patches The regression was introduced in 7.0.0-28 which includes a large upstream stable bump (v7.0.6 → v7.0.12). Two ASPM-related patches are the most likely culprits: 1. **`PCI/ASPM: Fix link state exit during switch upstream function removal`** (from upstream v7.0.12 stable) - Directly relevant: the GPU is connected through a PCIe switch (Navi 10 XL Upstream/Downstream Port). This patch modifies behavior during switch upstream function removal, which occurs at shutdown/reboot. A race condition in link state exit could explain the intermittent hang. 2. **`SAUCE: PCI: ASPM: Allow OS to configure ASPM where BIOS is incapable of`** (LP: #2072679) - Ubuntu-specific patch originally targeting Tiger Lake idle states. On AMD X570, the BIOS may intentionally not expose ASPM control; forcing OS control could lead to incorrect link state transitions during teardown. The fact that the GPU sits behind a PCIe switch makes patch #1 especially suspicious — the patch title literally describes the scenario (switch upstream function removal). ### Hardware - **CPU:** AMD Ryzen 7 5800X3D - **Motherboard:** Gigabyte X570 AORUS ELITE - **BIOS:** F40 (2025-10-28), American Megatrends International - **GPU:** AMD Radeon RX 6700 XT (Navi 22) [1002:73df] — connected via PCIe switch (Navi 10 XL Upstream [1002:1478] / Downstream [1002:1479]) - **NIC:** Intel I211 Gigabit - **NVMe:** 2× Phison E18 PCIe4 ### PCIe Topology (relevant) ``` [00:03.1] AMD Starship/Matisse GPP Bridge └─[09:00.0] AMD/ATI Navi 10 XL Upstream Port of PCI Express Switch └─[0a:00.0] AMD/ATI Navi 10 XL Downstream Port of PCI Express Switch ├─[0b:00.0] AMD/ATI Navi 22 (RX 6700 XT) └─[0b:00.1] AMD/ATI Navi 21/23 HDMI/DP Audio Controller ``` ### System Info - **OS:** Ubuntu 26.04 LTS (Resolute) - **Kernel (broken):** 7.0.0-29-generic #29-Ubuntu SMP PREEMPT_DYNAMIC (7.0.12) - **Kernel (working):** 7.0.0-27-generic (7.0.6) - **ASPM policy:** `[default] performance powersave powersupersave` - **ACPI Power Buttons:** PWRB (PNP0C0C:00) + PWRF (LNXPWRBN:00) ### Journal (last entries before hang) ``` systemd[1]: Reached target poweroff.target - System Power Off. systemd[1]: Shutting down. systemd-shutdown[1]: Syncing filesystems and block devices. systemd-shutdown[1]: Sending SIGTERM to remaining processes... systemd-journald[414]: Received SIGTERM from PID 1 (systemd-shutdow). systemd-journald[414]: Journal stopped ``` (System hangs after this point — no further progress, hard power-off required) ### Additional Notes - `amdgpu.runpm=0` was tested on 7.0.0-28 — did NOT help (rules out amdgpu runtime PM) - The `drm_fb_helper_damage_work hogged CPU for >10000us` warning appears in kernel logs, but this may be unrelated - The issue affects both shutdown and reboot equally, ruling out ACPI wakeup GPE issues ### Related - LP: #2072679 (SAUCE: PCI: ASPM: Allow OS to configure ASPM where BIOS is incapable of) - LP: #2156636 (Resolute update: v7.0.12 upstream stable release) ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: tommyq 2222 F.... wireplumber /dev/snd/controlC1: tommyq 2222 F.... wireplumber /dev/snd/controlC0: tommyq 2222 F.... wireplumber /dev/snd/seq: tommyq 2198 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 6 15:37:11 2026 InstallationDate: Installed on 2022-11-11 (1364 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE ProcEnviron: LANG=cs_CZ.UTF-8 LANGUAGE= PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=6e49607c-2ecc-46c8-869f-dca543a37ec6 ro ipv6.disable_ipv6=1 pcie_aspm=off quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RfKill: 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-03-28 (131 days ago) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 10/28/2025 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F40 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF40:bd10/28/2025:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaX570MB: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2162959/+subscriptions
[Bug 2164516] Re: [UBUNTU 22.04] s390/topology: Use zero-based numbering
** 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/2164516 Title: [UBUNTU 22.04] s390/topology: Use zero-based numbering Status in Linux: Triaged Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: New Status in linux source package in Noble: New Status in linux source package in Resolute: New Bug description: Description: s390/topology: Use zero-based numbering Symptom: Ids displayed by 'lscpu -ye' don't match HW Ids Problem: Hardware documentation, the Hardware Management Console and other tools like zmemtopo use zero-based numbering for socket, book, drawer. But the linux kernel displays one-based numbering in sysfs, procfs and lscpu. Reproduction: 'lscpu -ye' Affected Distros: Ubuntu 22.04, 24.04, 26.04 Solution: Correct the indices the kernel gets from HW sysinfo. Upstream-ID: 540f4a4f6ef806a28e794001bb4beac4840a6090 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2164516/+subscriptions
[Bug 2153155] Re: Fix bad audio record quality when volume above 50% on Framework PTL
This bug is awaiting verification that the linux- azure-7.0/7.0.0-1014.14~24.04.1 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- azure-7.0' to 'verification-done-noble-linux-azure-7.0'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure-7.0' to 'verification-failed-noble-linux-azure-7.0'. 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-azure-7.0-v2 verification-needed-noble-linux-azure-7.0 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2153155 Title: Fix bad audio record quality when volume above 50% on Framework PTL 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 source package in Noble: Invalid Status in linux-oem-6.17 source package in Noble: Fix Released Status in linux source package in Resolute: Fix Released Status in linux-oem-6.17 source package in Resolute: Invalid Bug description: [Impact] Framework PTL platform with Realtek ALC295 audio solution will have audio recording quality when the input volume is configure > 50%. [Fix] Fix by backporting the commit: 67c738152207 ("67c738152207") which fix mic boost on particular SSIDs of the Framework machines [Test Case] 1. Boot up the machine of new Framework PTL platforms with Realtek ALC295 audio solution 2. Go to g-s-d and select sound --> input (Internal Microphone) --> Adjust the input volume > 50% 3. Do `arecord` with the internal microphone and play the recorded clips. [Where problems could occur] It only limit the mic boost based on particular SSIDs. The risk of regression is limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2153155/+subscriptions
[Bug 2156559] Re: Fix no sound output device on Dell GhostRider PTL no camera SKU
This bug is awaiting verification that the linux- azure-7.0/7.0.0-1014.14~24.04.1 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- azure-7.0' to 'verification-done-noble-linux-azure-7.0'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure-7.0' to 'verification-failed-noble-linux-azure-7.0'. 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-azure-7.0-v2 verification-needed-noble-linux-azure-7.0 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2156559 Title: Fix no sound output device on Dell GhostRider PTL no camera SKU 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 source package in Noble: New Status in linux-oem-6.17 source package in Noble: Fix Released Status in linux source package in Resolute: Fix Released Status in linux-oem-6.17 source package in Resolute: Fix Committed Bug description: [Impact] SoundWire audio can come up with the wrong topology on Intel SOF systems. Playback or capture paths may not work as expected. Intel SoundWire (SDW) audio codecs may load the wrong topology. [Fix] Always append the dai_type to the DAI link and stream name. Upstream commit c84179a1d36b ("ASoC: Intel: sof_sdw: append dai type to dai link name unconditionally") fix this problem [Test Plan] On the Dell GhostRider PTL no Camera SKU: $ dmesg | grep -i sof $ aplay -l $ arecord -l Play and record audio: $ speaker-test -c 2 -t wav $ arecord -d 5 -f cd /tmp/test.wav && aplay /tmp/test.wav Without patch: wrong or missing topology selection on some configs; playback or capture path does not work as expected. With patch: correct topology loads; playback and capture work. [Where problems could occur] The change makes the dai_type suffix unconditional and drops the old name format. If a topology file still expects the old non-suffixed stream name, partial matching could miss and that topology would fail to bind. The change is limited to DAI link naming in one board driver, so a regression would be no/incorrect audio, not a kernel crash. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2156559/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-aws/5.15.0-1115.122)
All autopkgtests for the newly accepted linux-restricted-modules-aws (5.15.0-1115.122) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.2 (amd64, i386) nvidia-graphics-drivers-390/unknown (armhf) nvidia-graphics-drivers-450-server/450.248.02-0ubuntu0.22.04.1 (amd64) nvidia-graphics-drivers-470-server/470.256.02-0ubuntu0.22.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://ubuntu-archive-team.ubuntu.com/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-aws [1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest- failure/ Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
[Bug 2164570] Re: Le screen is not good, luminosity very low
*** This bug is a duplicate of bug 2161309 *** https://bugs.launchpad.net/bugs/2161309 ** This bug has been marked a duplicate of bug 2161309 Backlight regression -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2164570 Title: Le screen is not good, luminosity very low Status in linux package in Ubuntu: New Bug description: I have this problem since kernel 7.0.0.28 ...hard to see the screen .... I must stay with kernet 7.0.0.14 to be able to work correctly. .... My PC is a DELL 7390 ... Service tag G2RR1Z2 ....Ubuntu 7.0.0-14.14~24.04.3-generic 7.0.0 thanks to see whats happen and correct the problem in a future kernel. Best Regards JP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2164570/+subscriptions
[Bug 2164570] Re: Le screen is not good, luminosity very low
Luminosity means brightnness... -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2164570 Title: Le screen is not good, luminosity very low Status in linux package in Ubuntu: New Bug description: I have this problem since kernel 7.0.0.28 ...hard to see the screen .... I must stay with kernet 7.0.0.14 to be able to work correctly. .... My PC is a DELL 7390 ... Service tag G2RR1Z2 ....Ubuntu 7.0.0-14.14~24.04.3-generic 7.0.0 thanks to see whats happen and correct the problem in a future kernel. Best Regards JP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2164570/+subscriptions
[Bug 2164569] Re: Display regression with 7.0.0-28 and newer. Brightness and resume from suspend problems.
*** This bug is a duplicate of bug 2161309 *** https://bugs.launchpad.net/bugs/2161309 ** This bug has been marked a duplicate of bug 2161309 Backlight regression -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2164569 Title: Display regression with 7.0.0-28 and newer. Brightness and resume from suspend problems. Status in linux package in Ubuntu: New Bug description: Kernel 7.0.0-28-generic and 7.0.0-30-generic have caused a regression with thinkpad T440s where altering built in display brightness ceases to work and resuming the display after waking from sleep fails. Multiple warnings from display drivers provided via journalctl output. Kernel 7.0.0-27-generic does not present this behavior. ``` $ uname -a Linux T440s 7.0.0-30-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Fri Jul 31 18:22:54 UTC 2026 x86_64 GNU/Linux $ journalctl -b -1 | grep -iE "suspend|resume|drm|i915" | tail -80 Aug 18 19:52:44 T440s kernel: ACPI: bus type drm_connector registered Aug 18 19:52:44 T440s kernel: simple-framebuffer simple-framebuffer.0: [drm] Registered 1 planes with drm panic Aug 18 19:52:44 T440s kernel: [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on minor 0 Aug 18 19:52:44 T440s kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device Aug 18 19:52:44 T440s systemd[1]: modprobe@drm.service - Load Kernel Module drm skipped, unmet condition check ConditionKernelModuleLoaded=!drm Aug 18 19:52:46 T440s kernel: i915 0000:00:02.0: [drm] Found haswell/ult (device ID 0a16) integrated display version 7.00 stepping N/A Aug 18 19:52:46 T440s kernel: i915 0000:00:02.0: vgaarb: deactivate vga console Aug 18 19:52:46 T440s kernel: i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=io+mem Aug 18 19:52:46 T440s kernel: i915 0000:00:02.0: [drm] Registered 3 planes with drm panic Aug 18 19:52:46 T440s kernel: [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor 1 Aug 18 19:52:47 T440s kernel: fbcon: i915drmfb (fb0) is primary device Aug 18 19:52:47 T440s kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device Aug 18 19:52:47 T440s kernel: snd_hda_intel 0000:00:03.0: bound 0000:00:02.0 (ops intel_audio_component_bind_ops [i915]) Aug 18 19:52:50 T440s rtkit-daemon[1423]: Handling system-suspend using logind. Aug 18 19:52:51 T440s kwin_wayland_wrapper[1573]: No backend specified, automatically choosing drm Aug 18 20:03:58 T440s systemd-logind[1009]: The system will suspend now! Aug 18 20:03:58 T440s ModemManager[1189]: <msg> [sleep-monitor-systemd] system is about to suspend Aug 18 20:03:58 T440s systemd[1]: Starting systemd-suspend.service - System Suspend... Aug 18 20:03:58 T440s systemd-sleep[4653]: Performing sleep operation 'suspend'... Aug 18 20:03:58 T440s kernel: PM: suspend entry (deep) Aug 18 20:04:15 T440s kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 18 20:04:15 T440s kernel: i915 0000:00:02.0: [drm] CPU PWM1 enabled Aug 18 20:04:15 T440s kernel: WARNING: drivers/gpu/drm/i915/display/intel_display_power.c:1225 at assert_can_disable_lcpll+0x741/0x760 [i915], CPU#3: kworker/u16:19/4673 Aug 18 20:04:15 T440s kernel: Modules linked in: nls_utf8 cifs nls_ucs2_utils cifs_md4 netfs rfcomm snd_seq_dummy snd_hrtimer snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device ccm qrtr cmac algif_hash algif_skcipher af_alg bnep rmi_smbus rmi_core snd_hda_codec_intelhdmi snd_hda_codec_hdmi cmdlinepart spi_nor mtd at24 intel_rapl_msr uvcvideo snd_hda_codec_alc269 videobuf2_vmalloc snd_hda_codec_realtek_lib uvc btusb iwlmvm snd_ctl_led snd_hda_scodec_component videobuf2_memops btmtk snd_hda_codec_generic btrtl videobuf2_v4l2 mac80211 i2c_i801 intel_rapl_common videobuf2_common btbcm x86_pkg_temp_thermal intel_powerclamp videodev btintel snd_hda_intel rapl thinkpad_acpi spi_intel_platform libarc4 think_lmi i2c_smbus mei_pxp mei_hdcp spi_intel binfmt_misc intel_cstate firmware_attributes_class wmi_bmof i2c_mux snd_hda_codec bluetooth iwlwifi nvram mc i915 snd_hda_core snd_intel_dspcfg cfg80211 drm_buddy snd_intel_sdw_acpi ttm mei_me snd_hwdep drm_display_helper intel_smartconnect lpc_ich cec snd_pcm rc_core snd_timer mei Aug 18 20:04:15 T440s kernel: RIP: 0010:assert_can_disable_lcpll+0x747/0x760 [i915] Aug 18 20:04:15 T440s kernel: hsw_disable_lcpll.constprop.0+0x18/0x430 [i915] Aug 18 20:04:15 T440s kernel: hsw_enable_pc8+0x46/0xc0 [i915] Aug 18 20:04:15 T440s kernel: intel_display_power_suspend_late+0x69/0xf0 [i915] Aug 18 20:04:15 T440s kernel: ? intel_uncore_suspend+0x3d/0x50 [i915] Aug 18 20:04:15 T440s kernel: i915_drm_suspend_late+0x7e/0x100 [i915] Aug 18 20:04:15 T440s kernel: i915_pm_suspend_late+0x1d/0x40 [i915] Aug 18 20:04:15 T440s kernel: pm_generic_suspend_late+0x2b/0x40 Aug 18 20:04:15 T440s kernel: pci_pm_suspend_late+0x41/0x60 Aug 18 20:04:15 T440s kernel: ? __pfx_pci_pm_suspend_late+0x10/0x10 Aug 18 20:04:15 T440s kernel: device_suspend_late+0x114/0x2e0 Aug 18 20:04:15 T440s kernel: async_suspend_late+0x21/0x40 Aug 18 20:04:15 T440s kernel: i915 0000:00:02.0: [drm] PCH PWM1 enabled Aug 18 20:04:15 T440s kernel: WARNING: drivers/gpu/drm/i915/display/intel_display_power.c:1232 at assert_can_disable_lcpll+0x5e4/0x760 [i915], CPU#3: kworker/u16:19/4673 Aug 18 20:04:15 T440s kernel: Modules linked in: nls_utf8 cifs nls_ucs2_utils cifs_md4 netfs rfcomm snd_seq_dummy snd_hrtimer snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device ccm qrtr cmac algif_hash algif_skcipher af_alg bnep rmi_smbus rmi_core snd_hda_codec_intelhdmi snd_hda_codec_hdmi cmdlinepart spi_nor mtd at24 intel_rapl_msr uvcvideo snd_hda_codec_alc269 videobuf2_vmalloc snd_hda_codec_realtek_lib uvc btusb iwlmvm snd_ctl_led snd_hda_scodec_component videobuf2_memops btmtk snd_hda_codec_generic btrtl videobuf2_v4l2 mac80211 i2c_i801 intel_rapl_common videobuf2_common btbcm x86_pkg_temp_thermal intel_powerclamp videodev btintel snd_hda_intel rapl thinkpad_acpi spi_intel_platform libarc4 think_lmi i2c_smbus mei_pxp mei_hdcp spi_intel binfmt_misc intel_cstate firmware_attributes_class wmi_bmof i2c_mux snd_hda_codec bluetooth iwlwifi nvram mc i915 snd_hda_core snd_intel_dspcfg cfg80211 drm_buddy snd_intel_sdw_acpi ttm mei_me snd_hwdep drm_display_helper intel_smartconnect lpc_ich cec snd_pcm rc_core snd_timer mei Aug 18 20:04:15 T440s kernel: RIP: 0010:assert_can_disable_lcpll+0x5ea/0x760 [i915] Aug 18 20:04:15 T440s kernel: hsw_disable_lcpll.constprop.0+0x18/0x430 [i915] Aug 18 20:04:15 T440s kernel: hsw_enable_pc8+0x46/0xc0 [i915] Aug 18 20:04:15 T440s kernel: intel_display_power_suspend_late+0x69/0xf0 [i915] Aug 18 20:04:15 T440s kernel: ? intel_uncore_suspend+0x3d/0x50 [i915] Aug 18 20:04:15 T440s kernel: i915_drm_suspend_late+0x7e/0x100 [i915] Aug 18 20:04:15 T440s kernel: i915_pm_suspend_late+0x1d/0x40 [i915] Aug 18 20:04:15 T440s kernel: pm_generic_suspend_late+0x2b/0x40 Aug 18 20:04:15 T440s kernel: pci_pm_suspend_late+0x41/0x60 Aug 18 20:04:15 T440s kernel: ? __pfx_pci_pm_suspend_late+0x10/0x10 Aug 18 20:04:15 T440s kernel: device_suspend_late+0x114/0x2e0 Aug 18 20:04:15 T440s kernel: async_suspend_late+0x21/0x40 Aug 18 20:04:15 T440s kernel: ACPI: PM: Low-level resume complete Aug 18 20:04:15 T440s kernel: xhci_hcd 0000:00:14.0: xHC error in resume, USBSTS 0x411, Reinit Aug 18 20:04:15 T440s systemd-sleep[4653]: System returned from sleep operation 'suspend'. Aug 18 20:04:15 T440s kernel: PM: suspend exit Aug 18 20:04:16 T440s systemd[1]: systemd-suspend.service: Deactivated successfully. Aug 18 20:04:16 T440s systemd[1]: Finished systemd-suspend.service - System Suspend. Aug 18 20:04:16 T440s systemd[1]: Reached target suspend.target - Suspend. Aug 18 20:04:16 T440s systemd[1]: Stopped target suspend.target - Suspend. Aug 18 20:04:16 T440s systemd-logind[1009]: Operation 'suspend' finished. Aug 18 20:04:16 T440s rtkit-daemon[1423]: Resumed scheduling 7 threads. ``` ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-30-generic 7.0.0-30.30 ProcVersionSignature: Ubuntu 7.0.0-30.30-generic 7.0.12 Uname: Linux 7.0.0-30-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Aug 19 11:56:25 2026 InstallationDate: Installed on 2025-06-04 (441 days ago) InstallationMedia: Kubuntu 24.04.2 LTS "Noble Numbat" - Release amd64 (20250215) MachineType: LENOVO 20ARS1GX00 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-30-generic root=UUID=c6b8b31d-7408-4981-8844-9e50585c41a1 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-04-28 (114 days ago) dmi.bios.date: 12/10/2013 dmi.bios.release: 2.17 dmi.bios.vendor: LENOVO dmi.bios.version: GJET67WW (2.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARS1GX00 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: 0784298 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrGJET67WW(2.17):bd12/10/2013:br2.17:efr1.9:svnLENOVO:pn20ARS1GX00:pvrThinkPadT440s:rvnLENOVO:rn20ARS1GX00:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_20AR_BU_Think_FM_ThinkPadT440s:pfaThinkPadT440s: dmi.product.family: ThinkPad T440s dmi.product.name: 20ARS1GX00 dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2164569/+subscriptions
[Bug 2161098] Re: Random hard freezes caused by i915 kernel page fault in eb_relocate_parse_slow on MacBookAir6,2 (Intel HD 5000)acBookAir6,2 (Intel HD 5000)
Hi again, The test package I created has just finished building. It also contains some changes on top of the currently released kernel version, but those should not affect the fix patch I applied. You can install it as follows $ sudo add-apt-repository ppa:canonical-kernel-team/ppa $ sudo apt upgrade # This will install other 7.0.0-31-generic packages required $ sudo apt install path/to/linux-image-unsigned-7.0.0-31-generic_7.0.0-31.31~lp2161098_amd64.deb \ path/to/linux-modules-7.0.0-31-generic_7.0.0-31.31~lp2161098_amd64.deb # DOWNLOADED FROM [1] Don't forget to uninstall the PPA and packages once you're done testing. Some of the commands remove some packages you'll need to reinstall as well, and differ if you want to have the evental HWE kernel (the default for desktops) or the stable kernel. (default for servers) $ sudo apt remove linux-*-7.0.0-31-generic $ sudo add-apt-repository --remove ppa:canonical-kernel-team/ppa # IF YOU WANT THE EVENTUAL HWE KERNELS $ sudo apt install linux-image-generic-hwe-26.04 linux-headers-generic # IF YOU WANT THE STABLE KERNEL $ sudo apt install linux-image-generic linux-headers-generic Please test to see if this fixes the issue and/or creates any new bugs/instability when running typical tasks on your machine. [1]: https://launchpad.net/~cremfuelled/+archive/ubuntu/kernel/+build/33514389 -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161098 Title: Random hard freezes caused by i915 kernel page fault in eb_relocate_parse_slow on MacBookAir6,2 (Intel HD 5000)acBookAir6,2 (Intel HD 5000) Status in linux package in Ubuntu: In Progress Bug description: Hardware: - Apple MacBookAir6,2 - Intel Haswell HD Graphics 5000 (i915) Software: - Ubuntu 26.10 - Mesa 26.0.3 - Kernel 7.0.0-27 and 7.0.0-28 affected - Currently testing kernel 7.0.0-14 Problem: The system randomly hard freezes. The display remains unchanged with no graphical corruption, but the keyboard and mouse become completely unresponsive and only a hard power-off recovers the system. The freezes are not tied to any particular application. One crash happened while running Papers, but other freezes have occurred during normal desktop use. The previous boot journal contains the following kernel oops: BUG: unable to handle page fault Call trace: kfree() eb_relocate_parse_slow [i915] i915_gem_do_execbuffer [i915] i915_gem_execbuffer2_ioctl [i915] The same MacBook Air hardware is completely stable under macOS (including Big Sur), suggesting this is a Linux kernel regression rather than a hardware fault. The issue has occurred multiple times on kernels 7.0.0-27 and 7.0.0-28. I am now testing kernel 7.0.0-14 to determine whether the regression was introduced after that version. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic 7.0.0-14.14 ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: khaled 2072 F.... wireplumber /dev/snd/controlC0: khaled 2072 F.... wireplumber /dev/snd/seq: khaled 2048 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jul 17 16:19:07 2026 InstallationDate: Installed on 2026-07-14 (3 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) IwDevWlp3s0Link: Error: command ['iw', 'dev', 'wlp3s0', 'link'] failed with exit code 255: command failed: Operation not permitted (-1) Connected to <hidden-mac> (on wlp3s0) SSID: <hidden> freq: 5280.0 MachineType: Apple Inc. MacBookAir6,2 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-14-generic root=UUID=b8679823-0d43-482e-99df-035663cbd8cf ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/13/2023 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 478.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-7DF21CB3ED6977E5 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-7DF21CB3ED6977E5 dmi.modalias: dmi:bvnAppleInc.:bvr478.0.0.0.0:bd01/13/2023:br0.1:svnAppleInc.:pnMacBookAir6,2:pvr1.0:rvnAppleInc.:rnMac-7DF21CB3ED6977E5:rvrMacBookAir6,2:cvnAppleInc.:ct10:cvrMac-7DF21CB3ED6977E5:skuSystemSKU#:pfaMacBookAir: dmi.product.family: MacBook Air dmi.product.name: MacBookAir6,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161098/+subscriptions
Re: [Bug 2161309] Re: Backlight regression
Ohh I wanted to inform the necessary parties that I was able to fix my earlier started issue. Thanks for the feedback On Wed, 19 Aug 2026 at 19:01, Krystian Kaniewski <2161309@bugs.launchpad.net> wrote: > ** Also affects: linux (Ubuntu Resolute) > Importance: Undecided > Status: New > > ** Also affects: linux-hwe-7.0 (Ubuntu Resolute) > Importance: Undecided > Status: New > > ** Also affects: linux (Ubuntu Noble) > Importance: Undecided > Status: New > > ** Also affects: linux-hwe-7.0 (Ubuntu Noble) > Importance: Undecided > Status: New > > ** Changed in: linux (Ubuntu Resolute) > Status: New => Fix Committed > > ** Changed in: linux (Ubuntu Resolute) > Assignee: (unassigned) => Krystian Kaniewski (kkaniewski) > > ** Changed in: linux-hwe-7.0 (Ubuntu Noble) > Status: New => Fix Committed > > ** Changed in: linux-hwe-7.0 (Ubuntu Noble) > Importance: Undecided => Critical > > ** Changed in: linux-hwe-7.0 (Ubuntu Noble) > Assignee: (unassigned) => Krystian Kaniewski (kkaniewski) > > ** Changed in: linux (Ubuntu Noble) > Status: New => Invalid > > ** Changed in: linux-hwe-7.0 (Ubuntu Resolute) > Status: New => Invalid > > ** Changed in: linux (Ubuntu Noble) > Assignee: (unassigned) => Krystian Kaniewski (kkaniewski) > > ** Changed in: linux-hwe-7.0 (Ubuntu Resolute) > Assignee: (unassigned) => Krystian Kaniewski (kkaniewski) > > ** Changed in: linux (Ubuntu Resolute) > Importance: Undecided => Critical > > ** Changed in: linux (Ubuntu Resolute) > Importance: Critical => High > > ** Changed in: linux-hwe-7.0 (Ubuntu Noble) > Importance: Critical => High > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (2163479). > https://bugs.launchpad.net/bugs/2161309 > > Title: > Backlight regression > > Status in linux package in Ubuntu: > Fix Committed > Status in linux-hwe-7.0 package in Ubuntu: > Fix Committed > Status in linux source package in Noble: > Invalid > Status in linux-hwe-7.0 source package in Noble: > Fix Committed > Status in linux source package in Resolute: > Fix Committed > Status in linux-hwe-7.0 source package in Resolute: > Invalid > > Bug description: > ----------------------------- > > Possible workaround until 7.0.0-31 kernel is released > Boot with i915.enable_dpcd_backlight=0 parameter > > ----------------------------- > > > ThinkPad T480 > Intel UHD 620 > brightness works on 7.0.0-27 > brightness fails on 7.0.0-28 > /sys/class/backlight/intel_backlight changes but panel does not > > ProblemType: Bug > DistroRelease: Ubuntu 26.04 > Package: linux-image-7.0.0-27-generic 7.0.0-27.27 > ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 > Uname: Linux 7.0.0-27-generic x86_64 > ApportVersion: 2.34.0-0ubuntu2 > Architecture: amd64 > AudioDevicesInUse: > USER PID ACCESS COMMAND > /dev/snd/controlC0: neal 3608 F.... wireplumber > /dev/snd/seq: neal 3589 F.... pipewire > CasperMD5CheckResult: unknown > CurrentDesktop: ubuntu:GNOME > Date: Mon Jul 20 12:47:12 2026 > InstallationDate: Installed on 2026-07-12 (8 days ago) > InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 > (20260423.1) > MachineType: LENOVO 20L6S6L601 > ProcFB: 0 i915drmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic > root=UUID=1cea3fcd-0665-4cb4-a85a-4ebc58d5aed0 ro quiet splash > acpi_backlight=native > crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 09/06/2025 > dmi.bios.release: 1.56 > dmi.bios.vendor: LENOVO > dmi.bios.version: N24ET81W (1.56 ) > dmi.board.asset.tag: Not Available > dmi.board.name: 20L6S6L601 > dmi.board.vendor: LENOVO > dmi.board.version: SDK0J40697 WIN > dmi.chassis.asset.tag: No Asset Information > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: None > dmi.ec.firmware.release: 1.22 > dmi.modalias: > dmi:bvnLENOVO:bvrN24ET81W(1.56):bd09/06/2025:br1.56:efr1.22:svnLENOVO:pn20L6S6L601:pvrThinkPadT480:rvnLENOVO:rn20L6S6L601:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L6_BU_Think_FM_ThinkPadT480:pfaThinkPadT480: > dmi.product.family: ThinkPad T480 > dmi.product.name: 20L6S6L601 > dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 > dmi.product.version: ThinkPad T480 > dmi.sys.vendor: LENOVO > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161309/+subscriptions > > -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2161309 Title: Backlight regression Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-7.0 package in Ubuntu: Fix Committed Status in linux source package in Noble: Invalid Status in linux-hwe-7.0 source package in Noble: Fix Committed Status in linux source package in Resolute: Fix Committed Status in linux-hwe-7.0 source package in Resolute: Invalid Bug description: ----------------------------- Possible workaround until 7.0.0-31 kernel is released Boot with i915.enable_dpcd_backlight=0 parameter ----------------------------- ThinkPad T480 Intel UHD 620 brightness works on 7.0.0-27 brightness fails on 7.0.0-28 /sys/class/backlight/intel_backlight changes but panel does not ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-27-generic 7.0.0-27.27 ProcVersionSignature: Ubuntu 7.0.0-27.27-generic 7.0.6 Uname: Linux 7.0.0-27-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: neal 3608 F.... wireplumber /dev/snd/seq: neal 3589 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 20 12:47:12 2026 InstallationDate: Installed on 2026-07-12 (8 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 20L6S6L601 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-27-generic root=UUID=1cea3fcd-0665-4cb4-a85a-4ebc58d5aed0 ro quiet splash acpi_backlight=native crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2025 dmi.bios.release: 1.56 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET81W (1.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6S6L601 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrN24ET81W(1.56):bd09/06/2025:br1.56:efr1.22:svnLENOVO:pn20L6S6L601:pvrThinkPadT480:rvnLENOVO:rn20L6S6L601:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20L6_BU_Think_FM_ThinkPadT480:pfaThinkPadT480: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6S6L601 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2161309/+subscriptions
вторник
[Bug 2163945] Re: [Noble HWE 7.0][amdgpu][RX 6650 XT] Intermittent poweroff hang; 6.14.0-37 works, 7.0.0-28 and 7.0.0-29 fail
** 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/2163945 Title: [Noble HWE 7.0][amdgpu][RX 6650 XT] Intermittent poweroff hang; 6.14.0-37 works, 7.0.0-28 and 7.0.0-29 fail Status in linux package in Ubuntu: New Bug description: **Title** [Noble HWE 7.0][amdgpu][RX 6650 XT] Intermittent poweroff hang; 6.14.0-37 works, 7.0.0-28 and 7.0.0-29 fail **Description** I am experiencing an intermittent shutdown/poweroff hang after moving from the Ubuntu Noble HWE 6.14 kernel to HWE 7.0. The issue is reproducible with both: * linux-image-7.0.0-28-generic 7.0.0-28.28~24.04.1 * linux-image-7.0.0-29-generic 7.0.0-29.29~24.04.2 The same machine shuts down reliably with: * linux-image-6.14.0-37-generic 6.14.0-37.37~24.04.1 **Hardware** Motherboard: Gigabyte B550M DS3H rev. 1.4 BIOS: FF, 2025-10-28 GPU: AMD Radeon RX 6650 XT (Navi 23), amdgpu driver **Observed behaviour** When the problem occurs, shutdown starts normally and the displays turn off, but the computer does not complete the physical power-off. Reboot does not exhibit the issue. I have never reproduced the problem when rebooting the machine. The issue can also occur with: `sudo poweroff -f` This suggests that the problem is not simply caused by a userspace service failing to stop. **Kernel comparison** 6.14.0-37-generic: Poweroff works reliably. 7.0.0-28-generic: Intermittent poweroff hang. 7.0.0-29-generic: Intermittent poweroff hang. Reboot with the 7.0 kernels: Always works. This therefore appears to be a regression introduced between the Ubuntu HWE 6.14 and HWE 7.0 kernel series. **Shutdown logs** During a failed shutdown, userspace shutdown proceeds normally. Docker completes its shutdown successfully and NetworkManager exits successfully. The journal reaches the final `systemd-shutdown` stage: `systemd-shutdown[1]: Syncing filesystems and block devices.` `systemd-shutdown[1]: Sending SIGTERM to remaining processes...` The journal then stops as expected when systemd-journald is terminated. Shortly before this final shutdown phase, the kernel repeatedly reports messages similar to: `workqueue: drm_fb_helper_damage_work hogged CPU for >10000us, consider switching to WQ_UNBOUND` I do not know whether this DRM warning is causal, but I am mentioning it because it occurs immediately around the shutdown sequence on the affected kernels. **Related AMD shutdown fix** Ubuntu kernel 6.14.0-37 includes the fixes for LP #2115860 (“Poweroff not working consistently”), including several drm/amd shutdown/S5 fixes. However, the relevant shutdown/S5 behaviour appears to already exist in upstream Linux 7.0, so this does not appear to be simply a missing backport of LP #2115860. It may instead be a new regression in the 7.0 kernel series or an interaction exposed by later DRM/AMDGPU changes. **Steps to reproduce** 1. Boot kernel 7.0.0-28-generic or 7.0.0-29-generic. 2. Use the system normally. 3. Request a normal shutdown. 4. Intermittently, the displays turn off but the machine does not complete power-off. The same test has not reproduced the issue under 6.14.0-37-generic. **Expected result** The machine should completely power off. **Actual result** The shutdown sequence reaches its final stage, but the machine intermittently remains powered instead of completing power-off. --- ProblemType: Bug ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 CRDA: N/A CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 22.3 InstallationDate: Installed on 2026-07-22 (27 days ago) InstallationMedia: Linux Mint 22.3 "Zena" - Release amd64 20260108 IwConfig: lo no wireless extensions. enp6s0 no wireless extensions. docker0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B550M DS3H Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=94102f42-dca2-4dbb-a722-190ea16c6d05 ro amdgpu.runpm=0 systemd.log_level=debug systemd.log_target=kmsg printk.devkmsg=on ignore_loglevel ProcVersionSignature: Ubuntu 7.0.0-29.29~24.04.2-generic 7.0.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-7.0.0-29-generic N/A linux-backports-modules-7.0.0-29-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.29 RfKill: Tags: zena Uname: Linux 7.0.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker i2c lpadmin ollama plugdev render sambashare sudo users video _MarkForUpload: True dmi.bios.date: 10/28/2025 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FF dmi.board.asset.tag: Default string dmi.board.name: B550M DS3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFF:bd10/28/2025:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaB550MB: dmi.product.family: B550 MB dmi.product.name: B550M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 CRDA: N/A CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 22.3 InstallationDate: Installed on 2026-07-22 (27 days ago) InstallationMedia: Linux Mint 22.3 "Zena" - Release amd64 20260108 IwConfig: lo no wireless extensions. enp6s0 no wireless extensions. docker0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. B550M DS3H Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=94102f42-dca2-4dbb-a722-190ea16c6d05 ro amdgpu.runpm=0 systemd.log_level=debug systemd.log_target=kmsg printk.devkmsg=on ignore_loglevel ProcVersionSignature: Ubuntu 7.0.0-29.29~24.04.2-generic 7.0.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-7.0.0-29-generic N/A linux-backports-modules-7.0.0-29-generic N/A linux-firmware 20240318.git3b128b60-0ubuntu2.29 RfKill: Tags: zena Uname: Linux 7.0.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker i2c lpadmin ollama plugdev render sambashare sudo users video _MarkForUpload: True dmi.bios.date: 10/28/2025 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FF dmi.board.asset.tag: Default string dmi.board.name: B550M DS3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFF:bd10/28/2025:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550MDS3H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:pfaB550MB: dmi.product.family: B550 MB dmi.product.name: B550M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163945/+subscriptions
[Bug 2163620] Re: [Ubuntu 26.10] : KVM guest boot hangs on POWER11 host when processor compatibility mode is set to POWER10
** 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/2163620 Title: [Ubuntu 26.10] : KVM guest boot hangs on POWER11 host when processor compatibility mode is set to POWER10 Status in linux package in Ubuntu: In Progress Status in linux source package in Stonking: In Progress Bug description: [Impact] On a POWER11 system with the processor compatibility mode set to POWER10, Ubuntu 26.10 guest installation fails to boot on a KVM-enabled host. When a guest is created using virt-install and booted from the Ubuntu 26.10 installation ISO, the boot process hangs during early kernel initialization and the installer does not proceed further. [Fix] Apply the following patches from linux-next: - 884ea0283f4e KVM: PPC: Book3S HV: Validate arch_compat against host compatibility mode - ac3e65ddddf3 KVM: PPC: Introduce KVM_CAP_PPC_COMPAT_CAPS and wire up ioctl - b76fb087efcd KVM: PPC: Book3S HV: Implement compat CPU capability retrieval for KVM on PowerVM - 8735048f54ec KVM: PPC: Book3S HV: Add support for compat CPU capabilities for KVM on PowerNV - c1721e584244 KVM: PPC: Document KVM_PPC_GET_COMPAT_CAPS ioctl [Test Plan] - Setup KVM enabled host with Ubuntu26.10. - Install libvirt and qemu packages required for bringing up GUests - Create and boot an Ubuntu 26.10 KVM guest from the Ubuntu 26.10 installation ISO on a POWER11 LPAR running in POWER10 compatibility mode using the following command: ``` /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 'vm' --machine pseries --memory=10000 --vcpu=10,sockets=1,cores=10,threads=1 --import --nographics --os-variant ubuntu25.10 --serial pty --memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk path=/home/ubuntu26_10.qcow2,bus=scsi,size=50,format=qcow2 --network=bridge=virbr0,model=virtio --boot emulator=/usr/bin/qemu-system-ppc64 --cdrom /home/ubuntu-26.10-snapshot2-live-server-ppc64el.iso ``` [Regression Potential] The change is confined to powerpc nested virtualization code. Users of nested virtualization in powerpc may be affected. --- == Problem Description === On a POWER11 system with the processor compatibility mode set to POWER10, Ubuntu 26.10 guest installation fails to boot on a KVM-enabled host. When a guest is created using virt-install and booted from the Ubuntu 26.10 installation ISO, the boot process hangs during early kernel initialization and the installer does not proceed further. HOST ENV: OS : Ubuntu 26.10 (Stonking Stingray) kernel : 7.0.0-14-generic libvirt : libvirtd (libvirt) 12.0.0 qemu : QEMU emulator version 10.2.1 on host : # lscpu Architecture: ppc64le Byte Order: Little Endian CPU(s): 80 On-line CPU(s) list: 0-79 Model name: POWER10 (architected), altivec supported Model: 2.0 (pvr 0082 0200) Thread(s) per core: 8 Core(s) per socket: 10 Socket(s): 1 Virtualization features: Hypervisor vendor: pHyp Virtualization type: para Caches (sum of all): L1d: 640 KiB (20 instances) L1i: 960 KiB (20 instances) L2: 20 MiB (20 instances) L3: 80 MiB (20 instances) NUMA: NUMA node(s): 3 NUMA node0 CPU(s): NUMA node1 CPU(s): 0-79 NUMA node2 CPU(s): Vulnerabilities: Gather data sampling: Not affected Ghostwrite: Not affected Indirect target selection: Not affected Itlb multihit: Not affected L1tf: Not affected Mds: Not affected Meltdown: Not affected Mmio stale data: Not affected Old microcode: Not affected Reg file data sampling: Not affected Retbleed: Not affected Spec rstack overflow: Not affected Spec store bypass: Not affected Spectre v1: Mitigation; __user pointer sanitization, ori31 speculation barrier enabled Spectre v2: Mitigation; Software count cache flush (hardware accelerated), Software link stack flush Srbds: Not affected Tsa: Not affected Tsx async abort: Not affected Vmscape: Not affected Steps to re-create: =================== - Setup KVM enabled host with Ubuntu26.10. - Install libvirt and qemu packages required for bringing up GUests - Create and boot an Ubuntu 26.10 KVM guest from the Ubuntu 26.10 installation ISO on a POWER11 LPAR running in POWER10 compatibility mode using the following command: --logs-- /usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 'vm' --machine pseries --memory=10000 --vcpu=10,sockets=1,cores=10,threads=1 --import --nographics --os-variant ubuntu25.10 --serial pty --memballoon model=virtio --controller type=scsi,model=virtio-scsi --disk path=/home/ubuntu26_10.qcow2,bus=scsi,size=50,format=qcow2 --network=bridge=virbr0,model=virtio --boot emulator=/usr/bin/qemu-system-ppc64 --cdrom /home/ubuntu-26.10-snapshot2-live-server-ppc64el.iso WARNING CDROM media does not print to the text console by default, so you likely will not see text install output. You might want to use --location. See the man page for examples of using --location with CDROM media Starting install... Allocating 'ubuntu26_10.qcow2' | 50 GB 00:00:00 Creating domain... | 00:00:00 Running text console command: virsh --connect qemu:///system console vm Connected to domain 'vm' Escape character is ^] (Ctrl + ]) Populating /vdevice methods Populating /vdevice/vty@30000000 Populating /vdevice/nvram@71000000 Populating /pci@800000020000000 00 0800 (D) : 1af4 1000 virtio [ net ] 00 1000 (D) : 1af4 1004 virtio [ scsi ] Populating /pci@800000020000000/scsi@2 SCSI: Looking for devices 100000000000000 DISK : "QEMU QEMU HARDDISK 2.5+" 100000100000000 CD-ROM : "QEMU QEMU CD-ROM 2.5+" 00 1800 (D) : 1b36 000d serial bus [ usb-xhci ] 00 2000 (D) : 1af4 1003 virtio [ serial ] 00 2800 (D) : 1af4 1002 legacy-device* 00 3000 (D) : 1af4 1005 legacy-device* No NVRAM common partition, re-initializing... Scanning USB XHCI: Initializing Using default console: /vdevice/vty@30000000 Welcome to Open Firmware Copyright (c) 2004, 2017 IBM Corporation All rights reserved. This program and the accompanying materials are made available under the terms of the BSD License available at http://www.opensource.org/licenses/bsd-license.php Trying to load: from: /pci@800000020000000/scsi@2/disk@100000100000000 ... Successfully loaded Welcome to GRUB! error: couldn't examine /ibm,secure-boot property. error: unrecognized number. GNU GRUB version 2.14 +----------------------------------------------------------------------------+ |*Try or Install Ubuntu Server | | | | | | | | | | | | | | | | | | | | | | | +----------------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, `e' to edit the commands before booting or `c' for a command-line. OF stdout device is: /vdevice/vty@30000000 Preparing to boot Linux version 7.0.0-14-generic (buildd@bos03-ppc64el-029) (powerpc64le-linux-gnu-gcc (Ubuntu 15.2.0-16ubuntu1) 15.2.0, GNU ld (GNU Binutils for Ubuntu) 2.46) #14-Ubuntu SMP PREEMPT_DYNAMIC Mon Apr 13 11:10:37 UTC 2026 (Ubuntu 7.0.0-14.14-generic 7.0.0) Detected machine type: 0000000000000101 command line: BOOT_IMAGE=/casper/vmlinux quiet --- Max number of cores passed to firmware: 2048 (NR_CPUS = 2048) Calling ibm,client-architecture-support... == Comment: #2 == The patches are in ppc next now: c1721e584244 KVM: PPC: Document KVM_PPC_GET_COMPAT_CAPS ioctl 8735048f54ec KVM: PPC: Book3S HV: Add support for compat CPU capabilities for KVM on PowerNV b76fb087efcd KVM: PPC: Book3S HV: Implement compat CPU capability retrieval for KVM on PowerVM ac3e65ddddf3 KVM: PPC: Introduce KVM_CAP_PPC_COMPAT_CAPS and wire up ioctl 884ea0283f4e KVM: PPC: Book3S HV: Validate arch_compat against host compatibility mode Please note that one of the dependent patches had already made it to upstream. e4de1b9cb3b5 ("powerpc/dt_cpu_ftrs: Set CPU_FTR_P11_PVR for Power11 and later processors") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2163620/+subscriptions