пятница

[Bug 2172581] Re: [Regression] amdgpu: horizontal stripe glitches on DisplayPort monitor with RX 9060 XT on 7.0.0-38 (OK on 7.0.0-30)

I just saw it happen on 7.0.0-43 after upgrading today. I'm not sure if it's an intermittent issue that I didn't run into on 7.0.0-42 or if 7.0.0-43 reintroduces the problem -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2172581 Title: [Regression] amdgpu: horizontal stripe glitches on DisplayPort monitor with RX 9060 XT on 7.0.0-38 (OK on 7.0.0-30) Status in linux package in Ubuntu: Confirmed Bug description: Since kernel 7.0.0-38.38 was installed (Oct 14, 2026), I get brief display glitches on an AMD Radeon RX 9060 XT. Booting back into 7.0.0-30.30 makes them disappear completely. Mesa (26.0.8-1ubuntu0.3, installed Aug 26) and linux-firmware-amd-graphics (last updated Jul 25) were unchanged between the two kernels. Symptom: A split-second horizontal stripe or flash across the full width of the screen, drawn over all windows. It appears several times a day, typically when: - moving or resizing windows - scrolling - opening applications (e.g. LibreOffice, Teams) - pressing Enter at the SDDM login screen after a cold boot (seen with both   a wrong and a correct password; not seen on logout/login without reboot) Which monitor: - In-session glitches appear only on the left monitor. After swapping the   primary monitor so applications open on the right one, the glitches stayed   on the left monitor regardless of which apps were there. - Moving the left monitor's cable to a different DisplayPort output on the   GPU did not change anything. - One login glitch was observed on both monitors at the same moment. System: - Kubuntu 26.04 LTS, KDE Plasma 6.6.6, Frameworks 6.24.0, Qt 6.10.2, Wayland - GPU: AMD Radeon RX 9060 XT 16 GB [1002:7590, subsystem 1458:2429],   gfx1200, DCN 4.0.1, VBIOS 113-R906XTGO-F2 - CPU: Ryzen 9 7900X (integrated GPU disabled in BIOS) - Board: MSI B650 GAMING PLUS WIFI (MS-7E26), 32 GB RAM - Monitors (both DisplayPort):   - Left: [model, resolution, refresh rate, VRR on/off]   - Right: [model, resolution, refresh rate, VRR on/off] - Kernel cmdline extras: amdgpu.gpu_recovery=1 amdgpu.runpm=0 Tried on 7.0.0-38 without effect: - power_dpm_force_performance_level=high (set via udev at boot) - amdgpu.dcdebugmask=0x20000 - Disabling the CPU's integrated GPU - Reseating the cable / changing the GPU port Hardware seems fine: a Unigine Heaven run (OpenGL, 1440p, Ultra, extreme tessellation) showed no hardware-type artifacts, and everything is clean on 7.0.0-30. Possibly related (though not 100% sure), also only on 7.0.0-38: the Android Emulator (37.2.12, hardware graphics) alternates between the current and a stale frame when pulling down its notification shade. This is reliably reproducible, and gone on 7.0.0-30. dmesg at boot on 7.0.0-38 shows:   amdgpu 0000:03:00.0: [drm] REG_WAIT timeout 1us * 150000 tries - optc401_disable_crtc line:235 (Not yet checked whether this also appears on 7.0.0-30.) ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Oct 30 11:19:08 2026 InstallationDate: Installed on 2025-08-14 (441 days ago) InstallationMedia: Kubuntu 25.04 "Plucky Puffin" - Release amd64 (20250417) MachineType: Micro-Star International Co., Ltd. MS-7E26 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-7.0.0-38-generic root=UUID=3502296e-5c13-4e5a-a0d3-1ecd4f4367ad ro rootflags=subvol=@ quiet splash resume=UUID=e059f494-d020-4881-b09c-874773a0d2d8 amdgpu.gpu_recovery=1 amdgpu.runpm=0 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-24 (158 days ago) dmi.bios.date: 06/19/2025 dmi.bios.release: 5.35 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.L0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B650 GAMING PLUS WIFI (MS-7E26) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.L0:bd06/19/2025:br5.35:svnMicro-StarInternationalCo.,Ltd.:pnMS-7E26:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB650GAMINGPLUSWIFI(MS-7E26):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7E26 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172581/+subscriptions

[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-oracle/5.15.0-1118.124)

