** Also affects: linux-oem-6.17 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Noble)
Status: New => Won't Fix
** Changed in: linux (Ubuntu Questing)
Status: New => Won't Fix
** Changed in: linux-oem-6.17 (Ubuntu Questing)
Status: New => Invalid
** Changed in: linux-oem-6.17 (Ubuntu Resolute)
Status: New => Invalid
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2130252
Title:
Support Intel Scorpius Peak, Whale Peak WiFi/Bluetooth for Intel
WildCat Lake platforms
Status in linux package in Ubuntu:
New
Status in linux-firmware package in Ubuntu:
Incomplete
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-firmware source package in Noble:
Incomplete
Status in linux-oem-6.17 source package in Noble:
New
Status in linux source package in Questing:
Won't Fix
Status in linux-firmware source package in Questing:
Won't Fix
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
New
Status in linux-firmware source package in Resolute:
Incomplete
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
Device IDs
* BE211 (WhP2)
- Wi-Fi: PCI\VEN_8086&DEV_4D40&SUBSYS_41108086
- BT: USB\VID_8087&PID_0033
* BE213 (SpP2)
- Wi-Fi: PCI\VEN_8086&DEV_4D40&SUBSYS_43148086
- BT: USB\VID_8087&PID_0033
* AX211 (GfP2)
- Wi-Fi: PCI\VEN_8086&DEV_4D40&SUBSYS_40908086
- BT: USB\VID_8087&PID_0033
Firmware names
* FmP2
- WiFi:
- iwlwifi-bz-b0-fm-c0: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=9440754a9 (-101.ucode, in upstream tag 20251021), https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=0a041632c (-c101.ucode)
- iwlwifi-bz-b0-fm4-b0
- BT:
- ibt-00a0-0291-{iml.sfi,pci.sfi,pci.ddc}: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=c56e10ea8
* Whale Peak2
- WiFi:
- iwlwifi-bz-b0-wh-a0 (ES)
- iwlwifi-bz-b0-wh-b0
- BT:
- ibt-00a0-00a1-{iml.sfi,pci.sfi,pci.ddc} (ES)
- ibt-1190-01a1-{iml.sfi,pci.sfi,pci.ddc}: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/intel/ibt-1190-0041-iml.sfi?id=397e9a13dbb4f74d72a58b48ae83c7313e8cc724
* Scorpius Peak2
- WiFi:
- iwlwifi-bz-b0-wh-a0 (ES)
- iwlwifi-bz-b0-wh-b0
- BT:
- ibt-00a0-00a1-{iml.sfi,pci.sfi,pci.ddc} (ES)
- ibt-1190-01a1-{iml.sfi,pci.sfi,pci.ddc}: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/intel/ibt-1190-0041-iml.sfi?id=397e9a13dbb4f74d72a58b48ae83c7313e8cc724
* GfP2
- WiFi:
- iwlwifi-bz-b0-gf-a0: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=f2fbfd22d (in upstream tag 20251021)
- BT:
- ibt-00a0-0041-{iml.sfi,pci.sfi,pci.ddc}: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=f383a2642
- ibt-0190-0041-{iml.sfi,pci.sfi,pci.ddc}: https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/commit/?id=ee03c5fb3
- ibt-1190-0041-{iml.sfi,pci.sfi,pci.ddc}: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/intel/ibt-1190-0041-iml.sfi?id=397e9a13dbb4f74d72a58b48ae83c7313e8cc724
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2130252/+subscriptions
понедельник
[Bug 2060924] Re: [Lenovo Ubuntu 24.04 Bug] Can not detect iscsi disk storage and kernel show " detected conn error (1020)"
Just an update for 26.04, this is still not addressed and is not on the
plan anytime soon.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2060924
Title:
[Lenovo Ubuntu 24.04 Bug] Can not detect iscsi disk storage and kernel
show " detected conn error (1020)"
Status in subiquity:
Triaged
Status in linux package in Ubuntu:
Triaged
Bug description:
Description:
When installing Ubuntu 24.04 in remote iscsi storage disk, the installer can not detect the remote iscsi storage. After install Ubuntu 24.04 to a local disk and boot up to OS, the OS can not detect the remote iscsi disk either.
Reproduce Steps:
1. Install Ubunut 24.04
2. Boot into OS
3. perform command lsblk check remote disk, there isn't one appeared.
Configuration:
System: Lenovo SR655V3
OS:noble-live-server-amd64-0401.iso
BMC Version ：2.30 (Build ID: KAX321V)
UEFI Version:3.10 (Build ID: KAE115K)
CPU:Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz*2 M321R2GA3BB6-CQKMG*8
NIC adapter: Mellanox ConnectX-6 Lx 10/25GbE SFP28 2-port PCIe Ethernet Adapte
storage：Lenovo D7000 or Lenovo V7000
Expected results:
OS can recognize the remote iscsi disk
Actual results:
OS cannot recognize the remote iscsi disk.
Additional info:
1. Ubuntu 22.04 also have this issue, But RHEL9.4 hasn't.
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/2060924/+subscriptions
plan anytime soon.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2060924
Title:
[Lenovo Ubuntu 24.04 Bug] Can not detect iscsi disk storage and kernel
show " detected conn error (1020)"
Status in subiquity:
Triaged
Status in linux package in Ubuntu:
Triaged
Bug description:
Description:
When installing Ubuntu 24.04 in remote iscsi storage disk, the installer can not detect the remote iscsi storage. After install Ubuntu 24.04 to a local disk and boot up to OS, the OS can not detect the remote iscsi disk either.
Reproduce Steps:
1. Install Ubunut 24.04
2. Boot into OS
3. perform command lsblk check remote disk, there isn't one appeared.
Configuration:
System: Lenovo SR655V3
OS:noble-live-server-amd64-0401.iso
BMC Version ：2.30 (Build ID: KAX321V)
UEFI Version:3.10 (Build ID: KAE115K)
CPU:Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz*2 M321R2GA3BB6-CQKMG*8
NIC adapter: Mellanox ConnectX-6 Lx 10/25GbE SFP28 2-port PCIe Ethernet Adapte
storage：Lenovo D7000 or Lenovo V7000
Expected results:
OS can recognize the remote iscsi disk
Actual results:
OS cannot recognize the remote iscsi disk.
Additional info:
1. Ubuntu 22.04 also have this issue, But RHEL9.4 hasn't.
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/2060924/+subscriptions
[Bug 2143104] Re: Enable CirrusLogic audio solution CS42L45+CS35L63 on AMD and Intel PTL
** Description changed:
SRU Justification:
[Impact]
New Dell Yukon platform with CirrusLogic audio solution CS42L45+CS35L63 will have no basic audio functions w/o AMD ACP Driver Support.
================ Linux Kernel ========================
[Fix]
Backport new AMD ACP drivers of the following
ASoC: amd: acp: Add ACP7.0 match entries for Cirrus Logic parts
ASoC: amd: acp: Sort Cirrus Logic match entries
ASoC: amd: acp: Rename Cirrus Logic component match entries to include link a...
ASoC: amd: acp: Sort match table into most specific first
ASoC: amd: amd_sdw: Propagate the PCI subsystem Vendor and Device IDs
ASoC: amd: ps: Propagate the PCI subsystem Vendor and Device IDs
ASoC: amd: acp: Add ACP7.0 match entries for cs35l56 and cs42l43
- And patches https://lore.kernel.org/linux-
- sound/20260205164539.892403-1-Vijendar.Mukunda@amd.com/T/#t which are
- still under review.
+ And patches for support AMD 6MHz clock frequency for SoundWire
+ 27ab4f1e4909 soundwire: amd: refactor bandwidth calculation logic
+ 2a267a841084 soundwire: amd: add clock init control function
<=============== linux-firmware ========================
[Fix]
Backport the patch firmware from CirrusLogic
8ca12d638 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Dell laptops
53ec87319 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Lenovo laptops
4aaa9c557 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Dell laptops
[Test Case]
1. Boot up the machine of new Dell Yukon (PTL and GPT) platform with CirrusLogic CS42L45+CS35L63
2. Open settings->Sound->Output Device and make sure it's not Dummy audio devices
3. Click test icon for basic audio output functions
4. Use `arecord` to record and play the recorded audio file with `aplay` for basic speaker/microphone functions.
[Where problems could occur]
It adds the support for new CirrusLogic CS42L45+CS35L63. No regression expected at the current stage.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143104
Title:
Enable CirrusLogic audio solution CS42L45+CS35L63 on AMD and Intel PTL
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-firmware source package in Noble:
Fix Committed
Status in linux-oem-6.17 source package in Noble:
In Progress
Status in linux source package in Questing:
Won't Fix
Status in linux-firmware source package in Questing:
Fix Committed
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Incomplete
Status in linux-firmware source package in Resolute:
Fix Released
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
SRU Justification:
[Impact]
New Dell Yukon platform with CirrusLogic audio solution CS42L45+CS35L63 will have no basic audio functions w/o AMD ACP Driver Support.
================ Linux Kernel ========================
[Fix]
Backport new AMD ACP drivers of the following
ASoC: amd: acp: Add ACP7.0 match entries for Cirrus Logic parts
ASoC: amd: acp: Sort Cirrus Logic match entries
ASoC: amd: acp: Rename Cirrus Logic component match entries to include link a...
ASoC: amd: acp: Sort match table into most specific first
ASoC: amd: amd_sdw: Propagate the PCI subsystem Vendor and Device IDs
ASoC: amd: ps: Propagate the PCI subsystem Vendor and Device IDs
ASoC: amd: acp: Add ACP7.0 match entries for cs35l56 and cs42l43
And patches for support AMD 6MHz clock frequency for SoundWire
27ab4f1e4909 soundwire: amd: refactor bandwidth calculation logic
2a267a841084 soundwire: amd: add clock init control function
<=============== linux-firmware ========================
[Fix]
Backport the patch firmware from CirrusLogic
8ca12d638 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Dell laptops
53ec87319 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Lenovo laptops
4aaa9c557 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Dell laptops
[Test Case]
1. Boot up the machine of new Dell Yukon (PTL and GPT) platform with CirrusLogic CS42L45+CS35L63
2. Open settings->Sound->Output Device and make sure it's not Dummy audio devices
3. Click test icon for basic audio output functions
4. Use `arecord` to record and play the recorded audio file with `aplay` for basic speaker/microphone functions.
[Where problems could occur]
It adds the support for new CirrusLogic CS42L45+CS35L63. No regression expected at the current stage.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2143104/+subscriptions
SRU Justification:
[Impact]
New Dell Yukon platform with CirrusLogic audio solution CS42L45+CS35L63 will have no basic audio functions w/o AMD ACP Driver Support.
================ Linux Kernel ========================
[Fix]
Backport new AMD ACP drivers of the following
ASoC: amd: acp: Add ACP7.0 match entries for Cirrus Logic parts
ASoC: amd: acp: Sort Cirrus Logic match entries
ASoC: amd: acp: Rename Cirrus Logic component match entries to include link a...
ASoC: amd: acp: Sort match table into most specific first
ASoC: amd: amd_sdw: Propagate the PCI subsystem Vendor and Device IDs
ASoC: amd: ps: Propagate the PCI subsystem Vendor and Device IDs
ASoC: amd: acp: Add ACP7.0 match entries for cs35l56 and cs42l43
- And patches https://lore.kernel.org/linux-
- sound/20260205164539.892403-1-Vijendar.Mukunda@amd.com/T/#t which are
- still under review.
+ And patches for support AMD 6MHz clock frequency for SoundWire
+ 27ab4f1e4909 soundwire: amd: refactor bandwidth calculation logic
+ 2a267a841084 soundwire: amd: add clock init control function
<=============== linux-firmware ========================
[Fix]
Backport the patch firmware from CirrusLogic
8ca12d638 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Dell laptops
53ec87319 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Lenovo laptops
4aaa9c557 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Dell laptops
[Test Case]
1. Boot up the machine of new Dell Yukon (PTL and GPT) platform with CirrusLogic CS42L45+CS35L63
2. Open settings->Sound->Output Device and make sure it's not Dummy audio devices
3. Click test icon for basic audio output functions
4. Use `arecord` to record and play the recorded audio file with `aplay` for basic speaker/microphone functions.
[Where problems could occur]
It adds the support for new CirrusLogic CS42L45+CS35L63. No regression expected at the current stage.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143104
Title:
Enable CirrusLogic audio solution CS42L45+CS35L63 on AMD and Intel PTL
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-firmware source package in Noble:
Fix Committed
Status in linux-oem-6.17 source package in Noble:
In Progress
Status in linux source package in Questing:
Won't Fix
Status in linux-firmware source package in Questing:
Fix Committed
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Incomplete
Status in linux-firmware source package in Resolute:
Fix Released
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
SRU Justification:
[Impact]
New Dell Yukon platform with CirrusLogic audio solution CS42L45+CS35L63 will have no basic audio functions w/o AMD ACP Driver Support.
================ Linux Kernel ========================
[Fix]
Backport new AMD ACP drivers of the following
ASoC: amd: acp: Add ACP7.0 match entries for Cirrus Logic parts
ASoC: amd: acp: Sort Cirrus Logic match entries
ASoC: amd: acp: Rename Cirrus Logic component match entries to include link a...
ASoC: amd: acp: Sort match table into most specific first
ASoC: amd: amd_sdw: Propagate the PCI subsystem Vendor and Device IDs
ASoC: amd: ps: Propagate the PCI subsystem Vendor and Device IDs
ASoC: amd: acp: Add ACP7.0 match entries for cs35l56 and cs42l43
And patches for support AMD 6MHz clock frequency for SoundWire
27ab4f1e4909 soundwire: amd: refactor bandwidth calculation logic
2a267a841084 soundwire: amd: add clock init control function
<=============== linux-firmware ========================
[Fix]
Backport the patch firmware from CirrusLogic
8ca12d638 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Dell laptops
53ec87319 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Lenovo laptops
4aaa9c557 cirrus: cs42l45: Add CS42L45 SDCA codec firmware for Dell laptops
[Test Case]
1. Boot up the machine of new Dell Yukon (PTL and GPT) platform with CirrusLogic CS42L45+CS35L63
2. Open settings->Sound->Output Device and make sure it's not Dummy audio devices
3. Click test icon for basic audio output functions
4. Use `arecord` to record and play the recorded audio file with `aplay` for basic speaker/microphone functions.
[Where problems could occur]
It adds the support for new CirrusLogic CS42L45+CS35L63. No regression expected at the current stage.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2143104/+subscriptions
[Bug 2116144] Re: Realtek RTL8116AF SFP option module fails to get connected
** Tags added: jira-wtn-384
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2116144
Title:
Realtek RTL8116AF SFP option module fails to get connected
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Invalid
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux-oem-6.17 source package in Noble:
In Progress
Status in linux source package in Questing:
Invalid
Status in linux-oem-6.14 source package in Questing:
Invalid
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Incomplete
Status in linux-oem-6.14 source package in Resolute:
Invalid
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[Impact]
It cannot enable LAN when connecting with Realtek RTL8116AF SFP option module.
[Fix]
Realtek provides a patch to fix this issue.
[Test]
1.Connect transceiver and network cable to SFP option module.
2.Boot to OS.
3.Ping SUT and the network should work
[Where problems could occur]
The patch is dedicated for 8116 chip
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2116144/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2116144
Title:
Realtek RTL8116AF SFP option module fails to get connected
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Invalid
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux-oem-6.17 source package in Noble:
In Progress
Status in linux source package in Questing:
Invalid
Status in linux-oem-6.14 source package in Questing:
Invalid
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Incomplete
Status in linux-oem-6.14 source package in Resolute:
Invalid
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[Impact]
It cannot enable LAN when connecting with Realtek RTL8116AF SFP option module.
[Fix]
Realtek provides a patch to fix this issue.
[Test]
1.Connect transceiver and network cable to SFP option module.
2.Boot to OS.
3.Ping SUT and the network should work
[Where problems could occur]
The patch is dedicated for 8116 chip
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2116144/+subscriptions
[Bug 2143056] Re: ath12k/WCN7850 (FastConnect 7800) 5GHz scan failure on kernel 6.17 -- works on 6.14
Hi Mark,
Thank you for your detailed report on the ath12k/WCN7850 5GHz scan
failure on kernel 6.17.
I've investigated this issue and can confirm it's a known upstream
regression affecting the Qualcomm FastConnect 7800 (WCN785x) Wi-Fi
adapter when using Linux kernel 6.17+. The problem stems from frequency
range filtering logic introduced in kernel 6.17 that breaks single-phy
devices like yours.
Good news: patches to fix this have been submitted to the linux-wireless mailing list by Saikiran B on January 23, 2026 and are currently under review. You can read the discussion here:
https://lore.kernel.org/linux-wireless/20260123155750.6007-1-bjsaikiran@gmail.com/T/#t
In the meantime, your workaround of using kernel 6.14.0-37-generic is
confirmed effective. Please continue using that kernel until an upstream
fix is merged and backported to Ubuntu's stable releases.
Thanks again for helping improve Ubuntu!
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143056
Title:
ath12k/WCN7850 (FastConnect 7800) 5GHz scan failure on kernel 6.17 --
works on 6.14
Status in linux package in Ubuntu:
Confirmed
Bug description:
On kernel 6.17.0-14-generic, the Qualcomm FastConnect 7800 (WCN7850) Wi-Fi adapter is completely unable to detect or connect to 5GHz networks. Only 2.4GHz networks are visible. The issue does not occur on kernel 6.14.0-37-generic, confirming this is a 6.17 regression.
Symptoms:
No 5GHz networks appear in scan results (nmcli dev wifi list / iwlist scan)
Repeated "received scan start failure event" in dmesg
Throughput dropped from ~600 Mbps (5GHz on 6.14) to ~60 Mbps (2.4GHz only on 6.17)
phy#0 self-manages regulatory domain, setting country 00 with all 5GHz channels as PASSIVE-SCAN only
Hardware:
Qualcomm WCN785x Wi-Fi 7 FastConnect 7800, PCI 0000:09:00.0 rev 01
Subsystem: Foxconn International
Firmware: WLAN.HMT.1.1.c5-00284.1, build 2025-05-17
Driver: ath12k_pci (compiled into kernel, not a module)
Kernel log (6.17 boot):
```
ath12k_pci 0000:09:00.0: received scan start failure event
ath12k_pci 0000:09:00.0: received scan start failure event
ath12k_pci 0000:09:00.0: received scan start failure event
ath12k_pci 0000:09:00.0: received scan start failure event
```
Additional notes:
No ath12k firmware packages were updated prior to the regression
ath12k on 6.17 only exposes debug_mask and ftm_mode module params — no regulatory override available
country_code and reg_proto_off params are silently ignored
Workaround: Booting kernel 6.14.0-37-generic fully resolves the issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143056/+subscriptions
Thank you for your detailed report on the ath12k/WCN7850 5GHz scan
failure on kernel 6.17.
I've investigated this issue and can confirm it's a known upstream
regression affecting the Qualcomm FastConnect 7800 (WCN785x) Wi-Fi
adapter when using Linux kernel 6.17+. The problem stems from frequency
range filtering logic introduced in kernel 6.17 that breaks single-phy
devices like yours.
Good news: patches to fix this have been submitted to the linux-wireless mailing list by Saikiran B on January 23, 2026 and are currently under review. You can read the discussion here:
https://lore.kernel.org/linux-wireless/20260123155750.6007-1-bjsaikiran@gmail.com/T/#t
In the meantime, your workaround of using kernel 6.14.0-37-generic is
confirmed effective. Please continue using that kernel until an upstream
fix is merged and backported to Ubuntu's stable releases.
Thanks again for helping improve Ubuntu!
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143056
Title:
ath12k/WCN7850 (FastConnect 7800) 5GHz scan failure on kernel 6.17 --
works on 6.14
Status in linux package in Ubuntu:
Confirmed
Bug description:
On kernel 6.17.0-14-generic, the Qualcomm FastConnect 7800 (WCN7850) Wi-Fi adapter is completely unable to detect or connect to 5GHz networks. Only 2.4GHz networks are visible. The issue does not occur on kernel 6.14.0-37-generic, confirming this is a 6.17 regression.
Symptoms:
No 5GHz networks appear in scan results (nmcli dev wifi list / iwlist scan)
Repeated "received scan start failure event" in dmesg
Throughput dropped from ~600 Mbps (5GHz on 6.14) to ~60 Mbps (2.4GHz only on 6.17)
phy#0 self-manages regulatory domain, setting country 00 with all 5GHz channels as PASSIVE-SCAN only
Hardware:
Qualcomm WCN785x Wi-Fi 7 FastConnect 7800, PCI 0000:09:00.0 rev 01
Subsystem: Foxconn International
Firmware: WLAN.HMT.1.1.c5-00284.1, build 2025-05-17
Driver: ath12k_pci (compiled into kernel, not a module)
Kernel log (6.17 boot):
```
ath12k_pci 0000:09:00.0: received scan start failure event
ath12k_pci 0000:09:00.0: received scan start failure event
ath12k_pci 0000:09:00.0: received scan start failure event
ath12k_pci 0000:09:00.0: received scan start failure event
```
Additional notes:
No ath12k firmware packages were updated prior to the regression
ath12k on 6.17 only exposes debug_mask and ftm_mode module params — no regulatory override available
country_code and reg_proto_off params are silently ignored
Workaround: Booting kernel 6.14.0-37-generic fully resolves the issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2143056/+subscriptions
[Bug 2143056] [NEW] ath12k/WCN7850 (FastConnect 7800) 5GHz scan failure on kernel 6.17 -- works on 6.14
You have been subscribed to a public bug:
On kernel 6.17.0-14-generic, the Qualcomm FastConnect 7800 (WCN7850) Wi-Fi adapter is completely unable to detect or connect to 5GHz networks. Only 2.4GHz networks are visible. The issue does not occur on kernel 6.14.0-37-generic, confirming this is a 6.17 regression.
Symptoms:
No 5GHz networks appear in scan results (nmcli dev wifi list / iwlist scan)
Repeated "received scan start failure event" in dmesg
Throughput dropped from ~600 Mbps (5GHz on 6.14) to ~60 Mbps (2.4GHz only on 6.17)
phy#0 self-manages regulatory domain, setting country 00 with all 5GHz channels as PASSIVE-SCAN only
Hardware:
Qualcomm WCN785x Wi-Fi 7 FastConnect 7800, PCI 0000:09:00.0 rev 01
Subsystem: Foxconn International
Firmware: WLAN.HMT.1.1.c5-00284.1, build 2025-05-17
Driver: ath12k_pci (compiled into kernel, not a module)
Kernel log (6.17 boot):
```
ath12k_pci 0000:09:00.0: received scan start failure event
ath12k_pci 0000:09:00.0: received scan start failure event
ath12k_pci 0000:09:00.0: received scan start failure event
ath12k_pci 0000:09:00.0: received scan start failure event
```
Additional notes:
No ath12k firmware packages were updated prior to the regression
ath12k on 6.17 only exposes debug_mask and ftm_mode module params — no regulatory override available
country_code and reg_proto_off params are silently ignored
Workaround: Booting kernel 6.14.0-37-generic fully resolves the issue.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: ath12k kernel-6.17 regression wifi
--
ath12k/WCN7850 (FastConnect 7800) 5GHz scan failure on kernel 6.17 -- works on 6.14
https://bugs.launchpad.net/bugs/2143056
You received this bug notification because you are subscribed to linux in Ubuntu.
On kernel 6.17.0-14-generic, the Qualcomm FastConnect 7800 (WCN7850) Wi-Fi adapter is completely unable to detect or connect to 5GHz networks. Only 2.4GHz networks are visible. The issue does not occur on kernel 6.14.0-37-generic, confirming this is a 6.17 regression.
Symptoms:
No 5GHz networks appear in scan results (nmcli dev wifi list / iwlist scan)
Repeated "received scan start failure event" in dmesg
Throughput dropped from ~600 Mbps (5GHz on 6.14) to ~60 Mbps (2.4GHz only on 6.17)
phy#0 self-manages regulatory domain, setting country 00 with all 5GHz channels as PASSIVE-SCAN only
Hardware:
Qualcomm WCN785x Wi-Fi 7 FastConnect 7800, PCI 0000:09:00.0 rev 01
Subsystem: Foxconn International
Firmware: WLAN.HMT.1.1.c5-00284.1, build 2025-05-17
Driver: ath12k_pci (compiled into kernel, not a module)
Kernel log (6.17 boot):
```
ath12k_pci 0000:09:00.0: received scan start failure event
ath12k_pci 0000:09:00.0: received scan start failure event
ath12k_pci 0000:09:00.0: received scan start failure event
ath12k_pci 0000:09:00.0: received scan start failure event
```
Additional notes:
No ath12k firmware packages were updated prior to the regression
ath12k on 6.17 only exposes debug_mask and ftm_mode module params — no regulatory override available
country_code and reg_proto_off params are silently ignored
Workaround: Booting kernel 6.14.0-37-generic fully resolves the issue.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: ath12k kernel-6.17 regression wifi
--
ath12k/WCN7850 (FastConnect 7800) 5GHz scan failure on kernel 6.17 -- works on 6.14
https://bugs.launchpad.net/bugs/2143056
You received this bug notification because you are subscribed to linux in Ubuntu.
[Bug 2144592] Re: Punching hole through CephFS hosted file causes corruption when crossing 4MB RADOS object boundary
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2144592
Title:
Punching hole through CephFS hosted file causes corruption when
crossing 4MB RADOS object boundary
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Noble:
New
Bug description:
Running Ceph FS on Ubuntu 24.04 (6.8 kernel) - Ubuntu
6.8.0-100.100-generic 6.8.12
Enclosed script reproduce-ceph-punch-hole-corruption.py exposes issue
that we have found that on recent kernels CephFS silently corrupts
16KB of data before the requested hole when trying to punch a hole
through file (test uses fallocate()). Corruption only occurs when hole
touches or crosses a 4MB RADOS object boundary (4MB is the default
stripe size).
Execution shows the corruption:
# python3 ./reproduce-ceph-punch-hole-corruption.py /Shared_DataStore/
CephFS PUNCH_HOLE data corruption reproducer
============================================================
Mount point: /Shared_DataStore/
Object size: 4194304 (4 MiB)
Tests crossing 4MB object boundary (expect FAIL on buggy kernels):
------------------------------------------------------------
FAIL 1 page before boundary, 2 pages
hole=[4190208, 4198400) checked=[4173824, 4190208)
16384/16384 bytes read as 0x00 (expected 0xFF)
FAIL 2 pages before boundary, 4 pages
hole=[4186112, 4202496) checked=[4169728, 4186112)
16384/16384 bytes read as 0x00 (expected 0xFF)
FAIL 4 pages before boundary, 8 pages
hole=[4177920, 4210688) checked=[4161536, 4177920)
16384/16384 bytes read as 0x00 (expected 0xFF)
FAIL ends at boundary, 2 pages
hole=[4186112, 4194304) checked=[4169728, 4186112)
16384/16384 bytes read as 0x00 (expected 0xFF)
FAIL ends at boundary, 1 page
hole=[4190208, 4194304) checked=[4173824, 4190208)
16384/16384 bytes read as 0x00 (expected 0xFF)
Tests NOT crossing boundary (should always PASS):
------------------------------------------------------------
PASS within object 0
hole=[4161536, 4169728) checked=[4145152, 4161536)
PASS mid object 0
hole=[1048576, 1056768) checked=[1032192, 1048576)
PASS start of object 1
hole=[4194304, 4202496) checked=[4177920, 4194304)
PASS within object 1
hole=[5242880, 5251072) checked=[5226496, 5242880)
============================================================
Results: 4 passed, 5 failed out of 9
BUG CONFIRMED: This kernel has the CephFS PUNCH_HOLE corruption bug.
Enclosed is a patch submission detailing issue (AI created):
0001-ceph-fix-data-corruption-from-short-read-on-punch-hole.patch
With patch test script now passes:
# python3 /home/eceuser/reproduce-ceph-punch-hole-corruption.py /Shared_DataStore/
CephFS PUNCH_HOLE data corruption reproducer
============================================================
Mount point: /Shared_DataStore/
Object size: 4194304 (4 MiB)
Tests crossing 4MB object boundary (expect FAIL on buggy kernels):
------------------------------------------------------------
PASS 1 page before boundary, 2 pages
hole=[4190208, 4198400) checked=[4173824, 4190208)
PASS 2 pages before boundary, 4 pages
hole=[4186112, 4202496) checked=[4169728, 4186112)
PASS 4 pages before boundary, 8 pages
hole=[4177920, 4210688) checked=[4161536, 4177920)
PASS ends at boundary, 2 pages
hole=[4186112, 4194304) checked=[4169728, 4186112)
PASS ends at boundary, 1 page
hole=[4190208, 4194304) checked=[4173824, 4190208)
Tests NOT crossing boundary (should always PASS):
------------------------------------------------------------
PASS within object 0
hole=[4161536, 4169728) checked=[4145152, 4161536)
PASS mid object 0
hole=[1048576, 1056768) checked=[1032192, 1048576)
PASS start of object 1
hole=[4194304, 4202496) checked=[4177920, 4194304)
PASS within object 1
hole=[5242880, 5251072) checked=[5226496, 5242880)
============================================================
Results: 9 passed, 0 failed out of 9
All tests passed. This kernel is not affected (or the fix is applied).
Appears as if following commit causes the issue:
92b6cc5d1e7c ("netfs: Add iov_iters to (sub)requests to describe various buffers") by David Howells, authored 2023-09-27, committed 2023-12-24. Merged in v6.8-rc1.
This is only present in 6.8 and 6.9 kernels, 6.10 rewrote this
activity under ee4cdf7ba857 ("netfs: Speed up buffered reading") by
David Howells, 2024-07-02. Merged in v6.10.) which no longer has this
issue.
Asking for either analysis of enclosed patch to be included into
Stable or if there is another/better way to fix.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144592/+subscriptions
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2144592
Title:
Punching hole through CephFS hosted file causes corruption when
crossing 4MB RADOS object boundary
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Noble:
New
Bug description:
Running Ceph FS on Ubuntu 24.04 (6.8 kernel) - Ubuntu
6.8.0-100.100-generic 6.8.12
Enclosed script reproduce-ceph-punch-hole-corruption.py exposes issue
that we have found that on recent kernels CephFS silently corrupts
16KB of data before the requested hole when trying to punch a hole
through file (test uses fallocate()). Corruption only occurs when hole
touches or crosses a 4MB RADOS object boundary (4MB is the default
stripe size).
Execution shows the corruption:
# python3 ./reproduce-ceph-punch-hole-corruption.py /Shared_DataStore/
CephFS PUNCH_HOLE data corruption reproducer
============================================================
Mount point: /Shared_DataStore/
Object size: 4194304 (4 MiB)
Tests crossing 4MB object boundary (expect FAIL on buggy kernels):
------------------------------------------------------------
FAIL 1 page before boundary, 2 pages
hole=[4190208, 4198400) checked=[4173824, 4190208)
16384/16384 bytes read as 0x00 (expected 0xFF)
FAIL 2 pages before boundary, 4 pages
hole=[4186112, 4202496) checked=[4169728, 4186112)
16384/16384 bytes read as 0x00 (expected 0xFF)
FAIL 4 pages before boundary, 8 pages
hole=[4177920, 4210688) checked=[4161536, 4177920)
16384/16384 bytes read as 0x00 (expected 0xFF)
FAIL ends at boundary, 2 pages
hole=[4186112, 4194304) checked=[4169728, 4186112)
16384/16384 bytes read as 0x00 (expected 0xFF)
FAIL ends at boundary, 1 page
hole=[4190208, 4194304) checked=[4173824, 4190208)
16384/16384 bytes read as 0x00 (expected 0xFF)
Tests NOT crossing boundary (should always PASS):
------------------------------------------------------------
PASS within object 0
hole=[4161536, 4169728) checked=[4145152, 4161536)
PASS mid object 0
hole=[1048576, 1056768) checked=[1032192, 1048576)
PASS start of object 1
hole=[4194304, 4202496) checked=[4177920, 4194304)
PASS within object 1
hole=[5242880, 5251072) checked=[5226496, 5242880)
============================================================
Results: 4 passed, 5 failed out of 9
BUG CONFIRMED: This kernel has the CephFS PUNCH_HOLE corruption bug.
Enclosed is a patch submission detailing issue (AI created):
0001-ceph-fix-data-corruption-from-short-read-on-punch-hole.patch
With patch test script now passes:
# python3 /home/eceuser/reproduce-ceph-punch-hole-corruption.py /Shared_DataStore/
CephFS PUNCH_HOLE data corruption reproducer
============================================================
Mount point: /Shared_DataStore/
Object size: 4194304 (4 MiB)
Tests crossing 4MB object boundary (expect FAIL on buggy kernels):
------------------------------------------------------------
PASS 1 page before boundary, 2 pages
hole=[4190208, 4198400) checked=[4173824, 4190208)
PASS 2 pages before boundary, 4 pages
hole=[4186112, 4202496) checked=[4169728, 4186112)
PASS 4 pages before boundary, 8 pages
hole=[4177920, 4210688) checked=[4161536, 4177920)
PASS ends at boundary, 2 pages
hole=[4186112, 4194304) checked=[4169728, 4186112)
PASS ends at boundary, 1 page
hole=[4190208, 4194304) checked=[4173824, 4190208)
Tests NOT crossing boundary (should always PASS):
------------------------------------------------------------
PASS within object 0
hole=[4161536, 4169728) checked=[4145152, 4161536)
PASS mid object 0
hole=[1048576, 1056768) checked=[1032192, 1048576)
PASS start of object 1
hole=[4194304, 4202496) checked=[4177920, 4194304)
PASS within object 1
hole=[5242880, 5251072) checked=[5226496, 5242880)
============================================================
Results: 9 passed, 0 failed out of 9
All tests passed. This kernel is not affected (or the fix is applied).
Appears as if following commit causes the issue:
92b6cc5d1e7c ("netfs: Add iov_iters to (sub)requests to describe various buffers") by David Howells, authored 2023-09-27, committed 2023-12-24. Merged in v6.8-rc1.
This is only present in 6.8 and 6.9 kernels, 6.10 rewrote this
activity under ee4cdf7ba857 ("netfs: Speed up buffered reading") by
David Howells, 2024-07-02. Merged in v6.10.) which no longer has this
issue.
Asking for either analysis of enclosed patch to be included into
Stable or if there is another/better way to fix.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144592/+subscriptions
[Bug 2144526] Re: Git clone/fetch latest tag code not working
The git servers are under extreme load lately due to AI scrapers, and
the IS Team are struggling to keep them online. You might have noticed
that all web requests to git.launchpad.net return 503 these days.
My suggestion is to try again at a different time.
If possible, use a reference to upstream linux to reduce load on
launchpad servers.
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ git clone --reference ./linux git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble ubuntu-noble
$ cd ubuntu-noble
$ git remote add linus ../linux
$ git fetch linus
Thanks,
Matthew
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2144526
Title:
Git clone/fetch latest tag code not working
Status in linux package in Ubuntu:
Invalid
Bug description:
git clone https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/noble
Cloning of the code is not working.
Error message:
Failed to connect to git.launchpad.net port 443 after 42385 ms:
Couldn't connect to server.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144526/+subscriptions
the IS Team are struggling to keep them online. You might have noticed
that all web requests to git.launchpad.net return 503 these days.
My suggestion is to try again at a different time.
If possible, use a reference to upstream linux to reduce load on
launchpad servers.
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ git clone --reference ./linux git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble ubuntu-noble
$ cd ubuntu-noble
$ git remote add linus ../linux
$ git fetch linus
Thanks,
Matthew
** Changed in: linux (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2144526
Title:
Git clone/fetch latest tag code not working
Status in linux package in Ubuntu:
Invalid
Bug description:
git clone https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/noble
Cloning of the code is not working.
Error message:
Failed to connect to git.launchpad.net port 443 after 42385 ms:
Couldn't connect to server.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144526/+subscriptions
[Bug 2144522] Re: Dell Machines cannot boot into OS with 6.17.0-1012-oem
** Tags added: kernel-daily-bug
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2144522
Title:
Dell Machines cannot boot into OS with 6.17.0-1012-oem
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Invalid
Status in linux-oem-6.17 source package in Noble:
In Progress
Status in linux source package in Questing:
In Progress
Status in linux-oem-6.17 source package in Questing:
Invalid
Bug description:
[Impact]
Dell systems (CID: 202506-36819, 202506-36820, 202506-36823, 202506-36826) with
AMD GFX 11.0.4 (gfx11) graphics cannot boot into the OS after upgrading to
6.17.0-1012-oem. The machine becomes stuck during boot and cannot reach the
desktop. Booting with `nomodeset` works as a workaround, pointing to an amdgpu
driver initialization failure.
Failure rate: 4/4 (100%) on affected Dell systems.
[Fix]
Two patches fix this boot regression:
1. Raise the minimum MES firmware version for calling set_hw_resources_1 on
GC 11.0.4 from 0x50 to 0x52, ensuring firmware that cannot properly
initialize this call is not used.
upstream in mainline kernel v7.0:
1478a34470bf drm/amd: Set minimum version for set_hw_resource_1 on gfx11 to 0x52
2. Remove the MES LR compute workaround (enable_lr_compute_wa) from both
mes_v11_0.c and mes_v12_0.c, since the underlying issue was already fixed by
adjusting the VGPR size, and keeping the workaround causes instability with
newer GC microcode.
upstream in mainline kernel v7.0:
6b0d812971370 drm/amd: Disable MES LR compute W/A
[Test Plan]
Boot the affected machine with kernel 6.17.0-1012-oem (or later oem kernel).
Without the patches: System gets stuck during boot and cannot reach the OS
(amdgpu fails to initialize).
With the patches: System boots normally to the desktop without requiring
`nomodeset`.
To verify:
1. Boot without `nomodeset`
2. Check that the desktop loads successfully
3. Confirm no amdgpu-related errors blocking boot in dmesg:
$ sudo dmesg | grep -i "amdgpu\|mes\|drm"
[Where problems could occur]
These changes affect the amdgpu MES initialization path for gfx11 (mes_v11_0.c)
and gfx12 (mes_v12_0.c) hardware.
For patch 1: If the version threshold 0x52 is incorrect, machines with MES
firmware between 0x50 and 0x51 that previously worked could stop calling
set_hw_resources_1, potentially causing degraded GPU performance or missing
hardware resource configuration. This would manifest as graphical glitches,
GPU compute failures, or silent capability loss after MES initialization.
For patch 2: If the LR compute workaround was actually needed for some
gfx11/gfx12 product beyond gfx1151, removing it could cause GPU hangs or
compute workload failures on those variants. Symptoms would include GPU hangs,
DRM timeout errors, or compute job failures under load.
[Other Info]
Both patches are upstream in Linux 7.0 (merged via drm-next-2026-02-11).
=================================================================
[Summary]
Several Dell Machines failed to boot into OS on 6.17.0-1012-oem.
[Reproduce Steps]
1. Install the GM image (6.11).
2. Run the dist-upgrade to 6.17
3. sudo reboot
On 6.11, the machine can boot into OS after reboot. However, after
upgrading to 6.17, it becomes stuck during boot and cannot reach the
OS. However, if root is modified to nomodeset in 6.17, the machine can
boot into the OS successfully.
[Affected Machines]
https://certification.canonical.com/hardware/202506-36819/
https://certification.canonical.com/hardware/202506-36820/
https://certification.canonical.com/hardware/202506-36823/
https://certification.canonical.com/hardware/202506-36826/
[Failed Rate]
4/4 (100%)
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.17.0-1012-oem 6.17.0-1012.12
ProcVersionSignature: Ubuntu 6.17.0-1012.12-oem 6.17.9
Uname: Linux 6.17.0-1012-oem x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1271 F.... wireplumber
/dev/snd/controlC0: ubuntu 1271 F.... wireplumber
/dev/snd/seq: ubuntu 1266 F.... pipewire
CRDA: N/A
CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg
CasperMD5CheckResult: fail
Date: Mon Mar 16 03:28:36 2026
DistributionChannelDescriptor:
# This is the distribution channel descriptor for Ubuntu 24.04 for Dell
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-noble-oem-24.04b-proposed-20250617-524
InstallationDate: Installed on 2026-03-16 (0 days ago)
InstallationMedia: Ubuntu OEM 24.04.2 LTS "Noble Numbat" - Release amd64 (20250615)
MachineType: Dell Inc. Dell 16 DC16255
ProcFB: 0 simpledrmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-1012-oem root=UUID=d1b47013-8d11-47bc-9f6a-8046300ab97d ro nomodeset quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.17.0-1012-oem N/A
linux-backports-modules-6.17.0-1012-oem N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.25
SourcePackage: linux-oem-6.17
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/18/2025
dmi.bios.release: 5.3
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.4.10
dmi.board.asset.tag: AFTPASS
dmi.board.vendor: Dell Inc.
dmi.chassis.asset.tag: AFTPASS
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.4.10
dmi.modalias: dmi:bvnDellInc.:bvr0.4.10:bd06/18/2025:br5.3:svnDellInc.:pnDell16DC16255:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr0.4.10:sku0D95:
dmi.product.family: Inspiron
dmi.product.name: Dell 16 DC16255
dmi.product.sku: 0D95
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144522/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2144522
Title:
Dell Machines cannot boot into OS with 6.17.0-1012-oem
Status in linux package in Ubuntu:
Invalid
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Invalid
Status in linux-oem-6.17 source package in Noble:
In Progress
Status in linux source package in Questing:
In Progress
Status in linux-oem-6.17 source package in Questing:
Invalid
Bug description:
[Impact]
Dell systems (CID: 202506-36819, 202506-36820, 202506-36823, 202506-36826) with
AMD GFX 11.0.4 (gfx11) graphics cannot boot into the OS after upgrading to
6.17.0-1012-oem. The machine becomes stuck during boot and cannot reach the
desktop. Booting with `nomodeset` works as a workaround, pointing to an amdgpu
driver initialization failure.
Failure rate: 4/4 (100%) on affected Dell systems.
[Fix]
Two patches fix this boot regression:
1. Raise the minimum MES firmware version for calling set_hw_resources_1 on
GC 11.0.4 from 0x50 to 0x52, ensuring firmware that cannot properly
initialize this call is not used.
upstream in mainline kernel v7.0:
1478a34470bf drm/amd: Set minimum version for set_hw_resource_1 on gfx11 to 0x52
2. Remove the MES LR compute workaround (enable_lr_compute_wa) from both
mes_v11_0.c and mes_v12_0.c, since the underlying issue was already fixed by
adjusting the VGPR size, and keeping the workaround causes instability with
newer GC microcode.
upstream in mainline kernel v7.0:
6b0d812971370 drm/amd: Disable MES LR compute W/A
[Test Plan]
Boot the affected machine with kernel 6.17.0-1012-oem (or later oem kernel).
Without the patches: System gets stuck during boot and cannot reach the OS
(amdgpu fails to initialize).
With the patches: System boots normally to the desktop without requiring
`nomodeset`.
To verify:
1. Boot without `nomodeset`
2. Check that the desktop loads successfully
3. Confirm no amdgpu-related errors blocking boot in dmesg:
$ sudo dmesg | grep -i "amdgpu\|mes\|drm"
[Where problems could occur]
These changes affect the amdgpu MES initialization path for gfx11 (mes_v11_0.c)
and gfx12 (mes_v12_0.c) hardware.
For patch 1: If the version threshold 0x52 is incorrect, machines with MES
firmware between 0x50 and 0x51 that previously worked could stop calling
set_hw_resources_1, potentially causing degraded GPU performance or missing
hardware resource configuration. This would manifest as graphical glitches,
GPU compute failures, or silent capability loss after MES initialization.
For patch 2: If the LR compute workaround was actually needed for some
gfx11/gfx12 product beyond gfx1151, removing it could cause GPU hangs or
compute workload failures on those variants. Symptoms would include GPU hangs,
DRM timeout errors, or compute job failures under load.
[Other Info]
Both patches are upstream in Linux 7.0 (merged via drm-next-2026-02-11).
=================================================================
[Summary]
Several Dell Machines failed to boot into OS on 6.17.0-1012-oem.
[Reproduce Steps]
1. Install the GM image (6.11).
2. Run the dist-upgrade to 6.17
3. sudo reboot
On 6.11, the machine can boot into OS after reboot. However, after
upgrading to 6.17, it becomes stuck during boot and cannot reach the
OS. However, if root is modified to nomodeset in 6.17, the machine can
boot into the OS successfully.
[Affected Machines]
https://certification.canonical.com/hardware/202506-36819/
https://certification.canonical.com/hardware/202506-36820/
https://certification.canonical.com/hardware/202506-36823/
https://certification.canonical.com/hardware/202506-36826/
[Failed Rate]
4/4 (100%)
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.17.0-1012-oem 6.17.0-1012.12
ProcVersionSignature: Ubuntu 6.17.0-1012.12-oem 6.17.9
Uname: Linux 6.17.0-1012-oem x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1271 F.... wireplumber
/dev/snd/controlC0: ubuntu 1271 F.... wireplumber
/dev/snd/seq: ubuntu 1266 F.... pipewire
CRDA: N/A
CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg
CasperMD5CheckResult: fail
Date: Mon Mar 16 03:28:36 2026
DistributionChannelDescriptor:
# This is the distribution channel descriptor for Ubuntu 24.04 for Dell
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-noble-oem-24.04b-proposed-20250617-524
InstallationDate: Installed on 2026-03-16 (0 days ago)
InstallationMedia: Ubuntu OEM 24.04.2 LTS "Noble Numbat" - Release amd64 (20250615)
MachineType: Dell Inc. Dell 16 DC16255
ProcFB: 0 simpledrmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-1012-oem root=UUID=d1b47013-8d11-47bc-9f6a-8046300ab97d ro nomodeset quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.17.0-1012-oem N/A
linux-backports-modules-6.17.0-1012-oem N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.25
SourcePackage: linux-oem-6.17
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/18/2025
dmi.bios.release: 5.3
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.4.10
dmi.board.asset.tag: AFTPASS
dmi.board.vendor: Dell Inc.
dmi.chassis.asset.tag: AFTPASS
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.4.10
dmi.modalias: dmi:bvnDellInc.:bvr0.4.10:bd06/18/2025:br5.3:svnDellInc.:pnDell16DC16255:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr0.4.10:sku0D95:
dmi.product.family: Inspiron
dmi.product.name: Dell 16 DC16255
dmi.product.sku: 0D95
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144522/+subscriptions
[Bug 2144526] Re: Git clone/fetch latest tag code not working
** Tags added: kernel-daily-bug
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2144526
Title:
Git clone/fetch latest tag code not working
Status in linux package in Ubuntu:
New
Bug description:
git clone https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/noble
Cloning of the code is not working.
Error message:
Failed to connect to git.launchpad.net port 443 after 42385 ms:
Couldn't connect to server.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144526/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2144526
Title:
Git clone/fetch latest tag code not working
Status in linux package in Ubuntu:
New
Bug description:
git clone https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/noble
Cloning of the code is not working.
Error message:
Failed to connect to git.launchpad.net port 443 after 42385 ms:
Couldn't connect to server.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144526/+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
** Tags added: kernel-daily-bug
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/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
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144530/+subscriptions
--
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
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144530/+subscriptions
[Bug 2144537] Re: i915 WARN_ON call trace during CB/WB on MTL/ARL platforms
** Tags added: kernel-daily-bug
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2144537
Title:
i915 WARN_ON call trace during CB/WB on MTL/ARL platforms
Status in HWE Next:
New
Status in linux package in Ubuntu:
New
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
New
Status in linux-oem-6.17 source package in Noble:
In Progress
Status in linux source package in Questing:
New
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
New
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[Impact]
On Dell systems (CID: 202602-38397) with Intel XeLPDP/Arrow Lake-S display
(8086:7d67), the i915 driver produces a kernel WARNING during cold boot and
warm boot when no monitor is connected. The BIOS can leave TypeC HPD live
status bits set on an XeLPDP TC port indicating a connected device, while
TCSS (TypeC Subsystem) power has not been enabled. During driver probe,
this causes drm_WARN_ON to fire in xelpdp_tc_phy_get_hw_state() even
though the driver correctly handles this state afterwards.
The warning triggers failures in automated cold-boot/warm-boot stress test
plans (cold-boot-loop-test, warm-boot-loop-test).
Error log:
i915 0000:00:02.0: [drm] drm_WARN_ON((tc->mode == TC_PORT_DP_ALT || tc->mode == TC_PORT_LEGACY) && !xelpdp_tc_phy_tcss_power_is_enabled(tc))
WARNING: CPU: 7 PID: 591 at drivers/gpu/drm/i915/display/intel_tc.c:1177 xelpdp_tc_phy_get_hw_state+0x145/0x150 [i915]
Call Trace:
intel_tc_port_init_mode+0x73/0x270 [i915]
intel_tc_port_init+0x1e0/0x2a0 [i915]
intel_ddi_init+0xa9a/0x1220 [i915]
intel_setup_outputs+0x1f4/0xc20 [i915]
intel_display_driver_probe_nogem+0x16f/0x270 [i915]
i915_driver_probe+0x251/0x670 [i915]
[Fix]
Convert the drm_WARN_ON in xelpdp_tc_phy_get_hw_state() to a drm_dbg_kms()
message. The stale HPD bits left by BIOS are a known handoff condition that
the driver already handles correctly via intel_tc_port_update_mode(); the
WARN_ON is a false positive that need not be a warning.
This is consistent with the approach taken for the analogous AUX power check
in commit 5830231e6547 ("drm/i915/icl+/tc: Convert AUX powered WARN to a
debug message"), which is already in the tree.
https://lore.kernel.org/lkml/20260316093001.689992-1-acelan.kao@canonical.com/T/#u
[Test Plan]
Boot the system without a monitor connected and check dmesg:
$ sudo dmesg | grep -i "warn_on.*xelpdp\|WARNING.*intel_tc"
Without the patch: WARNING at intel_tc.c:1177 xelpdp_tc_phy_get_hw_state
is present in dmesg on affected hardware.
With the patch: No WARNING or drm_WARN_ON in dmesg related to
xelpdp_tc_phy_get_hw_state.
To stress test, run multiple cold/warm boot cycles:
$ sudo reboot # repeat 10+ times, check dmesg each boot
[Where problems could occur]
It may affect Intel XeLPDP TC port state detection in the i915 driver on
MTL/ARL platforms.
The WARN_ON being converted was asserting that TCSS power must be enabled
when the port mode is DP-alt or Legacy. By downgrading it to a debug
message, a genuinely unexpected hardware state (not just a BIOS handoff
artifact) could go unnoticed and silently result in incorrect TC port
mode initialisation. This could manifest as a TC/USB4 port failing to
enumerate connected devices or DisplayPort-alt mode not working on
affected TC ports after boot.
The risk is limited to XeLPDP platforms (MTL, ARL) and only triggers
during the specific BIOS handoff scenario where HPD bits are stale.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2144537/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2144537
Title:
i915 WARN_ON call trace during CB/WB on MTL/ARL platforms
Status in HWE Next:
New
Status in linux package in Ubuntu:
New
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
New
Status in linux-oem-6.17 source package in Noble:
In Progress
Status in linux source package in Questing:
New
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
New
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[Impact]
On Dell systems (CID: 202602-38397) with Intel XeLPDP/Arrow Lake-S display
(8086:7d67), the i915 driver produces a kernel WARNING during cold boot and
warm boot when no monitor is connected. The BIOS can leave TypeC HPD live
status bits set on an XeLPDP TC port indicating a connected device, while
TCSS (TypeC Subsystem) power has not been enabled. During driver probe,
this causes drm_WARN_ON to fire in xelpdp_tc_phy_get_hw_state() even
though the driver correctly handles this state afterwards.
The warning triggers failures in automated cold-boot/warm-boot stress test
plans (cold-boot-loop-test, warm-boot-loop-test).
Error log:
i915 0000:00:02.0: [drm] drm_WARN_ON((tc->mode == TC_PORT_DP_ALT || tc->mode == TC_PORT_LEGACY) && !xelpdp_tc_phy_tcss_power_is_enabled(tc))
WARNING: CPU: 7 PID: 591 at drivers/gpu/drm/i915/display/intel_tc.c:1177 xelpdp_tc_phy_get_hw_state+0x145/0x150 [i915]
Call Trace:
intel_tc_port_init_mode+0x73/0x270 [i915]
intel_tc_port_init+0x1e0/0x2a0 [i915]
intel_ddi_init+0xa9a/0x1220 [i915]
intel_setup_outputs+0x1f4/0xc20 [i915]
intel_display_driver_probe_nogem+0x16f/0x270 [i915]
i915_driver_probe+0x251/0x670 [i915]
[Fix]
Convert the drm_WARN_ON in xelpdp_tc_phy_get_hw_state() to a drm_dbg_kms()
message. The stale HPD bits left by BIOS are a known handoff condition that
the driver already handles correctly via intel_tc_port_update_mode(); the
WARN_ON is a false positive that need not be a warning.
This is consistent with the approach taken for the analogous AUX power check
in commit 5830231e6547 ("drm/i915/icl+/tc: Convert AUX powered WARN to a
debug message"), which is already in the tree.
https://lore.kernel.org/lkml/20260316093001.689992-1-acelan.kao@canonical.com/T/#u
[Test Plan]
Boot the system without a monitor connected and check dmesg:
$ sudo dmesg | grep -i "warn_on.*xelpdp\|WARNING.*intel_tc"
Without the patch: WARNING at intel_tc.c:1177 xelpdp_tc_phy_get_hw_state
is present in dmesg on affected hardware.
With the patch: No WARNING or drm_WARN_ON in dmesg related to
xelpdp_tc_phy_get_hw_state.
To stress test, run multiple cold/warm boot cycles:
$ sudo reboot # repeat 10+ times, check dmesg each boot
[Where problems could occur]
It may affect Intel XeLPDP TC port state detection in the i915 driver on
MTL/ARL platforms.
The WARN_ON being converted was asserting that TCSS power must be enabled
when the port mode is DP-alt or Legacy. By downgrading it to a debug
message, a genuinely unexpected hardware state (not just a BIOS handoff
artifact) could go unnoticed and silently result in incorrect TC port
mode initialisation. This could manifest as a TC/USB4 port failing to
enumerate connected devices or DisplayPort-alt mode not working on
affected TC ports after boot.
The risk is limited to XeLPDP platforms (MTL, ARL) and only triggers
during the specific BIOS handoff scenario where HPD bits are stale.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2144537/+subscriptions
[Bug 2144577] Re: BUG: kernel NULL pointer dereference in amdgpu
** Tags added: kernel-daily-bug
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2144577
Title:
BUG: kernel NULL pointer dereference in amdgpu
Status in linux package in Ubuntu:
New
Bug description:
Ubuntu 25.10 with kernel 6.17.0-19-generic doesn't boot on my PC. I
freezes on the booting screen, and the kernel logs show a bug:
kernel: Linux version 6.17.0-19-generic (buildd@lcy02-amd64-084) (x86_64-linux-gnu-gcc (Ubuntu 15.2.0-4ubuntu4) 15.2.0, GNU ld (GNU Binutils for Ubuntu) 2.45) #19-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 6 14:02:58 UTC 2026 (Ubuntu 6.17.0-19.19-generic 6.17.13)
kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.17.0-19-generic root=UUID=354e3c09-bfde-4e47-850f-fe872a882ae5 ro quiet splash radeon.si_support=0 amdgpu.si_support=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
# ...
kernel: [drm] Initialized amdgpu 3.64.0 for 0000:01:00.0 on minor 1
kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000
kernel: #PF: supervisor instruction fetch in kernel mode
kernel: #PF: error_code(0x0010) - not-present page
kernel: PGD 0 P4D 0
kernel: Oops: Oops: 0010 [#1] SMP PTI
kernel: CPU: 3 UID: 0 PID: 109 Comm: kworker/3:1 Not tainted 6.17.0-19-generic #19-Ubuntu PREEMPT(voluntary)
kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z77 Pro3, BIOS P1.10 04/10/2012
kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
kernel: RIP: 0010:0x0
kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
kernel: RSP: 0018:ffffce560061fdb0 EFLAGS: 00010246
kernel: RAX: 0000000000000000 RBX: 0000000000008000 RCX: 0000000000000001
kernel: RDX: 0000000000000002 RSI: 0000000000008000 RDI: ffff8a4a6d180000
kernel: RBP: ffffce560061fe08 R08: 0000000000000000 R09: 0000000000000000
kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
kernel: R13: 0000000000000000 R14: ffff8a4a6d180000 R15: 0000000000000000
kernel: FS: 0000000000000000(0000) GS:ffff8a4da87ff000(0000) knlGS:0000000000000000
kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: CR2: ffffffffffffffd6 CR3: 00000003de040002 CR4: 00000000001726f0
kernel: Call Trace:
kernel: <TASK>
kernel: amdgpu_gmc_flush_gpu_tlb_pasid+0xfd/0x480 [amdgpu]
kernel: amdgpu_tlb_fence_work+0x77/0x110 [amdgpu]
kernel: process_one_work+0x18e/0x370
kernel: worker_thread+0x317/0x450
kernel: ? _raw_spin_lock_irqsave+0xe/0x20
kernel: ? __pfx_worker_thread+0x10/0x10
kernel: kthread+0x10b/0x220
kernel: ? __pfx_kthread+0x10/0x10
kernel: ret_from_fork+0x134/0x150
kernel: ? __pfx_kthread+0x10/0x10
kernel: ret_from_fork_asm+0x1a/0x30
kernel: </TASK>
kernel: Modules linked in: rfcomm cmac algif_hash algif_skcipher af_alg bnep ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog nft_limit xt_limit xt_addrtype xt_mac xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat binfmt_misc nf_tables amdgpu(+) usblp intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel amdxcp at24 mei_hdcp mei_pxp kvm snd_hda_codec_atihdmi drm_panel_backlight_quirks gpu_sched irqbypass snd_hda_codec_hdmi drm_buddy snd_hda_codec_alc662 rapl btusb snd_hda_codec_realtek_lib intel_cstate snd_hda_codec_generic radeon btrtl snd_hda_intel btintel i2c_i801 btbcm snd_hda_codec btmtk i2c_smbus drm_ttm_helper i2c_mux ttm bluetooth snd_seq_midi snd_hda_core snd_seq_midi_event drm_exec snd_intel_dspcfg snd_rawmidi drm_suballoc_helper snd_intel_sdw_acpi drm_display_helper lpc_ich snd_hwdep snd_seq snd_pcm snd_seq_device cec snd_timer rc_core snd i2c_algo_bit soundcore mei_me mei intel_smartconnect joydev
kernel: input_leds mac_hid sch_fq_codel msr parport_pc ppdev lp parport efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 dm_crypt wacom uas usb_storage hid_generic usbhid hid r8169 polyval_clmulni ghash_clmulni_intel psmouse ahci realtek serio_raw libahci video wmi aesni_intel
kernel: CR2: 0000000000000000
kernel: ---[ end trace 0000000000000000 ]---
kernel: RIP: 0010:0x0
kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
kernel: RSP: 0018:ffffce560061fdb0 EFLAGS: 00010246
kernel: RAX: 0000000000000000 RBX: 0000000000008000 RCX: 0000000000000001
kernel: RDX: 0000000000000002 RSI: 0000000000008000 RDI: ffff8a4a6d180000
kernel: RBP: ffffce560061fe08 R08: 0000000000000000 R09: 0000000000000000
kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
kernel: R13: 0000000000000000 R14: ffff8a4a6d180000 R15: 0000000000000000
kernel: FS: 0000000000000000(0000) GS:ffff8a4da87ff000(0000) knlGS:0000000000000000
kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: CR2: ffffffffffffffd6 CR3: 00000003de040002 CR4: 00000000001726f0
kernel: note: kworker/3:1[109] exited with irqs disabled
kernel: loop50: detected capacity change from 0 to 8
kernel: fbcon: amdgpudrmfb (fb0) is primary device
kernel: fbcon: Deferring console take-over
kernel: amdgpu 0000:01:00.0: [drm] fb0: amdgpudrmfb frame buffer device
kernel: NET: Registered PF_QIPCRTR protocol family
kernel: sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 >
kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000
kernel: #PF: supervisor instruction fetch in kernel mode
kernel: #PF: error_code(0x0010) - not-present page
kernel: PGD 0 P4D 0
kernel: Oops: Oops: 0010 [#2] SMP PTI
kernel: CPU: 1 UID: 0 PID: 91 Comm: kworker/1:1 Tainted: G D 6.17.0-19-generic #19-Ubuntu PREEMPT(voluntary)
kernel: Tainted: [D]=DIE
kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z77 Pro3, BIOS P1.10 04/10/2012
kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
kernel: RIP: 0010:0x0
kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
kernel: RSP: 0000:ffffce5600477db0 EFLAGS: 00010246
kernel: RAX: 0000000000000000 RBX: 0000000000008001 RCX: 0000000000000001
kernel: RDX: 0000000000000002 RSI: 0000000000008001 RDI: ffff8a4a6d180000
kernel: RBP: ffffce5600477e08 R08: 0000000000000000 R09: 0000000000000000
kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
kernel: R13: 0000000000000000 R14: ffff8a4a6d180000 R15: 0000000000000000
kernel: FS: 0000000000000000(0000) GS:ffff8a4da86ff000(0000) knlGS:0000000000000000
kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: CR2: ffffffffffffffd6 CR3: 0000000101242006 CR4: 00000000001726f0
kernel: Call Trace:
kernel: <TASK>
kernel: amdgpu_gmc_flush_gpu_tlb_pasid+0xfd/0x480 [amdgpu]
kernel: amdgpu_tlb_fence_work+0x77/0x110 [amdgpu]
kernel: process_one_work+0x18e/0x370
kernel: worker_thread+0x317/0x450
kernel: ? _raw_spin_lock_irqsave+0xe/0x20
kernel: ? __pfx_worker_thread+0x10/0x10
kernel: kthread+0x10b/0x220
kernel: ? __pfx_kthread+0x10/0x10
kernel: ret_from_fork+0x134/0x150
kernel: ? __pfx_kthread+0x10/0x10
kernel: ret_from_fork_asm+0x1a/0x30
kernel: </TASK>
kernel: Modules linked in: qrtr rfcomm cmac algif_hash algif_skcipher af_alg bnep ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog nft_limit xt_limit xt_addrtype xt_mac xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat binfmt_misc nf_tables amdgpu usblp intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel amdxcp at24 mei_hdcp mei_pxp kvm snd_hda_codec_atihdmi drm_panel_backlight_quirks gpu_sched irqbypass snd_hda_codec_hdmi drm_buddy snd_hda_codec_alc662 rapl btusb snd_hda_codec_realtek_lib intel_cstate snd_hda_codec_generic radeon btrtl snd_hda_intel btintel i2c_i801 btbcm snd_hda_codec btmtk i2c_smbus drm_ttm_helper i2c_mux ttm bluetooth snd_seq_midi snd_hda_core snd_seq_midi_event drm_exec snd_intel_dspcfg snd_rawmidi drm_suballoc_helper snd_intel_sdw_acpi drm_display_helper lpc_ich snd_hwdep snd_seq snd_pcm snd_seq_device cec snd_timer rc_core snd i2c_algo_bit soundcore mei_me mei intel_smartconnect joydev
kernel: input_leds mac_hid sch_fq_codel msr parport_pc ppdev lp parport efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 dm_crypt wacom uas usb_storage hid_generic usbhid hid r8169 polyval_clmulni ghash_clmulni_intel psmouse ahci realtek serio_raw libahci video wmi aesni_intel
kernel: CR2: 0000000000000000
kernel: ---[ end trace 0000000000000000 ]---
kernel: RIP: 0010:0x0
kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
kernel: RSP: 0018:ffffce560061fdb0 EFLAGS: 00010246
kernel: RAX: 0000000000000000 RBX: 0000000000008000 RCX: 0000000000000001
kernel: RDX: 0000000000000002 RSI: 0000000000008000 RDI: ffff8a4a6d180000
kernel: RBP: ffffce560061fe08 R08: 0000000000000000 R09: 0000000000000000
kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
kernel: R13: 0000000000000000 R14: ffff8a4a6d180000 R15: 0000000000000000
kernel: FS: 0000000000000000(0000) GS:ffff8a4da86ff000(0000) knlGS:0000000000000000
kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: CR2: ffffffffffffffd6 CR3: 0000000101242006 CR4: 00000000001726f0
kernel: note: kworker/1:1[91] exited with irqs disabled
The previous kernel 6.17.0-14-generic boots without any issues.
I'll try to attach the required information using `apport-collect -p linux BUG#`, but it'll be collected after successfully booting with 6.17.0-14, whereas the bug occurs with 6.17.0-19.
---
ProblemType: Bug
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: mateusz 3017 F.... wireplumber
/dev/snd/controlC1: mateusz 3017 F.... wireplumber
/dev/snd/seq: mateusz 2999 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 25.10
InstallationDate: Installed on 2020-10-14 (1979 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: linux (not installed)
ProcEnviron:
LANG=pl_PL.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-14-generic root=UUID=354e3c09-bfde-4e47-850f-fe872a882ae5 ro quiet splash radeon.si_support=0 amdgpu.si_support=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
ProcVersionSignature: Ubuntu 6.17.0-14.14-generic 6.17.9
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
RfKill:
0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
Tags: questing
Uname: Linux 6.17.0-14-generic x86_64
UpgradeStatus: Upgraded to questing on 2026-01-10 (65 days ago)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 04/10/2012
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: Z77 Pro3
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd04/10/2012:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Pro3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144577/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2144577
Title:
BUG: kernel NULL pointer dereference in amdgpu
Status in linux package in Ubuntu:
New
Bug description:
Ubuntu 25.10 with kernel 6.17.0-19-generic doesn't boot on my PC. I
freezes on the booting screen, and the kernel logs show a bug:
kernel: Linux version 6.17.0-19-generic (buildd@lcy02-amd64-084) (x86_64-linux-gnu-gcc (Ubuntu 15.2.0-4ubuntu4) 15.2.0, GNU ld (GNU Binutils for Ubuntu) 2.45) #19-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 6 14:02:58 UTC 2026 (Ubuntu 6.17.0-19.19-generic 6.17.13)
kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.17.0-19-generic root=UUID=354e3c09-bfde-4e47-850f-fe872a882ae5 ro quiet splash radeon.si_support=0 amdgpu.si_support=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
# ...
kernel: [drm] Initialized amdgpu 3.64.0 for 0000:01:00.0 on minor 1
kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000
kernel: #PF: supervisor instruction fetch in kernel mode
kernel: #PF: error_code(0x0010) - not-present page
kernel: PGD 0 P4D 0
kernel: Oops: Oops: 0010 [#1] SMP PTI
kernel: CPU: 3 UID: 0 PID: 109 Comm: kworker/3:1 Not tainted 6.17.0-19-generic #19-Ubuntu PREEMPT(voluntary)
kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z77 Pro3, BIOS P1.10 04/10/2012
kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
kernel: RIP: 0010:0x0
kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
kernel: RSP: 0018:ffffce560061fdb0 EFLAGS: 00010246
kernel: RAX: 0000000000000000 RBX: 0000000000008000 RCX: 0000000000000001
kernel: RDX: 0000000000000002 RSI: 0000000000008000 RDI: ffff8a4a6d180000
kernel: RBP: ffffce560061fe08 R08: 0000000000000000 R09: 0000000000000000
kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
kernel: R13: 0000000000000000 R14: ffff8a4a6d180000 R15: 0000000000000000
kernel: FS: 0000000000000000(0000) GS:ffff8a4da87ff000(0000) knlGS:0000000000000000
kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: CR2: ffffffffffffffd6 CR3: 00000003de040002 CR4: 00000000001726f0
kernel: Call Trace:
kernel: <TASK>
kernel: amdgpu_gmc_flush_gpu_tlb_pasid+0xfd/0x480 [amdgpu]
kernel: amdgpu_tlb_fence_work+0x77/0x110 [amdgpu]
kernel: process_one_work+0x18e/0x370
kernel: worker_thread+0x317/0x450
kernel: ? _raw_spin_lock_irqsave+0xe/0x20
kernel: ? __pfx_worker_thread+0x10/0x10
kernel: kthread+0x10b/0x220
kernel: ? __pfx_kthread+0x10/0x10
kernel: ret_from_fork+0x134/0x150
kernel: ? __pfx_kthread+0x10/0x10
kernel: ret_from_fork_asm+0x1a/0x30
kernel: </TASK>
kernel: Modules linked in: rfcomm cmac algif_hash algif_skcipher af_alg bnep ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog nft_limit xt_limit xt_addrtype xt_mac xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat binfmt_misc nf_tables amdgpu(+) usblp intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel amdxcp at24 mei_hdcp mei_pxp kvm snd_hda_codec_atihdmi drm_panel_backlight_quirks gpu_sched irqbypass snd_hda_codec_hdmi drm_buddy snd_hda_codec_alc662 rapl btusb snd_hda_codec_realtek_lib intel_cstate snd_hda_codec_generic radeon btrtl snd_hda_intel btintel i2c_i801 btbcm snd_hda_codec btmtk i2c_smbus drm_ttm_helper i2c_mux ttm bluetooth snd_seq_midi snd_hda_core snd_seq_midi_event drm_exec snd_intel_dspcfg snd_rawmidi drm_suballoc_helper snd_intel_sdw_acpi drm_display_helper lpc_ich snd_hwdep snd_seq snd_pcm snd_seq_device cec snd_timer rc_core snd i2c_algo_bit soundcore mei_me mei intel_smartconnect joydev
kernel: input_leds mac_hid sch_fq_codel msr parport_pc ppdev lp parport efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 dm_crypt wacom uas usb_storage hid_generic usbhid hid r8169 polyval_clmulni ghash_clmulni_intel psmouse ahci realtek serio_raw libahci video wmi aesni_intel
kernel: CR2: 0000000000000000
kernel: ---[ end trace 0000000000000000 ]---
kernel: RIP: 0010:0x0
kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
kernel: RSP: 0018:ffffce560061fdb0 EFLAGS: 00010246
kernel: RAX: 0000000000000000 RBX: 0000000000008000 RCX: 0000000000000001
kernel: RDX: 0000000000000002 RSI: 0000000000008000 RDI: ffff8a4a6d180000
kernel: RBP: ffffce560061fe08 R08: 0000000000000000 R09: 0000000000000000
kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
kernel: R13: 0000000000000000 R14: ffff8a4a6d180000 R15: 0000000000000000
kernel: FS: 0000000000000000(0000) GS:ffff8a4da87ff000(0000) knlGS:0000000000000000
kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: CR2: ffffffffffffffd6 CR3: 00000003de040002 CR4: 00000000001726f0
kernel: note: kworker/3:1[109] exited with irqs disabled
kernel: loop50: detected capacity change from 0 to 8
kernel: fbcon: amdgpudrmfb (fb0) is primary device
kernel: fbcon: Deferring console take-over
kernel: amdgpu 0000:01:00.0: [drm] fb0: amdgpudrmfb frame buffer device
kernel: NET: Registered PF_QIPCRTR protocol family
kernel: sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 sdb7 >
kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000
kernel: #PF: supervisor instruction fetch in kernel mode
kernel: #PF: error_code(0x0010) - not-present page
kernel: PGD 0 P4D 0
kernel: Oops: Oops: 0010 [#2] SMP PTI
kernel: CPU: 1 UID: 0 PID: 91 Comm: kworker/1:1 Tainted: G D 6.17.0-19-generic #19-Ubuntu PREEMPT(voluntary)
kernel: Tainted: [D]=DIE
kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./Z77 Pro3, BIOS P1.10 04/10/2012
kernel: Workqueue: events amdgpu_tlb_fence_work [amdgpu]
kernel: RIP: 0010:0x0
kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
kernel: RSP: 0000:ffffce5600477db0 EFLAGS: 00010246
kernel: RAX: 0000000000000000 RBX: 0000000000008001 RCX: 0000000000000001
kernel: RDX: 0000000000000002 RSI: 0000000000008001 RDI: ffff8a4a6d180000
kernel: RBP: ffffce5600477e08 R08: 0000000000000000 R09: 0000000000000000
kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
kernel: R13: 0000000000000000 R14: ffff8a4a6d180000 R15: 0000000000000000
kernel: FS: 0000000000000000(0000) GS:ffff8a4da86ff000(0000) knlGS:0000000000000000
kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: CR2: ffffffffffffffd6 CR3: 0000000101242006 CR4: 00000000001726f0
kernel: Call Trace:
kernel: <TASK>
kernel: amdgpu_gmc_flush_gpu_tlb_pasid+0xfd/0x480 [amdgpu]
kernel: amdgpu_tlb_fence_work+0x77/0x110 [amdgpu]
kernel: process_one_work+0x18e/0x370
kernel: worker_thread+0x317/0x450
kernel: ? _raw_spin_lock_irqsave+0xe/0x20
kernel: ? __pfx_worker_thread+0x10/0x10
kernel: kthread+0x10b/0x220
kernel: ? __pfx_kthread+0x10/0x10
kernel: ret_from_fork+0x134/0x150
kernel: ? __pfx_kthread+0x10/0x10
kernel: ret_from_fork_asm+0x1a/0x30
kernel: </TASK>
kernel: Modules linked in: qrtr rfcomm cmac algif_hash algif_skcipher af_alg bnep ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog nft_limit xt_limit xt_addrtype xt_mac xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat binfmt_misc nf_tables amdgpu usblp intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel amdxcp at24 mei_hdcp mei_pxp kvm snd_hda_codec_atihdmi drm_panel_backlight_quirks gpu_sched irqbypass snd_hda_codec_hdmi drm_buddy snd_hda_codec_alc662 rapl btusb snd_hda_codec_realtek_lib intel_cstate snd_hda_codec_generic radeon btrtl snd_hda_intel btintel i2c_i801 btbcm snd_hda_codec btmtk i2c_smbus drm_ttm_helper i2c_mux ttm bluetooth snd_seq_midi snd_hda_core snd_seq_midi_event drm_exec snd_intel_dspcfg snd_rawmidi drm_suballoc_helper snd_intel_sdw_acpi drm_display_helper lpc_ich snd_hwdep snd_seq snd_pcm snd_seq_device cec snd_timer rc_core snd i2c_algo_bit soundcore mei_me mei intel_smartconnect joydev
kernel: input_leds mac_hid sch_fq_codel msr parport_pc ppdev lp parport efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 dm_crypt wacom uas usb_storage hid_generic usbhid hid r8169 polyval_clmulni ghash_clmulni_intel psmouse ahci realtek serio_raw libahci video wmi aesni_intel
kernel: CR2: 0000000000000000
kernel: ---[ end trace 0000000000000000 ]---
kernel: RIP: 0010:0x0
kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
kernel: RSP: 0018:ffffce560061fdb0 EFLAGS: 00010246
kernel: RAX: 0000000000000000 RBX: 0000000000008000 RCX: 0000000000000001
kernel: RDX: 0000000000000002 RSI: 0000000000008000 RDI: ffff8a4a6d180000
kernel: RBP: ffffce560061fe08 R08: 0000000000000000 R09: 0000000000000000
kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
kernel: R13: 0000000000000000 R14: ffff8a4a6d180000 R15: 0000000000000000
kernel: FS: 0000000000000000(0000) GS:ffff8a4da86ff000(0000) knlGS:0000000000000000
kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: CR2: ffffffffffffffd6 CR3: 0000000101242006 CR4: 00000000001726f0
kernel: note: kworker/1:1[91] exited with irqs disabled
The previous kernel 6.17.0-14-generic boots without any issues.
I'll try to attach the required information using `apport-collect -p linux BUG#`, but it'll be collected after successfully booting with 6.17.0-14, whereas the bug occurs with 6.17.0-19.
---
ProblemType: Bug
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: mateusz 3017 F.... wireplumber
/dev/snd/controlC1: mateusz 3017 F.... wireplumber
/dev/snd/seq: mateusz 2999 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 25.10
InstallationDate: Installed on 2020-10-14 (1979 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
Package: linux (not installed)
ProcEnviron:
LANG=pl_PL.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-14-generic root=UUID=354e3c09-bfde-4e47-850f-fe872a882ae5 ro quiet splash radeon.si_support=0 amdgpu.si_support=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
ProcVersionSignature: Ubuntu 6.17.0-14.14-generic 6.17.9
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
RfKill:
0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
Tags: questing
Uname: Linux 6.17.0-14-generic x86_64
UpgradeStatus: Upgraded to questing on 2026-01-10 (65 days ago)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 04/10/2012
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: Z77 Pro3
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd04/10/2012:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Pro3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144577/+subscriptions
Подписаться на:
Комментарии (Atom)