Thank you, Mario!
I now have both AMD-owned outputs working.
I had a Good Boot with amdgpu/yellow_carp_dmcub.bin from the commit
below.
e758135298cc2652403f3ddd7f5b99463a34036aac406fc93e21bdaa3d54be3f
/lib/firmware/updates/amdgpu/yellow_carp_dmcub.bin
===
git commit:
43c969c122346f46f0523e046df99f1d7825c6d1
amdgpu: update dmcub fw for various DCN version waynelin* 18.07.25, 10:58
===
amdgpu: update dmcub fw for various DCN version
From internal commit b0d01933b8b8b3ce0666538ceac20179e6d4c842
Tested with DC v3.2.342
- Update SSC from 0.0125 to 0.125
- Adjust rate control
Signed-off-by: waynelin <Wayne.Lin@amd.com>
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2144530
Title:
Regression on Acer Nitro AN17-41: amdgpu DC/DMUB fails to light up
internal eDP and Radeon-routed USB-C/DP outputs on Ubuntu 26.04 /
kernel 6.19, while Ubuntu 24.04.4 live works
Status in linux package in Ubuntu:
New
Status in linux-firmware package in Ubuntu:
New
Bug description:
Problem summary
===============
On an Acer Nitro AN17-41 laptop, Ubuntu 26.04 development branch with
kernel 6.19.0-9-generic fails to display video when the internal panel
and/or external USB-C display output are owned by the AMD iGPU.
This appears to be a regression or behavior change in the newer Linux graphics stack, because the same machine and same monitor path work under:
- Windows 11
- Ubuntu 24.04.4 live ISO
The machine has:
- Acer Nitro AN17-41
- BIOS V1.25
- AMD Rembrandt / Radeon 680M iGPU (1002:1681)
- NVIDIA GeForce RTX 4050 Mobile / Max-Q dGPU (10de:28e1)
I collected logs over SSH from another device in the failing cases
because the machine was still alive even when both displays were
black.
Observed behavior on Ubuntu 26.04 / kernel 6.19
================================================
When AMD owns the display outputs, the system boots but the displays
stay black.
This affects:
- the internal eDP panel
- an external monitor connected through the USB-C / DP output routed to Radeon
The logs repeatedly show amdgpu DC / DMUB failures such as:
- "Failed to enable ASSR"
- "No reply for DMUB command: status=3"
- "DMCUB error - collecting diagnostic data"
- "Error queueing DMUB command: status=2"
- "enabling link ... failed: 15"
In the failing cases, DRM can still detect AMD-owned outputs as
connected and enabled, but they remain black.
Environment
===========
OS:
- Ubuntu 26.04 (Resolute Raccoon development branch)
Kernel:
- 6.19.0-9-generic
Secure Boot:
- enabled
Hardware:
- Acer Nitro AN17-41
- BIOS V1.25
- AMD Radeon 680M iGPU
- NVIDIA RTX 4050 Mobile dGPU
Regression evidence
===================
I now have a working Linux control case on the same laptop and same
physical USB-C monitor path.
Tested with:
- Ubuntu 24.04.4 LTS live ISO
Results on Ubuntu 24.04.4:
1. Auto / hybrid mode:
- internal panel works
- external monitor connected to the Radeon-routed USB-C/DP output also works
2. NVIDIA GPU Only mode:
- internal panel works
- the same external monitor on the Radeon-routed USB-C/DP output also works in my test
In both Ubuntu 24.04.4 test cases, the displays light up normally and
I do not see the repeated amdgpu DC/DMUB failure pattern that appears
on Ubuntu 26.04 / kernel 6.19.
This strongly suggests:
- the hardware is capable of driving both outputs under Linux
- the Radeon-routed USB-C output is not fundamentally broken on this laptop
- the issue is more likely a regression or missing quirk in the newer graphics/kernel stack used in Ubuntu 26.04
Additional control evidence
===========================
The same USB-C monitor connected to the Radeon-routed USB-C output
also works in Windows 11 when switching to Extend mode with Win+P.
This further suggests that the physical hardware path is functional,
and that the failing configuration is specific to the newer Linux
graphics stack.
What works
==========
1. NVIDIA GPU Only mode in firmware / BIOS on Ubuntu 26.04:
- the internal laptop panel works
2. Windows 11:
- the USB-C monitor connected to the Radeon-routed USB-C output works in Extend mode
3. Ubuntu 24.04.4 live ISO:
- Auto / hybrid mode works
- internal panel works
- Radeon-routed USB-C/DP external monitor works
- NVIDIA GPU Only mode also worked in my test, including the same USB-C monitor
What does not work
==================
On Ubuntu 26.04 / kernel 6.19:
1. Hybrid / normal mode:
- if the internal panel is owned by AMD, the panel stays black
2. AMD-only test:
- booting with
module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm
- internal eDP stays black
- external USB-C/DP monitor routed to Radeon also stays black
This strongly suggests the issue is not caused by nvidia-drm handoff
or by both DRM stacks loading together.
How to reproduce
================
Case A: Hybrid / normal mode on Ubuntu 26.04
1. Boot Ubuntu 26.04 on Acer Nitro AN17-41.
2. Let the machine use its normal hybrid graphics routing.
3. If the internal panel is owned by AMD, the panel remains black.
Case B: AMD-only test on Ubuntu 26.04
1. Boot with:
module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm
2. Connect an external monitor to the USB-C / DP output routed to Radeon before power-on.
3. Boot Ubuntu.
4. Result: both the internal panel and the external USB-C display remain black, although the system is alive and reachable over SSH.
Case C: Verbose DRM logging on Ubuntu 26.04
1. Boot with:
drm.debug=0x1e log_buf_len=4M module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm
2. Result: same black screens, with detailed DRM / amdgpu logging showing DMUB / ASSR / link enable failures.
Expected result
===============
When AMD owns the internal eDP panel and/or Radeon-routed USB-C/DP
output, the displays should light up normally and the system should
reach a visible graphical session.
Actual result
=============
The system boots, but the displays stay black. Logs indicate failures
in amdgpu DC / DMUB while trying to bring up AMD-owned display links.
Important log patterns
======================
Examples consistently seen in the affected Ubuntu 26.04 boots:
- "Skipping amdgpu DM backlight registration"
- "Failed to get EDID from ACPI: -19" (seen in verbose DRM logging)
- "boot timing validation failed ..."
- "Failed to enable ASSR"
- "No reply for DMUB command: status=3"
- "DMCUB error - collecting diagnostic data"
- "Error queueing DMUB command: status=2"
- "enabling link 0 failed: 15"
- "enabling link 2 failed: 15"
Why I think this is a kernel/amdgpu issue
=========================================
The issue reproduces when NVIDIA modules are blacklisted, so it does
not appear to depend on nvidia-drm being active.
The internal panel and the Radeon-routed external USB-C/DP output can
both be detected as connected/enabled by DRM, but they still remain
black.
The same hardware and same USB-C path work:
- on Windows 11
- on Ubuntu 24.04.4 live ISO
This makes it look like an amdgpu DC / DMUB / link bring-up failure in the newer Ubuntu 26.04 graphics stack, rather than:
- a simple EDID-not-found case
- a generic Optimus/MUX problem
- a pure backlight-only issue
- a userspace / compositor-only issue
- a fundamental hardware limitation of the laptop
Tests already performed
=======================
On Ubuntu 26.04:
1. Normal hybrid boot
- black internal display when AMD owns it
2. NVIDIA GPU Only mode
- internal panel works
3. AMD-only boot with:
module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm
- both internal eDP and Radeon-routed USB-C/DP stayed black
4. Verbose DRM boot with:
drm.debug=0x1e log_buf_len=4M
- same failure, more detailed DMUB / ASSR / link logs
5. Test with:
amdgpu.sg_display=0
- no improvement
6. Test with:
amdgpu.abmlevel=0
- no improvement
On Ubuntu 24.04.4 live ISO:
7. Auto / hybrid mode
- internal panel works
- Radeon-routed USB-C/DP external monitor works
8. NVIDIA GPU Only mode
- internal panel works
- the same Radeon-routed USB-C/DP external monitor also worked in my test
Attachments
===========
I am attaching log bundles from these scenarios:
- gpu-badboot4-nvidiablacklist.zip
- gpu-badboot5-nvidiablacklistamdusbc.zip
- gpu-badboot6-nvidiablacklistamdusbcdbg.zip
- gpu-goodboot7-nvidiaonly-w-usbc-radeon.zip
- gpu-badboot8-sgzero.zip
- gpu-badboot9-abmzero.zip
- gpu-goodboot10-u24044.zip
- gpu-goodboot11-u24045.zip
These include:
- journalctl / dmesg output
- DRM connector status and enabled state
- lspci / module state
- backlight info
- EDID decode output
- verbose DRM logs where applicable
I can reproduce this reliably and I can collect additional logs over
SSH because the machine stays alive even when both displays are black.
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-image-6.19.0-9-generic 6.19.0-9.9
ProcVersionSignature: Ubuntu 6.19.0-9.9-generic 6.19.5
Uname: Linux 6.19.0-9-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: denixx 6079 F.... wireplumber
/dev/snd/controlC0: denixx 6079 F.... wireplumber
/dev/snd/controlC1: denixx 6079 F.... wireplumber
/dev/snd/seq: denixx 6059 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 16 08:26:28 2026
InstallationDate: Installed on 2026-03-15 (1 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20260313)
IwDevWlp4s0Link: Not connected.
MachineType: Acer Nitro AN17-41
ProcEnviron:
LANG=uk_UA.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB:
0 amdgpudrmfb
1 nvidia-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.19.0-9-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2024
dmi.bios.release: 1.25
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: V1.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Spacia_PEH
dmi.board.vendor: RB
dmi.board.version: V1.25
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.11
dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.25:bd09/18/2024:br1.25:efr1.11:svnAcer:pnNitroAN17-41:pvrV1.25:rvnRB:rnSpacia_PEH:rvrV1.25:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000:
dmi.product.family: Acer Nitro 17
dmi.product.name: Nitro AN17-41
dmi.product.sku: 0000000000000000
dmi.product.version: V1.25
dmi.sys.vendor: Acer
---
ProblemType: Bug
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: ubuntu 4446 F.... wireplumber
/dev/snd/controlC0: ubuntu 4446 F.... wireplumber
/dev/snd/controlC1: ubuntu 4446 F.... wireplumber
/dev/snd/seq: ubuntu 4430 F.... pipewire
CasperMD5CheckResult: pass
CasperVersion: 26.04.0
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 26.04
IwDevWlp4s0Link: Not connected.
LiveMediaBuild: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20260316)
MachineType: Acer Nitro AN17-41
NonfreeKernelModules: zfs
Package: linux (not installed)
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB:
0 amdgpudrmfb
1 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash
ProcVersionSignature: Ubuntu 6.19.0-9.9-generic 6.19.5
Tags: resolute wayland-session
Uname: Linux 6.19.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
_MarkForUpload: True
dmi.bios.date: 09/18/2024
dmi.bios.release: 1.25
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: V1.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Spacia_PEH
dmi.board.vendor: RB
dmi.board.version: V1.25
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.11
dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.25:bd09/18/2024:br1.25:efr1.11:svnAcer:pnNitroAN17-41:pvrV1.25:rvnRB:rnSpacia_PEH:rvrV1.25:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000:
dmi.product.family: Acer Nitro 17
dmi.product.name: Nitro AN17-41
dmi.product.sku: 0000000000000000
dmi.product.version: V1.25
dmi.sys.vendor: Acer
---
ProblemType: Bug
ApportVersion: 2.33.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: ubuntu 4386 F.... wireplumber
/dev/snd/controlC0: ubuntu 4386 F.... wireplumber
/dev/snd/controlC1: ubuntu 4386 F.... wireplumber
/dev/snd/seq: ubuntu 4370 F.... pipewire
CasperMD5CheckMismatches: ./boot/grub/i386-pc/eltorito.img
CasperMD5CheckResult: fail
CasperVersion: 26.04.1
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 26.04
IwDevWlp4s0Link: Not connected.
LiveMediaBuild: Ubuntu 26.04 "Resolute Raccoon" - Daily amd64 (20260322)
MachineType: Acer Nitro AN17-41
NonfreeKernelModules: zfs
Package: linux (not installed)
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB:
0 amdgpudrmfb
1 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash drm.debug=0x1e log_buf_len=4M
ProcVersionSignature: Ubuntu 7.0.0-7.7-generic 7.0.0-rc3
Tags: resolute wayland-session
Uname: Linux 7.0.0-7-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
_MarkForUpload: True
dmi.bios.date: 09/18/2024
dmi.bios.release: 1.25
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: V1.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Spacia_PEH
dmi.board.vendor: RB
dmi.board.version: V1.25
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.11
dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.25:bd09/18/2024:br1.25:efr1.11:svnAcer:pnNitroAN17-41:pvrV1.25:rvnRB:rnSpacia_PEH:rvrV1.25:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000:pfaAcerNitro17:
dmi.product.family: Acer Nitro 17
dmi.product.name: Nitro AN17-41
dmi.product.sku: 0000000000000000
dmi.product.version: V1.25
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144530/+subscriptions
суббота
[Bug 2147274] Re: Regression: Framework audio expansion card fails after AC to battery transition (6.17.0-20)
Actually, you don't even have to switch to battery power for the audio
to stop working. Just pause the YouTube video for several minutes. Audio
will stop when attempting to resume the video. Bug was definitely
introduced with kernel 6.17.0-20-generic as when reverting to kernel
6.17.0-19-generic the audio works as expected.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2147274
Title:
Regression: Framework audio expansion card fails after AC to battery
transition (6.17.0-20)
Status in linux package in Ubuntu:
New
Bug description:
System:
- Framework laptop (AMD)
- Using Framework audio expansion card (USB audio device)
Regression between kernel versions:
- 6.17.0-19-generic → works correctly
- 6.17.0-20-generic → broken
Steps to reproduce:
1. Boot into 6.17.0-20-generic
2. Start audio playback (e.g., YouTube in Firefox)
3. Disconnect AC power (switch to battery)
Expected result:
Audio continues working normally.
Actual result:
- Audio stops working
- Firefox creates multiple audio streams in mixer
- PipeWire becomes unstable (may hang when restarting)
- Audio device still visible via lsusb but unusable
- Unplugging/replugging audio jack does not recover device
- Reboot required to restore functionality
Additional notes:
- Issue does NOT occur on 6.17.0-19-generic under identical conditions
- Appears related to power state transition (AC → battery)
- Device remains present on USB bus but audio interface is non-functional
Workaround:
Booting into 6.17.0-19-generic avoids the issue.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-20-generic 6.17.0-20.20
ProcVersionSignature: Ubuntu 6.17.0-20.20-generic 6.17.13
Uname: Linux 6.17.0-20-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Sat Apr 4 11:31:59 2026
InstallationDate: Installed on 2026-03-18 (17 days ago)
InstallationMedia: Xubuntu 25.10 "Questing Quokka" - Release amd64 (20251008.1)
MachineType: Framework Laptop 16 (AMD Ryzen AI 300 Series)
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-20-generic root=UUID=0a1e98a4-f95b-4b83-a5c7-f3f0a2fbcc39 ro quiet splash amdgpu.dcdebugmask=0x12 usbcore.autosuspend=-1 rootdelay=3 vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/13/2026
dmi.bios.release: 3.5
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.05
dmi.board.asset.tag: *
dmi.board.name: FRANMHCP09
dmi.board.vendor: Framework
dmi.board.version: A9
dmi.chassis.asset.tag: FRAGAJCPA955010025
dmi.chassis.type: 10
dmi.chassis.vendor: Framework
dmi.chassis.version: A9
dmi.modalias: dmi:bvnINSYDECorp.:bvr03.05:bd03/13/2026:br3.5:svnFramework:pnLaptop16(AMDRyzenAI300Series):pvrA9:rvnFramework:rnFRANMHCP09:rvrA9:cvnFramework:ct10:cvrA9:skuFRAGAJCP09:
dmi.product.family: Laptop 16
dmi.product.name: Laptop 16 (AMD Ryzen AI 300 Series)
dmi.product.sku: FRAGAJCP09
dmi.product.version: A9
dmi.sys.vendor: Framework
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147274/+subscriptions
to stop working. Just pause the YouTube video for several minutes. Audio
will stop when attempting to resume the video. Bug was definitely
introduced with kernel 6.17.0-20-generic as when reverting to kernel
6.17.0-19-generic the audio works as expected.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2147274
Title:
Regression: Framework audio expansion card fails after AC to battery
transition (6.17.0-20)
Status in linux package in Ubuntu:
New
Bug description:
System:
- Framework laptop (AMD)
- Using Framework audio expansion card (USB audio device)
Regression between kernel versions:
- 6.17.0-19-generic → works correctly
- 6.17.0-20-generic → broken
Steps to reproduce:
1. Boot into 6.17.0-20-generic
2. Start audio playback (e.g., YouTube in Firefox)
3. Disconnect AC power (switch to battery)
Expected result:
Audio continues working normally.
Actual result:
- Audio stops working
- Firefox creates multiple audio streams in mixer
- PipeWire becomes unstable (may hang when restarting)
- Audio device still visible via lsusb but unusable
- Unplugging/replugging audio jack does not recover device
- Reboot required to restore functionality
Additional notes:
- Issue does NOT occur on 6.17.0-19-generic under identical conditions
- Appears related to power state transition (AC → battery)
- Device remains present on USB bus but audio interface is non-functional
Workaround:
Booting into 6.17.0-19-generic avoids the issue.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-20-generic 6.17.0-20.20
ProcVersionSignature: Ubuntu 6.17.0-20.20-generic 6.17.13
Uname: Linux 6.17.0-20-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Sat Apr 4 11:31:59 2026
InstallationDate: Installed on 2026-03-18 (17 days ago)
InstallationMedia: Xubuntu 25.10 "Questing Quokka" - Release amd64 (20251008.1)
MachineType: Framework Laptop 16 (AMD Ryzen AI 300 Series)
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-20-generic root=UUID=0a1e98a4-f95b-4b83-a5c7-f3f0a2fbcc39 ro quiet splash amdgpu.dcdebugmask=0x12 usbcore.autosuspend=-1 rootdelay=3 vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/13/2026
dmi.bios.release: 3.5
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.05
dmi.board.asset.tag: *
dmi.board.name: FRANMHCP09
dmi.board.vendor: Framework
dmi.board.version: A9
dmi.chassis.asset.tag: FRAGAJCPA955010025
dmi.chassis.type: 10
dmi.chassis.vendor: Framework
dmi.chassis.version: A9
dmi.modalias: dmi:bvnINSYDECorp.:bvr03.05:bd03/13/2026:br3.5:svnFramework:pnLaptop16(AMDRyzenAI300Series):pvrA9:rvnFramework:rnFRANMHCP09:rvrA9:cvnFramework:ct10:cvrA9:skuFRAGAJCP09:
dmi.product.family: Laptop 16
dmi.product.name: Laptop 16 (AMD Ryzen AI 300 Series)
dmi.product.sku: FRAGAJCP09
dmi.product.version: A9
dmi.sys.vendor: Framework
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147274/+subscriptions
[Bug 2144530] Re: Regression on Acer Nitro AN17-41: amdgpu DC/DMUB fails to light up internal eDP and Radeon-routed USB-C/DP outputs on Ubuntu 26.04 / kernel 6.19, while Ubuntu 24.04.4 live works
** Attachment added: "gpu-goodboot22-u2604.zip"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144530/+attachment/5958672/+files/gpu-goodboot22-u2604.zip
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2144530
Title:
Regression on Acer Nitro AN17-41: amdgpu DC/DMUB fails to light up
internal eDP and Radeon-routed USB-C/DP outputs on Ubuntu 26.04 /
kernel 6.19, while Ubuntu 24.04.4 live works
Status in linux package in Ubuntu:
New
Status in linux-firmware package in Ubuntu:
New
Bug description:
Problem summary
===============
On an Acer Nitro AN17-41 laptop, Ubuntu 26.04 development branch with
kernel 6.19.0-9-generic fails to display video when the internal panel
and/or external USB-C display output are owned by the AMD iGPU.
This appears to be a regression or behavior change in the newer Linux graphics stack, because the same machine and same monitor path work under:
- Windows 11
- Ubuntu 24.04.4 live ISO
The machine has:
- Acer Nitro AN17-41
- BIOS V1.25
- AMD Rembrandt / Radeon 680M iGPU (1002:1681)
- NVIDIA GeForce RTX 4050 Mobile / Max-Q dGPU (10de:28e1)
I collected logs over SSH from another device in the failing cases
because the machine was still alive even when both displays were
black.
Observed behavior on Ubuntu 26.04 / kernel 6.19
================================================
When AMD owns the display outputs, the system boots but the displays
stay black.
This affects:
- the internal eDP panel
- an external monitor connected through the USB-C / DP output routed to Radeon
The logs repeatedly show amdgpu DC / DMUB failures such as:
- "Failed to enable ASSR"
- "No reply for DMUB command: status=3"
- "DMCUB error - collecting diagnostic data"
- "Error queueing DMUB command: status=2"
- "enabling link ... failed: 15"
In the failing cases, DRM can still detect AMD-owned outputs as
connected and enabled, but they remain black.
Environment
===========
OS:
- Ubuntu 26.04 (Resolute Raccoon development branch)
Kernel:
- 6.19.0-9-generic
Secure Boot:
- enabled
Hardware:
- Acer Nitro AN17-41
- BIOS V1.25
- AMD Radeon 680M iGPU
- NVIDIA RTX 4050 Mobile dGPU
Regression evidence
===================
I now have a working Linux control case on the same laptop and same
physical USB-C monitor path.
Tested with:
- Ubuntu 24.04.4 LTS live ISO
Results on Ubuntu 24.04.4:
1. Auto / hybrid mode:
- internal panel works
- external monitor connected to the Radeon-routed USB-C/DP output also works
2. NVIDIA GPU Only mode:
- internal panel works
- the same external monitor on the Radeon-routed USB-C/DP output also works in my test
In both Ubuntu 24.04.4 test cases, the displays light up normally and
I do not see the repeated amdgpu DC/DMUB failure pattern that appears
on Ubuntu 26.04 / kernel 6.19.
This strongly suggests:
- the hardware is capable of driving both outputs under Linux
- the Radeon-routed USB-C output is not fundamentally broken on this laptop
- the issue is more likely a regression or missing quirk in the newer graphics/kernel stack used in Ubuntu 26.04
Additional control evidence
===========================
The same USB-C monitor connected to the Radeon-routed USB-C output
also works in Windows 11 when switching to Extend mode with Win+P.
This further suggests that the physical hardware path is functional,
and that the failing configuration is specific to the newer Linux
graphics stack.
What works
==========
1. NVIDIA GPU Only mode in firmware / BIOS on Ubuntu 26.04:
- the internal laptop panel works
2. Windows 11:
- the USB-C monitor connected to the Radeon-routed USB-C output works in Extend mode
3. Ubuntu 24.04.4 live ISO:
- Auto / hybrid mode works
- internal panel works
- Radeon-routed USB-C/DP external monitor works
- NVIDIA GPU Only mode also worked in my test, including the same USB-C monitor
What does not work
==================
On Ubuntu 26.04 / kernel 6.19:
1. Hybrid / normal mode:
- if the internal panel is owned by AMD, the panel stays black
2. AMD-only test:
- booting with
module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm
- internal eDP stays black
- external USB-C/DP monitor routed to Radeon also stays black
This strongly suggests the issue is not caused by nvidia-drm handoff
or by both DRM stacks loading together.
How to reproduce
================
Case A: Hybrid / normal mode on Ubuntu 26.04
1. Boot Ubuntu 26.04 on Acer Nitro AN17-41.
2. Let the machine use its normal hybrid graphics routing.
3. If the internal panel is owned by AMD, the panel remains black.
Case B: AMD-only test on Ubuntu 26.04
1. Boot with:
module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm
2. Connect an external monitor to the USB-C / DP output routed to Radeon before power-on.
3. Boot Ubuntu.
4. Result: both the internal panel and the external USB-C display remain black, although the system is alive and reachable over SSH.
Case C: Verbose DRM logging on Ubuntu 26.04
1. Boot with:
drm.debug=0x1e log_buf_len=4M module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm
2. Result: same black screens, with detailed DRM / amdgpu logging showing DMUB / ASSR / link enable failures.
Expected result
===============
When AMD owns the internal eDP panel and/or Radeon-routed USB-C/DP
output, the displays should light up normally and the system should
reach a visible graphical session.
Actual result
=============
The system boots, but the displays stay black. Logs indicate failures
in amdgpu DC / DMUB while trying to bring up AMD-owned display links.
Important log patterns
======================
Examples consistently seen in the affected Ubuntu 26.04 boots:
- "Skipping amdgpu DM backlight registration"
- "Failed to get EDID from ACPI: -19" (seen in verbose DRM logging)
- "boot timing validation failed ..."
- "Failed to enable ASSR"
- "No reply for DMUB command: status=3"
- "DMCUB error - collecting diagnostic data"
- "Error queueing DMUB command: status=2"
- "enabling link 0 failed: 15"
- "enabling link 2 failed: 15"
Why I think this is a kernel/amdgpu issue
=========================================
The issue reproduces when NVIDIA modules are blacklisted, so it does
not appear to depend on nvidia-drm being active.
The internal panel and the Radeon-routed external USB-C/DP output can
both be detected as connected/enabled by DRM, but they still remain
black.
The same hardware and same USB-C path work:
- on Windows 11
- on Ubuntu 24.04.4 live ISO
This makes it look like an amdgpu DC / DMUB / link bring-up failure in the newer Ubuntu 26.04 graphics stack, rather than:
- a simple EDID-not-found case
- a generic Optimus/MUX problem
- a pure backlight-only issue
- a userspace / compositor-only issue
- a fundamental hardware limitation of the laptop
Tests already performed
=======================
On Ubuntu 26.04:
1. Normal hybrid boot
- black internal display when AMD owns it
2. NVIDIA GPU Only mode
- internal panel works
3. AMD-only boot with:
module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm
- both internal eDP and Radeon-routed USB-C/DP stayed black
4. Verbose DRM boot with:
drm.debug=0x1e log_buf_len=4M
- same failure, more detailed DMUB / ASSR / link logs
5. Test with:
amdgpu.sg_display=0
- no improvement
6. Test with:
amdgpu.abmlevel=0
- no improvement
On Ubuntu 24.04.4 live ISO:
7. Auto / hybrid mode
- internal panel works
- Radeon-routed USB-C/DP external monitor works
8. NVIDIA GPU Only mode
- internal panel works
- the same Radeon-routed USB-C/DP external monitor also worked in my test
Attachments
===========
I am attaching log bundles from these scenarios:
- gpu-badboot4-nvidiablacklist.zip
- gpu-badboot5-nvidiablacklistamdusbc.zip
- gpu-badboot6-nvidiablacklistamdusbcdbg.zip
- gpu-goodboot7-nvidiaonly-w-usbc-radeon.zip
- gpu-badboot8-sgzero.zip
- gpu-badboot9-abmzero.zip
- gpu-goodboot10-u24044.zip
- gpu-goodboot11-u24045.zip
These include:
- journalctl / dmesg output
- DRM connector status and enabled state
- lspci / module state
- backlight info
- EDID decode output
- verbose DRM logs where applicable
I can reproduce this reliably and I can collect additional logs over
SSH because the machine stays alive even when both displays are black.
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-image-6.19.0-9-generic 6.19.0-9.9
ProcVersionSignature: Ubuntu 6.19.0-9.9-generic 6.19.5
Uname: Linux 6.19.0-9-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: denixx 6079 F.... wireplumber
/dev/snd/controlC0: denixx 6079 F.... wireplumber
/dev/snd/controlC1: denixx 6079 F.... wireplumber
/dev/snd/seq: denixx 6059 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 16 08:26:28 2026
InstallationDate: Installed on 2026-03-15 (1 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20260313)
IwDevWlp4s0Link: Not connected.
MachineType: Acer Nitro AN17-41
ProcEnviron:
LANG=uk_UA.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB:
0 amdgpudrmfb
1 nvidia-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.19.0-9-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2024
dmi.bios.release: 1.25
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: V1.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Spacia_PEH
dmi.board.vendor: RB
dmi.board.version: V1.25
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.11
dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.25:bd09/18/2024:br1.25:efr1.11:svnAcer:pnNitroAN17-41:pvrV1.25:rvnRB:rnSpacia_PEH:rvrV1.25:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000:
dmi.product.family: Acer Nitro 17
dmi.product.name: Nitro AN17-41
dmi.product.sku: 0000000000000000
dmi.product.version: V1.25
dmi.sys.vendor: Acer
---
ProblemType: Bug
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: ubuntu 4446 F.... wireplumber
/dev/snd/controlC0: ubuntu 4446 F.... wireplumber
/dev/snd/controlC1: ubuntu 4446 F.... wireplumber
/dev/snd/seq: ubuntu 4430 F.... pipewire
CasperMD5CheckResult: pass
CasperVersion: 26.04.0
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 26.04
IwDevWlp4s0Link: Not connected.
LiveMediaBuild: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20260316)
MachineType: Acer Nitro AN17-41
NonfreeKernelModules: zfs
Package: linux (not installed)
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB:
0 amdgpudrmfb
1 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash
ProcVersionSignature: Ubuntu 6.19.0-9.9-generic 6.19.5
Tags: resolute wayland-session
Uname: Linux 6.19.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
_MarkForUpload: True
dmi.bios.date: 09/18/2024
dmi.bios.release: 1.25
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: V1.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Spacia_PEH
dmi.board.vendor: RB
dmi.board.version: V1.25
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.11
dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.25:bd09/18/2024:br1.25:efr1.11:svnAcer:pnNitroAN17-41:pvrV1.25:rvnRB:rnSpacia_PEH:rvrV1.25:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000:
dmi.product.family: Acer Nitro 17
dmi.product.name: Nitro AN17-41
dmi.product.sku: 0000000000000000
dmi.product.version: V1.25
dmi.sys.vendor: Acer
---
ProblemType: Bug
ApportVersion: 2.33.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: ubuntu 4386 F.... wireplumber
/dev/snd/controlC0: ubuntu 4386 F.... wireplumber
/dev/snd/controlC1: ubuntu 4386 F.... wireplumber
/dev/snd/seq: ubuntu 4370 F.... pipewire
CasperMD5CheckMismatches: ./boot/grub/i386-pc/eltorito.img
CasperMD5CheckResult: fail
CasperVersion: 26.04.1
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 26.04
IwDevWlp4s0Link: Not connected.
LiveMediaBuild: Ubuntu 26.04 "Resolute Raccoon" - Daily amd64 (20260322)
MachineType: Acer Nitro AN17-41
NonfreeKernelModules: zfs
Package: linux (not installed)
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB:
0 amdgpudrmfb
1 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash drm.debug=0x1e log_buf_len=4M
ProcVersionSignature: Ubuntu 7.0.0-7.7-generic 7.0.0-rc3
Tags: resolute wayland-session
Uname: Linux 7.0.0-7-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
_MarkForUpload: True
dmi.bios.date: 09/18/2024
dmi.bios.release: 1.25
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: V1.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Spacia_PEH
dmi.board.vendor: RB
dmi.board.version: V1.25
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.11
dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.25:bd09/18/2024:br1.25:efr1.11:svnAcer:pnNitroAN17-41:pvrV1.25:rvnRB:rnSpacia_PEH:rvrV1.25:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000:pfaAcerNitro17:
dmi.product.family: Acer Nitro 17
dmi.product.name: Nitro AN17-41
dmi.product.sku: 0000000000000000
dmi.product.version: V1.25
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144530/+subscriptions
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144530/+attachment/5958672/+files/gpu-goodboot22-u2604.zip
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2144530
Title:
Regression on Acer Nitro AN17-41: amdgpu DC/DMUB fails to light up
internal eDP and Radeon-routed USB-C/DP outputs on Ubuntu 26.04 /
kernel 6.19, while Ubuntu 24.04.4 live works
Status in linux package in Ubuntu:
New
Status in linux-firmware package in Ubuntu:
New
Bug description:
Problem summary
===============
On an Acer Nitro AN17-41 laptop, Ubuntu 26.04 development branch with
kernel 6.19.0-9-generic fails to display video when the internal panel
and/or external USB-C display output are owned by the AMD iGPU.
This appears to be a regression or behavior change in the newer Linux graphics stack, because the same machine and same monitor path work under:
- Windows 11
- Ubuntu 24.04.4 live ISO
The machine has:
- Acer Nitro AN17-41
- BIOS V1.25
- AMD Rembrandt / Radeon 680M iGPU (1002:1681)
- NVIDIA GeForce RTX 4050 Mobile / Max-Q dGPU (10de:28e1)
I collected logs over SSH from another device in the failing cases
because the machine was still alive even when both displays were
black.
Observed behavior on Ubuntu 26.04 / kernel 6.19
================================================
When AMD owns the display outputs, the system boots but the displays
stay black.
This affects:
- the internal eDP panel
- an external monitor connected through the USB-C / DP output routed to Radeon
The logs repeatedly show amdgpu DC / DMUB failures such as:
- "Failed to enable ASSR"
- "No reply for DMUB command: status=3"
- "DMCUB error - collecting diagnostic data"
- "Error queueing DMUB command: status=2"
- "enabling link ... failed: 15"
In the failing cases, DRM can still detect AMD-owned outputs as
connected and enabled, but they remain black.
Environment
===========
OS:
- Ubuntu 26.04 (Resolute Raccoon development branch)
Kernel:
- 6.19.0-9-generic
Secure Boot:
- enabled
Hardware:
- Acer Nitro AN17-41
- BIOS V1.25
- AMD Radeon 680M iGPU
- NVIDIA RTX 4050 Mobile dGPU
Regression evidence
===================
I now have a working Linux control case on the same laptop and same
physical USB-C monitor path.
Tested with:
- Ubuntu 24.04.4 LTS live ISO
Results on Ubuntu 24.04.4:
1. Auto / hybrid mode:
- internal panel works
- external monitor connected to the Radeon-routed USB-C/DP output also works
2. NVIDIA GPU Only mode:
- internal panel works
- the same external monitor on the Radeon-routed USB-C/DP output also works in my test
In both Ubuntu 24.04.4 test cases, the displays light up normally and
I do not see the repeated amdgpu DC/DMUB failure pattern that appears
on Ubuntu 26.04 / kernel 6.19.
This strongly suggests:
- the hardware is capable of driving both outputs under Linux
- the Radeon-routed USB-C output is not fundamentally broken on this laptop
- the issue is more likely a regression or missing quirk in the newer graphics/kernel stack used in Ubuntu 26.04
Additional control evidence
===========================
The same USB-C monitor connected to the Radeon-routed USB-C output
also works in Windows 11 when switching to Extend mode with Win+P.
This further suggests that the physical hardware path is functional,
and that the failing configuration is specific to the newer Linux
graphics stack.
What works
==========
1. NVIDIA GPU Only mode in firmware / BIOS on Ubuntu 26.04:
- the internal laptop panel works
2. Windows 11:
- the USB-C monitor connected to the Radeon-routed USB-C output works in Extend mode
3. Ubuntu 24.04.4 live ISO:
- Auto / hybrid mode works
- internal panel works
- Radeon-routed USB-C/DP external monitor works
- NVIDIA GPU Only mode also worked in my test, including the same USB-C monitor
What does not work
==================
On Ubuntu 26.04 / kernel 6.19:
1. Hybrid / normal mode:
- if the internal panel is owned by AMD, the panel stays black
2. AMD-only test:
- booting with
module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm
- internal eDP stays black
- external USB-C/DP monitor routed to Radeon also stays black
This strongly suggests the issue is not caused by nvidia-drm handoff
or by both DRM stacks loading together.
How to reproduce
================
Case A: Hybrid / normal mode on Ubuntu 26.04
1. Boot Ubuntu 26.04 on Acer Nitro AN17-41.
2. Let the machine use its normal hybrid graphics routing.
3. If the internal panel is owned by AMD, the panel remains black.
Case B: AMD-only test on Ubuntu 26.04
1. Boot with:
module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm
2. Connect an external monitor to the USB-C / DP output routed to Radeon before power-on.
3. Boot Ubuntu.
4. Result: both the internal panel and the external USB-C display remain black, although the system is alive and reachable over SSH.
Case C: Verbose DRM logging on Ubuntu 26.04
1. Boot with:
drm.debug=0x1e log_buf_len=4M module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm
2. Result: same black screens, with detailed DRM / amdgpu logging showing DMUB / ASSR / link enable failures.
Expected result
===============
When AMD owns the internal eDP panel and/or Radeon-routed USB-C/DP
output, the displays should light up normally and the system should
reach a visible graphical session.
Actual result
=============
The system boots, but the displays stay black. Logs indicate failures
in amdgpu DC / DMUB while trying to bring up AMD-owned display links.
Important log patterns
======================
Examples consistently seen in the affected Ubuntu 26.04 boots:
- "Skipping amdgpu DM backlight registration"
- "Failed to get EDID from ACPI: -19" (seen in verbose DRM logging)
- "boot timing validation failed ..."
- "Failed to enable ASSR"
- "No reply for DMUB command: status=3"
- "DMCUB error - collecting diagnostic data"
- "Error queueing DMUB command: status=2"
- "enabling link 0 failed: 15"
- "enabling link 2 failed: 15"
Why I think this is a kernel/amdgpu issue
=========================================
The issue reproduces when NVIDIA modules are blacklisted, so it does
not appear to depend on nvidia-drm being active.
The internal panel and the Radeon-routed external USB-C/DP output can
both be detected as connected/enabled by DRM, but they still remain
black.
The same hardware and same USB-C path work:
- on Windows 11
- on Ubuntu 24.04.4 live ISO
This makes it look like an amdgpu DC / DMUB / link bring-up failure in the newer Ubuntu 26.04 graphics stack, rather than:
- a simple EDID-not-found case
- a generic Optimus/MUX problem
- a pure backlight-only issue
- a userspace / compositor-only issue
- a fundamental hardware limitation of the laptop
Tests already performed
=======================
On Ubuntu 26.04:
1. Normal hybrid boot
- black internal display when AMD owns it
2. NVIDIA GPU Only mode
- internal panel works
3. AMD-only boot with:
module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm
- both internal eDP and Radeon-routed USB-C/DP stayed black
4. Verbose DRM boot with:
drm.debug=0x1e log_buf_len=4M
- same failure, more detailed DMUB / ASSR / link logs
5. Test with:
amdgpu.sg_display=0
- no improvement
6. Test with:
amdgpu.abmlevel=0
- no improvement
On Ubuntu 24.04.4 live ISO:
7. Auto / hybrid mode
- internal panel works
- Radeon-routed USB-C/DP external monitor works
8. NVIDIA GPU Only mode
- internal panel works
- the same Radeon-routed USB-C/DP external monitor also worked in my test
Attachments
===========
I am attaching log bundles from these scenarios:
- gpu-badboot4-nvidiablacklist.zip
- gpu-badboot5-nvidiablacklistamdusbc.zip
- gpu-badboot6-nvidiablacklistamdusbcdbg.zip
- gpu-goodboot7-nvidiaonly-w-usbc-radeon.zip
- gpu-badboot8-sgzero.zip
- gpu-badboot9-abmzero.zip
- gpu-goodboot10-u24044.zip
- gpu-goodboot11-u24045.zip
These include:
- journalctl / dmesg output
- DRM connector status and enabled state
- lspci / module state
- backlight info
- EDID decode output
- verbose DRM logs where applicable
I can reproduce this reliably and I can collect additional logs over
SSH because the machine stays alive even when both displays are black.
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-image-6.19.0-9-generic 6.19.0-9.9
ProcVersionSignature: Ubuntu 6.19.0-9.9-generic 6.19.5
Uname: Linux 6.19.0-9-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: denixx 6079 F.... wireplumber
/dev/snd/controlC0: denixx 6079 F.... wireplumber
/dev/snd/controlC1: denixx 6079 F.... wireplumber
/dev/snd/seq: denixx 6059 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 16 08:26:28 2026
InstallationDate: Installed on 2026-03-15 (1 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20260313)
IwDevWlp4s0Link: Not connected.
MachineType: Acer Nitro AN17-41
ProcEnviron:
LANG=uk_UA.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB:
0 amdgpudrmfb
1 nvidia-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.19.0-9-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2024
dmi.bios.release: 1.25
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: V1.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Spacia_PEH
dmi.board.vendor: RB
dmi.board.version: V1.25
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.11
dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.25:bd09/18/2024:br1.25:efr1.11:svnAcer:pnNitroAN17-41:pvrV1.25:rvnRB:rnSpacia_PEH:rvrV1.25:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000:
dmi.product.family: Acer Nitro 17
dmi.product.name: Nitro AN17-41
dmi.product.sku: 0000000000000000
dmi.product.version: V1.25
dmi.sys.vendor: Acer
---
ProblemType: Bug
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: ubuntu 4446 F.... wireplumber
/dev/snd/controlC0: ubuntu 4446 F.... wireplumber
/dev/snd/controlC1: ubuntu 4446 F.... wireplumber
/dev/snd/seq: ubuntu 4430 F.... pipewire
CasperMD5CheckResult: pass
CasperVersion: 26.04.0
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 26.04
IwDevWlp4s0Link: Not connected.
LiveMediaBuild: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20260316)
MachineType: Acer Nitro AN17-41
NonfreeKernelModules: zfs
Package: linux (not installed)
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB:
0 amdgpudrmfb
1 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash
ProcVersionSignature: Ubuntu 6.19.0-9.9-generic 6.19.5
Tags: resolute wayland-session
Uname: Linux 6.19.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
_MarkForUpload: True
dmi.bios.date: 09/18/2024
dmi.bios.release: 1.25
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: V1.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Spacia_PEH
dmi.board.vendor: RB
dmi.board.version: V1.25
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.11
dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.25:bd09/18/2024:br1.25:efr1.11:svnAcer:pnNitroAN17-41:pvrV1.25:rvnRB:rnSpacia_PEH:rvrV1.25:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000:
dmi.product.family: Acer Nitro 17
dmi.product.name: Nitro AN17-41
dmi.product.sku: 0000000000000000
dmi.product.version: V1.25
dmi.sys.vendor: Acer
---
ProblemType: Bug
ApportVersion: 2.33.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: ubuntu 4386 F.... wireplumber
/dev/snd/controlC0: ubuntu 4386 F.... wireplumber
/dev/snd/controlC1: ubuntu 4386 F.... wireplumber
/dev/snd/seq: ubuntu 4370 F.... pipewire
CasperMD5CheckMismatches: ./boot/grub/i386-pc/eltorito.img
CasperMD5CheckResult: fail
CasperVersion: 26.04.1
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 26.04
IwDevWlp4s0Link: Not connected.
LiveMediaBuild: Ubuntu 26.04 "Resolute Raccoon" - Daily amd64 (20260322)
MachineType: Acer Nitro AN17-41
NonfreeKernelModules: zfs
Package: linux (not installed)
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB:
0 amdgpudrmfb
1 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash drm.debug=0x1e log_buf_len=4M
ProcVersionSignature: Ubuntu 7.0.0-7.7-generic 7.0.0-rc3
Tags: resolute wayland-session
Uname: Linux 7.0.0-7-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
_MarkForUpload: True
dmi.bios.date: 09/18/2024
dmi.bios.release: 1.25
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: V1.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Spacia_PEH
dmi.board.vendor: RB
dmi.board.version: V1.25
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.11
dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.25:bd09/18/2024:br1.25:efr1.11:svnAcer:pnNitroAN17-41:pvrV1.25:rvnRB:rnSpacia_PEH:rvrV1.25:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000:pfaAcerNitro17:
dmi.product.family: Acer Nitro 17
dmi.product.name: Nitro AN17-41
dmi.product.sku: 0000000000000000
dmi.product.version: V1.25
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144530/+subscriptions
[Bug 2144530] Re: Regression on Acer Nitro AN17-41: amdgpu DC/DMUB fails to light up internal eDP and Radeon-routed USB-C/DP outputs on Ubuntu 26.04 / kernel 6.19, while Ubuntu 24.04.4 live works
** Attachment added: "gpu-goodboot21-u2604.zip"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144530/+attachment/5958671/+files/gpu-goodboot21-u2604.zip
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2144530
Title:
Regression on Acer Nitro AN17-41: amdgpu DC/DMUB fails to light up
internal eDP and Radeon-routed USB-C/DP outputs on Ubuntu 26.04 /
kernel 6.19, while Ubuntu 24.04.4 live works
Status in linux package in Ubuntu:
New
Status in linux-firmware package in Ubuntu:
New
Bug description:
Problem summary
===============
On an Acer Nitro AN17-41 laptop, Ubuntu 26.04 development branch with
kernel 6.19.0-9-generic fails to display video when the internal panel
and/or external USB-C display output are owned by the AMD iGPU.
This appears to be a regression or behavior change in the newer Linux graphics stack, because the same machine and same monitor path work under:
- Windows 11
- Ubuntu 24.04.4 live ISO
The machine has:
- Acer Nitro AN17-41
- BIOS V1.25
- AMD Rembrandt / Radeon 680M iGPU (1002:1681)
- NVIDIA GeForce RTX 4050 Mobile / Max-Q dGPU (10de:28e1)
I collected logs over SSH from another device in the failing cases
because the machine was still alive even when both displays were
black.
Observed behavior on Ubuntu 26.04 / kernel 6.19
================================================
When AMD owns the display outputs, the system boots but the displays
stay black.
This affects:
- the internal eDP panel
- an external monitor connected through the USB-C / DP output routed to Radeon
The logs repeatedly show amdgpu DC / DMUB failures such as:
- "Failed to enable ASSR"
- "No reply for DMUB command: status=3"
- "DMCUB error - collecting diagnostic data"
- "Error queueing DMUB command: status=2"
- "enabling link ... failed: 15"
In the failing cases, DRM can still detect AMD-owned outputs as
connected and enabled, but they remain black.
Environment
===========
OS:
- Ubuntu 26.04 (Resolute Raccoon development branch)
Kernel:
- 6.19.0-9-generic
Secure Boot:
- enabled
Hardware:
- Acer Nitro AN17-41
- BIOS V1.25
- AMD Radeon 680M iGPU
- NVIDIA RTX 4050 Mobile dGPU
Regression evidence
===================
I now have a working Linux control case on the same laptop and same
physical USB-C monitor path.
Tested with:
- Ubuntu 24.04.4 LTS live ISO
Results on Ubuntu 24.04.4:
1. Auto / hybrid mode:
- internal panel works
- external monitor connected to the Radeon-routed USB-C/DP output also works
2. NVIDIA GPU Only mode:
- internal panel works
- the same external monitor on the Radeon-routed USB-C/DP output also works in my test
In both Ubuntu 24.04.4 test cases, the displays light up normally and
I do not see the repeated amdgpu DC/DMUB failure pattern that appears
on Ubuntu 26.04 / kernel 6.19.
This strongly suggests:
- the hardware is capable of driving both outputs under Linux
- the Radeon-routed USB-C output is not fundamentally broken on this laptop
- the issue is more likely a regression or missing quirk in the newer graphics/kernel stack used in Ubuntu 26.04
Additional control evidence
===========================
The same USB-C monitor connected to the Radeon-routed USB-C output
also works in Windows 11 when switching to Extend mode with Win+P.
This further suggests that the physical hardware path is functional,
and that the failing configuration is specific to the newer Linux
graphics stack.
What works
==========
1. NVIDIA GPU Only mode in firmware / BIOS on Ubuntu 26.04:
- the internal laptop panel works
2. Windows 11:
- the USB-C monitor connected to the Radeon-routed USB-C output works in Extend mode
3. Ubuntu 24.04.4 live ISO:
- Auto / hybrid mode works
- internal panel works
- Radeon-routed USB-C/DP external monitor works
- NVIDIA GPU Only mode also worked in my test, including the same USB-C monitor
What does not work
==================
On Ubuntu 26.04 / kernel 6.19:
1. Hybrid / normal mode:
- if the internal panel is owned by AMD, the panel stays black
2. AMD-only test:
- booting with
module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm
- internal eDP stays black
- external USB-C/DP monitor routed to Radeon also stays black
This strongly suggests the issue is not caused by nvidia-drm handoff
or by both DRM stacks loading together.
How to reproduce
================
Case A: Hybrid / normal mode on Ubuntu 26.04
1. Boot Ubuntu 26.04 on Acer Nitro AN17-41.
2. Let the machine use its normal hybrid graphics routing.
3. If the internal panel is owned by AMD, the panel remains black.
Case B: AMD-only test on Ubuntu 26.04
1. Boot with:
module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm
2. Connect an external monitor to the USB-C / DP output routed to Radeon before power-on.
3. Boot Ubuntu.
4. Result: both the internal panel and the external USB-C display remain black, although the system is alive and reachable over SSH.
Case C: Verbose DRM logging on Ubuntu 26.04
1. Boot with:
drm.debug=0x1e log_buf_len=4M module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm
2. Result: same black screens, with detailed DRM / amdgpu logging showing DMUB / ASSR / link enable failures.
Expected result
===============
When AMD owns the internal eDP panel and/or Radeon-routed USB-C/DP
output, the displays should light up normally and the system should
reach a visible graphical session.
Actual result
=============
The system boots, but the displays stay black. Logs indicate failures
in amdgpu DC / DMUB while trying to bring up AMD-owned display links.
Important log patterns
======================
Examples consistently seen in the affected Ubuntu 26.04 boots:
- "Skipping amdgpu DM backlight registration"
- "Failed to get EDID from ACPI: -19" (seen in verbose DRM logging)
- "boot timing validation failed ..."
- "Failed to enable ASSR"
- "No reply for DMUB command: status=3"
- "DMCUB error - collecting diagnostic data"
- "Error queueing DMUB command: status=2"
- "enabling link 0 failed: 15"
- "enabling link 2 failed: 15"
Why I think this is a kernel/amdgpu issue
=========================================
The issue reproduces when NVIDIA modules are blacklisted, so it does
not appear to depend on nvidia-drm being active.
The internal panel and the Radeon-routed external USB-C/DP output can
both be detected as connected/enabled by DRM, but they still remain
black.
The same hardware and same USB-C path work:
- on Windows 11
- on Ubuntu 24.04.4 live ISO
This makes it look like an amdgpu DC / DMUB / link bring-up failure in the newer Ubuntu 26.04 graphics stack, rather than:
- a simple EDID-not-found case
- a generic Optimus/MUX problem
- a pure backlight-only issue
- a userspace / compositor-only issue
- a fundamental hardware limitation of the laptop
Tests already performed
=======================
On Ubuntu 26.04:
1. Normal hybrid boot
- black internal display when AMD owns it
2. NVIDIA GPU Only mode
- internal panel works
3. AMD-only boot with:
module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm
- both internal eDP and Radeon-routed USB-C/DP stayed black
4. Verbose DRM boot with:
drm.debug=0x1e log_buf_len=4M
- same failure, more detailed DMUB / ASSR / link logs
5. Test with:
amdgpu.sg_display=0
- no improvement
6. Test with:
amdgpu.abmlevel=0
- no improvement
On Ubuntu 24.04.4 live ISO:
7. Auto / hybrid mode
- internal panel works
- Radeon-routed USB-C/DP external monitor works
8. NVIDIA GPU Only mode
- internal panel works
- the same Radeon-routed USB-C/DP external monitor also worked in my test
Attachments
===========
I am attaching log bundles from these scenarios:
- gpu-badboot4-nvidiablacklist.zip
- gpu-badboot5-nvidiablacklistamdusbc.zip
- gpu-badboot6-nvidiablacklistamdusbcdbg.zip
- gpu-goodboot7-nvidiaonly-w-usbc-radeon.zip
- gpu-badboot8-sgzero.zip
- gpu-badboot9-abmzero.zip
- gpu-goodboot10-u24044.zip
- gpu-goodboot11-u24045.zip
These include:
- journalctl / dmesg output
- DRM connector status and enabled state
- lspci / module state
- backlight info
- EDID decode output
- verbose DRM logs where applicable
I can reproduce this reliably and I can collect additional logs over
SSH because the machine stays alive even when both displays are black.
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-image-6.19.0-9-generic 6.19.0-9.9
ProcVersionSignature: Ubuntu 6.19.0-9.9-generic 6.19.5
Uname: Linux 6.19.0-9-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: denixx 6079 F.... wireplumber
/dev/snd/controlC0: denixx 6079 F.... wireplumber
/dev/snd/controlC1: denixx 6079 F.... wireplumber
/dev/snd/seq: denixx 6059 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 16 08:26:28 2026
InstallationDate: Installed on 2026-03-15 (1 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20260313)
IwDevWlp4s0Link: Not connected.
MachineType: Acer Nitro AN17-41
ProcEnviron:
LANG=uk_UA.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB:
0 amdgpudrmfb
1 nvidia-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.19.0-9-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2024
dmi.bios.release: 1.25
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: V1.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Spacia_PEH
dmi.board.vendor: RB
dmi.board.version: V1.25
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.11
dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.25:bd09/18/2024:br1.25:efr1.11:svnAcer:pnNitroAN17-41:pvrV1.25:rvnRB:rnSpacia_PEH:rvrV1.25:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000:
dmi.product.family: Acer Nitro 17
dmi.product.name: Nitro AN17-41
dmi.product.sku: 0000000000000000
dmi.product.version: V1.25
dmi.sys.vendor: Acer
---
ProblemType: Bug
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: ubuntu 4446 F.... wireplumber
/dev/snd/controlC0: ubuntu 4446 F.... wireplumber
/dev/snd/controlC1: ubuntu 4446 F.... wireplumber
/dev/snd/seq: ubuntu 4430 F.... pipewire
CasperMD5CheckResult: pass
CasperVersion: 26.04.0
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 26.04
IwDevWlp4s0Link: Not connected.
LiveMediaBuild: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20260316)
MachineType: Acer Nitro AN17-41
NonfreeKernelModules: zfs
Package: linux (not installed)
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB:
0 amdgpudrmfb
1 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash
ProcVersionSignature: Ubuntu 6.19.0-9.9-generic 6.19.5
Tags: resolute wayland-session
Uname: Linux 6.19.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
_MarkForUpload: True
dmi.bios.date: 09/18/2024
dmi.bios.release: 1.25
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: V1.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Spacia_PEH
dmi.board.vendor: RB
dmi.board.version: V1.25
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.11
dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.25:bd09/18/2024:br1.25:efr1.11:svnAcer:pnNitroAN17-41:pvrV1.25:rvnRB:rnSpacia_PEH:rvrV1.25:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000:
dmi.product.family: Acer Nitro 17
dmi.product.name: Nitro AN17-41
dmi.product.sku: 0000000000000000
dmi.product.version: V1.25
dmi.sys.vendor: Acer
---
ProblemType: Bug
ApportVersion: 2.33.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: ubuntu 4386 F.... wireplumber
/dev/snd/controlC0: ubuntu 4386 F.... wireplumber
/dev/snd/controlC1: ubuntu 4386 F.... wireplumber
/dev/snd/seq: ubuntu 4370 F.... pipewire
CasperMD5CheckMismatches: ./boot/grub/i386-pc/eltorito.img
CasperMD5CheckResult: fail
CasperVersion: 26.04.1
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 26.04
IwDevWlp4s0Link: Not connected.
LiveMediaBuild: Ubuntu 26.04 "Resolute Raccoon" - Daily amd64 (20260322)
MachineType: Acer Nitro AN17-41
NonfreeKernelModules: zfs
Package: linux (not installed)
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB:
0 amdgpudrmfb
1 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash drm.debug=0x1e log_buf_len=4M
ProcVersionSignature: Ubuntu 7.0.0-7.7-generic 7.0.0-rc3
Tags: resolute wayland-session
Uname: Linux 7.0.0-7-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
_MarkForUpload: True
dmi.bios.date: 09/18/2024
dmi.bios.release: 1.25
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: V1.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Spacia_PEH
dmi.board.vendor: RB
dmi.board.version: V1.25
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.11
dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.25:bd09/18/2024:br1.25:efr1.11:svnAcer:pnNitroAN17-41:pvrV1.25:rvnRB:rnSpacia_PEH:rvrV1.25:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000:pfaAcerNitro17:
dmi.product.family: Acer Nitro 17
dmi.product.name: Nitro AN17-41
dmi.product.sku: 0000000000000000
dmi.product.version: V1.25
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144530/+subscriptions
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144530/+attachment/5958671/+files/gpu-goodboot21-u2604.zip
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2144530
Title:
Regression on Acer Nitro AN17-41: amdgpu DC/DMUB fails to light up
internal eDP and Radeon-routed USB-C/DP outputs on Ubuntu 26.04 /
kernel 6.19, while Ubuntu 24.04.4 live works
Status in linux package in Ubuntu:
New
Status in linux-firmware package in Ubuntu:
New
Bug description:
Problem summary
===============
On an Acer Nitro AN17-41 laptop, Ubuntu 26.04 development branch with
kernel 6.19.0-9-generic fails to display video when the internal panel
and/or external USB-C display output are owned by the AMD iGPU.
This appears to be a regression or behavior change in the newer Linux graphics stack, because the same machine and same monitor path work under:
- Windows 11
- Ubuntu 24.04.4 live ISO
The machine has:
- Acer Nitro AN17-41
- BIOS V1.25
- AMD Rembrandt / Radeon 680M iGPU (1002:1681)
- NVIDIA GeForce RTX 4050 Mobile / Max-Q dGPU (10de:28e1)
I collected logs over SSH from another device in the failing cases
because the machine was still alive even when both displays were
black.
Observed behavior on Ubuntu 26.04 / kernel 6.19
================================================
When AMD owns the display outputs, the system boots but the displays
stay black.
This affects:
- the internal eDP panel
- an external monitor connected through the USB-C / DP output routed to Radeon
The logs repeatedly show amdgpu DC / DMUB failures such as:
- "Failed to enable ASSR"
- "No reply for DMUB command: status=3"
- "DMCUB error - collecting diagnostic data"
- "Error queueing DMUB command: status=2"
- "enabling link ... failed: 15"
In the failing cases, DRM can still detect AMD-owned outputs as
connected and enabled, but they remain black.
Environment
===========
OS:
- Ubuntu 26.04 (Resolute Raccoon development branch)
Kernel:
- 6.19.0-9-generic
Secure Boot:
- enabled
Hardware:
- Acer Nitro AN17-41
- BIOS V1.25
- AMD Radeon 680M iGPU
- NVIDIA RTX 4050 Mobile dGPU
Regression evidence
===================
I now have a working Linux control case on the same laptop and same
physical USB-C monitor path.
Tested with:
- Ubuntu 24.04.4 LTS live ISO
Results on Ubuntu 24.04.4:
1. Auto / hybrid mode:
- internal panel works
- external monitor connected to the Radeon-routed USB-C/DP output also works
2. NVIDIA GPU Only mode:
- internal panel works
- the same external monitor on the Radeon-routed USB-C/DP output also works in my test
In both Ubuntu 24.04.4 test cases, the displays light up normally and
I do not see the repeated amdgpu DC/DMUB failure pattern that appears
on Ubuntu 26.04 / kernel 6.19.
This strongly suggests:
- the hardware is capable of driving both outputs under Linux
- the Radeon-routed USB-C output is not fundamentally broken on this laptop
- the issue is more likely a regression or missing quirk in the newer graphics/kernel stack used in Ubuntu 26.04
Additional control evidence
===========================
The same USB-C monitor connected to the Radeon-routed USB-C output
also works in Windows 11 when switching to Extend mode with Win+P.
This further suggests that the physical hardware path is functional,
and that the failing configuration is specific to the newer Linux
graphics stack.
What works
==========
1. NVIDIA GPU Only mode in firmware / BIOS on Ubuntu 26.04:
- the internal laptop panel works
2. Windows 11:
- the USB-C monitor connected to the Radeon-routed USB-C output works in Extend mode
3. Ubuntu 24.04.4 live ISO:
- Auto / hybrid mode works
- internal panel works
- Radeon-routed USB-C/DP external monitor works
- NVIDIA GPU Only mode also worked in my test, including the same USB-C monitor
What does not work
==================
On Ubuntu 26.04 / kernel 6.19:
1. Hybrid / normal mode:
- if the internal panel is owned by AMD, the panel stays black
2. AMD-only test:
- booting with
module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm
- internal eDP stays black
- external USB-C/DP monitor routed to Radeon also stays black
This strongly suggests the issue is not caused by nvidia-drm handoff
or by both DRM stacks loading together.
How to reproduce
================
Case A: Hybrid / normal mode on Ubuntu 26.04
1. Boot Ubuntu 26.04 on Acer Nitro AN17-41.
2. Let the machine use its normal hybrid graphics routing.
3. If the internal panel is owned by AMD, the panel remains black.
Case B: AMD-only test on Ubuntu 26.04
1. Boot with:
module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm
2. Connect an external monitor to the USB-C / DP output routed to Radeon before power-on.
3. Boot Ubuntu.
4. Result: both the internal panel and the external USB-C display remain black, although the system is alive and reachable over SSH.
Case C: Verbose DRM logging on Ubuntu 26.04
1. Boot with:
drm.debug=0x1e log_buf_len=4M module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm
2. Result: same black screens, with detailed DRM / amdgpu logging showing DMUB / ASSR / link enable failures.
Expected result
===============
When AMD owns the internal eDP panel and/or Radeon-routed USB-C/DP
output, the displays should light up normally and the system should
reach a visible graphical session.
Actual result
=============
The system boots, but the displays stay black. Logs indicate failures
in amdgpu DC / DMUB while trying to bring up AMD-owned display links.
Important log patterns
======================
Examples consistently seen in the affected Ubuntu 26.04 boots:
- "Skipping amdgpu DM backlight registration"
- "Failed to get EDID from ACPI: -19" (seen in verbose DRM logging)
- "boot timing validation failed ..."
- "Failed to enable ASSR"
- "No reply for DMUB command: status=3"
- "DMCUB error - collecting diagnostic data"
- "Error queueing DMUB command: status=2"
- "enabling link 0 failed: 15"
- "enabling link 2 failed: 15"
Why I think this is a kernel/amdgpu issue
=========================================
The issue reproduces when NVIDIA modules are blacklisted, so it does
not appear to depend on nvidia-drm being active.
The internal panel and the Radeon-routed external USB-C/DP output can
both be detected as connected/enabled by DRM, but they still remain
black.
The same hardware and same USB-C path work:
- on Windows 11
- on Ubuntu 24.04.4 live ISO
This makes it look like an amdgpu DC / DMUB / link bring-up failure in the newer Ubuntu 26.04 graphics stack, rather than:
- a simple EDID-not-found case
- a generic Optimus/MUX problem
- a pure backlight-only issue
- a userspace / compositor-only issue
- a fundamental hardware limitation of the laptop
Tests already performed
=======================
On Ubuntu 26.04:
1. Normal hybrid boot
- black internal display when AMD owns it
2. NVIDIA GPU Only mode
- internal panel works
3. AMD-only boot with:
module_blacklist=nvidia,nvidia_drm,nvidia_modeset,nvidia_uvm
- both internal eDP and Radeon-routed USB-C/DP stayed black
4. Verbose DRM boot with:
drm.debug=0x1e log_buf_len=4M
- same failure, more detailed DMUB / ASSR / link logs
5. Test with:
amdgpu.sg_display=0
- no improvement
6. Test with:
amdgpu.abmlevel=0
- no improvement
On Ubuntu 24.04.4 live ISO:
7. Auto / hybrid mode
- internal panel works
- Radeon-routed USB-C/DP external monitor works
8. NVIDIA GPU Only mode
- internal panel works
- the same Radeon-routed USB-C/DP external monitor also worked in my test
Attachments
===========
I am attaching log bundles from these scenarios:
- gpu-badboot4-nvidiablacklist.zip
- gpu-badboot5-nvidiablacklistamdusbc.zip
- gpu-badboot6-nvidiablacklistamdusbcdbg.zip
- gpu-goodboot7-nvidiaonly-w-usbc-radeon.zip
- gpu-badboot8-sgzero.zip
- gpu-badboot9-abmzero.zip
- gpu-goodboot10-u24044.zip
- gpu-goodboot11-u24045.zip
These include:
- journalctl / dmesg output
- DRM connector status and enabled state
- lspci / module state
- backlight info
- EDID decode output
- verbose DRM logs where applicable
I can reproduce this reliably and I can collect additional logs over
SSH because the machine stays alive even when both displays are black.
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-image-6.19.0-9-generic 6.19.0-9.9
ProcVersionSignature: Ubuntu 6.19.0-9.9-generic 6.19.5
Uname: Linux 6.19.0-9-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: denixx 6079 F.... wireplumber
/dev/snd/controlC0: denixx 6079 F.... wireplumber
/dev/snd/controlC1: denixx 6079 F.... wireplumber
/dev/snd/seq: denixx 6059 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 16 08:26:28 2026
InstallationDate: Installed on 2026-03-15 (1 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20260313)
IwDevWlp4s0Link: Not connected.
MachineType: Acer Nitro AN17-41
ProcEnviron:
LANG=uk_UA.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB:
0 amdgpudrmfb
1 nvidia-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.19.0-9-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2024
dmi.bios.release: 1.25
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: V1.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Spacia_PEH
dmi.board.vendor: RB
dmi.board.version: V1.25
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.11
dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.25:bd09/18/2024:br1.25:efr1.11:svnAcer:pnNitroAN17-41:pvrV1.25:rvnRB:rnSpacia_PEH:rvrV1.25:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000:
dmi.product.family: Acer Nitro 17
dmi.product.name: Nitro AN17-41
dmi.product.sku: 0000000000000000
dmi.product.version: V1.25
dmi.sys.vendor: Acer
---
ProblemType: Bug
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: ubuntu 4446 F.... wireplumber
/dev/snd/controlC0: ubuntu 4446 F.... wireplumber
/dev/snd/controlC1: ubuntu 4446 F.... wireplumber
/dev/snd/seq: ubuntu 4430 F.... pipewire
CasperMD5CheckResult: pass
CasperVersion: 26.04.0
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 26.04
IwDevWlp4s0Link: Not connected.
LiveMediaBuild: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20260316)
MachineType: Acer Nitro AN17-41
NonfreeKernelModules: zfs
Package: linux (not installed)
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB:
0 amdgpudrmfb
1 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash
ProcVersionSignature: Ubuntu 6.19.0-9.9-generic 6.19.5
Tags: resolute wayland-session
Uname: Linux 6.19.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
_MarkForUpload: True
dmi.bios.date: 09/18/2024
dmi.bios.release: 1.25
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: V1.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Spacia_PEH
dmi.board.vendor: RB
dmi.board.version: V1.25
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.11
dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.25:bd09/18/2024:br1.25:efr1.11:svnAcer:pnNitroAN17-41:pvrV1.25:rvnRB:rnSpacia_PEH:rvrV1.25:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000:
dmi.product.family: Acer Nitro 17
dmi.product.name: Nitro AN17-41
dmi.product.sku: 0000000000000000
dmi.product.version: V1.25
dmi.sys.vendor: Acer
---
ProblemType: Bug
ApportVersion: 2.33.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC2: ubuntu 4386 F.... wireplumber
/dev/snd/controlC0: ubuntu 4386 F.... wireplumber
/dev/snd/controlC1: ubuntu 4386 F.... wireplumber
/dev/snd/seq: ubuntu 4370 F.... pipewire
CasperMD5CheckMismatches: ./boot/grub/i386-pc/eltorito.img
CasperMD5CheckResult: fail
CasperVersion: 26.04.1
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 26.04
IwDevWlp4s0Link: Not connected.
LiveMediaBuild: Ubuntu 26.04 "Resolute Raccoon" - Daily amd64 (20260322)
MachineType: Acer Nitro AN17-41
NonfreeKernelModules: zfs
Package: linux (not installed)
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB:
0 amdgpudrmfb
1 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash drm.debug=0x1e log_buf_len=4M
ProcVersionSignature: Ubuntu 7.0.0-7.7-generic 7.0.0-rc3
Tags: resolute wayland-session
Uname: Linux 7.0.0-7-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
_MarkForUpload: True
dmi.bios.date: 09/18/2024
dmi.bios.release: 1.25
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: V1.25
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Spacia_PEH
dmi.board.vendor: RB
dmi.board.version: V1.25
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 1.11
dmi.modalias: dmi:bvnINSYDECorp.:bvrV1.25:bd09/18/2024:br1.25:efr1.11:svnAcer:pnNitroAN17-41:pvrV1.25:rvnRB:rnSpacia_PEH:rvrV1.25:cvnAcer:ct10:cvrChassisVersion:sku0000000000000000:pfaAcerNitro17:
dmi.product.family: Acer Nitro 17
dmi.product.name: Nitro AN17-41
dmi.product.sku: 0000000000000000
dmi.product.version: V1.25
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144530/+subscriptions
[Bug 2146485] Re: IdeaPad Slim 5 16AKP10 (83HY): intermittent keyboard keystroke drops at i8042 kernel driver level
Hello,
Unfortunately, I already am running the latest version of the BIOS
(R0CN27WW).
I checked BIOS historical modification from their Readme file, but it
doesn't specify any modifications about keyboard behaviour in the EC
Firmware part.
I think I'll end up contacting Lenovo support directly, and hope they
have a fix for it.
But still, thank you for trying to help !
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146485
Title:
IdeaPad Slim 5 16AKP10 (83HY): intermittent keyboard keystroke drops
at i8042 kernel driver level
Status in linux package in Ubuntu:
Confirmed
Bug description:
On a Lenovo IdeaPad Slim 5 16AKP10 (model 83HY), the built-in keyboard
intermittently begins dropping keystrokes after a variable uptime
(sometimes hours, sometimes days). The issue clears on reboot and does
not persist across power cycles.
Hardware:
System: Lenovo IdeaPad Slim 5 16AKP10 (83HY)
BIOS: R0CN22WW
OS: Linux Mint 22.3
Kernel: 6.17.0-14-generic and 6.17.0-19-generic (issue present on both)
Diagnosis:
evtest confirms keystroke drops are occurring at the kernel input driver level, not in X11 or the compositor
dmesg shows no i8042 errors during affected sessions
/proc/interrupts shows normal i8042 interrupt counts during the
problem
Memory, swap, CPU load, and thermals are all normal during affected
sessions
The i8042 module is built-in and cannot be reloaded to recover without
a full reboot
Boot parameter i8042.nopnp (added based on kernel warning at boot:
"PS/2 appears to have AUX port disabled, if this is incorrect please
boot with i8042.nopnp") improved perceived keyboard latency but did
not prevent recurrence of drops
TLP 1.6.1 is installed and manages power; forcing USB autosuspend to
"on" during an affected session did not resolve the issue
$ cat /proc/interrupts | grep i8042
1: 0 28512 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-IO-APIC 1-edge i8042
Kernel boot messages:
i8042: PNP detection disabled
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2
Current kernel cmdline:
quiet splash kvm.enable_virt_at_load=0 i8042.nopnp
Expected behavior: Keyboard input should be reliable throughout a
session without requiring a reboot to restore normal function.
Workaround: Reboot restores normal keyboard function until the issue
recurs.
Possibly significant point: I am a fast typist but I experience this
even when typing very slowly.
Attached archive contains:
$ cat /proc/version_signature > ~/version.log
$ sudo lspci -vnvn > ~/lspci-vnvn.log
$ sudo dmesg > ~/dmesg.log
$ cat /proc/interrupts > ~/interrupts.log
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146485/+subscriptions
Unfortunately, I already am running the latest version of the BIOS
(R0CN27WW).
I checked BIOS historical modification from their Readme file, but it
doesn't specify any modifications about keyboard behaviour in the EC
Firmware part.
I think I'll end up contacting Lenovo support directly, and hope they
have a fix for it.
But still, thank you for trying to help !
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2146485
Title:
IdeaPad Slim 5 16AKP10 (83HY): intermittent keyboard keystroke drops
at i8042 kernel driver level
Status in linux package in Ubuntu:
Confirmed
Bug description:
On a Lenovo IdeaPad Slim 5 16AKP10 (model 83HY), the built-in keyboard
intermittently begins dropping keystrokes after a variable uptime
(sometimes hours, sometimes days). The issue clears on reboot and does
not persist across power cycles.
Hardware:
System: Lenovo IdeaPad Slim 5 16AKP10 (83HY)
BIOS: R0CN22WW
OS: Linux Mint 22.3
Kernel: 6.17.0-14-generic and 6.17.0-19-generic (issue present on both)
Diagnosis:
evtest confirms keystroke drops are occurring at the kernel input driver level, not in X11 or the compositor
dmesg shows no i8042 errors during affected sessions
/proc/interrupts shows normal i8042 interrupt counts during the
problem
Memory, swap, CPU load, and thermals are all normal during affected
sessions
The i8042 module is built-in and cannot be reloaded to recover without
a full reboot
Boot parameter i8042.nopnp (added based on kernel warning at boot:
"PS/2 appears to have AUX port disabled, if this is incorrect please
boot with i8042.nopnp") improved perceived keyboard latency but did
not prevent recurrence of drops
TLP 1.6.1 is installed and manages power; forcing USB autosuspend to
"on" during an affected session did not resolve the issue
$ cat /proc/interrupts | grep i8042
1: 0 28512 0 0 0 0 0 0 0 0 0 0 0 0 0 0 IR-IO-APIC 1-edge i8042
Kernel boot messages:
i8042: PNP detection disabled
serio: i8042 KBD port at 0x60,0x64 irq 1
input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input2
Current kernel cmdline:
quiet splash kvm.enable_virt_at_load=0 i8042.nopnp
Expected behavior: Keyboard input should be reliable throughout a
session without requiring a reboot to restore normal function.
Workaround: Reboot restores normal keyboard function until the issue
recurs.
Possibly significant point: I am a fast typist but I experience this
even when typing very slowly.
Attached archive contains:
$ cat /proc/version_signature > ~/version.log
$ sudo lspci -vnvn > ~/lspci-vnvn.log
$ sudo dmesg > ~/dmesg.log
$ cat /proc/interrupts > ~/interrupts.log
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2146485/+subscriptions
[Bug 2147274] [NEW] Regression: Framework audio expansion card fails after AC to battery transition (6.17.0-20)
Public bug reported:
System:
- Framework laptop (AMD)
- Using Framework audio expansion card (USB audio device)
Regression between kernel versions:
- 6.17.0-19-generic → works correctly
- 6.17.0-20-generic → broken
Steps to reproduce:
1. Boot into 6.17.0-20-generic
2. Start audio playback (e.g., YouTube in Firefox)
3. Disconnect AC power (switch to battery)
Expected result:
Audio continues working normally.
Actual result:
- Audio stops working
- Firefox creates multiple audio streams in mixer
- PipeWire becomes unstable (may hang when restarting)
- Audio device still visible via lsusb but unusable
- Unplugging/replugging audio jack does not recover device
- Reboot required to restore functionality
Additional notes:
- Issue does NOT occur on 6.17.0-19-generic under identical conditions
- Appears related to power state transition (AC → battery)
- Device remains present on USB bus but audio interface is non-functional
Workaround:
Booting into 6.17.0-19-generic avoids the issue.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-20-generic 6.17.0-20.20
ProcVersionSignature: Ubuntu 6.17.0-20.20-generic 6.17.13
Uname: Linux 6.17.0-20-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Sat Apr 4 11:31:59 2026
InstallationDate: Installed on 2026-03-18 (17 days ago)
InstallationMedia: Xubuntu 25.10 "Questing Quokka" - Release amd64 (20251008.1)
MachineType: Framework Laptop 16 (AMD Ryzen AI 300 Series)
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-20-generic root=UUID=0a1e98a4-f95b-4b83-a5c7-f3f0a2fbcc39 ro quiet splash amdgpu.dcdebugmask=0x12 usbcore.autosuspend=-1 rootdelay=3 vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/13/2026
dmi.bios.release: 3.5
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.05
dmi.board.asset.tag: *
dmi.board.name: FRANMHCP09
dmi.board.vendor: Framework
dmi.board.version: A9
dmi.chassis.asset.tag: FRAGAJCPA955010025
dmi.chassis.type: 10
dmi.chassis.vendor: Framework
dmi.chassis.version: A9
dmi.modalias: dmi:bvnINSYDECorp.:bvr03.05:bd03/13/2026:br3.5:svnFramework:pnLaptop16(AMDRyzenAI300Series):pvrA9:rvnFramework:rnFRANMHCP09:rvrA9:cvnFramework:ct10:cvrA9:skuFRAGAJCP09:
dmi.product.family: Laptop 16
dmi.product.name: Laptop 16 (AMD Ryzen AI 300 Series)
dmi.product.sku: FRAGAJCP09
dmi.product.version: A9
dmi.sys.vendor: Framework
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug questing
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2147274
Title:
Regression: Framework audio expansion card fails after AC to battery
transition (6.17.0-20)
Status in linux package in Ubuntu:
New
Bug description:
System:
- Framework laptop (AMD)
- Using Framework audio expansion card (USB audio device)
Regression between kernel versions:
- 6.17.0-19-generic → works correctly
- 6.17.0-20-generic → broken
Steps to reproduce:
1. Boot into 6.17.0-20-generic
2. Start audio playback (e.g., YouTube in Firefox)
3. Disconnect AC power (switch to battery)
Expected result:
Audio continues working normally.
Actual result:
- Audio stops working
- Firefox creates multiple audio streams in mixer
- PipeWire becomes unstable (may hang when restarting)
- Audio device still visible via lsusb but unusable
- Unplugging/replugging audio jack does not recover device
- Reboot required to restore functionality
Additional notes:
- Issue does NOT occur on 6.17.0-19-generic under identical conditions
- Appears related to power state transition (AC → battery)
- Device remains present on USB bus but audio interface is non-functional
Workaround:
Booting into 6.17.0-19-generic avoids the issue.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-20-generic 6.17.0-20.20
ProcVersionSignature: Ubuntu 6.17.0-20.20-generic 6.17.13
Uname: Linux 6.17.0-20-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Sat Apr 4 11:31:59 2026
InstallationDate: Installed on 2026-03-18 (17 days ago)
InstallationMedia: Xubuntu 25.10 "Questing Quokka" - Release amd64 (20251008.1)
MachineType: Framework Laptop 16 (AMD Ryzen AI 300 Series)
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-20-generic root=UUID=0a1e98a4-f95b-4b83-a5c7-f3f0a2fbcc39 ro quiet splash amdgpu.dcdebugmask=0x12 usbcore.autosuspend=-1 rootdelay=3 vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/13/2026
dmi.bios.release: 3.5
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.05
dmi.board.asset.tag: *
dmi.board.name: FRANMHCP09
dmi.board.vendor: Framework
dmi.board.version: A9
dmi.chassis.asset.tag: FRAGAJCPA955010025
dmi.chassis.type: 10
dmi.chassis.vendor: Framework
dmi.chassis.version: A9
dmi.modalias: dmi:bvnINSYDECorp.:bvr03.05:bd03/13/2026:br3.5:svnFramework:pnLaptop16(AMDRyzenAI300Series):pvrA9:rvnFramework:rnFRANMHCP09:rvrA9:cvnFramework:ct10:cvrA9:skuFRAGAJCP09:
dmi.product.family: Laptop 16
dmi.product.name: Laptop 16 (AMD Ryzen AI 300 Series)
dmi.product.sku: FRAGAJCP09
dmi.product.version: A9
dmi.sys.vendor: Framework
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147274/+subscriptions
System:
- Framework laptop (AMD)
- Using Framework audio expansion card (USB audio device)
Regression between kernel versions:
- 6.17.0-19-generic → works correctly
- 6.17.0-20-generic → broken
Steps to reproduce:
1. Boot into 6.17.0-20-generic
2. Start audio playback (e.g., YouTube in Firefox)
3. Disconnect AC power (switch to battery)
Expected result:
Audio continues working normally.
Actual result:
- Audio stops working
- Firefox creates multiple audio streams in mixer
- PipeWire becomes unstable (may hang when restarting)
- Audio device still visible via lsusb but unusable
- Unplugging/replugging audio jack does not recover device
- Reboot required to restore functionality
Additional notes:
- Issue does NOT occur on 6.17.0-19-generic under identical conditions
- Appears related to power state transition (AC → battery)
- Device remains present on USB bus but audio interface is non-functional
Workaround:
Booting into 6.17.0-19-generic avoids the issue.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-20-generic 6.17.0-20.20
ProcVersionSignature: Ubuntu 6.17.0-20.20-generic 6.17.13
Uname: Linux 6.17.0-20-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Sat Apr 4 11:31:59 2026
InstallationDate: Installed on 2026-03-18 (17 days ago)
InstallationMedia: Xubuntu 25.10 "Questing Quokka" - Release amd64 (20251008.1)
MachineType: Framework Laptop 16 (AMD Ryzen AI 300 Series)
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-20-generic root=UUID=0a1e98a4-f95b-4b83-a5c7-f3f0a2fbcc39 ro quiet splash amdgpu.dcdebugmask=0x12 usbcore.autosuspend=-1 rootdelay=3 vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/13/2026
dmi.bios.release: 3.5
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.05
dmi.board.asset.tag: *
dmi.board.name: FRANMHCP09
dmi.board.vendor: Framework
dmi.board.version: A9
dmi.chassis.asset.tag: FRAGAJCPA955010025
dmi.chassis.type: 10
dmi.chassis.vendor: Framework
dmi.chassis.version: A9
dmi.modalias: dmi:bvnINSYDECorp.:bvr03.05:bd03/13/2026:br3.5:svnFramework:pnLaptop16(AMDRyzenAI300Series):pvrA9:rvnFramework:rnFRANMHCP09:rvrA9:cvnFramework:ct10:cvrA9:skuFRAGAJCP09:
dmi.product.family: Laptop 16
dmi.product.name: Laptop 16 (AMD Ryzen AI 300 Series)
dmi.product.sku: FRAGAJCP09
dmi.product.version: A9
dmi.sys.vendor: Framework
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug questing
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2147274
Title:
Regression: Framework audio expansion card fails after AC to battery
transition (6.17.0-20)
Status in linux package in Ubuntu:
New
Bug description:
System:
- Framework laptop (AMD)
- Using Framework audio expansion card (USB audio device)
Regression between kernel versions:
- 6.17.0-19-generic → works correctly
- 6.17.0-20-generic → broken
Steps to reproduce:
1. Boot into 6.17.0-20-generic
2. Start audio playback (e.g., YouTube in Firefox)
3. Disconnect AC power (switch to battery)
Expected result:
Audio continues working normally.
Actual result:
- Audio stops working
- Firefox creates multiple audio streams in mixer
- PipeWire becomes unstable (may hang when restarting)
- Audio device still visible via lsusb but unusable
- Unplugging/replugging audio jack does not recover device
- Reboot required to restore functionality
Additional notes:
- Issue does NOT occur on 6.17.0-19-generic under identical conditions
- Appears related to power state transition (AC → battery)
- Device remains present on USB bus but audio interface is non-functional
Workaround:
Booting into 6.17.0-19-generic avoids the issue.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-20-generic 6.17.0-20.20
ProcVersionSignature: Ubuntu 6.17.0-20.20-generic 6.17.13
Uname: Linux 6.17.0-20-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Sat Apr 4 11:31:59 2026
InstallationDate: Installed on 2026-03-18 (17 days ago)
InstallationMedia: Xubuntu 25.10 "Questing Quokka" - Release amd64 (20251008.1)
MachineType: Framework Laptop 16 (AMD Ryzen AI 300 Series)
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-20-generic root=UUID=0a1e98a4-f95b-4b83-a5c7-f3f0a2fbcc39 ro quiet splash amdgpu.dcdebugmask=0x12 usbcore.autosuspend=-1 rootdelay=3 vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/13/2026
dmi.bios.release: 3.5
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.05
dmi.board.asset.tag: *
dmi.board.name: FRANMHCP09
dmi.board.vendor: Framework
dmi.board.version: A9
dmi.chassis.asset.tag: FRAGAJCPA955010025
dmi.chassis.type: 10
dmi.chassis.vendor: Framework
dmi.chassis.version: A9
dmi.modalias: dmi:bvnINSYDECorp.:bvr03.05:bd03/13/2026:br3.5:svnFramework:pnLaptop16(AMDRyzenAI300Series):pvrA9:rvnFramework:rnFRANMHCP09:rvrA9:cvnFramework:ct10:cvrA9:skuFRAGAJCP09:
dmi.product.family: Laptop 16
dmi.product.name: Laptop 16 (AMD Ryzen AI 300 Series)
dmi.product.sku: FRAGAJCP09
dmi.product.version: A9
dmi.sys.vendor: Framework
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147274/+subscriptions
[Bug 2147249] [NEW] System randomly suspends
Public bug reported:
The system suspends randomly since one or two weeks ago. The issue
happens specially while playing games (Genshin Impact), so it may be
related to a high energy demand.
Logs show some errors related to hardware (missing symbols in ACPI
BIOS). My device (HP OMEN 16) is known for a BIOS non-compliant with
Linux systems. I tried updating from bios version F.25 to F.31, but
issues persist.
There were no issues a couple weeks ago, so a system update may be
related, but I don't remember the exact date the issues started
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-20-generic 6.17.0-20.20
ProcVersionSignature: Ubuntu 6.17.0-20.20-generic 6.17.13
Uname: Linux 6.17.0-20-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 4 12:28:24 2026
InstallationDate: Installed on 2025-12-26 (99 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: HP OMEN by HP Gaming Laptop 16-xf0xxx
ProcEnviron:
LANG=es_ES.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-20-generic root=UUID=c0e4fef4-5db9-4a20-862b-db56e160e19c ro quiet splash acpi_osi=! "acpi_osi=Windows 2015" pcie_aspm=off 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.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/20/2025
dmi.bios.release: 15.31
dmi.bios.vendor: Insyde
dmi.bios.version: F.31
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8BCA
dmi.board.vendor: HP
dmi.board.version: 77.54
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 77.54
dmi.modalias: dmi:bvnInsyde:bvrF.31:bd11/20/2025:br15.31:efr77.54:svnHP:pnOMENbyHPGamingLaptop16-xf0xxx:pvrType1ProductConfigId:rvnHP:rn8BCA:rvr77.54:cvnHP:ct10:cvrChassisVersion:sku836Q2EA#ABE:
dmi.product.family: 103C_5335M7 HP OMEN
dmi.product.name: OMEN by HP Gaming Laptop 16-xf0xxx
dmi.product.sku: 836Q2EA#ABE
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug questing 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/2147249
Title:
System randomly suspends
Status in linux package in Ubuntu:
New
Bug description:
The system suspends randomly since one or two weeks ago. The issue
happens specially while playing games (Genshin Impact), so it may be
related to a high energy demand.
Logs show some errors related to hardware (missing symbols in ACPI
BIOS). My device (HP OMEN 16) is known for a BIOS non-compliant with
Linux systems. I tried updating from bios version F.25 to F.31, but
issues persist.
There were no issues a couple weeks ago, so a system update may be
related, but I don't remember the exact date the issues started
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-20-generic 6.17.0-20.20
ProcVersionSignature: Ubuntu 6.17.0-20.20-generic 6.17.13
Uname: Linux 6.17.0-20-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 4 12:28:24 2026
InstallationDate: Installed on 2025-12-26 (99 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: HP OMEN by HP Gaming Laptop 16-xf0xxx
ProcEnviron:
LANG=es_ES.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-20-generic root=UUID=c0e4fef4-5db9-4a20-862b-db56e160e19c ro quiet splash acpi_osi=! "acpi_osi=Windows 2015" pcie_aspm=off 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.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/20/2025
dmi.bios.release: 15.31
dmi.bios.vendor: Insyde
dmi.bios.version: F.31
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8BCA
dmi.board.vendor: HP
dmi.board.version: 77.54
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 77.54
dmi.modalias: dmi:bvnInsyde:bvrF.31:bd11/20/2025:br15.31:efr77.54:svnHP:pnOMENbyHPGamingLaptop16-xf0xxx:pvrType1ProductConfigId:rvnHP:rn8BCA:rvr77.54:cvnHP:ct10:cvrChassisVersion:sku836Q2EA#ABE:
dmi.product.family: 103C_5335M7 HP OMEN
dmi.product.name: OMEN by HP Gaming Laptop 16-xf0xxx
dmi.product.sku: 836Q2EA#ABE
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147249/+subscriptions
The system suspends randomly since one or two weeks ago. The issue
happens specially while playing games (Genshin Impact), so it may be
related to a high energy demand.
Logs show some errors related to hardware (missing symbols in ACPI
BIOS). My device (HP OMEN 16) is known for a BIOS non-compliant with
Linux systems. I tried updating from bios version F.25 to F.31, but
issues persist.
There were no issues a couple weeks ago, so a system update may be
related, but I don't remember the exact date the issues started
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-20-generic 6.17.0-20.20
ProcVersionSignature: Ubuntu 6.17.0-20.20-generic 6.17.13
Uname: Linux 6.17.0-20-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 4 12:28:24 2026
InstallationDate: Installed on 2025-12-26 (99 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: HP OMEN by HP Gaming Laptop 16-xf0xxx
ProcEnviron:
LANG=es_ES.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-20-generic root=UUID=c0e4fef4-5db9-4a20-862b-db56e160e19c ro quiet splash acpi_osi=! "acpi_osi=Windows 2015" pcie_aspm=off 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.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/20/2025
dmi.bios.release: 15.31
dmi.bios.vendor: Insyde
dmi.bios.version: F.31
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8BCA
dmi.board.vendor: HP
dmi.board.version: 77.54
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 77.54
dmi.modalias: dmi:bvnInsyde:bvrF.31:bd11/20/2025:br15.31:efr77.54:svnHP:pnOMENbyHPGamingLaptop16-xf0xxx:pvrType1ProductConfigId:rvnHP:rn8BCA:rvr77.54:cvnHP:ct10:cvrChassisVersion:sku836Q2EA#ABE:
dmi.product.family: 103C_5335M7 HP OMEN
dmi.product.name: OMEN by HP Gaming Laptop 16-xf0xxx
dmi.product.sku: 836Q2EA#ABE
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug questing 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/2147249
Title:
System randomly suspends
Status in linux package in Ubuntu:
New
Bug description:
The system suspends randomly since one or two weeks ago. The issue
happens specially while playing games (Genshin Impact), so it may be
related to a high energy demand.
Logs show some errors related to hardware (missing symbols in ACPI
BIOS). My device (HP OMEN 16) is known for a BIOS non-compliant with
Linux systems. I tried updating from bios version F.25 to F.31, but
issues persist.
There were no issues a couple weeks ago, so a system update may be
related, but I don't remember the exact date the issues started
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-20-generic 6.17.0-20.20
ProcVersionSignature: Ubuntu 6.17.0-20.20-generic 6.17.13
Uname: Linux 6.17.0-20-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 4 12:28:24 2026
InstallationDate: Installed on 2025-12-26 (99 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: HP OMEN by HP Gaming Laptop 16-xf0xxx
ProcEnviron:
LANG=es_ES.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-20-generic root=UUID=c0e4fef4-5db9-4a20-862b-db56e160e19c ro quiet splash acpi_osi=! "acpi_osi=Windows 2015" pcie_aspm=off 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.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/20/2025
dmi.bios.release: 15.31
dmi.bios.vendor: Insyde
dmi.bios.version: F.31
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8BCA
dmi.board.vendor: HP
dmi.board.version: 77.54
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 77.54
dmi.modalias: dmi:bvnInsyde:bvrF.31:bd11/20/2025:br15.31:efr77.54:svnHP:pnOMENbyHPGamingLaptop16-xf0xxx:pvrType1ProductConfigId:rvnHP:rn8BCA:rvr77.54:cvnHP:ct10:cvrChassisVersion:sku836Q2EA#ABE:
dmi.product.family: 103C_5335M7 HP OMEN
dmi.product.name: OMEN by HP Gaming Laptop 16-xf0xxx
dmi.product.sku: 836Q2EA#ABE
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147249/+subscriptions
[Bug 2147246] [NEW] USB keyboard and mouse stop working on Linux kernel 6.17.0-20-generic (works on 6.17.0-19)
Public bug reported:
Bug Description (detailed)
System: Kubuntu 25.10
Kernel versions tested: 6.17.0-19 (works fine), 6.17.0-20 (problem occurs)
Problem:
After updating to kernel 6.17.0-20-generic, USB input devices stop working in certain configurations:
Upon login, keyboard works but mouse does not.
Moving the mouse to a USB 2.0 port temporarily restores mouse functionality, but keyboard then stops working.
Both devices work correctly on kernel 6.17.0-19.
Additional details:
No firmware updates or other changes were made between kernels.
Issue appears to be related to USB input devices handling in the new kernel.
/lib/firmware remains unchanged between the kernels.
Workarounds (temporary) include switching USB ports between 2.0 and 3.0, but this is not reliable.
Steps to reproduce:
Boot Kubuntu 25.10 with kernel 6.17.0-20.
Attempt to use keyboard and mouse via USB 3.0 ports.
Observe that one of the devices fails while the other works.
Switch mouse to USB 2.0 – mouse works, keyboard stops.
Expected behavior:
All USB input devices should work as they do on 6.17.0-19.
Impact:
Blocks normal use of the system, requiring kernel rollback to continue work.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-20-generic 6.17.0-20.20
ProcVersionSignature: Ubuntu 6.17.0-19.19-generic 6.17.13
Uname: Linux 6.17.0-19-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: kingscrafts 1419 F.... wireplumber
/dev/snd/seq: kingscrafts 1415 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sat Apr 4 12:53:26 2026
InstallationDate: Installed on 2026-03-20 (15 days ago)
InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: Hewlett-Packard HP Compaq Pro 6300 SFF
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-19-generic root=UUID=13d9f65b-c541-4b53-a9d4-1a8628551c57 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2013
dmi.bios.release: 2.90
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: K01 v02.90
dmi.board.name: 339A
dmi.board.vendor: Hewlett-Packard
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:br2.90:svnHewlett-Packard:pnHPCompaqPro6300SFF:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct4:cvr:skuH6B37EP#ABA:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP Compaq Pro 6300 SFF
dmi.product.sku: H6B37EP#ABA
dmi.sys.vendor: Hewlett-Packard
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug questing 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/2147246
Title:
USB keyboard and mouse stop working on Linux kernel 6.17.0-20-generic
(works on 6.17.0-19)
Status in linux package in Ubuntu:
New
Bug description:
Bug Description (detailed)
System: Kubuntu 25.10
Kernel versions tested: 6.17.0-19 (works fine), 6.17.0-20 (problem occurs)
Problem:
After updating to kernel 6.17.0-20-generic, USB input devices stop working in certain configurations:
Upon login, keyboard works but mouse does not.
Moving the mouse to a USB 2.0 port temporarily restores mouse functionality, but keyboard then stops working.
Both devices work correctly on kernel 6.17.0-19.
Additional details:
No firmware updates or other changes were made between kernels.
Issue appears to be related to USB input devices handling in the new kernel.
/lib/firmware remains unchanged between the kernels.
Workarounds (temporary) include switching USB ports between 2.0 and 3.0, but this is not reliable.
Steps to reproduce:
Boot Kubuntu 25.10 with kernel 6.17.0-20.
Attempt to use keyboard and mouse via USB 3.0 ports.
Observe that one of the devices fails while the other works.
Switch mouse to USB 2.0 – mouse works, keyboard stops.
Expected behavior:
All USB input devices should work as they do on 6.17.0-19.
Impact:
Blocks normal use of the system, requiring kernel rollback to continue work.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-20-generic 6.17.0-20.20
ProcVersionSignature: Ubuntu 6.17.0-19.19-generic 6.17.13
Uname: Linux 6.17.0-19-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: kingscrafts 1419 F.... wireplumber
/dev/snd/seq: kingscrafts 1415 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sat Apr 4 12:53:26 2026
InstallationDate: Installed on 2026-03-20 (15 days ago)
InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: Hewlett-Packard HP Compaq Pro 6300 SFF
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-19-generic root=UUID=13d9f65b-c541-4b53-a9d4-1a8628551c57 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2013
dmi.bios.release: 2.90
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: K01 v02.90
dmi.board.name: 339A
dmi.board.vendor: Hewlett-Packard
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:br2.90:svnHewlett-Packard:pnHPCompaqPro6300SFF:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct4:cvr:skuH6B37EP#ABA:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP Compaq Pro 6300 SFF
dmi.product.sku: H6B37EP#ABA
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147246/+subscriptions
Bug Description (detailed)
System: Kubuntu 25.10
Kernel versions tested: 6.17.0-19 (works fine), 6.17.0-20 (problem occurs)
Problem:
After updating to kernel 6.17.0-20-generic, USB input devices stop working in certain configurations:
Upon login, keyboard works but mouse does not.
Moving the mouse to a USB 2.0 port temporarily restores mouse functionality, but keyboard then stops working.
Both devices work correctly on kernel 6.17.0-19.
Additional details:
No firmware updates or other changes were made between kernels.
Issue appears to be related to USB input devices handling in the new kernel.
/lib/firmware remains unchanged between the kernels.
Workarounds (temporary) include switching USB ports between 2.0 and 3.0, but this is not reliable.
Steps to reproduce:
Boot Kubuntu 25.10 with kernel 6.17.0-20.
Attempt to use keyboard and mouse via USB 3.0 ports.
Observe that one of the devices fails while the other works.
Switch mouse to USB 2.0 – mouse works, keyboard stops.
Expected behavior:
All USB input devices should work as they do on 6.17.0-19.
Impact:
Blocks normal use of the system, requiring kernel rollback to continue work.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-20-generic 6.17.0-20.20
ProcVersionSignature: Ubuntu 6.17.0-19.19-generic 6.17.13
Uname: Linux 6.17.0-19-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: kingscrafts 1419 F.... wireplumber
/dev/snd/seq: kingscrafts 1415 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sat Apr 4 12:53:26 2026
InstallationDate: Installed on 2026-03-20 (15 days ago)
InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: Hewlett-Packard HP Compaq Pro 6300 SFF
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-19-generic root=UUID=13d9f65b-c541-4b53-a9d4-1a8628551c57 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2013
dmi.bios.release: 2.90
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: K01 v02.90
dmi.board.name: 339A
dmi.board.vendor: Hewlett-Packard
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:br2.90:svnHewlett-Packard:pnHPCompaqPro6300SFF:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct4:cvr:skuH6B37EP#ABA:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP Compaq Pro 6300 SFF
dmi.product.sku: H6B37EP#ABA
dmi.sys.vendor: Hewlett-Packard
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug questing 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/2147246
Title:
USB keyboard and mouse stop working on Linux kernel 6.17.0-20-generic
(works on 6.17.0-19)
Status in linux package in Ubuntu:
New
Bug description:
Bug Description (detailed)
System: Kubuntu 25.10
Kernel versions tested: 6.17.0-19 (works fine), 6.17.0-20 (problem occurs)
Problem:
After updating to kernel 6.17.0-20-generic, USB input devices stop working in certain configurations:
Upon login, keyboard works but mouse does not.
Moving the mouse to a USB 2.0 port temporarily restores mouse functionality, but keyboard then stops working.
Both devices work correctly on kernel 6.17.0-19.
Additional details:
No firmware updates or other changes were made between kernels.
Issue appears to be related to USB input devices handling in the new kernel.
/lib/firmware remains unchanged between the kernels.
Workarounds (temporary) include switching USB ports between 2.0 and 3.0, but this is not reliable.
Steps to reproduce:
Boot Kubuntu 25.10 with kernel 6.17.0-20.
Attempt to use keyboard and mouse via USB 3.0 ports.
Observe that one of the devices fails while the other works.
Switch mouse to USB 2.0 – mouse works, keyboard stops.
Expected behavior:
All USB input devices should work as they do on 6.17.0-19.
Impact:
Blocks normal use of the system, requiring kernel rollback to continue work.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-20-generic 6.17.0-20.20
ProcVersionSignature: Ubuntu 6.17.0-19.19-generic 6.17.13
Uname: Linux 6.17.0-19-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: kingscrafts 1419 F.... wireplumber
/dev/snd/seq: kingscrafts 1415 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sat Apr 4 12:53:26 2026
InstallationDate: Installed on 2026-03-20 (15 days ago)
InstallationMedia: Kubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: Hewlett-Packard HP Compaq Pro 6300 SFF
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-19-generic root=UUID=13d9f65b-c541-4b53-a9d4-1a8628551c57 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2013
dmi.bios.release: 2.90
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: K01 v02.90
dmi.board.name: 339A
dmi.board.vendor: Hewlett-Packard
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:br2.90:svnHewlett-Packard:pnHPCompaqPro6300SFF:pvr:rvnHewlett-Packard:rn339A:rvr:cvnHewlett-Packard:ct4:cvr:skuH6B37EP#ABA:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP Compaq Pro 6300 SFF
dmi.product.sku: H6B37EP#ABA
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147246/+subscriptions
[Bug 2147007] Re: Resolute kernel 7.0-10 kernel hangs on chattr stress test
** Changed in: linux (Ubuntu Resolute)
Status: New => Fix Committed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2147007
Title:
Resolute kernel 7.0-10 kernel hangs on chattr stress test
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Resolute:
Fix Committed
Bug description:
Summary:
Resolute Linux kernel 7.0-10 locks up on stress-ng chattr stress test
on am64, arm64, s390x, ppc64 (and maybe more) architectures.
Test procedure:
Install the Resulute daily server ISO into a VM, 8 CPU threads, 4GB
RAM, 25GB disk storage using ext4 as the file system. I'm using a
Intel(R) Core(TM) Ultra 9 285K for my server.
enable deb-src in /etc/apt/sources.list.d/*
sudo apt-get update
sudo apt-get build-dep stress-ng
git clone https://github.com/ColinIanKing/stress-ng
cd stress-ng
make clean
make -j 8
make verify-test-all
The chattr test takes a while and after a couple of minutes, the
chattr stressor produces repeated kernel errors:
INFO: task jbd2/dm-0.8:337 blocked for more than 122 seconds
This occurs on a range of architectures and is a regression from the
previous 6.x kernel results
This is a release blocker kernel issue in my opinon.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147007/+subscriptions
Status: New => Fix Committed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2147007
Title:
Resolute kernel 7.0-10 kernel hangs on chattr stress test
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Resolute:
Fix Committed
Bug description:
Summary:
Resolute Linux kernel 7.0-10 locks up on stress-ng chattr stress test
on am64, arm64, s390x, ppc64 (and maybe more) architectures.
Test procedure:
Install the Resulute daily server ISO into a VM, 8 CPU threads, 4GB
RAM, 25GB disk storage using ext4 as the file system. I'm using a
Intel(R) Core(TM) Ultra 9 285K for my server.
enable deb-src in /etc/apt/sources.list.d/*
sudo apt-get update
sudo apt-get build-dep stress-ng
git clone https://github.com/ColinIanKing/stress-ng
cd stress-ng
make clean
make -j 8
make verify-test-all
The chattr test takes a while and after a couple of minutes, the
chattr stressor produces repeated kernel errors:
INFO: task jbd2/dm-0.8:337 blocked for more than 122 seconds
This occurs on a range of architectures and is a regression from the
previous 6.x kernel results
This is a release blocker kernel issue in my opinon.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2147007/+subscriptions
[Bug 1763144] Re: Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows
I am experiencing significant slowdowns for my X220 and T480 with noble.
And I believe this is the reasons, but I am not sure. My only solution
so far is to disable thermald completely.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1763144
Title:
Significantly lower power and thermal limits on ThinkPad T480s (and
probably others) than on Windows
Status in linux package in Ubuntu:
Invalid
Status in thermald package in Ubuntu:
Incomplete
Bug description:
A ThinkPad T480s under windows has a power limit of 44W, both short
and long term, with a thermal maximum of about 93C or so. Under Linux,
the power limits are 44W and 15W (short) or so, and the thermal limit
is 80C, causing a significant performance loss.
Looking at MSR and MCHBAR values, we can see that the values are
correctly at 44W in the MSR, but the MCHBAR is set to a lower value:
$ sudo rdmsr -a 0x610
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
$ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
0x0042816000dd8078
Setting the MCHBAR to the same value as the MSR register solves the problem. At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.
The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
-d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
in performance comparative to Windows.
Most of the analysis is based on the analysis in
https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/
This applies to all bionic kernels I have tested so far, including
Ubuntu 4.15.0-13.14-generic 4.15.10
---
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/pcmC2D0p: jak 5881 F...m pulseaudio
/dev/snd/controlC2: jak 5881 F.... pulseaudio
/dev/snd/controlC1: jak 5881 F.... pulseaudio
/dev/snd/controlC0: jak 5881 F.... pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-03-14 (28 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
MachineType: LENOVO 20L8S02D00
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware 1.173
Tags: bionic
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/22/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N22ET31W (1.08 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L8S02D00
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.modalias: dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480s
dmi.product.name: 20L8S02D00
dmi.product.version: ThinkPad T480s
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763144/+subscriptions
And I believe this is the reasons, but I am not sure. My only solution
so far is to disable thermald completely.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1763144
Title:
Significantly lower power and thermal limits on ThinkPad T480s (and
probably others) than on Windows
Status in linux package in Ubuntu:
Invalid
Status in thermald package in Ubuntu:
Incomplete
Bug description:
A ThinkPad T480s under windows has a power limit of 44W, both short
and long term, with a thermal maximum of about 93C or so. Under Linux,
the power limits are 44W and 15W (short) or so, and the thermal limit
is 80C, causing a significant performance loss.
Looking at MSR and MCHBAR values, we can see that the values are
correctly at 44W in the MSR, but the MCHBAR is set to a lower value:
$ sudo rdmsr -a 0x610
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
42816000dd8160
$ sudo /home/jak/Downloads/iotools-1.5/iotools mmio_read64 0xfed159a0
0x0042816000dd8078
Setting the MCHBAR to the same value as the MSR register solves the problem. At some point intel-rapl seems to reduce overall frequency to 600 MHz, though.
The thermal limit is configured in MSR register 0x1a2; rdmsr -f 29:24
-d 0x1a2 returns 20. Setting those bits to 7 increases it, resulting
in performance comparative to Windows.
Most of the analysis is based on the analysis in
https://www.reddit.com/r/thinkpad/comments/870u0a/t480s_linux_throttling_bug/
This applies to all bionic kernels I have tested so far, including
Ubuntu 4.15.0-13.14-generic 4.15.10
---
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/pcmC2D0p: jak 5881 F...m pulseaudio
/dev/snd/controlC2: jak 5881 F.... pulseaudio
/dev/snd/controlC1: jak 5881 F.... pulseaudio
/dev/snd/controlC0: jak 5881 F.... pulseaudio
CurrentDesktop: GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-03-14 (28 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313)
MachineType: LENOVO 20L8S02D00
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: root=/dev/mapper/ubuntu--vg-root ro rootflags=subvol=@ quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
RelatedPackageVersions:
linux-restricted-modules-4.15.0-13-generic N/A
linux-backports-modules-4.15.0-13-generic N/A
linux-firmware 1.173
Tags: bionic
Uname: Linux 4.15.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/22/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N22ET31W (1.08 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20L8S02D00
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.modalias: dmi:bvnLENOVO:bvrN22ET31W(1.08):bd01/22/2018:svnLENOVO:pn20L8S02D00:pvrThinkPadT480s:rvnLENOVO:rn20L8S02D00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T480s
dmi.product.name: 20L8S02D00
dmi.product.version: ThinkPad T480s
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763144/+subscriptions
пятница
[Bug 1786013] Autopkgtest regression report (linux-meta-nvidia-6.17/6.17.0-1015.15)
All autopkgtests for the newly accepted linux-meta-nvidia-6.17 (6.17.0-1015.15) for noble have finished running.
The following regressions have been reported in tests triggered by the package:
linux-nvidia-6.17/6.17.0-1015.15 (arm64)
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/noble/update_excuses.html#linux-meta-nvidia-6.17
[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
The following regressions have been reported in tests triggered by the package:
linux-nvidia-6.17/6.17.0-1015.15 (arm64)
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/noble/update_excuses.html#linux-meta-nvidia-6.17
[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 1786013] Autopkgtest regression report (linux-meta-nvidia-6.8/6.8.0-1051.54~22.04.1)
All autopkgtests for the newly accepted linux-meta-nvidia-6.8 (6.8.0-1051.54~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
linux-nvidia-6.8/6.8.0-1051.54~22.04.1 (arm64)
snapd/2.73+ubuntu22.04.1 (arm64)
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-meta-nvidia-6.8
[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
The following regressions have been reported in tests triggered by the package:
linux-nvidia-6.8/6.8.0-1051.54~22.04.1 (arm64)
snapd/2.73+ubuntu22.04.1 (arm64)
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-meta-nvidia-6.8
[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 1786013] Autopkgtest regression report (linux-meta-azure-nvidia/6.8.0-1033.36)
All autopkgtests for the newly accepted linux-meta-azure-nvidia (6.8.0-1033.36) for noble have finished running.
The following regressions have been reported in tests triggered by the package:
linux-azure-nvidia/6.8.0-1033.36 (arm64)
systemd/255.4-1ubuntu8.14 (arm64)
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/noble/update_excuses.html#linux-meta-azure-nvidia
[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
The following regressions have been reported in tests triggered by the package:
linux-azure-nvidia/6.8.0-1033.36 (arm64)
systemd/255.4-1ubuntu8.14 (arm64)
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/noble/update_excuses.html#linux-meta-azure-nvidia
[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
Подписаться на:
Комментарии (Atom)