All autopkgtests for the newly accepted linux-restricted-modules-oracle (5.15.0-1118.124) 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, armhf, i386) nvidia-graphics-drivers-450-server/unknown (amd64) nvidia-graphics-drivers-470/unknown (amd64) nvidia-graphics-drivers-470-server/470.256.02-0ubuntu0.22.04.6 (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-oracle [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 2174359] Re: Fix stale NVL PCD-S S0ix_LPM telemetry constants

** 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/2174359 Title: Fix stale NVL PCD-S S0ix_LPM telemetry constants Status in linux package in Ubuntu: New Status in linux-oem-7.3 package in Ubuntu: New Status in linux source package in Resolute: Invalid Status in linux-oem-7.3 source package in Resolute: New Status in linux source package in Stonking: New Status in linux-oem-7.3 source package in Stonking: Invalid Bug description: [Impact] The Nova Lake PCD-S S0ix_LPM telemetry layout changed. The PCD-S telemetry GUID was changed to reflect the layout change, per the client GUID revision rule. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174359/+subscriptions

[Bug 2174384] Re: linux-amd-embedded: Add the MAX96717 and MAX96724 GMSL drivers on the maxim-serdes framework

** 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/2174384 Title: linux-amd-embedded: Add the MAX96717 and MAX96724 GMSL drivers on the maxim-serdes framework Status in linux package in Ubuntu: New Status in linux source package in Resolute: Confirmed Bug description: This bug targets the linux-amd-embedded kernel (Ubuntu 26.04 Resolute, 7.0, amd64). linux-amd-embedded is not yet available in the archive, so the bug is filed against the linux package for now. [Impact] The linux-amd-embedded kernel has no driver for the Maxim MAX96724 GMSL2/3 quad deserializer (only the limited staging MAX96712 driver on arm64), and its MAX96717 serializer driver does not use the Maxim GMSL2/3 serializer and deserializer framework (maxim-serdes). Mainline v7.4-rc1 replaces both with new drivers on the maxim-serdes framework, which is already in linux-amd-embedded (LP: #2174067). [Fix] * Cherry-pick from mainline (v7.4-rc1): - e9159c0dede8 ("dt-bindings: media: i2c: max96717: add support for I2C ATR") - f79e3e2b3f00 ("dt-bindings: media: i2c: max96717: add support for pinctrl/pinconf") - f4dffb66fd35 ("dt-bindings: media: i2c: max96717: add support for MAX9295A") - c89989bb92f8 ("dt-bindings: media: i2c: max96717: add support for MAX96793") - ea15bcd94f0f ("media: i2c: maxim-serdes: add MAX96717 driver") - 458d2429d351 ("dt-bindings: media: i2c: max96712: use pattern properties for ports") - 6a9de7a6a80e ("dt-bindings: media: i2c: max96712: add support for I2C ATR") - 7c829723323b ("dt-bindings: media: i2c: max96712: add support for POC supplies") - 876af7e019db ("dt-bindings: media: i2c: max96712: add support for MAX96724F/R") - 9263d2961cc7 ("dt-bindings: media: i2c: max96712: add control-channel-port property") - bccc36c35947 ("media: i2c: maxim-serdes: add MAX96724 driver") * Backport from mainline (v7.4-rc1), adapted to the v7.0 versions of the removed files: - 2c4d9084a634 ("media: i2c: remove MAX96717 driver") - 9e88bdefadd4 ("staging: media: remove MAX96712 driver") * Enable VIDEO_MAX96724 in the amd-embedded config annotations, keep VIDEO_MAX96717 and drop the removed VIDEO_MAX96712. [Test Plan] * Build the linux-amd-embedded kernel for all flavours and check that updateconfigs passes. * Boot the kernel in an LXD VM and load the max96717 and max96724 modules. [Where problems could occur] The old MAX96717 driver and the staging MAX96712 driver are replaced by the new drivers on the maxim-serdes framework. Users of these devices may need to update their device tree to the new bindings. VIDEO_MAX96712 is no longer built on arm64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174384/+subscriptions

[Bug 2174389] Re: Noble: incorrect backport of io_uring/kbuf: check if target buffer list is still legacy on recycle

** 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/2174389 Title: Noble: incorrect backport of io_uring/kbuf: check if target buffer list is still legacy on recycle Status in linux package in Ubuntu: New Bug description: After finding out https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2167919 I wanted to check if there are more incorrectly backported fixes in Noble kernel. While checking for other backports I found incorrectly resolved upstream commit c2c185be5c85d ("io_uring/kbuf: check if target buffer list is still legacy on recycle") in our 0c4f963808549 backport. Our backport omitted cleanup when a selected legacy buffer cannot be returned to its original group. I would guess that it was resolved this way as this is how upstream did it for v6.6. Problem is, v6.8 is more like v6.18 (where the upstream fix landed) than v6.6 in this context. This is due to https://github.com/torvalds/linux/commit/b3a4dbc89d40 being introduced in v6.7 If you compare the io_destroy_buffers() in v6.6, it iterates over the ctx->io_buffers_pages (as it uses custom allocator which tracks all the pages is allocated) so it doesn't need pointers for individual "objects". This single "slot" in a page is not put into reusable list so the memory is kinda lost but not forever as it will be recovered when the whole page is deallocated eventually. The buffer pointer can be owned by one of 4 objects: - `ctx->io_buffers_cache` (initially or moved from `req->kbuf` in `__io_put_kbuf()` or from `ctx->io_buffers_comp` in `io_refill_buffer_cache()` - `ctx->io_buffers_comp` (moved from `req->kbuf` in `__io_put_kbuf()`) - `bl->buf_list` (moved from `ctx->io_buffers_cache` in `io_add_buffers()`) - `req->kbuf` (moved from `bl->buf_list` inside of `io_provided_buffer_select()`) Before that backported patch, the `io_kbuf_recycle_legacy` would always recycle the buffer by putting it back to the buf_list but now this may not happen and in this case the buffer is not present on any list anymore and `req->kbuf` is cleared so all the pointers for this buffer are lost. If you look at the io_destroy_buffers() in v6.6, it collects all buffers from `bl->buf_list` and from `ctx->io_buffers_comp` back to `ctx->io_buffers_cache` and then frees only buffers on `ctx->io_buffers_cache`. So before the loop is called, the io_buffers_cache consists of: - never used buffers (that were there always - the buffers moved from bl->buf_list - the buffers moved from io_buffers_cache So when io_kbuf_recycle_legacy is called, the buffer is owned by req->kbuf only and is not present on any of those lists. While previously the function would always move the buffer back to bl->buf_list before discarding it, the code can now (after backporting c2c185be5c85d) skip moving it but still clear req->kbuf which was the only reference to it creating a leak. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174389/+subscriptions

[Bug 2174401] Re: GPF in __run_timers (LIST_POISON timer) on 7.0.0-43-generic, reproducible with snap LibreOffice docx>pdf conversion

** 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/2174401 Title: GPF in __run_timers (LIST_POISON timer) on 7.0.0-43-generic, reproducible with snap LibreOffice docx>pdf conversion Status in linux package in Ubuntu: New Bug description: Kernel crashes with a general protection fault in __run_timers (address 0xdead00000000012a, list poison), suggesting a timer freed while still pending. Kdump captured a vmcore. Reproducible: happens when converting a .docx to PDF with the LibreOffice snap (also headless: libreoffice --headless --convert-to pdf). Has happened more than once. At the moment of the crash, the log shows AppArmor DENIED events for snap.libreoffice.libreoffice and snap.prompting-client.daemon (AppArmor prompting active). Kernel: 7.0.0-43-generic #43-Ubuntu, Not tainted Hardware: ASUS ExpertBook B1502CBA, BIOS B1502CBA.317 04/27/2026 Oops: general protection fault, probably for non-canonical address 0xdead00000000012a RIP: 0010:__run_timers+0x1e0/0x2c0 Call Trace (IRQ): run_timer_softirq, handle_softirqs, __irq_exit_rcu, sysvec_apic_timer_interrupt; task: cpuidle_enter_state (swapper/1) Full dmesg attached. vmcore (≈350 MB) available on request. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-43-generic 7.0.0-43.43 ProcVersionSignature: Ubuntu 7.0.0-43.43-generic 7.0.14 Uname: Linux 7.0.0-43-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: kaveen-amarasekara 3986 F.... pipewire kaveen-amarasekara 3997 F.... wireplumber /dev/snd/seq: kaveen-amarasekara 3986 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Nov 13 18:20:55 2026 InstallationDate: Installed on 2026-09-18 (56 days ago) InstallationMedia: Ubuntu 26.04.1 LTS "Resolute Raccoon" - Release amd64 (20260826) MachineType: ASUSTeK COMPUTER INC. ASUS EXPERTBOOK B1502CBA_B1502CBA ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-43-generic root=UUID=3a895c67-1e59-4435-b1d0-e347cf641da2 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2026 dmi.bios.release: 5.26 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: B1502CBA.317 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: B1502CBA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 17.2 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrB1502CBA.317:bd04/27/2026:br5.26:efr17.2:svnASUSTeKCOMPUTERINC.:pnASUSEXPERTBOOKB1502CBA_B1502CBA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnB1502CBA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:pfaASUSEXPERTBOOK: dmi.product.family: ASUS EXPERTBOOK dmi.product.name: ASUS EXPERTBOOK B1502CBA_B1502CBA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174401/+subscriptions

[Bug 2174426] Re: keyboard locked after suspend

** 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/2174426 Title: keyboard locked after suspend Status in linux package in Ubuntu: New Bug description: when we suspend our laptop we can awake it using keyboard but once login screen visible the inbuild keyboard is locked and we can not use anykey (we have to use external or onscreen). 1. then i try unbing and biding atkbd and it worked 2. try updating grub file with GRUB_CMDLINE_LINUX_DEFAULT with bunch of option like i8042.reset,i8042.nupup etc but once suspend its the same issue again ProblemType: Bug DistroRelease: Ubuntu 25.10 Package: linux-image-6.17.0-41-generic 6.17.0-41.41 ProcVersionSignature: Ubuntu 6.17.0-41.41-generic 6.17.13 Uname: Linux 6.17.0-41-generic x86_64 ApportVersion: 2.33.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: dharam 2132 F.... wireplumber /dev/snd/controlC0: dharam 2132 F.... wireplumber /dev/snd/seq: dharam 2109 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Nov 13 22:27:54 2026 InstallationDate: Installed on 2025-12-23 (325 days ago) InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007) MachineType: LENOVO 83KA ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-41-generic root=UUID=b1a5a3ba-e545-4658-ba63-9047089b7228 ro quiet splash apparmor=0 i8042.nopnp crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7 RelatedPackageVersions: firmware-sof N/A linux-firmware 20250901.git993ff19b-0ubuntu1.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/11/2026 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: QACN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76485WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad Slim 3 15AHP10 dmi.ec.firmware.release: 1.26 dmi.modalias: dmi:bvnLENOVO:bvrQACN31WW:bd08/11/2026:br1.31:efr1.26:svnLENOVO:pn83KA:pvrIdeaPadSlim315AHP10:rvnLENOVO:rnLNVNB161216:rvrSDK0T76485WIN:cvnLENOVO:ct10:cvrIdeaPadSlim315AHP10:skuLENOVO_MT_83KA_BU_idea_FM_IdeaPadSlim315AHP10: dmi.product.family: IdeaPad Slim 3 15AHP10 dmi.product.name: 83KA dmi.product.sku: LENOVO_MT_83KA_BU_idea_FM_IdeaPad Slim 3 15AHP10 dmi.product.version: IdeaPad Slim 3 15AHP10 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174426/+subscriptions

[Bug 2174441] Re: [Rembrandt/Radeon 660M] Hard freeze with DMCUB errors and flip_done timeouts, triggered by GNOME Night Light transition with PSR enabled

** 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/2174441 Title: [Rembrandt/Radeon 660M] Hard freeze with DMCUB errors and flip_done timeouts, triggered by GNOME Night Light transition with PSR enabled Status in linux package in Ubuntu: New Bug description: Hardware: Lenovo Yoga 7 14ARB7, AMD Ryzen 5 6600U, Radeon 660M (YELLOW_CARP 1002:1681 rev C2, DCN 3.1.2) Software: Ubuntu 26.04, GNOME on Wayland, kernel 7.0.0-43-generic (also seen on 7.0.0-42), linux-firmware-amd-graphics 20260319.git217ca6e4-0ubuntu3.1 DMUB firmware: 0x0400004A Internal panel: eDP-1, PSR enabled (sink PSR ver 3) Problem: The system freezes completely during normal desktop use (no keyboard/mouse response, only a forced power-off helps). On 2026-11-11 and 2026-11-12 this happened 9 times, often within a few minutes after each reboot. Kernel log before a freeze (2026-11-12): amdgpu 0000:33:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data amdgpu 0000:33:00.0: [drm] *ERROR* [CRTC:364:crtc-0] flip_done timed out amdgpu 0000:33:00.0: [drm] *ERROR* [CONNECTOR:378:eDP-1] commit wait timed out amdgpu 0000:33:00.0: [drm] REG_WAIT timeout 1us * 100000 tries - mpc2_assert_idle_mpcc line:481 amdgpu 0000:33:00.0: [drm] REG_WAIT timeout 1000us * 30 tries - dcn31_wait_for_det_apply line:118 amdgpu 0000:33:00.0: [drm] REG_WAIT timeout 1us * 100000 tries - optc31_disable_crtc line:145 In some freezes nothing is logged at all, presumably because the system hangs before the journal is written to disk. Trigger: GNOME Night Light with automatic schedule (sunset to sunrise) was enabled in early November. GNOME ramps the colour temperature during the hour before sunset. All DMCUB errors in the journal (which goes back to 2026-07-16) fall into that window: 2026-11-02 16:28, 16:47 2026-11-10 15:52 2026-11-11 15:35, 15:42, 15:49, 15:53 2026-11-12 16:01, 16:06, 16:12, 16:39 (local sunset during that period: approx. 17:05 down to 16:45 CET). No DMCUB errors at all between 2026-07-16 and 2026-11-01. Workaround: amdgpu.dcdebugmask=0x10 (PSR disabled), active since 2026-11-12 16:50. Night Light was disabled shortly afterwards as well, so both changes are in effect. No freeze and no DMCUB error since then, including the following afternoon. Possibly related: drm/amd #4141 (similar symptoms on Phoenix/780M), LP #2024774 (older Rembrandt PSR-SU freezes). The attached log is the kernel log of the affected boot on 2026-11-12. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-43-generic 7.0.0-43.43 ProcVersionSignature: Ubuntu 7.0.0-43.43-generic 7.0.14 Uname: Linux 7.0.0-43-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Nov 13 20:38:35 2026 InstallationDate: Installed on 2026-07-16 (120 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 82QF ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-43-generic root=UUID=58bdab56-df28-4954-9a74-857323b15e10 ro quiet splash amdgpu.dcdebugmask=0x10 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: 12/06/2024 dmi.bios.release: 1.48 dmi.bios.vendor: LENOVO dmi.bios.version: K5CN48WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 14ARB7 dmi.ec.firmware.release: 1.45 dmi.modalias: dmi:bvnLENOVO:bvrK5CN48WW:bd12/06/2024:br1.48:efr1.45:svnLENOVO:pn82QF:pvrYoga714ARB7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga714ARB7:skuLENOVO_MT_82QF_BU_idea_FM_Yoga714ARB7:pfaYoga714ARB7: dmi.product.family: Yoga 7 14ARB7 dmi.product.name: 82QF dmi.product.sku: LENOVO_MT_82QF_BU_idea_FM_Yoga 7 14ARB7 dmi.product.version: Yoga 7 14ARB7 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174441/+subscriptions

[Bug 2172416] Re: Laptop doesn't stay in suspend since kernel 7.0.0-38 (btintel_pcie returns -16)

Same here, Thinkpad T14s Gen 6 and 7.0.0-1018-oem -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2172416 Title: Laptop doesn't stay in suspend since kernel 7.0.0-38 (btintel_pcie returns -16) Status in linux package in Ubuntu: Confirmed Bug description: Since the update to kernel 7.0.0-38, my laptop (ThinkPad T14s Gen 6, Lunar Lake) often fails to suspend when I close the lid. It wakes up again right away and retries about every 30 seconds until I re-open the lid. This has happened 10 times since the update. Twice it kept going for about 8 hours (>900 failed attempts each) until the battery ran out. The journal shows this on every failed attempt: Bluetooth: hci0: Timeout (500 ms) on tx completion Bluetooth: hci0: Failed to send frame (-62) Bluetooth: hci0: Timeout (200 ms) on alive interrupt for D2 entry, retry count 0 Bluetooth: hci0: Timeout (200 ms) on alive interrupt for D2 entry, retry count 1 Bluetooth: hci0: Timeout (200 ms) on alive interrupt for D2 entry, retry count 2 btintel_pcie 0000:00:14.7: PM: pci_pm_suspend(): btintel_pcie_suspend [btintel_pcie] returns -16 btintel_pcie 0000:00:14.7: PM: failed to suspend async: error -16 PM: Some devices failed to suspend, or early wake event detected systemd-sleep: Failed to put system to sleep. System resumed again: Device or resource busy I also see "Bluetooth: hci0: Failed to get mac access (-62)" at least once in every boot on 7.0.0-38, never on older kernels. It looks like a regression to me. Counting suspends in my journal: 7.0.0-22: 20 ok, 0 failed 7.0.0-27: 220 ok, 0 failed 7.0.0-31: 16 ok, 0 failed 7.0.0-38: 36 ok, 3520 failed (in 10 lid-close episodes) BIOS and Bluetooth firmware are the same on 7.0.0-31 and 7.0.0-38. The 7.0.0-38 changelog has several btintel/btintel_pcie changes that might be related. It doesn't happen every time: about 1 in 5 suspends on 7.0.0-38 (10 of 46). I haven't found a pattern. When it happens, it shows up in journalctl -b | grep -E 'btintel_pcie.*-16|Failed to put system to sleep' Workaround: a script in /usr/lib/systemd/system-sleep/ that unloads the module before suspend and loads it again after resume. Suspend worked with it so far: case "$1" in pre) modprobe -r btintel_pcie ;; post) modprobe btintel_pcie ;; esac Possibly related upstream (I'm not sure it's the same problem): https://bugzilla.kernel.org/show_bug.cgi?id=221481, with a fix in mainline after 7.3 (commit 12997a385f71). ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-38-generic 7.0.0-38.38 ProcVersionSignature: Ubuntu 7.0.0-38.38-generic 7.0.14 Uname: Linux 7.0.0-38-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: henning 4013 F.... pipewire henning 4022 F.... wireplumber /dev/snd/seq: henning 4013 F.... pipewire CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Oct 28 21:35:26 2026 InstallationDate: Installed on 2026-06-11 (139 days ago) InstallationMedia: Ubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423.1) MachineType: LENOVO 21QXCTO1WW ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-7.0.0-38-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2026 dmi.bios.release: 1.16 dmi.bios.vendor: LENOVO dmi.bios.version: N4IET30W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 21QXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnLENOVO:bvrN4IET30W(1.16):bd06/16/2026:br1.16:efr1.12:svnLENOVO:pn21QXCTO1WW:pvrThinkPadT14sGen6:rvnLENOVO:rn21QXCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21QX_BU_Think_FM_ThinkPadT14sGen6:pfaThinkPadT14sGen6: dmi.product.family: ThinkPad T14s Gen 6 dmi.product.name: 21QXCTO1WW dmi.product.sku: LENOVO_MT_21QX_BU_Think_FM_ThinkPad T14s Gen 6 dmi.product.version: ThinkPad T14s Gen 6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2172416/+subscriptions

четверг

[Bug 2170572] Re: linux-image-7.0.0-38-generic randomly freezes Lenovo Legion 5

I have verified 7.0.0-44.44 fixes this on resolute for me. Similar circumstances (pebble unit tests not snapd, inside a workshop). I was able to reliably hit this, updated only the kernel to this, now it is resolved. --- I made lockups a panic: $ sysctl kernel.softlockup_panic kernel.hardlockup_panic kernel.panic_on_rcu_stall kernel.hung_task_panic kernel.panic kernel.sysrq kernel.softlockup_panic = 1 kernel.hardlockup_panic = 1 kernel.panic_on_rcu_stall = 1 kernel.hung_task_panic = 1 kernel.panic = 10 kernel.sysrq = 184 Also needed to disable kdump and have the panic go into uefi pstore... zfs root is not great for kdump. --- Oops#1 Part3 <4>[ 2834.156165] PKRU: 55555554 <4>[ 2834.156166] Call Trace: <4>[ 2834.156168] <TASK> <4>[ 2834.156172] aa_label_is_subset+0x3f/0x70 <4>[ 2834.156175] update_sk_ctx+0xfd/0x2c0 <4>[ 2834.156178] aa_unix_file_perm+0x5c2/0x740 <4>[ 2834.156182] aa_sock_file_perm+0x91/0xf0 <4>[ 2834.156185] aa_file_perm+0x36c/0x3b0 <4>[ 2834.156188] apparmor_file_permission+0x58/0x1c0 <4>[ 2834.156190] ? srso_alias_return_thunk+0x5/0xfbef5 <4>[ 2834.156194] ? aa_unix_sock_perm+0x83/0x1e0 <4>[ 2834.156196] ? srso_alias_return_thunk+0x5/0xfbef5 <4>[ 2834.156199] security_file_permission+0x5b/0x170 <4>[ 2834.156202] rw_verify_area+0x57/0x180 <4>[ 2834.156206] vfs_write+0x7c/0x490 <4>[ 2834.156209] ? aa_do_perms+0xbb/0x120 <4>[ 2834.156212] ? srso_alias_return_thunk+0x5/0xfbef5 <4>[ 2834.156215] ksys_write+0xc6/0xf0 <4>[ 2834.156217] __x64_sys_write+0x19/0x30 <4>[ 2834.156220] x64_sys_call+0x22f/0x2390 <4>[ 2834.156223] do_syscall_64+0x105/0x580 <4>[ 2834.156229] ? srso_alias_return_thunk+0x5/0xfbef5 <4>[ 2834.156231] ? aa_unix_sock_perm+0x83/0x1e0 <4>[ 2834.156234] ? srso_alias_return_thunk+0x5/0xfbef5 <4>[ 2834.156235] ? __check_object_size+0x51/0x100 <4>[ 2834.156239] ? srso_alias_return_thunk+0x5/0xfbef5 <4>[ 2834.156241] ? move_addr_to_user+0xd6/0x170 <4>[ 2834.156245] ? srso_alias_return_thunk+0x5/0xfbef5 <4>[ 2834.156247] ? do_getsockname+0x85/0xc0 <4>[ 2834.156251] ? srso_alias_return_thunk+0x5/0xfbef5 <4>[ 2834.156253] ? __sys_getsockname+0x8f/0xd0 <4>[ 2834.156256] ? srso_alias_return_thunk+0x5/0xfbef5 <4>[ 2834.156258] ? srso_alias_return_thunk+0x5/0xfbef5 <4>[ 2834.156260] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 Oops#1 Part2 <4>[ 2834.156262] ? srso_alias_return_thunk+0x5/0xfbef5 <4>[ 2834.156264] ? do_syscall_64+0x140/0x580 <4>[ 2834.156267] ? srso_alias_return_thunk+0x5/0xfbef5 <4>[ 2834.156269] ? __x64_sys_epoll_ctl+0x6c/0xb0 <4>[ 2834.156272] ? srso_alias_return_thunk+0x5/0xfbef5 <4>[ 2834.156274] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 <4>[ 2834.156277] ? srso_alias_return_thunk+0x5/0xfbef5 <4>[ 2834.156279] ? do_syscall_64+0x140/0x580 <4>[ 2834.156281] ? srso_alias_return_thunk+0x5/0xfbef5 <4>[ 2834.156283] ? srso_alias_return_thunk+0x5/0xfbef5 <4>[ 2834.156285] ? arch_exit_to_user_mode_prepare.isra.0+0xd/0xe0 <4>[ 2834.156287] ? srso_alias_return_thunk+0x5/0xfbef5 <4>[ 2834.156289] ? do_syscall_64+0x140/0x580 <4>[ 2834.156291] ? srso_alias_return_thunk+0x5/0xfbef5 <4>[ 2834.156293] ? irqentry_exit+0x97/0x6f0 <4>[ 2834.156296] ? srso_alias_return_thunk+0x5/0xfbef5 <4>[ 2834.156298] ? exc_page_fault+0x94/0x1e0 <4>[ 2834.156300] entry_SYSCALL_64_after_hwframe+0x76/0x7e <4>[ 2834.156302] RIP: 0033:0x4152ee <4>[ 2834.156320] Code: ff cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc 49 89 f2 48 89 fa 48 89 ce 48 89 df 0f 05 <48> 3d 01 f0 ff ff 76 13 48 f7 d8 48 89 c1 48 c7 c0 ff ff ff ff bb <4>[ 2834.156322] RSP: 002b:00002f83ec75f448 EFLAGS: 00000206 ORIG_RAX: 0000000000000001 <4>[ 2834.156324] RAX: ffffffffffffffda RBX: 0000000000000009 RCX: 00000000004152ee <4>[ 2834.156326] RDX: 0000000000000009 RSI: 00002f83ec75f6f0 RDI: 0000000000000009 <4>[ 2834.156327] RBP: 00002f83ec75f488 R08: 0000000000000000 R09: 0000000000000000 <4>[ 2834.156328] R10: 0000000000000000 R11: 0000000000000206 R12: 00002f83ec75f5b8 Oops#1 Part1 <4>[ 2834.156330] R13: 0000000000000005 R14: 00002f83ec704f00 R15: ffffffffffffffff <4>[ 2834.156334] </TASK> <4>[ 2834.156335] Modules linked in: veth vhost_net tap btrfs libblake2b xor raid6_pq vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock nft_masq nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 bridge stp llc nf_tables nfnetlink rfcomm snd_seq_dummy snd_hrtimer qrtr cmac algif_hash algif_skcipher af_alg bnep binfmt_misc amd_atl intel_rapl_msr nls_iso8859_1 intel_rapl_common snd_hda_codec_alc662 snd_hda_codec_realtek_lib snd_hda_codec_generic snd_hda_codec_atihdmi snd_hda_codec_hdmi edac_mce_amd snd_hda_intel joydev input_leds rtw89_8852ce amdgpu snd_hda_codec rtw89_8852c snd_hda_core rtw89_pci snd_intel_dspcfg snd_intel_sdw_acpi snd_hwdep rtw89_core snd_pcm kvm_amd snd_seq_midi kvm snd_seq_midi_event amdxcp drm_panel_backlight_quirks mac80211 snd_rawmidi gpu_sched btusb drm_buddy irqbypass btmtk drm_ttm_helper rapl btrtl ttm snd_seq btbcm drm_exec btintel drm_suballoc_helper snd_seq_device snd_timer nzxt_kraken3 bluetooth drm_display_helper gigabyte_wmi wmi_bmof r8169 i2c_piix4 cfg80211 <4>[ 2834.156412] k10temp cec snd rc_core i2c_smbus libarc4 i2c_algo_bit realtek soundcore phylink mac_hid sch_fq_codel efi_pstore hid_logitech_hidpp zfs(PO) spl(O) hid_logitech_dj uas usb_storage hid_generic usbhid hid nvme ahci libahci nvme_core nvme_keyring ghash_clmulni_intel nvme_auth ccp video hkdf wmi dm_mirror dm_region_hash dm_log lp ppdev parport msr dmi_sysfs autofs4 aesni_intel <4>[ 2834.156451] CR2: 000000000000004c <4>[ 2834.156453] ---[ end trace 0000000000000000 ]--- -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2170572 Title: linux-image-7.0.0-38-generic randomly freezes Lenovo Legion 5 Status in linux package in Ubuntu: Invalid Status in linux source package in Resolute: Fix Committed Status in linux source package in Stonking: Fix Committed Bug description: == SRU Justification == -- Impact An apparmor change in v7.2 caused a NULL pointer validation in some cases. At least one of those happens in a critical section leaving a held lock behind. Which in the end causes the kernel to hang. -- Fix A fix to this was recently released upstream. It would at some point get pulled via stable updates but given the severity of the bug should be given priority. commit 4de32fd05ce9 Author: Maxime Bélair <maxime.belair@canonical.com> Date: Mon Aug 24 17:58:02 2026 +0200 apparmor: fix NULL ctx->peer derefs in unix socket ctx updates -- Test case This seems to require certain HW/setup to happen. And even then might need several restarts. -- Regression potential Anywhere within the area of apparmor controlled socket access. --- original description --- An unattended upgrade from the 7.0.0-31-generic kernel to the 7.0.0-38-generic kernel started causing random freezes on my Lenovo Legion 5 15IAX10 laptop, reverting back to 7.0.0-34-generic seems to fix my issues. I was able to switch to a tty and take a photo (attached), it seems like a kernel bug where CPU is stuck on a spin lock waiting for something. ``` $ grep -C 2 -i "linux-image" /var/log/apt/history.log Start-Date: 2026-10-08 09:10:45 Commandline: /usr/bin/unattended-upgrade Install: linux-modules-7.0.0-38-generic:amd64 (7.0.0-38.38, automatic), linux-image-7.0.0-38-generic:amd64 (7.0.0-38.38, automatic), linux-headers-7.0.0-38-generic:amd64 (7.0.0-38.38, automatic), linux-tools-7.0.0-38:amd64 (7.0.0-38.38, automatic), linux-headers-7.0.0-38:amd64 (7.0.0-38.38, automatic), linux-tools-7.0.0-38-generic:amd64 (7.0.0-38.38, automatic), linux-main-modules-zfs-7.0.0-38-generic:amd64 (7.0.0-38.38, automatic) Upgrade: linux-generic-hwe-24.04:amd64 (7.0.0-34.34, 7.0.0-38.38), linux-image-generic-hwe-26.04:amd64 (7.0.0-34.34, 7.0.0-38.38), linux-tools-common:amd64 (7.0.0-34.34, 7.0.0-38.38), linux-headers-generic:amd64 (7.0.0-34.34, 7.0.0-38.38), linux-perf:amd64 (7.0.0-34.34, 7.0.0-38.38), linux-headers-generic-hwe-26.04:amd64 (7.0.0-34.34, 7.0.0-38.38), linux-generic-hwe-26.04:amd64 (7.0.0-34.34, 7.0.0-38.38), linux-generic:amd64 (7.0.0-34.34, 7.0.0-38.38), linux-image-generic:amd64 (7.0.0-34.34, 7.0.0-38.38), bpftool:amd64 (7.7.0+7.0.0-34.34, 7.7.0+7.0.0-38.38), linux-libc-dev:amd64 (7.0.0-34.34, 7.0.0-38.38) End-Date: 2026-10-08 09:11:28 -- Start-Date: 2026-10-08 09:12:00 Commandline: /usr/bin/unattended-upgrade Remove: linux-image-7.0.0-31-generic:amd64 (7.0.0-31.31), linux-modules-7.0.0-31-generic:amd64 (7.0.0-31.31), linux-main-modules-zfs-7.0.0-31-generic:amd64 (7.0.0-31.31+2) End-Date: 2026-10-08 09:12:06 ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2170572/+subscriptions

[Bug 2174327] Re: **Unexpected system crash when disconnected from charger and docking station**

** 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/2174327 Title: **Unexpected system crash when disconnected from charger and docking station** Status in linux package in Ubuntu: New Bug description: Ubuntu 22.04 LTS on Dell Latitude 5420 (Intel i7-1185G7, 16 GB RAM). The system unexpectedly crashed while running Google Chrome and other applications. The laptop was disconnected from its charger and docking station and operating on battery power. The exact cause is unknown. Possible power-management, battery, graphics-driver, or kernel-related issue. Please investigate the crash logs and system stability during battery operation. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-147-generic 6.8.0-147.147 ProcVersionSignature: Ubuntu 6.8.0-147.147-generic 6.8.12 Uname: Linux 6.8.0-147-generic x86_64 ApportVersion: 2.28.3-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: qd91 58617 F.... wireplumber /dev/snd/controlC0: qd91 58617 F.... wireplumber /dev/snd/seq: qd91 58613 F.... pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Nov 12 18:39:24 2026 InstallationDate: Installed on 2024-02-08 (1008 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Dell Inc. Latitude 5420 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-147-generic root=UUID=02738a08-52ac-4d19-88c9-cacd3b303bbb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.8.0-147-generic N/A linux-backports-modules-6.8.0-147-generic N/A linux-firmware 20240318.git3b128b60.0ubuntu3.1 SourcePackage: linux UpgradeStatus: Upgraded to noble on 2024-05-22 (904 days ago) dmi.bios.date: 06/30/2026 dmi.bios.release: 1.56 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.56.0 dmi.board.name: 0772C9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.56.0:bd06/30/2026:br1.56:svnDellInc.:pnLatitude5420:pvr:rvnDellInc.:rn0772C9:rvrA00:cvnDellInc.:ct10:cvr:sku0A20: dmi.product.family: Latitude dmi.product.name: Latitude 5420 dmi.product.sku: 0A20 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174327/+subscriptions

[Bug 2173937] Re: Upgrade 26.04 to 7.0.0-43-generic and WLAN-Stick TP-Link TL-WN821N Version 3

Is what being processed? -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2173937 Title: Upgrade 26.04 to 7.0.0-43-generic and WLAN-Stick TP-Link TL-WN821N Version 3 Status in linux package in Ubuntu: New Bug description: Upgrade from Kernel 7.0.0-42-generic WLAN-Stick TP-Link TL-WN821N Version 3 works properly and fine to 7.0.0-43-generic does not active WLAN-Stick TP-Link TL-WN821N Version 3 not working any more, no LEDs are on the stick Ubuntu shows saved "WLAN-Networks" in WLAN Graphical-Settings but it is unable to connect it. Please help me! Thank you from Berny! ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-42-generic 7.0.0-42.42 ProcVersionSignature: Ubuntu 7.0.0-42.42-generic 7.0.14 Uname: Linux 7.0.0-42-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: bernhard 2296 F.... wireplumber /dev/snd/controlC0: bernhard 2296 F.... wireplumber /dev/snd/seq: bernhard 2284 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Nov 10 23:57:22 2026 MachineType: Acer Aspire XC-605 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-42-generic root=UUID=1b7bf562-f899-4f06-8edb-1d28e8c4d82c ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-10-06 (35 days ago) dmi.bios.date: 11/08/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P11-A2 dmi.board.name: Aspire XC-605 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP11-A2:bd11/08/2013:br4.6:svnAcer:pnAspireXC-605:pvr:rvnAcer:rnAspireXC-605:rvr:cvnAcer:ct3:cvr:sku:pfaAcerDesktop: dmi.product.family: Acer Desktop dmi.product.name: Aspire XC-605 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2173937/+subscriptions

[Bug 2174347] [NEW] S3 Resume

Public bug reported: AMD B850 (ASUS B850M AYW GAMING WIFI, BIOS 1804), mem_sleep_default=deep, s2idle works on -43, S3 hangs at ACPI entry with no resume ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-43-generic 7.0.0-43.43 ProcVersionSignature: Ubuntu 7.0.0-43.43-generic 7.0.14 Uname: Linux 7.0.0-43-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: abbaspaliwala 2337 F.... wireplumber /dev/snd/controlC0: abbaspaliwala 2337 F.... wireplumber /dev/snd/controlC1: abbaspaliwala 2337 F.... wireplumber /dev/snd/seq: abbaspaliwala 2327 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Nov 13 03:48:18 2026 InstallationDate: Installed on 2026-08-27 (77 days ago) InstallationMedia: Kubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423) IwDevWlp10s0Link: Not connected. MachineType: ASUS System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-43-generic root=UUID=f747f1bc-a448-46d9-a071-273a8cbd352a ro quiet splash mem_sleep_default=deep resume=UUID=f747f1bc-a448-46d9-a071-273a8cbd352a resume_offset=116738048 zswap.enabled=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2026 dmi.bios.release: 18.4 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1804 dmi.board.asset.tag: Default string dmi.board.name: B850M AYW GAMING WIFI 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.:bvr1804:bd09/15/2026:br18.4:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB850MAYWGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug resolute wayland-session -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2174347 Title: S3 Resume Status in linux package in Ubuntu: New Bug description: AMD B850 (ASUS B850M AYW GAMING WIFI, BIOS 1804), mem_sleep_default=deep, s2idle works on -43, S3 hangs at ACPI entry with no resume ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-43-generic 7.0.0-43.43 ProcVersionSignature: Ubuntu 7.0.0-43.43-generic 7.0.14 Uname: Linux 7.0.0-43-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC2: abbaspaliwala 2337 F.... wireplumber /dev/snd/controlC0: abbaspaliwala 2337 F.... wireplumber /dev/snd/controlC1: abbaspaliwala 2337 F.... wireplumber /dev/snd/seq: abbaspaliwala 2327 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Nov 13 03:48:18 2026 InstallationDate: Installed on 2026-08-27 (77 days ago) InstallationMedia: Kubuntu 26.04 "Resolute Raccoon" - Release amd64 (20260423) IwDevWlp10s0Link: Not connected. MachineType: ASUS System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-43-generic root=UUID=f747f1bc-a448-46d9-a071-273a8cbd352a ro quiet splash mem_sleep_default=deep resume=UUID=f747f1bc-a448-46d9-a071-273a8cbd352a resume_offset=116738048 zswap.enabled=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2026 dmi.bios.release: 18.4 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1804 dmi.board.asset.tag: Default string dmi.board.name: B850M AYW GAMING WIFI 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.:bvr1804:bd09/15/2026:br18.4:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB850MAYWGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:pfaTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2174347/+subscriptions