All autopkgtests for the newly accepted linux-meta-gkeop (6.8.0-1033.36) for noble have finished running.
The following regressions have been reported in tests triggered by the package:
linux-gkeop/6.8.0-1033.36 (amd64)
systemd/255.4-1ubuntu8.12 (amd64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#linux-meta-gkeop
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
пятница
[Bug 2138754] Re: [ath12k wcn7850] 5 GHz Wi-Fi broken in kernel 6.17+ due to broken frequency range filtering
Hi,
I have updated board-2.bin from
https://launchpad.net/ubuntu/+source/linux-
firmware/20250901.git993ff19b-0ubuntu1.8
And I can confirm that 5ghz is working now.
Here is the md5 for reference.
saikiran@saikiran-Yoga-Slim-7-14Q8X9:/lib/firmware/ath12k/WCN7850/hw2.0$ md5sum board-2.bin
4b0cb2416db49e39c8c7e3302067d22e board-2.bin
saikiran@saikiran-Yoga-Slim-7-14Q8X9:/lib/firmware/ath12k/WCN7850/hw2.0$
Thanks!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2138754
Title:
[ath12k wcn7850] 5 GHz Wi-Fi broken in kernel 6.17+ due to broken
frequency range filtering
Status in linux package in Ubuntu:
Invalid
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux source package in Questing:
Invalid
Status in linux-firmware source package in Questing:
Fix Committed
Bug description:
[ Impact ]
5 GHz Wi-Fi networks are completely undetectable on Qualcomm WCN7850
(ath12k) starting with kernel 6.17, breaking wireless connectivity for
Snapdragon X Elite laptops.
Affected Hardware:
- Device: Lenovo Yoga Slim 7x (Snapdragon X Elite)
- Wi-Fi chipset: Qualcomm WCN7850 (ath12k_pci, hw2.0)
- Firmware: WLAN.HMT.1.1.c5-00302
Kernel Versions:
- Working: 6.16.0-21-qcom-x1e (5 GHz detected and functional)
- Broken: 6.17.x, 6.18.0-9-qcom-x1e (no 5 GHz BSS detected)
- Tested fix on: 6.19-rc5 (fully functional with patches)
Ubuntu Version:
Ubuntu 25.10
Symptoms:
- No 5 GHz networks appear in available network list
- `iw dev <interface> scan` shows only 2.4 GHz channels (1-13)
- 2.4 GHz networks work normally
- Regulatory domain correctly set (IN)
- No firmware loading errors
- Issue persists across multiple access points (ISP router on channel 36, Samsung hotspot)
[ Fix ]
Update ath12k/WCN7850/hw2.0/board-2.bin firmware.
[ Test Case ]
- 5 GHz Wi-Fi fully functional on current Questing kernel
- Both 2.4 GHz and 5 GHz networks detected and connectable
- Multiple access points tested successfully
- No firmware errors in dmesg
[ Where Problems Could Occur ]
Opaque firmware that - when loaded - can cause the usual kernel
problems (hang, freeze, stall, crash, ...)
[ Additional Information ]
Root Cause:
Broken frequency range filtering logic introduced between kernel 6.16 and 6.17. The regression involves changes to ath12k firmware statistics handling and regulatory domain synchronization that cause firmware protocol errors (-71, EPROTO) during 5 GHz scan preparation.
Investigation Details:
Initial suspicion was ASPM-related (commit e9cf6413e6a80), but symbol analysis confirmed this commit was not present in affected kernels. Subsequent analysis identified firmware statistics handling changes (commits bd6ec81 and 2977567) that altered state management and triggered the regression.
Fix:
A series of patches has been developed and tested on kernel 6.19-rc5:
Primary fix (critical):
- Patch 06: Remove broken frequency range filtering logic
Complete patch series attached:
- 9eb6d6bb9eb01e9767b8ad70bf503c1631d64c71 (Remove broken frequency range filtering) -- Primary fix
- 5946e4c0763755535f7f9f89761828b68a8019d1 (Improvements & cleanup)
- 26a6a6263f6c8919ade47f18814335e52384d474 (Improvements & cleanup)
- dae0671ab05a3a30cbba5e8b1f41e45a80c3900f (Improvements & cleanup)
- 9126482be6353f03a2844f60be1a569bc14a6738 (Improvements & cleanup)
Testing Results:
- 5 GHz Wi-Fi fully functional on kernel 6.19-rc5 with patch series applied
- Both 2.4 GHz and 5 GHz networks detected and connectable
- Multiple access points tested successfully
- No firmware errors in dmesg
Complete Technical Analysis:
Full investigation details, logs, and patch series available at:
https://bugs.launchpad.net/ubuntu-concept/+bug/2138308
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2138754/+subscriptions
I have updated board-2.bin from
https://launchpad.net/ubuntu/+source/linux-
firmware/20250901.git993ff19b-0ubuntu1.8
And I can confirm that 5ghz is working now.
Here is the md5 for reference.
saikiran@saikiran-Yoga-Slim-7-14Q8X9:/lib/firmware/ath12k/WCN7850/hw2.0$ md5sum board-2.bin
4b0cb2416db49e39c8c7e3302067d22e board-2.bin
saikiran@saikiran-Yoga-Slim-7-14Q8X9:/lib/firmware/ath12k/WCN7850/hw2.0$
Thanks!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2138754
Title:
[ath12k wcn7850] 5 GHz Wi-Fi broken in kernel 6.17+ due to broken
frequency range filtering
Status in linux package in Ubuntu:
Invalid
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux source package in Questing:
Invalid
Status in linux-firmware source package in Questing:
Fix Committed
Bug description:
[ Impact ]
5 GHz Wi-Fi networks are completely undetectable on Qualcomm WCN7850
(ath12k) starting with kernel 6.17, breaking wireless connectivity for
Snapdragon X Elite laptops.
Affected Hardware:
- Device: Lenovo Yoga Slim 7x (Snapdragon X Elite)
- Wi-Fi chipset: Qualcomm WCN7850 (ath12k_pci, hw2.0)
- Firmware: WLAN.HMT.1.1.c5-00302
Kernel Versions:
- Working: 6.16.0-21-qcom-x1e (5 GHz detected and functional)
- Broken: 6.17.x, 6.18.0-9-qcom-x1e (no 5 GHz BSS detected)
- Tested fix on: 6.19-rc5 (fully functional with patches)
Ubuntu Version:
Ubuntu 25.10
Symptoms:
- No 5 GHz networks appear in available network list
- `iw dev <interface> scan` shows only 2.4 GHz channels (1-13)
- 2.4 GHz networks work normally
- Regulatory domain correctly set (IN)
- No firmware loading errors
- Issue persists across multiple access points (ISP router on channel 36, Samsung hotspot)
[ Fix ]
Update ath12k/WCN7850/hw2.0/board-2.bin firmware.
[ Test Case ]
- 5 GHz Wi-Fi fully functional on current Questing kernel
- Both 2.4 GHz and 5 GHz networks detected and connectable
- Multiple access points tested successfully
- No firmware errors in dmesg
[ Where Problems Could Occur ]
Opaque firmware that - when loaded - can cause the usual kernel
problems (hang, freeze, stall, crash, ...)
[ Additional Information ]
Root Cause:
Broken frequency range filtering logic introduced between kernel 6.16 and 6.17. The regression involves changes to ath12k firmware statistics handling and regulatory domain synchronization that cause firmware protocol errors (-71, EPROTO) during 5 GHz scan preparation.
Investigation Details:
Initial suspicion was ASPM-related (commit e9cf6413e6a80), but symbol analysis confirmed this commit was not present in affected kernels. Subsequent analysis identified firmware statistics handling changes (commits bd6ec81 and 2977567) that altered state management and triggered the regression.
Fix:
A series of patches has been developed and tested on kernel 6.19-rc5:
Primary fix (critical):
- Patch 06: Remove broken frequency range filtering logic
Complete patch series attached:
- 9eb6d6bb9eb01e9767b8ad70bf503c1631d64c71 (Remove broken frequency range filtering) -- Primary fix
- 5946e4c0763755535f7f9f89761828b68a8019d1 (Improvements & cleanup)
- 26a6a6263f6c8919ade47f18814335e52384d474 (Improvements & cleanup)
- dae0671ab05a3a30cbba5e8b1f41e45a80c3900f (Improvements & cleanup)
- 9126482be6353f03a2844f60be1a569bc14a6738 (Improvements & cleanup)
Testing Results:
- 5 GHz Wi-Fi fully functional on kernel 6.19-rc5 with patch series applied
- Both 2.4 GHz and 5 GHz networks detected and connectable
- Multiple access points tested successfully
- No firmware errors in dmesg
Complete Technical Analysis:
Full investigation details, logs, and patch series available at:
https://bugs.launchpad.net/ubuntu-concept/+bug/2138308
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2138754/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-meta-gke/6.8.0-1046.51)
All autopkgtests for the newly accepted linux-meta-gke (6.8.0-1046.51) for noble have finished running.
The following regressions have been reported in tests triggered by the package:
linux-gke/6.8.0-1046.51 (amd64)
systemd/255.4-1ubuntu8.12 (amd64, arm64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#linux-meta-gke
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
The following regressions have been reported in tests triggered by the package:
linux-gke/6.8.0-1046.51 (amd64)
systemd/255.4-1ubuntu8.12 (amd64, arm64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#linux-meta-gke
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-meta/6.8.0-104.104)
All autopkgtests for the newly accepted linux-meta (6.8.0-104.104) for noble have finished running.
The following regressions have been reported in tests triggered by the package:
diffoscope/unknown (ppc64el)
dpdk-kmods/unknown (ppc64el)
initramfs-tools/0.142ubuntu25.8 (arm64)
lxc/unknown (ppc64el)
network-manager/1.46.0-1ubuntu2.5 (ppc64el)
systemd/255.4-1ubuntu8.12 (arm64)
ubuntu-drivers-common/unknown (ppc64el)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#linux-meta
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
The following regressions have been reported in tests triggered by the package:
diffoscope/unknown (ppc64el)
dpdk-kmods/unknown (ppc64el)
initramfs-tools/0.142ubuntu25.8 (arm64)
lxc/unknown (ppc64el)
network-manager/1.46.0-1ubuntu2.5 (ppc64el)
systemd/255.4-1ubuntu8.12 (arm64)
ubuntu-drivers-common/unknown (ppc64el)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#linux-meta
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-meta-hwe-6.8/6.8.0-104.104~22.04.1)
All autopkgtests for the newly accepted linux-meta-hwe-6.8 (6.8.0-104.104~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
dpdk-kmods/unknown (ppc64el)
glibc/2.35-0ubuntu3.13 (arm64)
glibc/unknown (ppc64el)
systemd/249.11-0ubuntu3.17 (amd64, arm64)
systemd/unknown (ppc64el)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-hwe-6.8
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
The following regressions have been reported in tests triggered by the package:
dpdk-kmods/unknown (ppc64el)
glibc/2.35-0ubuntu3.13 (arm64)
glibc/unknown (ppc64el)
systemd/249.11-0ubuntu3.17 (amd64, arm64)
systemd/unknown (ppc64el)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-hwe-6.8
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
[Bug 2140602] Re: Bionic generic kernel is missing current wireless-regdb maintainer (Chen-Yu Tsai) key
It doesn't seem like a good idea for Ubuntu to rely on upstream
signatures for updates, for exactly this kind of problem. AIUI, Debian
replaces the key in its kernels and signs the regulatory db themselves.
Can Ubuntu do this? What would the migration path look like?
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2140602
Title:
Bionic generic kernel is missing current wireless-regdb maintainer
(Chen-Yu Tsai) key
Status in linux package in Ubuntu:
New
Status in wireless-regdb package in Ubuntu:
New
Status in linux source package in Bionic:
New
Status in wireless-regdb source package in Bionic:
New
Bug description:
[ SRU Justification ]
[ Impact ]
Chen-Yu Tsai took over ownership of wireless-regdb from Seth Forshee
a few years ago, which changed the signing key of future
wireless-regdb releases.
All generic Ubuntu kernels that *don't* use CRDA have the config
option CONFIG_CFG80211_USE_KERNEL_REGDB_KEYS=y which requires the
wireless-regdb signing key to be present in the kernel so it can
validate the db signature. Thus, a commit (and follow-up fix) was
added to all upstream stable kernels to add the new key:
fb768d3b13ff ("wifi: cfg80211: Add my certificate")
3c2a8ebe3fe6 ("wifi: cfg80211: fix certs build to not depend on file order")
This config option is also set for bionic 4.15, but these patches
were not backported, so it can't validate the db. This prevents
the db from being read, and a new regulatory domain cannot be set.
Additionally, when the cfg80211 module is loaded, it prints this:
[ 191.029155] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 191.031124] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 191.031594] PKCS#7 signature not signed with a trusted key
[ 191.033142] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid
When the above patches are applied to the kernel, db file can be
validated and the domain can be set. The dmesg log no longer shows
the error message:
[ 3.638756] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 3.639242] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 3.639348] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
It should be noted that these patches were included in upstream stable
update v4.14.335 and v4.19.304, so they have been validated for similar
kernels already.
This only affects bionic because later kernels have the patches, and
earlier releases use CRDA to get the key instead of the kernel internals.
[ Test Plan ]
Steps to reproduce:
On a bionic system running generic 4.15:
1. Make sure cfg80211 module is present and wireless-regdb is installed:
$ sudo apt install linux-modules-extra-$(uname -r) wireless-regdb iw
2. If the module is not loaded automatically, load it:
$ sudo modprobe cfg80211
3. Observe the error message printed in dmesg. For additional
confirmation, you can also try (and fail) to set the domain:
$ sudo iw reg get # returns 00 domain
$ sudo iw reg set US
$ sudo iw reg get # still returns 00, failed to change to US
To test the fix, you can run these same steps, but the error message
should not be present and the `iw` commands should successfully
change the domain.
[ Where problems could occur ]
There is a low regression risk because these patches only add a new cert
key, and do not remove the existing sforshee key. Since regdb
domain setting operations may not have worked before this fix, it will
change system behaviour by allowing domains to be set, and the dmesg
log will differ.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2140602/+subscriptions
signatures for updates, for exactly this kind of problem. AIUI, Debian
replaces the key in its kernels and signs the regulatory db themselves.
Can Ubuntu do this? What would the migration path look like?
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2140602
Title:
Bionic generic kernel is missing current wireless-regdb maintainer
(Chen-Yu Tsai) key
Status in linux package in Ubuntu:
New
Status in wireless-regdb package in Ubuntu:
New
Status in linux source package in Bionic:
New
Status in wireless-regdb source package in Bionic:
New
Bug description:
[ SRU Justification ]
[ Impact ]
Chen-Yu Tsai took over ownership of wireless-regdb from Seth Forshee
a few years ago, which changed the signing key of future
wireless-regdb releases.
All generic Ubuntu kernels that *don't* use CRDA have the config
option CONFIG_CFG80211_USE_KERNEL_REGDB_KEYS=y which requires the
wireless-regdb signing key to be present in the kernel so it can
validate the db signature. Thus, a commit (and follow-up fix) was
added to all upstream stable kernels to add the new key:
fb768d3b13ff ("wifi: cfg80211: Add my certificate")
3c2a8ebe3fe6 ("wifi: cfg80211: fix certs build to not depend on file order")
This config option is also set for bionic 4.15, but these patches
were not backported, so it can't validate the db. This prevents
the db from being read, and a new regulatory domain cannot be set.
Additionally, when the cfg80211 module is loaded, it prints this:
[ 191.029155] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 191.031124] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 191.031594] PKCS#7 signature not signed with a trusted key
[ 191.033142] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid
When the above patches are applied to the kernel, db file can be
validated and the domain can be set. The dmesg log no longer shows
the error message:
[ 3.638756] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 3.639242] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 3.639348] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
It should be noted that these patches were included in upstream stable
update v4.14.335 and v4.19.304, so they have been validated for similar
kernels already.
This only affects bionic because later kernels have the patches, and
earlier releases use CRDA to get the key instead of the kernel internals.
[ Test Plan ]
Steps to reproduce:
On a bionic system running generic 4.15:
1. Make sure cfg80211 module is present and wireless-regdb is installed:
$ sudo apt install linux-modules-extra-$(uname -r) wireless-regdb iw
2. If the module is not loaded automatically, load it:
$ sudo modprobe cfg80211
3. Observe the error message printed in dmesg. For additional
confirmation, you can also try (and fail) to set the domain:
$ sudo iw reg get # returns 00 domain
$ sudo iw reg set US
$ sudo iw reg get # still returns 00, failed to change to US
To test the fix, you can run these same steps, but the error message
should not be present and the `iw` commands should successfully
change the domain.
[ Where problems could occur ]
There is a low regression risk because these patches only add a new cert
key, and do not remove the existing sforshee key. Since regdb
domain setting operations may not have worked before this fix, it will
change system behaviour by allowing domains to be set, and the dmesg
log will differ.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2140602/+subscriptions
[Bug 2142293] [NEW] WCN7850 / FastConnect 7800 Wi-Fi 7 not working — ath12k_pci module missing
Public bug reported:
The Qualcomm FastConnect 7800 (WCN7850) Wi-Fi 7 adapter is detected and the ath12k_pci module loads, but probe fails due to an unrecognized hardware revision.
Commands and output:
lspci -nn | grep -i qualcomm
uname -r
lsmod | grep ath
sudo dmesg | grep -i ath12k
ls /lib/firmware/ath12k/
09:00.0 Network controller [0280]: Qualcomm Technologies, Inc WCN785x Wi-Fi 7(802.11be) 320MHz 2x2 [FastConnect 7800] [17cb:1107] (rev 01)
6.17.0-14-generic
ath12k 987136 0
qmi_helpers 28672 1 ath12k
mac80211 1884160 1 ath12k
cfg80211 1478656 2 ath12k,mac80211
qcom_scm 53248 1 ath12k
mhi 139264 1 ath12k
[ 4.547060] ath12k_pci 0000:09:00.0: BAR 0 [mem 0xf6200000-0xf63fffff 64bit]: assigned
[ 4.547084] ath12k_pci 0000:09:00.0: enabling device (0000 -> 0002)
[ 5.005891] ath12k_pci 0000:09:00.0: Unknown hardware version found for WCN7850: 0xf
[ 5.005949] ath12k_pci 0000:09:00.0: probe with driver ath12k_pci failed with error -95
QCN9274 WCN7850
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142293
Title:
WCN7850 / FastConnect 7800 Wi-Fi 7 not working — ath12k_pci module
missing
Status in linux package in Ubuntu:
New
Bug description:
The Qualcomm FastConnect 7800 (WCN7850) Wi-Fi 7 adapter is detected and the ath12k_pci module loads, but probe fails due to an unrecognized hardware revision.
Commands and output:
lspci -nn | grep -i qualcomm
uname -r
lsmod | grep ath
sudo dmesg | grep -i ath12k
ls /lib/firmware/ath12k/
09:00.0 Network controller [0280]: Qualcomm Technologies, Inc WCN785x Wi-Fi 7(802.11be) 320MHz 2x2 [FastConnect 7800] [17cb:1107] (rev 01)
6.17.0-14-generic
ath12k 987136 0
qmi_helpers 28672 1 ath12k
mac80211 1884160 1 ath12k
cfg80211 1478656 2 ath12k,mac80211
qcom_scm 53248 1 ath12k
mhi 139264 1 ath12k
[ 4.547060] ath12k_pci 0000:09:00.0: BAR 0 [mem 0xf6200000-0xf63fffff 64bit]: assigned
[ 4.547084] ath12k_pci 0000:09:00.0: enabling device (0000 -> 0002)
[ 5.005891] ath12k_pci 0000:09:00.0: Unknown hardware version found for WCN7850: 0xf
[ 5.005949] ath12k_pci 0000:09:00.0: probe with driver ath12k_pci failed with error -95
QCN9274 WCN7850
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142293/+subscriptions
The Qualcomm FastConnect 7800 (WCN7850) Wi-Fi 7 adapter is detected and the ath12k_pci module loads, but probe fails due to an unrecognized hardware revision.
Commands and output:
lspci -nn | grep -i qualcomm
uname -r
lsmod | grep ath
sudo dmesg | grep -i ath12k
ls /lib/firmware/ath12k/
09:00.0 Network controller [0280]: Qualcomm Technologies, Inc WCN785x Wi-Fi 7(802.11be) 320MHz 2x2 [FastConnect 7800] [17cb:1107] (rev 01)
6.17.0-14-generic
ath12k 987136 0
qmi_helpers 28672 1 ath12k
mac80211 1884160 1 ath12k
cfg80211 1478656 2 ath12k,mac80211
qcom_scm 53248 1 ath12k
mhi 139264 1 ath12k
[ 4.547060] ath12k_pci 0000:09:00.0: BAR 0 [mem 0xf6200000-0xf63fffff 64bit]: assigned
[ 4.547084] ath12k_pci 0000:09:00.0: enabling device (0000 -> 0002)
[ 5.005891] ath12k_pci 0000:09:00.0: Unknown hardware version found for WCN7850: 0xf
[ 5.005949] ath12k_pci 0000:09:00.0: probe with driver ath12k_pci failed with error -95
QCN9274 WCN7850
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142293
Title:
WCN7850 / FastConnect 7800 Wi-Fi 7 not working — ath12k_pci module
missing
Status in linux package in Ubuntu:
New
Bug description:
The Qualcomm FastConnect 7800 (WCN7850) Wi-Fi 7 adapter is detected and the ath12k_pci module loads, but probe fails due to an unrecognized hardware revision.
Commands and output:
lspci -nn | grep -i qualcomm
uname -r
lsmod | grep ath
sudo dmesg | grep -i ath12k
ls /lib/firmware/ath12k/
09:00.0 Network controller [0280]: Qualcomm Technologies, Inc WCN785x Wi-Fi 7(802.11be) 320MHz 2x2 [FastConnect 7800] [17cb:1107] (rev 01)
6.17.0-14-generic
ath12k 987136 0
qmi_helpers 28672 1 ath12k
mac80211 1884160 1 ath12k
cfg80211 1478656 2 ath12k,mac80211
qcom_scm 53248 1 ath12k
mhi 139264 1 ath12k
[ 4.547060] ath12k_pci 0000:09:00.0: BAR 0 [mem 0xf6200000-0xf63fffff 64bit]: assigned
[ 4.547084] ath12k_pci 0000:09:00.0: enabling device (0000 -> 0002)
[ 5.005891] ath12k_pci 0000:09:00.0: Unknown hardware version found for WCN7850: 0xf
[ 5.005949] ath12k_pci 0000:09:00.0: probe with driver ath12k_pci failed with error -95
QCN9274 WCN7850
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142293/+subscriptions
[Bug 2142118] Re: Kernel 6.8.0-100: route cache corrupts external IPs as broadcast on systems with VLAN interfaces
It's confirm. I don't have any issues since I installed
6.8.0-103-generic
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142118
Title:
Kernel 6.8.0-100: route cache corrupts external IPs as broadcast on
systems with VLAN interfaces
Status in linux package in Ubuntu:
New
Status in linux source package in Noble:
New
Bug description:
Description:
- Regression from: 6.8.0-94 (works) to 6.8.0-100 (broken)
- Setup: Dual default routes — physical interface (enp0s31f6, DHCP, metric 100) + VLAN (enp0s31f6.3, static, metric 200)
- Symptom: ip route get 8.8.8.8 returns broadcast 8.8.8.8 ... cache <local,brd> — kernel classifies external unicast IPs as
broadcast, blocking all outbound UDP/ICMP
- Impact: All outbound DNS, NTP, ping fail with "Permission denied"
- Workaround: sudo ip route flush cache temporarily fixes it, but it recurs
- Confirmed: Booting into 6.8.0-94 resolves the issue
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142118/+subscriptions
6.8.0-103-generic
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142118
Title:
Kernel 6.8.0-100: route cache corrupts external IPs as broadcast on
systems with VLAN interfaces
Status in linux package in Ubuntu:
New
Status in linux source package in Noble:
New
Bug description:
Description:
- Regression from: 6.8.0-94 (works) to 6.8.0-100 (broken)
- Setup: Dual default routes — physical interface (enp0s31f6, DHCP, metric 100) + VLAN (enp0s31f6.3, static, metric 200)
- Symptom: ip route get 8.8.8.8 returns broadcast 8.8.8.8 ... cache <local,brd> — kernel classifies external unicast IPs as
broadcast, blocking all outbound UDP/ICMP
- Impact: All outbound DNS, NTP, ping fail with "Permission denied"
- Workaround: sudo ip route flush cache temporarily fixes it, but it recurs
- Confirmed: Booting into 6.8.0-94 resolves the issue
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142118/+subscriptions
[Bug 2141216] Re: Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT (andgpu SMU resume failure)
Just to be sure, once you rebooted after installing the new kernel,
please make sure the test kernel is running, by executing
uname -a
this should report
Linux ubuntu-questing-secure-boot 6.17.0-15-generic #15afaina1-Ubuntu
SMP PREEMPT_DYNAMIC Fri Feb 20 10:24:49 UTC 20 x86_64 GNU/Linux
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141216
Title:
Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT
(andgpu SMU resume failure)
Status in linux package in Ubuntu:
New
Status in linux source package in Questing:
Triaged
Bug description:
Summary: Suspend/resume broken after latest Ubuntu update on AMD RX
What Happens: After suspend, system wakes but display remains black. VT switching (Ctrl–Alt–F3) does not work. Only hard reboot recovers.
Regression: This started immediately after a recent Ubuntu update
Hardware: AMD RX 960 XT (Nav 44) + AMD Raphael iGPU
Relevant logs: SMU resume failure. GPU ring timeouts, GPU ring timeouts, devcoredump created (already captured by ubuntu-bug tool)
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-12-generic 6.17.0-12.12
ProcVersionSignature: Ubuntu 6.17.0-12.12-generic 6.17.2
Uname: Linux 6.17.0-12-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 7 17:54:17 2026
InstallationDate: Installed on 2025-10-20 (110 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: ASUS System Product Name
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-12-generic root=UUID=3412c7b3-e116-4927-b603-3da7641a647b ro quiet splash mem_sleep_default=s2idle crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2025
dmi.bios.release: 32.65
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3265
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B650E-E WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3265:bd06/11/2025:br32.65:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB650E-EWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141216/+subscriptions
please make sure the test kernel is running, by executing
uname -a
this should report
Linux ubuntu-questing-secure-boot 6.17.0-15-generic #15afaina1-Ubuntu
SMP PREEMPT_DYNAMIC Fri Feb 20 10:24:49 UTC 20 x86_64 GNU/Linux
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141216
Title:
Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT
(andgpu SMU resume failure)
Status in linux package in Ubuntu:
New
Status in linux source package in Questing:
Triaged
Bug description:
Summary: Suspend/resume broken after latest Ubuntu update on AMD RX
What Happens: After suspend, system wakes but display remains black. VT switching (Ctrl–Alt–F3) does not work. Only hard reboot recovers.
Regression: This started immediately after a recent Ubuntu update
Hardware: AMD RX 960 XT (Nav 44) + AMD Raphael iGPU
Relevant logs: SMU resume failure. GPU ring timeouts, GPU ring timeouts, devcoredump created (already captured by ubuntu-bug tool)
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-12-generic 6.17.0-12.12
ProcVersionSignature: Ubuntu 6.17.0-12.12-generic 6.17.2
Uname: Linux 6.17.0-12-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 7 17:54:17 2026
InstallationDate: Installed on 2025-10-20 (110 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: ASUS System Product Name
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-12-generic root=UUID=3412c7b3-e116-4927-b603-3da7641a647b ro quiet splash mem_sleep_default=s2idle crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2025
dmi.bios.release: 32.65
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3265
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B650E-E WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3265:bd06/11/2025:br32.65:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB650E-EWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141216/+subscriptions
[Bug 2141216] Re: Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT (andgpu SMU resume failure)
Hi Mike, the new package is built and correctly runs as well, so I'm
sharing a full guide on how to test it.
First of all, just in case, mark your current kernel as "hold", so it won't be uninstalled
sudo apt-mark hold linux-image-6.17.0-14-generic
This will allow us to always come back to this image in case of a
catastrophic failure.
Now, download the 2 important packages manually by running:
wget https://launchpad.net/~alessiofaina/+archive/ubuntu/launchpad-bug-2141216/+files/linux-image-unsigned-6.17.0-15-generic_6.17.0-15.15afaina1_amd64.deb
wget https://launchpad.net/~alessiofaina/+archive/ubuntu/launchpad-bug-2141216/+files/linux-modules-6.17.0-15-generic_6.17.0-15.15afaina1_amd64.deb
Those commands will download the deb packages of the kernel we want to
install.
Now let's install those packages:
sudo dpkg -i ./linux-modules-6.17.0-15-generic_6.17.0-15.15afaina1_amd64.deb ./linux-image-unsigned-6.17.0-15-generic_6.17.0-15.15afaina1_amd64.deb
This will install the new UNSIGNED kernel in your machine. The kernel
will not run, as it's not signed by Canonical, so now we need to do
another step to be able to run it.
There are 2 ways to do this. The "easiest" way, is to disable "secure boot" in your machine temporarily.
You can do this by rebooting the machine, entering the UEFI bios by pressing ESC, F10 or F12 (depends on your machine unfortunately, I can't tell), and modifying the security parameters in the BIOS.
After disabling the secure boot option, you will be able to boot the kernel I shared with you.
Without this step, you will get a message along the lines of
"error: bad shim signature"
"error: you need to load the kernel first"
and you will be bounced back to GRUB and from there you will need to select "Advanced ..." and choose the 6.17.0-14 kernel to boot back into the machine.
There is another way to sign the kernel with a self-signed key, I'll
share it with you if you don't feel confident with the BIOS modification
step.
After the testing, please uninstall my kernel by running
sudo apt remove linux-image-unsigned-6.17.0-15-generic
sudo apt remove linux-modules-6.17.0-15-generic
and unmark the kernel from the hold status.
sudo apt-mark unhold linux-image-6.17.0-14-generic
After the reboot, please re-enable the "Secure boot" option in the BIOS,
as without it, you are exposed to a variety of security vulnerabilities.
edit: adding all the forgotten "sudo"
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141216
Title:
Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT
(andgpu SMU resume failure)
Status in linux package in Ubuntu:
New
Status in linux source package in Questing:
Triaged
Bug description:
Summary: Suspend/resume broken after latest Ubuntu update on AMD RX
What Happens: After suspend, system wakes but display remains black. VT switching (Ctrl–Alt–F3) does not work. Only hard reboot recovers.
Regression: This started immediately after a recent Ubuntu update
Hardware: AMD RX 960 XT (Nav 44) + AMD Raphael iGPU
Relevant logs: SMU resume failure. GPU ring timeouts, GPU ring timeouts, devcoredump created (already captured by ubuntu-bug tool)
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-12-generic 6.17.0-12.12
ProcVersionSignature: Ubuntu 6.17.0-12.12-generic 6.17.2
Uname: Linux 6.17.0-12-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 7 17:54:17 2026
InstallationDate: Installed on 2025-10-20 (110 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: ASUS System Product Name
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-12-generic root=UUID=3412c7b3-e116-4927-b603-3da7641a647b ro quiet splash mem_sleep_default=s2idle crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2025
dmi.bios.release: 32.65
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3265
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B650E-E WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3265:bd06/11/2025:br32.65:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB650E-EWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141216/+subscriptions
sharing a full guide on how to test it.
First of all, just in case, mark your current kernel as "hold", so it won't be uninstalled
sudo apt-mark hold linux-image-6.17.0-14-generic
This will allow us to always come back to this image in case of a
catastrophic failure.
Now, download the 2 important packages manually by running:
wget https://launchpad.net/~alessiofaina/+archive/ubuntu/launchpad-bug-2141216/+files/linux-image-unsigned-6.17.0-15-generic_6.17.0-15.15afaina1_amd64.deb
wget https://launchpad.net/~alessiofaina/+archive/ubuntu/launchpad-bug-2141216/+files/linux-modules-6.17.0-15-generic_6.17.0-15.15afaina1_amd64.deb
Those commands will download the deb packages of the kernel we want to
install.
Now let's install those packages:
sudo dpkg -i ./linux-modules-6.17.0-15-generic_6.17.0-15.15afaina1_amd64.deb ./linux-image-unsigned-6.17.0-15-generic_6.17.0-15.15afaina1_amd64.deb
This will install the new UNSIGNED kernel in your machine. The kernel
will not run, as it's not signed by Canonical, so now we need to do
another step to be able to run it.
There are 2 ways to do this. The "easiest" way, is to disable "secure boot" in your machine temporarily.
You can do this by rebooting the machine, entering the UEFI bios by pressing ESC, F10 or F12 (depends on your machine unfortunately, I can't tell), and modifying the security parameters in the BIOS.
After disabling the secure boot option, you will be able to boot the kernel I shared with you.
Without this step, you will get a message along the lines of
"error: bad shim signature"
"error: you need to load the kernel first"
and you will be bounced back to GRUB and from there you will need to select "Advanced ..." and choose the 6.17.0-14 kernel to boot back into the machine.
There is another way to sign the kernel with a self-signed key, I'll
share it with you if you don't feel confident with the BIOS modification
step.
After the testing, please uninstall my kernel by running
sudo apt remove linux-image-unsigned-6.17.0-15-generic
sudo apt remove linux-modules-6.17.0-15-generic
and unmark the kernel from the hold status.
sudo apt-mark unhold linux-image-6.17.0-14-generic
After the reboot, please re-enable the "Secure boot" option in the BIOS,
as without it, you are exposed to a variety of security vulnerabilities.
edit: adding all the forgotten "sudo"
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141216
Title:
Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT
(andgpu SMU resume failure)
Status in linux package in Ubuntu:
New
Status in linux source package in Questing:
Triaged
Bug description:
Summary: Suspend/resume broken after latest Ubuntu update on AMD RX
What Happens: After suspend, system wakes but display remains black. VT switching (Ctrl–Alt–F3) does not work. Only hard reboot recovers.
Regression: This started immediately after a recent Ubuntu update
Hardware: AMD RX 960 XT (Nav 44) + AMD Raphael iGPU
Relevant logs: SMU resume failure. GPU ring timeouts, GPU ring timeouts, devcoredump created (already captured by ubuntu-bug tool)
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-12-generic 6.17.0-12.12
ProcVersionSignature: Ubuntu 6.17.0-12.12-generic 6.17.2
Uname: Linux 6.17.0-12-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 7 17:54:17 2026
InstallationDate: Installed on 2025-10-20 (110 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: ASUS System Product Name
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-12-generic root=UUID=3412c7b3-e116-4927-b603-3da7641a647b ro quiet splash mem_sleep_default=s2idle crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2025
dmi.bios.release: 32.65
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3265
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B650E-E WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3265:bd06/11/2025:br32.65:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB650E-EWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141216/+subscriptions
[Bug 2141778] Re: Change of ABI in 6.8.0 kernel breaks some OTT modules
This bug is awaiting verification that the linux/6.8.0-104.104 kernel in
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-noble-linux' to 'verification-done-noble-linux'. If
the problem still exists, change the tag 'verification-needed-noble-
linux' to 'verification-failed-noble-linux'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-noble-linux-v2 verification-needed-noble-linux
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141778
Title:
Change of ABI in 6.8.0 kernel breaks some OTT modules
Status in linux package in Ubuntu:
New
Status in linux source package in Noble:
New
Bug description:
This patch from stable updates changed some ABI that some out-of-tree
driver depends on:
https://lore.kernel.org/all/1761508983-937977-1-git-send-email-
tariqt@nvidia.com/#r.
internal reference:
http://test-db.kernel:8080/test_suite_full_console_log/?test_suite_run_id=1889057
Analyzed and reported by Jacob Martin
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141778/+subscriptions
-proposed solves the problem. Please test the kernel and update this bug
with the results. If the problem is solved, change the tag
'verification-needed-noble-linux' to 'verification-done-noble-linux'. If
the problem still exists, change the tag 'verification-needed-noble-
linux' to 'verification-failed-noble-linux'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-noble-linux-v2 verification-needed-noble-linux
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141778
Title:
Change of ABI in 6.8.0 kernel breaks some OTT modules
Status in linux package in Ubuntu:
New
Status in linux source package in Noble:
New
Bug description:
This patch from stable updates changed some ABI that some out-of-tree
driver depends on:
https://lore.kernel.org/all/1761508983-937977-1-git-send-email-
tariqt@nvidia.com/#r.
internal reference:
http://test-db.kernel:8080/test_suite_full_console_log/?test_suite_run_id=1889057
Analyzed and reported by Jacob Martin
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141778/+subscriptions
[Bug 2142271] [NEW] Ubuntu 24.04.3 HWE kernel failed to boot on Dell PE R7725(AMD Turin CPU) server.
*** This bug is a security vulnerability ***
Private security bug reported:
Ubuntu 24.04.3 LTS with HWE kernel fails to boot on Dell PowerEdge R7725 servers.
During boot, the system repeatedly outputs: "stdin: Invalid argument" and eventually prompts for boot options (e.g., "Attempt interactive netboot from a URL?"). The system does not proceed to load the operating system.
Steps to Repro:
1. Download the Ubuntu 24.04.3 LTS ISO image with the Hardware Enablement (HWE) kernel.
2. Prepare a bootable installation media (ISO mounted via virtual media or USB).
3. Access the Dell PowerEdge R7725 server and configure it to boot from the prepared installation media.
4. Start the boot process using the HWE kernel option from the GRUB menu.
5. Observe the console output during the boot sequence.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "AMD_serial logs.txt"
https://bugs.launchpad.net/bugs/2142271/+attachment/5947411/+files/AMD_serial%20logs.txt
** Information type changed from Public to Private Security
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142271
Title:
Ubuntu 24.04.3 HWE kernel failed to boot on Dell PE R7725(AMD Turin
CPU) server.
Status in linux package in Ubuntu:
New
Bug description:
Ubuntu 24.04.3 LTS with HWE kernel fails to boot on Dell PowerEdge R7725 servers.
During boot, the system repeatedly outputs: "stdin: Invalid argument" and eventually prompts for boot options (e.g., "Attempt interactive netboot from a URL?"). The system does not proceed to load the operating system.
Steps to Repro:
1. Download the Ubuntu 24.04.3 LTS ISO image with the Hardware Enablement (HWE) kernel.
2. Prepare a bootable installation media (ISO mounted via virtual media or USB).
3. Access the Dell PowerEdge R7725 server and configure it to boot from the prepared installation media.
4. Start the boot process using the HWE kernel option from the GRUB menu.
5. Observe the console output during the boot sequence.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142271/+subscriptions
Private security bug reported:
Ubuntu 24.04.3 LTS with HWE kernel fails to boot on Dell PowerEdge R7725 servers.
During boot, the system repeatedly outputs: "stdin: Invalid argument" and eventually prompts for boot options (e.g., "Attempt interactive netboot from a URL?"). The system does not proceed to load the operating system.
Steps to Repro:
1. Download the Ubuntu 24.04.3 LTS ISO image with the Hardware Enablement (HWE) kernel.
2. Prepare a bootable installation media (ISO mounted via virtual media or USB).
3. Access the Dell PowerEdge R7725 server and configure it to boot from the prepared installation media.
4. Start the boot process using the HWE kernel option from the GRUB menu.
5. Observe the console output during the boot sequence.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "AMD_serial logs.txt"
https://bugs.launchpad.net/bugs/2142271/+attachment/5947411/+files/AMD_serial%20logs.txt
** Information type changed from Public to Private Security
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142271
Title:
Ubuntu 24.04.3 HWE kernel failed to boot on Dell PE R7725(AMD Turin
CPU) server.
Status in linux package in Ubuntu:
New
Bug description:
Ubuntu 24.04.3 LTS with HWE kernel fails to boot on Dell PowerEdge R7725 servers.
During boot, the system repeatedly outputs: "stdin: Invalid argument" and eventually prompts for boot options (e.g., "Attempt interactive netboot from a URL?"). The system does not proceed to load the operating system.
Steps to Repro:
1. Download the Ubuntu 24.04.3 LTS ISO image with the Hardware Enablement (HWE) kernel.
2. Prepare a bootable installation media (ISO mounted via virtual media or USB).
3. Access the Dell PowerEdge R7725 server and configure it to boot from the prepared installation media.
4. Start the boot process using the HWE kernel option from the GRUB menu.
5. Observe the console output during the boot sequence.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142271/+subscriptions
[Bug 2141216] Re: Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT (andgpu SMU resume failure)
Don't worry Mike, you did good.
I'll spin a new kernel and give you detailed instructions during the
day, sorry if I haven't done it before.
To make it easier I will create a kernel with a higher version number
(15.15) and give you more instructions on how to install and switch the
kernel, while maintaining the previous kernels intact, plus the
instructions to get back to the previous kernel.
Sorry, I took too many things for granted. It will take me a bit, I'll
come back to you as soon as possible.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141216
Title:
Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT
(andgpu SMU resume failure)
Status in linux package in Ubuntu:
New
Status in linux source package in Questing:
Triaged
Bug description:
Summary: Suspend/resume broken after latest Ubuntu update on AMD RX
What Happens: After suspend, system wakes but display remains black. VT switching (Ctrl–Alt–F3) does not work. Only hard reboot recovers.
Regression: This started immediately after a recent Ubuntu update
Hardware: AMD RX 960 XT (Nav 44) + AMD Raphael iGPU
Relevant logs: SMU resume failure. GPU ring timeouts, GPU ring timeouts, devcoredump created (already captured by ubuntu-bug tool)
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-12-generic 6.17.0-12.12
ProcVersionSignature: Ubuntu 6.17.0-12.12-generic 6.17.2
Uname: Linux 6.17.0-12-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 7 17:54:17 2026
InstallationDate: Installed on 2025-10-20 (110 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: ASUS System Product Name
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-12-generic root=UUID=3412c7b3-e116-4927-b603-3da7641a647b ro quiet splash mem_sleep_default=s2idle crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2025
dmi.bios.release: 32.65
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3265
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B650E-E WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3265:bd06/11/2025:br32.65:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB650E-EWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141216/+subscriptions
I'll spin a new kernel and give you detailed instructions during the
day, sorry if I haven't done it before.
To make it easier I will create a kernel with a higher version number
(15.15) and give you more instructions on how to install and switch the
kernel, while maintaining the previous kernels intact, plus the
instructions to get back to the previous kernel.
Sorry, I took too many things for granted. It will take me a bit, I'll
come back to you as soon as possible.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141216
Title:
Suspend/resume broken after latest Ubuntu update on AMD RX 960 XT
(andgpu SMU resume failure)
Status in linux package in Ubuntu:
New
Status in linux source package in Questing:
Triaged
Bug description:
Summary: Suspend/resume broken after latest Ubuntu update on AMD RX
What Happens: After suspend, system wakes but display remains black. VT switching (Ctrl–Alt–F3) does not work. Only hard reboot recovers.
Regression: This started immediately after a recent Ubuntu update
Hardware: AMD RX 960 XT (Nav 44) + AMD Raphael iGPU
Relevant logs: SMU resume failure. GPU ring timeouts, GPU ring timeouts, devcoredump created (already captured by ubuntu-bug tool)
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-12-generic 6.17.0-12.12
ProcVersionSignature: Ubuntu 6.17.0-12.12-generic 6.17.2
Uname: Linux 6.17.0-12-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 7 17:54:17 2026
InstallationDate: Installed on 2025-10-20 (110 days ago)
InstallationMedia: Ubuntu 25.10 "Questing Quokka" - Release amd64 (20251007)
MachineType: ASUS System Product Name
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-12-generic root=UUID=3412c7b3-e116-4927-b603-3da7641a647b ro quiet splash mem_sleep_default=s2idle crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/11/2025
dmi.bios.release: 32.65
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3265
dmi.board.asset.tag: Default string
dmi.board.name: TUF GAMING B650E-E WIFI
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3265:bd06/11/2025:br32.65:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGB650E-EWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2141216/+subscriptions
Подписаться на:
Комментарии (Atom)