I ran another test, with linux-firmware 20240318.git3b128b60-0ubuntu2.10
and kernel 6.8.0-48, the last combination which never had any problems
when it was current (around March 2025).
Still I am getting wifi failures.
Either the issue is related to a package other than firmware or kernel,
or I am really experiencing hardware issues (though that is unlikely
IMHO), or there's something I haven't thought of yet. I've run out of
ideas to try.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2128724
Title:
iwlwifi crashing after some hours, leaving WiFi broken
Status in linux package in Ubuntu:
Confirmed
Status in linux-firmware package in Ubuntu:
New
Bug description:
Hi,
I get the attached kernel error some hours after boot (depends on traffic, but always happen at least during 2 days). Wi-Fi connection is gone then.
Best regards
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-83-generic 6.8.0-83.83
ProcVersionSignature: Ubuntu 6.8.0-83.83-generic 6.8.12
Uname: Linux 6.8.0-83-generic x86_64
NonfreeKernelModules: zfs
AlsaDevices:
total 0
crw-rw----+ 1 root audio 116, 1 Oct 17 10:29 seq
crw-rw----+ 1 root audio 116, 33 Oct 17 10:29 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: unknown
Date: Fri Oct 17 16:49:22 2025
InstallationDate: Installed on 2025-04-04 (196 days ago)
InstallationMedia: Ubuntu-Server 24.04.2 LTS "Noble Numbat" - Release amd64 (20250216.2)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: HPE ProLiant MicroServer Gen10
PciMultimedia:
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=linux
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-83-generic root=UUID=4e4eecef-2f9e-437d-8f0d-57e5f3c9bf21 ro
RelatedPackageVersions:
linux-restricted-modules-6.8.0-83-generic N/A
linux-backports-modules-6.8.0-83-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.17
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/19/2020
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.12
dmi.board.asset.tag: Default string
dmi.board.name: ProLiant MicroServer Gen10
dmi.board.vendor: HPE
dmi.board.version: 871721-001
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 1
dmi.chassis.vendor: HPE
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/19/2020:br5.12:svnHPE:pnProLiantMicroServerGen10:pvrRevB:rvnHPE:rnProLiantMicroServerGen10:rvr871721-001:cvnHPE:ct1:cvrDefaultstring:sku873830-421:
dmi.product.family: ProLiant
dmi.product.name: ProLiant MicroServer Gen10
dmi.product.sku: 873830-421
dmi.product.version: Rev B
dmi.sys.vendor: HPE
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2128724/+subscriptions
пятница
[Bug 2144380] Re: macvlan: observe an RCU grace period in macvlan_common_newlink() error path
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Ian Whitfield (ijwhitfield)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2144380
Title:
macvlan: observe an RCU grace period in macvlan_common_newlink() error
path
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
New
Status in linux source package in Noble:
New
Status in linux source package in Questing:
New
Bug description:
SRU Justification
[Impact]
This is a follow-up fix to the CVE-2026-23209 fix already applied to
the Jammy, Noble, and Questing trees. The ESM kernel trees did not
already get the CVE-2026-23209 fix applied, so the follow-up was added
in the initial patchset for those kernels, and this LP bug is not
needed there. For generally available kernels, this LP bug was made to
specifically track the follow-up being applied.
Commit message of the follow-up:
macvlan_common_newlink() might have made @dev visible before
detecting an error, and its caller will directly call free_netdev(dev).
We must respect an RCU period, either in macvlan or the core networking
stack.
After adding a temporary mdelay(1000) in macvlan_forward_source_one()
to open the race window, valis repro was:
ip link add p1 type veth peer p2
ip link set address 00:00:00:00:00:20 dev p1
ip link set up dev p1
ip link set up dev p2
ip link add mv0 link p2 type macvlan mode source
(ip link add invalid% link p2 type macvlan mode source macaddr add
00:00:00:00:00:20 &) ; sleep 0.5 ; ping -c1 -I p1 1.2.3.4
PING 1.2.3.4 (1.2.3.4): 56 data bytes
RTNETLINK answers: Invalid argument
BUG: KASAN: slab-use-after-free in macvlan_forward_source
(drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)
Read of size 8 at addr ffff888016bb89c0 by task e/175
CPU: 1 UID: 1000 PID: 175 Comm: e Not tainted 6.19.0-rc8+ #33 NONE
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014
Call Trace:
<IRQ>
dump_stack_lvl (lib/dump_stack.c:123)
print_report (mm/kasan/report.c:379 mm/kasan/report.c:482)
? macvlan_forward_source (drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)
kasan_report (mm/kasan/report.c:597)
? macvlan_forward_source (drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)
macvlan_forward_source (drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)
? tasklet_init (kernel/softirq.c:983)
macvlan_handle_frame (drivers/net/macvlan.c:501)
Allocated by task 169:
kasan_save_stack (mm/kasan/common.c:58)
kasan_save_track (./arch/x86/include/asm/current.h:25
mm/kasan/common.c:70 mm/kasan/common.c:79)
__kasan_kmalloc (mm/kasan/common.c:419)
__kvmalloc_node_noprof (./include/linux/kasan.h:263 mm/slub.c:5657
mm/slub.c:7140)
alloc_netdev_mqs (net/core/dev.c:12012)
rtnl_create_link (net/core/rtnetlink.c:3648)
rtnl_newlink (net/core/rtnetlink.c:3830 net/core/rtnetlink.c:3957
net/core/rtnetlink.c:4072)
rtnetlink_rcv_msg (net/core/rtnetlink.c:6958)
netlink_rcv_skb (net/netlink/af_netlink.c:2550)
netlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)
netlink_sendmsg (net/netlink/af_netlink.c:1894)
__sys_sendto (net/socket.c:727 net/socket.c:742 net/socket.c:2206)
__x64_sys_sendto (net/socket.c:2209)
do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)
entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:131)
Freed by task 169:
kasan_save_stack (mm/kasan/common.c:58)
kasan_save_track (./arch/x86/include/asm/current.h:25
mm/kasan/common.c:70 mm/kasan/common.c:79)
kasan_save_free_info (mm/kasan/generic.c:587)
__kasan_slab_free (mm/kasan/common.c:287)
kfree (mm/slub.c:6674 mm/slub.c:6882)
rtnl_newlink (net/core/rtnetlink.c:3845 net/core/rtnetlink.c:3957
net/core/rtnetlink.c:4072)
rtnetlink_rcv_msg (net/core/rtnetlink.c:6958)
netlink_rcv_skb (net/netlink/af_netlink.c:2550)
netlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)
netlink_sendmsg (net/netlink/af_netlink.c:1894)
__sys_sendto (net/socket.c:727 net/socket.c:742 net/socket.c:2206)
__x64_sys_sendto (net/socket.c:2209)
do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)
entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:131)
[Backport]
The patch was applied cleanly.
[Fix]
Questing: Cherry-pick
Noble: Cherry-pick
Jammy: Cherry-pick
Focal: Included in initial CVE-2026-23209 patchset
Bionic: Included in initial CVE-2026-23209 patchset
Xenial: not affected
Trusty: not affected
[Test Case]
Compile and boot tested.
[Where problems could occur]
This fix affects those who use MAC-VLAN to create virtual interfaces that map
packets to or from specific MAC addresses to a particular interface. An issue
with this fix would be visible to the user via a kernel crash or networking
issues with virtual interfaces (containers/VMs).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144380/+subscriptions
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Ian Whitfield (ijwhitfield)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2144380
Title:
macvlan: observe an RCU grace period in macvlan_common_newlink() error
path
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
New
Status in linux source package in Noble:
New
Status in linux source package in Questing:
New
Bug description:
SRU Justification
[Impact]
This is a follow-up fix to the CVE-2026-23209 fix already applied to
the Jammy, Noble, and Questing trees. The ESM kernel trees did not
already get the CVE-2026-23209 fix applied, so the follow-up was added
in the initial patchset for those kernels, and this LP bug is not
needed there. For generally available kernels, this LP bug was made to
specifically track the follow-up being applied.
Commit message of the follow-up:
macvlan_common_newlink() might have made @dev visible before
detecting an error, and its caller will directly call free_netdev(dev).
We must respect an RCU period, either in macvlan or the core networking
stack.
After adding a temporary mdelay(1000) in macvlan_forward_source_one()
to open the race window, valis repro was:
ip link add p1 type veth peer p2
ip link set address 00:00:00:00:00:20 dev p1
ip link set up dev p1
ip link set up dev p2
ip link add mv0 link p2 type macvlan mode source
(ip link add invalid% link p2 type macvlan mode source macaddr add
00:00:00:00:00:20 &) ; sleep 0.5 ; ping -c1 -I p1 1.2.3.4
PING 1.2.3.4 (1.2.3.4): 56 data bytes
RTNETLINK answers: Invalid argument
BUG: KASAN: slab-use-after-free in macvlan_forward_source
(drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)
Read of size 8 at addr ffff888016bb89c0 by task e/175
CPU: 1 UID: 1000 PID: 175 Comm: e Not tainted 6.19.0-rc8+ #33 NONE
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014
Call Trace:
<IRQ>
dump_stack_lvl (lib/dump_stack.c:123)
print_report (mm/kasan/report.c:379 mm/kasan/report.c:482)
? macvlan_forward_source (drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)
kasan_report (mm/kasan/report.c:597)
? macvlan_forward_source (drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)
macvlan_forward_source (drivers/net/macvlan.c:408 drivers/net/macvlan.c:444)
? tasklet_init (kernel/softirq.c:983)
macvlan_handle_frame (drivers/net/macvlan.c:501)
Allocated by task 169:
kasan_save_stack (mm/kasan/common.c:58)
kasan_save_track (./arch/x86/include/asm/current.h:25
mm/kasan/common.c:70 mm/kasan/common.c:79)
__kasan_kmalloc (mm/kasan/common.c:419)
__kvmalloc_node_noprof (./include/linux/kasan.h:263 mm/slub.c:5657
mm/slub.c:7140)
alloc_netdev_mqs (net/core/dev.c:12012)
rtnl_create_link (net/core/rtnetlink.c:3648)
rtnl_newlink (net/core/rtnetlink.c:3830 net/core/rtnetlink.c:3957
net/core/rtnetlink.c:4072)
rtnetlink_rcv_msg (net/core/rtnetlink.c:6958)
netlink_rcv_skb (net/netlink/af_netlink.c:2550)
netlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)
netlink_sendmsg (net/netlink/af_netlink.c:1894)
__sys_sendto (net/socket.c:727 net/socket.c:742 net/socket.c:2206)
__x64_sys_sendto (net/socket.c:2209)
do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)
entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:131)
Freed by task 169:
kasan_save_stack (mm/kasan/common.c:58)
kasan_save_track (./arch/x86/include/asm/current.h:25
mm/kasan/common.c:70 mm/kasan/common.c:79)
kasan_save_free_info (mm/kasan/generic.c:587)
__kasan_slab_free (mm/kasan/common.c:287)
kfree (mm/slub.c:6674 mm/slub.c:6882)
rtnl_newlink (net/core/rtnetlink.c:3845 net/core/rtnetlink.c:3957
net/core/rtnetlink.c:4072)
rtnetlink_rcv_msg (net/core/rtnetlink.c:6958)
netlink_rcv_skb (net/netlink/af_netlink.c:2550)
netlink_unicast (net/netlink/af_netlink.c:1319 net/netlink/af_netlink.c:1344)
netlink_sendmsg (net/netlink/af_netlink.c:1894)
__sys_sendto (net/socket.c:727 net/socket.c:742 net/socket.c:2206)
__x64_sys_sendto (net/socket.c:2209)
do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94)
entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:131)
[Backport]
The patch was applied cleanly.
[Fix]
Questing: Cherry-pick
Noble: Cherry-pick
Jammy: Cherry-pick
Focal: Included in initial CVE-2026-23209 patchset
Bionic: Included in initial CVE-2026-23209 patchset
Xenial: not affected
Trusty: not affected
[Test Case]
Compile and boot tested.
[Where problems could occur]
This fix affects those who use MAC-VLAN to create virtual interfaces that map
packets to or from specific MAC addresses to a particular interface. An issue
with this fix would be visible to the user via a kernel crash or networking
issues with virtual interfaces (containers/VMs).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144380/+subscriptions
[Bug 2143030] Re: U26.04 initramfs missing emmc modules
** Changed in: dracut (Ubuntu Resolute)
Status: In Progress => Fix Committed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143030
Title:
U26.04 initramfs missing emmc modules
Status in dracut package in Ubuntu:
Fix Committed
Status in linux package in Ubuntu:
Invalid
Status in dracut source package in Resolute:
Fix Committed
Status in linux source package in Resolute:
Invalid
Bug description:
in ubuntu 24.04 , emmc related modules is default available in
initramsfs
user@localhost:~$ sudo lsinitramfs /boot/initrd.img-6.17.0-14-generic | grep -Ei '(mmc_block|mmc_core|cqhci|sdhci).*.ko'
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/core/mmc_block.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/cqhci.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci-acpi.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci-pci.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci-pltfm.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci-uhs2.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci-xenon-driver.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci_f_sdh30.ko.zst
In ubuntu 26.04, emmc related modules is not available in initramfs
user@localhost:~$ sudo lsinitramfs /boot/initrd.img-6.18.0-9-generic | grep -Ei '(mmc_block|mmc_core|cqhci|sdhci).*.ko'
user@localhost:~$ echo $?
1
The missing emmc modules in initramfs unfortunately lead to disk image
of ubuntu26.04 failed to boot in emmc.
user@localhost:~$ lsb_release -rd
Description: Ubuntu Resolute Raccoon (development branch)
Release: 26.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2143030/+subscriptions
Status: In Progress => Fix Committed
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2143030
Title:
U26.04 initramfs missing emmc modules
Status in dracut package in Ubuntu:
Fix Committed
Status in linux package in Ubuntu:
Invalid
Status in dracut source package in Resolute:
Fix Committed
Status in linux source package in Resolute:
Invalid
Bug description:
in ubuntu 24.04 , emmc related modules is default available in
initramsfs
user@localhost:~$ sudo lsinitramfs /boot/initrd.img-6.17.0-14-generic | grep -Ei '(mmc_block|mmc_core|cqhci|sdhci).*.ko'
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/core/mmc_block.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/cqhci.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci-acpi.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci-pci.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci-pltfm.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci-uhs2.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci-xenon-driver.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci.ko.zst
usr/lib/modules/6.17.0-14-generic/kernel/drivers/mmc/host/sdhci_f_sdh30.ko.zst
In ubuntu 26.04, emmc related modules is not available in initramfs
user@localhost:~$ sudo lsinitramfs /boot/initrd.img-6.18.0-9-generic | grep -Ei '(mmc_block|mmc_core|cqhci|sdhci).*.ko'
user@localhost:~$ echo $?
1
The missing emmc modules in initramfs unfortunately lead to disk image
of ubuntu26.04 failed to boot in emmc.
user@localhost:~$ lsb_release -rd
Description: Ubuntu Resolute Raccoon (development branch)
Release: 26.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dracut/+bug/2143030/+subscriptions
[Bug 2140602] Re: Bionic generic kernel is missing current wireless-regdb maintainer (Chen-Yu Tsai) key
Confirmed the problem is present:
$ uname -a
Linux ip-172-31-31-245 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
dmesg:
[ 2127.613362] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 2127.617786] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 2127.622906] PKCS#7 signature not signed with a trusted key
[ 2127.626330] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid
sudo iw reg set US does not set the domain.
Installed generic kernel from esm-proposed:
$ uname -a
Linux ip-172-31-31-245 4.15.0-248-generic #260-Ubuntu SMP Fri Mar 13 17:23:39 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux
dmesg:
[ 72.661053] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 72.664441] cfg80211: Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[ 72.664657] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
sudo iw reg set US now succeeds in setting the domain.
** Tags removed: verification-needed-bionic-linux
** Tags added: verification-done-bionic-linux
--
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
$ uname -a
Linux ip-172-31-31-245 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
dmesg:
[ 2127.613362] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 2127.617786] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[ 2127.622906] PKCS#7 signature not signed with a trusted key
[ 2127.626330] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid
sudo iw reg set US does not set the domain.
Installed generic kernel from esm-proposed:
$ uname -a
Linux ip-172-31-31-245 4.15.0-248-generic #260-Ubuntu SMP Fri Mar 13 17:23:39 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux
dmesg:
[ 72.661053] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 72.664441] cfg80211: Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[ 72.664657] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
sudo iw reg set US now succeeds in setting the domain.
** Tags removed: verification-needed-bionic-linux
** Tags added: verification-done-bionic-linux
--
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 2144976] [NEW] no file /etc/default/grub
Public bug reported:
the file /etc/default/grub is not here
jpb@jpb-B760M-U26: ~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Resolute Raccoon (development branch)
Release: 26.04
Codename: resolute
jpb@jpb-B760M-U26: ~ $ uname -a
Linux jpb-B760M-U26.04 7.0.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 12 11:34:39 UTC 2026 x86_64 GNU/Linux
jpb@jpb-B760M-U26: ~ $ jpb@jpb-B760M-U26: ~ $ ls -als /etc/default/g*
total 12
4 drwxr-xr-x 2 root root 4096 Mar 13 06:32 .
4 drwxr-xr-x 4 root root 4096 Mar 18 08:15 ..
4 -rw-r--r-- 1 root root 133 Feb 11 23:26 kdump-tools.cfg
** 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/2144976
Title:
no file /etc/default/grub
Status in linux package in Ubuntu:
New
Bug description:
the file /etc/default/grub is not here
jpb@jpb-B760M-U26: ~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Resolute Raccoon (development branch)
Release: 26.04
Codename: resolute
jpb@jpb-B760M-U26: ~ $ uname -a
Linux jpb-B760M-U26.04 7.0.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 12 11:34:39 UTC 2026 x86_64 GNU/Linux
jpb@jpb-B760M-U26: ~ $ jpb@jpb-B760M-U26: ~ $ ls -als /etc/default/g*
total 12
4 drwxr-xr-x 2 root root 4096 Mar 13 06:32 .
4 drwxr-xr-x 4 root root 4096 Mar 18 08:15 ..
4 -rw-r--r-- 1 root root 133 Feb 11 23:26 kdump-tools.cfg
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144976/+subscriptions
the file /etc/default/grub is not here
jpb@jpb-B760M-U26: ~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Resolute Raccoon (development branch)
Release: 26.04
Codename: resolute
jpb@jpb-B760M-U26: ~ $ uname -a
Linux jpb-B760M-U26.04 7.0.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 12 11:34:39 UTC 2026 x86_64 GNU/Linux
jpb@jpb-B760M-U26: ~ $ jpb@jpb-B760M-U26: ~ $ ls -als /etc/default/g*
total 12
4 drwxr-xr-x 2 root root 4096 Mar 13 06:32 .
4 drwxr-xr-x 4 root root 4096 Mar 18 08:15 ..
4 -rw-r--r-- 1 root root 133 Feb 11 23:26 kdump-tools.cfg
** 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/2144976
Title:
no file /etc/default/grub
Status in linux package in Ubuntu:
New
Bug description:
the file /etc/default/grub is not here
jpb@jpb-B760M-U26: ~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Resolute Raccoon (development branch)
Release: 26.04
Codename: resolute
jpb@jpb-B760M-U26: ~ $ uname -a
Linux jpb-B760M-U26.04 7.0.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 12 11:34:39 UTC 2026 x86_64 GNU/Linux
jpb@jpb-B760M-U26: ~ $ jpb@jpb-B760M-U26: ~ $ ls -als /etc/default/g*
total 12
4 drwxr-xr-x 2 root root 4096 Mar 13 06:32 .
4 drwxr-xr-x 4 root root 4096 Mar 18 08:15 ..
4 -rw-r--r-- 1 root root 133 Feb 11 23:26 kdump-tools.cfg
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144976/+subscriptions
[Bug 2142087] Re: simpledrm fails to hand off /dev/dri/card0 to amdgpu on Picasso/Raven2, causing GDM crash and black screen
Update — March 20, 2026:
After a GDM update (46.2-1ubuntu1~24.04.6), the crash no longer reproduces on this hardware. Tested on both kernel 6.17.0-14 (original crash kernel) and 6.17.0-19 without the initcall_blacklist workaround.
GDM now correctly ignores card0 (simpledrm) and goes directly to card1 (amdgpu) on both kernels. The GDM patch local-display-factory-Match-simpledrm-in-a-substring-inst.patch is present and effective on AMD Picasso/Raven2 [1002:15d8].
The underlying kernel-level handoff issue remains — simpledrm still occupies minor 0 and amdgpu gets minor 1 — but the GDM-level fix now prevents the crash on this hardware.
Full proof attached.
** Attachment added: "Boot logs from kernel 6.17.0-14 and 6.17.0-19 showing GDM patch now effective on AMD Picasso/Raven2"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142087/+attachment/5954263/+files/bug-2142087-update-proof.txt
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142087
Title:
simpledrm fails to hand off /dev/dri/card0 to amdgpu on
Picasso/Raven2, causing GDM crash and black screen
Status in linux package in Ubuntu:
New
Bug description:
Affects:
Ubuntu 24.04.3 LTS, Kernel 6.17.0-14-generic
Hardware:
AMD Picasso/Raven 2 [Radeon Vega Series] [1002:15d8]
Description:
On AMD Picasso/Raven2 APUs, the simpledrm framebuffer driver initializes during early boot and claims /dev/dri/card0. When the amdgpu driver loads ~16 seconds later, simpledrm fails to properly hand off the device. This forces amdgpu to register as /dev/dri/card1 instead.
GDM/GNOME Shell expects the primary GPU at card0. When it finds simpledrm there (which cannot do hardware-accelerated rendering), it crashes with:
Failed to ensure KMS FB ID on /dev/dri/card0: drmModeAddFB failed: No such device
GDM automatically retries and eventually discovers card1 (the real amdgpu), but this causes:
Login screen crash on first attempt
Black screen with cursor for ~5-10 seconds
Random boot failures requiring multiple reboots
Steps to Reproduce:
Boot Ubuntu 24.04.3 with kernel 6.17.0-14 on AMD Picasso/Raven2 hardware
Observe black screen after UEFI logo
Check ls -la /dev/dri/ from TTY2 → shows only card1
Check dmesg → simpledrm on minor 0, amdgpu on minor 1
Expected:
amdgpu should claim /dev/dri/card0, GDM should start cleanly
Actual:
simpledrm blocks card0, amdgpu gets card1, GDM crashes and retries
Workaround:
Add to /etc/default/grub:
GRUB_CMDLINE_LINUX_DEFAULT="... initcall_blacklist=simpledrm_platform_driver_init"
Then sudo update-grub and reboot.
This prevents simpledrm from loading, allowing amdgpu to properly claim card0.
Attachments:
bug-card1-proof.txt (shows card1 without workaround)
bug-dmesg-card1.txt (kernel logs showing simpledrm/amdgpu conflict)
bug-gnome-crash.txt (GDM crash and retry sequence)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142087/+subscriptions
After a GDM update (46.2-1ubuntu1~24.04.6), the crash no longer reproduces on this hardware. Tested on both kernel 6.17.0-14 (original crash kernel) and 6.17.0-19 without the initcall_blacklist workaround.
GDM now correctly ignores card0 (simpledrm) and goes directly to card1 (amdgpu) on both kernels. The GDM patch local-display-factory-Match-simpledrm-in-a-substring-inst.patch is present and effective on AMD Picasso/Raven2 [1002:15d8].
The underlying kernel-level handoff issue remains — simpledrm still occupies minor 0 and amdgpu gets minor 1 — but the GDM-level fix now prevents the crash on this hardware.
Full proof attached.
** Attachment added: "Boot logs from kernel 6.17.0-14 and 6.17.0-19 showing GDM patch now effective on AMD Picasso/Raven2"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142087/+attachment/5954263/+files/bug-2142087-update-proof.txt
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142087
Title:
simpledrm fails to hand off /dev/dri/card0 to amdgpu on
Picasso/Raven2, causing GDM crash and black screen
Status in linux package in Ubuntu:
New
Bug description:
Affects:
Ubuntu 24.04.3 LTS, Kernel 6.17.0-14-generic
Hardware:
AMD Picasso/Raven 2 [Radeon Vega Series] [1002:15d8]
Description:
On AMD Picasso/Raven2 APUs, the simpledrm framebuffer driver initializes during early boot and claims /dev/dri/card0. When the amdgpu driver loads ~16 seconds later, simpledrm fails to properly hand off the device. This forces amdgpu to register as /dev/dri/card1 instead.
GDM/GNOME Shell expects the primary GPU at card0. When it finds simpledrm there (which cannot do hardware-accelerated rendering), it crashes with:
Failed to ensure KMS FB ID on /dev/dri/card0: drmModeAddFB failed: No such device
GDM automatically retries and eventually discovers card1 (the real amdgpu), but this causes:
Login screen crash on first attempt
Black screen with cursor for ~5-10 seconds
Random boot failures requiring multiple reboots
Steps to Reproduce:
Boot Ubuntu 24.04.3 with kernel 6.17.0-14 on AMD Picasso/Raven2 hardware
Observe black screen after UEFI logo
Check ls -la /dev/dri/ from TTY2 → shows only card1
Check dmesg → simpledrm on minor 0, amdgpu on minor 1
Expected:
amdgpu should claim /dev/dri/card0, GDM should start cleanly
Actual:
simpledrm blocks card0, amdgpu gets card1, GDM crashes and retries
Workaround:
Add to /etc/default/grub:
GRUB_CMDLINE_LINUX_DEFAULT="... initcall_blacklist=simpledrm_platform_driver_init"
Then sudo update-grub and reboot.
This prevents simpledrm from loading, allowing amdgpu to properly claim card0.
Attachments:
bug-card1-proof.txt (shows card1 without workaround)
bug-dmesg-card1.txt (kernel logs showing simpledrm/amdgpu conflict)
bug-gnome-crash.txt (GDM crash and retry sequence)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142087/+subscriptions
[Bug 1726299] Re: Apple Thunderbolt 2 to FireWire adapter not working
** Changed in: linux
Status: Confirmed => Incomplete
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1726299
Title:
Apple Thunderbolt 2 to FireWire adapter not working
Status in Linux:
Incomplete
Status in linux package in Ubuntu:
Confirmed
Bug description:
The adapter is connected through an Apple Thunderbolt 3 to Thunderbolt
2 adapter. Ubuntu seems not to recognize the Firewire adapter.
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 17.04
Release: 17.04
Codename: zesty
uname -r
4.10.0-19-generic
sudo lshw -short
H/W-Pfad Gerät Klasse Beschreibung
===============================================================
system Z170N-Gaming 5 (Default string)
/0 bus Z170N-Gaming 5
/0/0 memory 64KiB BIOS
/0/3d memory 16GiB Systemspeicher
/0/3d/0 memory 8GiB DIMM DDR4 Synchron 2133 MHz (0,5 ns)
/0/3d/1 memory Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME <EMAIL@ADDRESS>POT-Creatio
/0/3d/2 memory 8GiB DIMM DDR4 Synchron 2133 MHz (0,5 ns)
/0/3d/3 memory Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME <EMAIL@ADDRESS>POT-Creatio
/0/43 memory 128KiB L1 Cache
/0/44 memory 512KiB L2 Cache
/0/45 memory 3MiB L3 Cache
/0/46 processor Intel(R) Core(TM) i3-6100T CPU @ 3.20GHz
/0/100 bridge Skylake Host Bridge/DRAM Registers
/0/100/1 bridge Skylake PCIe Controller (x16)
/0/100/1/0 display Oland GL [FirePro W2100]
/0/100/1/0.1 multimedia Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series]
/0/100/14 bus Sunrise Point-H USB 3.0 xHCI Controller
/0/100/14/0 usb1 bus xHCI Host Controller
/0/100/14/0/6 input USB Gaming Keyboard
/0/100/14/0/d communication Bluetooth-Schnittstelle
/0/100/14/1 usb2 bus xHCI Host Controller
/0/100/14/1/5 scsi6 storage Storage Media
/0/100/14/1/5/0.0.0 /dev/sdb disk 15GB Storage Media
/0/100/14/1/5/0.0.0/0 /dev/sdb disk 15GB
/0/100/14/1/5/0.0.0/0/2 /dev/sdb2 volume 15EiB Windows FAT Laufwerk
/0/100/16 communication Sunrise Point-H CSME HECI #1
/0/100/17 storage Sunrise Point-H SATA controller [AHCI mode]
/0/100/1b bridge Sunrise Point-H PCI Root Port #17
/0/100/1b.2 bridge Sunrise Point-H PCI Root Port #19
/0/100/1b.3 bridge Sunrise Point-H PCI Root Port #20
/0/100/1c bridge Sunrise Point-H PCI Express Root Port #1
/0/100/1c/0 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
/0/100/1c/0/0 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
/0/100/1c/0/1 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
/0/100/1c/0/2 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
/0/100/1c/0/2/0 bus DSL6540 USB 3.1 Controller [Alpine Ridge]
/0/100/1c/0/2/0/0 usb3 bus xHCI Host Controller
/0/100/1c/0/2/0/0/1 generic Thunderbolt 3 (USB-C) to Thunderbolt 2 Adapter
/0/100/1c/0/2/0/0/2 input USB Optical Mouse
/0/100/1c/0/2/0/1 usb4 bus xHCI Host Controller
/0/100/1c/0/4 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
/0/100/1c.2 bridge Sunrise Point-H PCI Express Root Port #3
/0/100/1c.3 bridge Sunrise Point-H PCI Express Root Port #4
/0/100/1c.4 bridge Sunrise Point-H PCI Express Root Port #5
/0/100/1c.4/0 enp13s0 network Killer E2400 Gigabit Ethernet Controller
/0/100/1c.5 bridge Sunrise Point-H PCI Express Root Port #6
/0/100/1c.5/0 wlp14s0 network Wireless 8260
/0/100/1c.6 bridge Sunrise Point-H PCI Express Root Port #7
/0/100/1c.7 bridge Sunrise Point-H PCI Express Root Port #8
/0/100/1d bridge Sunrise Point-H PCI Express Root Port #9
/0/100/1f bridge Sunrise Point-H LPC Controller
/0/100/1f.2 memory Memory controller
/0/100/1f.3 multimedia Sunrise Point-H HD Audio
/0/100/1f.4 bus Sunrise Point-H SMBus
/0/1 scsi4 storage
/0/1/0.0.0 /dev/sda disk 480GB TOSHIBA-TR150
/0/1/0.0.0/1 /dev/sda1 volume 511MiB Windows FAT Laufwerk
/0/1/0.0.0/2 /dev/sda2 volume 438GiB EXT4-Laufwerk
/0/1/0.0.0/3 /dev/sda3 volume 8068MiB Linux swap Laufwerk
/1
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1726299/+subscriptions
Status: Confirmed => Incomplete
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1726299
Title:
Apple Thunderbolt 2 to FireWire adapter not working
Status in Linux:
Incomplete
Status in linux package in Ubuntu:
Confirmed
Bug description:
The adapter is connected through an Apple Thunderbolt 3 to Thunderbolt
2 adapter. Ubuntu seems not to recognize the Firewire adapter.
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 17.04
Release: 17.04
Codename: zesty
uname -r
4.10.0-19-generic
sudo lshw -short
H/W-Pfad Gerät Klasse Beschreibung
===============================================================
system Z170N-Gaming 5 (Default string)
/0 bus Z170N-Gaming 5
/0/0 memory 64KiB BIOS
/0/3d memory 16GiB Systemspeicher
/0/3d/0 memory 8GiB DIMM DDR4 Synchron 2133 MHz (0,5 ns)
/0/3d/1 memory Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME <EMAIL@ADDRESS>POT-Creatio
/0/3d/2 memory 8GiB DIMM DDR4 Synchron 2133 MHz (0,5 ns)
/0/3d/3 memory Project-Id-Version: lshwReport-Msgid-Bugs-To: FULL NAME <EMAIL@ADDRESS>POT-Creatio
/0/43 memory 128KiB L1 Cache
/0/44 memory 512KiB L2 Cache
/0/45 memory 3MiB L3 Cache
/0/46 processor Intel(R) Core(TM) i3-6100T CPU @ 3.20GHz
/0/100 bridge Skylake Host Bridge/DRAM Registers
/0/100/1 bridge Skylake PCIe Controller (x16)
/0/100/1/0 display Oland GL [FirePro W2100]
/0/100/1/0.1 multimedia Cape Verde/Pitcairn HDMI Audio [Radeon HD 7700/7800 Series]
/0/100/14 bus Sunrise Point-H USB 3.0 xHCI Controller
/0/100/14/0 usb1 bus xHCI Host Controller
/0/100/14/0/6 input USB Gaming Keyboard
/0/100/14/0/d communication Bluetooth-Schnittstelle
/0/100/14/1 usb2 bus xHCI Host Controller
/0/100/14/1/5 scsi6 storage Storage Media
/0/100/14/1/5/0.0.0 /dev/sdb disk 15GB Storage Media
/0/100/14/1/5/0.0.0/0 /dev/sdb disk 15GB
/0/100/14/1/5/0.0.0/0/2 /dev/sdb2 volume 15EiB Windows FAT Laufwerk
/0/100/16 communication Sunrise Point-H CSME HECI #1
/0/100/17 storage Sunrise Point-H SATA controller [AHCI mode]
/0/100/1b bridge Sunrise Point-H PCI Root Port #17
/0/100/1b.2 bridge Sunrise Point-H PCI Root Port #19
/0/100/1b.3 bridge Sunrise Point-H PCI Root Port #20
/0/100/1c bridge Sunrise Point-H PCI Express Root Port #1
/0/100/1c/0 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
/0/100/1c/0/0 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
/0/100/1c/0/1 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
/0/100/1c/0/2 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
/0/100/1c/0/2/0 bus DSL6540 USB 3.1 Controller [Alpine Ridge]
/0/100/1c/0/2/0/0 usb3 bus xHCI Host Controller
/0/100/1c/0/2/0/0/1 generic Thunderbolt 3 (USB-C) to Thunderbolt 2 Adapter
/0/100/1c/0/2/0/0/2 input USB Optical Mouse
/0/100/1c/0/2/0/1 usb4 bus xHCI Host Controller
/0/100/1c/0/4 bridge DSL6540 Thunderbolt 3 Bridge [Alpine Ridge 4C 2015]
/0/100/1c.2 bridge Sunrise Point-H PCI Express Root Port #3
/0/100/1c.3 bridge Sunrise Point-H PCI Express Root Port #4
/0/100/1c.4 bridge Sunrise Point-H PCI Express Root Port #5
/0/100/1c.4/0 enp13s0 network Killer E2400 Gigabit Ethernet Controller
/0/100/1c.5 bridge Sunrise Point-H PCI Express Root Port #6
/0/100/1c.5/0 wlp14s0 network Wireless 8260
/0/100/1c.6 bridge Sunrise Point-H PCI Express Root Port #7
/0/100/1c.7 bridge Sunrise Point-H PCI Express Root Port #8
/0/100/1d bridge Sunrise Point-H PCI Express Root Port #9
/0/100/1f bridge Sunrise Point-H LPC Controller
/0/100/1f.2 memory Memory controller
/0/100/1f.3 multimedia Sunrise Point-H HD Audio
/0/100/1f.4 bus Sunrise Point-H SMBus
/0/1 scsi4 storage
/0/1/0.0.0 /dev/sda disk 480GB TOSHIBA-TR150
/0/1/0.0.0/1 /dev/sda1 volume 511MiB Windows FAT Laufwerk
/0/1/0.0.0/2 /dev/sda2 volume 438GiB EXT4-Laufwerk
/0/1/0.0.0/3 /dev/sda3 volume 8068MiB Linux swap Laufwerk
/1
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1726299/+subscriptions
[Bug 2138824] Re: Questing update: v6.17.11 upstream stable release
Hi, we got reports from our freedesktop gitlab[1] that this commit:
- drm/amdgpu: attach tlb fence to the PTs update
Has root caused GPU hangs during video call or workloads like llama and
Steam. See [1] for details. The symptom is constant MES buffer full
message:
Jan 06 15:42:34 fw13 kernel: amdgpu 0000:c1:00.0: amdgpu: MES ring buffer is full.
Jan 06 15:42:36 fw13 kernel: amdgpu 0000:c1:00.0: amdgpu: MES ring buffer is full.
Jan 06 15:42:39 fw13 kernel: amdgpu 0000:c1:00.0: amdgpu: MES ring buffer is full.
The commit is f48f5bcb6e5a in Questing.
Unfortunately, I don't have a reliable way to reproduce it, and it seems
to take hours or even days to manifest, making it hard to file an SRU.
But if there happens to be any user report similar issue to you, the fix
is [2].
[1] https://gitlab.freedesktop.org/drm/amd/-/issues/4749
[2] https://lore.kernel.org/amd-gfx/20260316151636.1122226-1-alexander.deucher@amd.com/
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #4749
https://gitlab.freedesktop.org/drm/amd/-/issues/4749
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2138824
Title:
Questing update: v6.17.11 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Questing:
Fix Released
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v6.17.11 upstream stable release
from git://git.kernel.org/
can: kvaser_usb: leaf: Fix potential infinite loop in command parsers
can: gs_usb: gs_usb_xmit_callback(): fix handling of failed transmitted URBs
can: gs_usb: gs_usb_receive_bulk_callback(): check actual_length before accessing header
can: gs_usb: gs_usb_receive_bulk_callback(): check actual_length before accessing data
Bluetooth: btusb: mediatek: Fix kernel crash when releasing mtk iso interface
Bluetooth: hci_core: Fix triggering cmd_timer for HCI_OP_NOP
Bluetooth: hci_sock: Prevent race in socket write iter and sock bind
Bluetooth: hci_core: lookup hci_conn on RX path on protocol side
Bluetooth: SMP: Fix not generating mackey and ltk when repairing
veth: reduce XDP no_direct return section to fix race
drm/bridge: sii902x: Fix HDMI detection with DRM_BRIDGE_ATTACH_NO_CONNECTOR
net: phy: mxl-gpy: fix bogus error on USXGMII and integrated PHY
platform/x86: intel: punit_ipc: fix memory corruption
net: aquantia: Add missing descriptor cache invalidation on ATL2
net: phy: mxl-gpy: fix link properties on USXGMII and internal PHYs
net: lan966x: Fix the initialization of taprio
drm/xe: Fix conversion from clock ticks to milliseconds
net/mlx5e: Fix validation logic in rate limiting
team: Move team device type change at the end of team_port_add
net: sxgbe: fix potential NULL dereference in sxgbe_rx()
xsk: avoid overwriting skb fields for multi-buffer traffic
xsk: avoid data corruption on cq descriptor number
drm/amdgpu: fix cyan_skillfish2 gpu info fw handling
dma-direct: Fix missing sg_dma_len assignment in P2PDMA bus mappings
net: wwan: mhi: Keep modem name match with Foxconn T99W640
net: dsa: sja1105: fix SGMII linking at 10M or 100M but not passing traffic
eth: fbnic: Fix counter roll-over issue
net: atlantic: fix fragment overflow handling in RX path
net: mctp: unconditionally set skb->dev on dst output
net: fec: cancel perout_timer when PEROUT is disabled
net: fec: do not update PEROUT if it is enabled
net: fec: do not allow enabling PPS and PEROUT simultaneously
net: fec: do not register PPS event for PEROUT
iio: st_lsm6dsx: Fixed calibrated timestamp calculation
usb: gadget: renesas_usbf: Handle devm_pm_runtime_enable() errors
mailbox: mailbox-test: Fix debugfs_create_dir error checking
mailbox: mtk-cmdq: Refine DMA address handling for the command buffer
mailbox: pcc: don't zero error register
spi: spi-cadence-quadspi: Remove duplicate pm_runtime_put_autosuspend() call
spi: spi-cadence-quadspi: Enable pm runtime earlier to avoid imbalance
fs/namespace: fix reference leak in grab_requested_mnt_ns
afs: Fix delayed allocation of a cell's anonymous key
ovl: fail ovl_lock_rename_workdir() if either target is unhashed
riscv: dts: allwinner: d1: fix vlenb property
spi: tegra114: remove Kconfig dependency on TEGRA20_APB_DMA
spi: amlogic-spifc-a1: Handle devm_pm_runtime_enable() errors
spi: spi-nxp-fspi: Add OCT-DTR mode support
spi: nxp-fspi: Propagate fwnode in ACPI case as well
spi: bcm63xx: fix premature CS deassertion on RX-only transactions
afs: Fix uninit var in afs_alloc_anon_key()
timekeeping: Fix error code in tk_aux_sysfs_init()
Revert "perf/x86: Always store regs->ip in perf_callchain_kernel()"
iio: buffer-dma: support getting the DMA channel
iio: buffer-dmaengine: enable .get_dma_dev()
iio: buffer: support getting dma channel from the buffer
iio: humditiy: hdc3020: fix units for temperature and humidity measurement
iio: humditiy: hdc3020: fix units for thresholds and hysteresis
iio: imu: st_lsm6dsx: fix array size for st_lsm6dsx_settings fields
iio: pressure: bmp280: correct meas_time_us calculation
iio:common:ssp_sensors: Fix an error handling path ssp_probe()
iio: adc: stm32-dfsdm: fix st,adc-alt-channel property handling
iio: accel: bmc150: Fix irq assumption regression
iio: accel: fix ADXL355 startup race condition
iio: adc: ad4030: Fix _scale value for common-mode channels
iio: adc: ad7124: fix temperature channel
iio: adc: ad7280a: fix ad7280_store_balance_timer()
iio: adc: ad7380: fix SPI offload trigger rate
iio: adc: rtq6056: Correct the sign bit index
MIPS: mm: Prevent a TLB shutdown on initial uniquification
MIPS: mm: kmalloc tlb_vpn array to avoid stack overflow
virtio-net: avoid unnecessary checksum calculation on guest RX
vhost: rewind next_avail_head while discarding descriptors
tracing: Fix WARN_ON in tracing_buffers_mmap_close for split VMAs
ALSA: hda/cirrus fix cs420x MacPro 6,1 inverted jack detection
ALSA: usb-audio: Add DSD quirk for LEAK Stereo 230
arm64: dts: imx8dxl-ss-conn: swap interrupts number of eqos
arm64: dts: imx8dxl: Correct pcie-ep interrupt number
arm64: dts: imx8qm-mek: fix mux-controller select/enable-gpios polarity
ARM: dts: nxp: imx6ul: correct SAI3 interrupt line
atm/fore200e: Fix possible data race in fore200e_open()
Bluetooth: btusb: mediatek: Avoid btusb_mtk_claim_iso_intf() NULL deref
can: rcar_canfd: Fix CAN-FD mode as default
can: sja1000: fix max irq loop handling
can: sun4i_can: sun4i_can_interrupt(): fix max irq loop handling
ceph: fix crash in process_v2_sparse_read() for encrypted directories
counter: microchip-tcb-capture: Allow shared IRQ for multi-channel TCBs
dm-verity: fix unreliable memory allocation
drivers/usb/dwc3: fix PCI parent check
drm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup
smb: client: fix memory leak in cifs_construct_tcon()
thunderbolt: Add support for Intel Wildcat Lake
slimbus: ngd: Fix reference count leak in qcom_slim_ngd_notify_slaves
nvmem: layouts: fix nvmem_layout_bus_uevent
pmdomain: tegra: Add GENPD_FLAG_NO_STAY_ON flag
r8169: fix RTL8127 hang on suspend/shutdown
regulator: rtq2208: Correct buck group2 phase mapping logic
regulator: rtq2208: Correct LDO2 logic judgment bits
io_uring/net: ensure vectored buffer node import is tied to notification
firmware: stratix10-svc: fix bug in saving controller data
iommufd/driver: Fix counter initialization for counted_by annotation
mm/huge_memory: fix NULL pointer deference when splitting folio
mm/memfd: fix information leak in hugetlb folios
mmc: sdhci-of-dwcmshc: Promote the th1520 reset handling to ip level
mptcp: clear scheduled subflows on retransmit
mptcp: Initialise rcv_mss before calling tcp_send_active_reset() in mptcp_do_fastclose().
serial: 8250: Fix 8250_rsa symbol loop
serial: amba-pl011: prefer dma_mapping_error() over explicit address checking
most: usb: fix double free on late probe failure
usb: cdns3: Fix double resource release in cdns3_pci_probe
usb: gadget: f_eem: Fix memory leak in eem_unwrap
usb: renesas_usbhs: Fix synchronous external abort on unbind
usb: storage: Fix memory leak in USB bulk transport
USB: storage: Remove subclass and protocol overrides from Novatek quirk
usb: storage: sddr55: Reject out-of-bound new_pba
usb: typec: ucsi: psy: Set max current to zero when disconnected
usb: uas: fix urb unmapping issue when the uas device is remove during ongoing data transfer
usb: dwc3: pci: add support for the Intel Nova Lake -S
usb: dwc3: pci: Sort out the Intel device IDs
usb: dwc3: Fix race condition between concurrent dwc3_remove_requests() call paths
xhci: fix stale flag preventig URBs after link state error is cleared
xhci: dbgtty: Fix data corruption when transmitting data form DbC to host
xhci: dbgtty: fix device unregister
USB: serial: ftdi_sio: add support for u-blox EVK-M101
USB: serial: option: add support for Rolling RW101R-GL
drm: sti: fix device leaks at component probe
drm/i915/psr: Reject async flips when selective fetch is enabled
drm/xe/guc: Fix stack_depot usage
drm/amdgpu: attach tlb fence to the PTs update
drm/amd/amdgpu: reserve vm invalidation engine for uni_mes
drm/amd/display: Check NULL before accessing
drm/amd/display: Don't change brightness for disabled connectors
drm/amd/display: Increase EDID read retries
net: dsa: microchip: common: Fix checks on irq_find_mapping()
net: dsa: microchip: ptp: Fix checks on irq_find_mapping()
net: dsa: microchip: Don't free uninitialized ksz_irq
net: dsa: microchip: Free previously initialized ports on init failures
net: dsa: microchip: Fix symetry in ksz_ptp_msg_irq_{setup/free}()
libceph: fix potential use-after-free in have_mon_and_osd_map()
libceph: prevent potential out-of-bounds writes in handle_auth_session_key()
libceph: replace BUG_ON with bounds check for map->max_osd
mm: swap: remove duplicate nr_swap_pages decrement in get_swap_page_of_type()
usb: udc: Add trace event for usb_gadget_set_state
usb: gadget: udc: fix use-after-free in usb_gadget_state_work
Revert "ACPI: Suppress misleading SPCR console message when SPCR table is absent"
spi: cadence-quadspi: Fix cqspi_probe() error handling for runtime pm
Linux 6.17.11
UBUNTU: Upstream stable to v6.17.11
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2138824/+subscriptions
- drm/amdgpu: attach tlb fence to the PTs update
Has root caused GPU hangs during video call or workloads like llama and
Steam. See [1] for details. The symptom is constant MES buffer full
message:
Jan 06 15:42:34 fw13 kernel: amdgpu 0000:c1:00.0: amdgpu: MES ring buffer is full.
Jan 06 15:42:36 fw13 kernel: amdgpu 0000:c1:00.0: amdgpu: MES ring buffer is full.
Jan 06 15:42:39 fw13 kernel: amdgpu 0000:c1:00.0: amdgpu: MES ring buffer is full.
The commit is f48f5bcb6e5a in Questing.
Unfortunately, I don't have a reliable way to reproduce it, and it seems
to take hours or even days to manifest, making it hard to file an SRU.
But if there happens to be any user report similar issue to you, the fix
is [2].
[1] https://gitlab.freedesktop.org/drm/amd/-/issues/4749
[2] https://lore.kernel.org/amd-gfx/20260316151636.1122226-1-alexander.deucher@amd.com/
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #4749
https://gitlab.freedesktop.org/drm/amd/-/issues/4749
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2138824
Title:
Questing update: v6.17.11 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Questing:
Fix Released
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v6.17.11 upstream stable release
from git://git.kernel.org/
can: kvaser_usb: leaf: Fix potential infinite loop in command parsers
can: gs_usb: gs_usb_xmit_callback(): fix handling of failed transmitted URBs
can: gs_usb: gs_usb_receive_bulk_callback(): check actual_length before accessing header
can: gs_usb: gs_usb_receive_bulk_callback(): check actual_length before accessing data
Bluetooth: btusb: mediatek: Fix kernel crash when releasing mtk iso interface
Bluetooth: hci_core: Fix triggering cmd_timer for HCI_OP_NOP
Bluetooth: hci_sock: Prevent race in socket write iter and sock bind
Bluetooth: hci_core: lookup hci_conn on RX path on protocol side
Bluetooth: SMP: Fix not generating mackey and ltk when repairing
veth: reduce XDP no_direct return section to fix race
drm/bridge: sii902x: Fix HDMI detection with DRM_BRIDGE_ATTACH_NO_CONNECTOR
net: phy: mxl-gpy: fix bogus error on USXGMII and integrated PHY
platform/x86: intel: punit_ipc: fix memory corruption
net: aquantia: Add missing descriptor cache invalidation on ATL2
net: phy: mxl-gpy: fix link properties on USXGMII and internal PHYs
net: lan966x: Fix the initialization of taprio
drm/xe: Fix conversion from clock ticks to milliseconds
net/mlx5e: Fix validation logic in rate limiting
team: Move team device type change at the end of team_port_add
net: sxgbe: fix potential NULL dereference in sxgbe_rx()
xsk: avoid overwriting skb fields for multi-buffer traffic
xsk: avoid data corruption on cq descriptor number
drm/amdgpu: fix cyan_skillfish2 gpu info fw handling
dma-direct: Fix missing sg_dma_len assignment in P2PDMA bus mappings
net: wwan: mhi: Keep modem name match with Foxconn T99W640
net: dsa: sja1105: fix SGMII linking at 10M or 100M but not passing traffic
eth: fbnic: Fix counter roll-over issue
net: atlantic: fix fragment overflow handling in RX path
net: mctp: unconditionally set skb->dev on dst output
net: fec: cancel perout_timer when PEROUT is disabled
net: fec: do not update PEROUT if it is enabled
net: fec: do not allow enabling PPS and PEROUT simultaneously
net: fec: do not register PPS event for PEROUT
iio: st_lsm6dsx: Fixed calibrated timestamp calculation
usb: gadget: renesas_usbf: Handle devm_pm_runtime_enable() errors
mailbox: mailbox-test: Fix debugfs_create_dir error checking
mailbox: mtk-cmdq: Refine DMA address handling for the command buffer
mailbox: pcc: don't zero error register
spi: spi-cadence-quadspi: Remove duplicate pm_runtime_put_autosuspend() call
spi: spi-cadence-quadspi: Enable pm runtime earlier to avoid imbalance
fs/namespace: fix reference leak in grab_requested_mnt_ns
afs: Fix delayed allocation of a cell's anonymous key
ovl: fail ovl_lock_rename_workdir() if either target is unhashed
riscv: dts: allwinner: d1: fix vlenb property
spi: tegra114: remove Kconfig dependency on TEGRA20_APB_DMA
spi: amlogic-spifc-a1: Handle devm_pm_runtime_enable() errors
spi: spi-nxp-fspi: Add OCT-DTR mode support
spi: nxp-fspi: Propagate fwnode in ACPI case as well
spi: bcm63xx: fix premature CS deassertion on RX-only transactions
afs: Fix uninit var in afs_alloc_anon_key()
timekeeping: Fix error code in tk_aux_sysfs_init()
Revert "perf/x86: Always store regs->ip in perf_callchain_kernel()"
iio: buffer-dma: support getting the DMA channel
iio: buffer-dmaengine: enable .get_dma_dev()
iio: buffer: support getting dma channel from the buffer
iio: humditiy: hdc3020: fix units for temperature and humidity measurement
iio: humditiy: hdc3020: fix units for thresholds and hysteresis
iio: imu: st_lsm6dsx: fix array size for st_lsm6dsx_settings fields
iio: pressure: bmp280: correct meas_time_us calculation
iio:common:ssp_sensors: Fix an error handling path ssp_probe()
iio: adc: stm32-dfsdm: fix st,adc-alt-channel property handling
iio: accel: bmc150: Fix irq assumption regression
iio: accel: fix ADXL355 startup race condition
iio: adc: ad4030: Fix _scale value for common-mode channels
iio: adc: ad7124: fix temperature channel
iio: adc: ad7280a: fix ad7280_store_balance_timer()
iio: adc: ad7380: fix SPI offload trigger rate
iio: adc: rtq6056: Correct the sign bit index
MIPS: mm: Prevent a TLB shutdown on initial uniquification
MIPS: mm: kmalloc tlb_vpn array to avoid stack overflow
virtio-net: avoid unnecessary checksum calculation on guest RX
vhost: rewind next_avail_head while discarding descriptors
tracing: Fix WARN_ON in tracing_buffers_mmap_close for split VMAs
ALSA: hda/cirrus fix cs420x MacPro 6,1 inverted jack detection
ALSA: usb-audio: Add DSD quirk for LEAK Stereo 230
arm64: dts: imx8dxl-ss-conn: swap interrupts number of eqos
arm64: dts: imx8dxl: Correct pcie-ep interrupt number
arm64: dts: imx8qm-mek: fix mux-controller select/enable-gpios polarity
ARM: dts: nxp: imx6ul: correct SAI3 interrupt line
atm/fore200e: Fix possible data race in fore200e_open()
Bluetooth: btusb: mediatek: Avoid btusb_mtk_claim_iso_intf() NULL deref
can: rcar_canfd: Fix CAN-FD mode as default
can: sja1000: fix max irq loop handling
can: sun4i_can: sun4i_can_interrupt(): fix max irq loop handling
ceph: fix crash in process_v2_sparse_read() for encrypted directories
counter: microchip-tcb-capture: Allow shared IRQ for multi-channel TCBs
dm-verity: fix unreliable memory allocation
drivers/usb/dwc3: fix PCI parent check
drm, fbcon, vga_switcheroo: Avoid race condition in fbcon setup
smb: client: fix memory leak in cifs_construct_tcon()
thunderbolt: Add support for Intel Wildcat Lake
slimbus: ngd: Fix reference count leak in qcom_slim_ngd_notify_slaves
nvmem: layouts: fix nvmem_layout_bus_uevent
pmdomain: tegra: Add GENPD_FLAG_NO_STAY_ON flag
r8169: fix RTL8127 hang on suspend/shutdown
regulator: rtq2208: Correct buck group2 phase mapping logic
regulator: rtq2208: Correct LDO2 logic judgment bits
io_uring/net: ensure vectored buffer node import is tied to notification
firmware: stratix10-svc: fix bug in saving controller data
iommufd/driver: Fix counter initialization for counted_by annotation
mm/huge_memory: fix NULL pointer deference when splitting folio
mm/memfd: fix information leak in hugetlb folios
mmc: sdhci-of-dwcmshc: Promote the th1520 reset handling to ip level
mptcp: clear scheduled subflows on retransmit
mptcp: Initialise rcv_mss before calling tcp_send_active_reset() in mptcp_do_fastclose().
serial: 8250: Fix 8250_rsa symbol loop
serial: amba-pl011: prefer dma_mapping_error() over explicit address checking
most: usb: fix double free on late probe failure
usb: cdns3: Fix double resource release in cdns3_pci_probe
usb: gadget: f_eem: Fix memory leak in eem_unwrap
usb: renesas_usbhs: Fix synchronous external abort on unbind
usb: storage: Fix memory leak in USB bulk transport
USB: storage: Remove subclass and protocol overrides from Novatek quirk
usb: storage: sddr55: Reject out-of-bound new_pba
usb: typec: ucsi: psy: Set max current to zero when disconnected
usb: uas: fix urb unmapping issue when the uas device is remove during ongoing data transfer
usb: dwc3: pci: add support for the Intel Nova Lake -S
usb: dwc3: pci: Sort out the Intel device IDs
usb: dwc3: Fix race condition between concurrent dwc3_remove_requests() call paths
xhci: fix stale flag preventig URBs after link state error is cleared
xhci: dbgtty: Fix data corruption when transmitting data form DbC to host
xhci: dbgtty: fix device unregister
USB: serial: ftdi_sio: add support for u-blox EVK-M101
USB: serial: option: add support for Rolling RW101R-GL
drm: sti: fix device leaks at component probe
drm/i915/psr: Reject async flips when selective fetch is enabled
drm/xe/guc: Fix stack_depot usage
drm/amdgpu: attach tlb fence to the PTs update
drm/amd/amdgpu: reserve vm invalidation engine for uni_mes
drm/amd/display: Check NULL before accessing
drm/amd/display: Don't change brightness for disabled connectors
drm/amd/display: Increase EDID read retries
net: dsa: microchip: common: Fix checks on irq_find_mapping()
net: dsa: microchip: ptp: Fix checks on irq_find_mapping()
net: dsa: microchip: Don't free uninitialized ksz_irq
net: dsa: microchip: Free previously initialized ports on init failures
net: dsa: microchip: Fix symetry in ksz_ptp_msg_irq_{setup/free}()
libceph: fix potential use-after-free in have_mon_and_osd_map()
libceph: prevent potential out-of-bounds writes in handle_auth_session_key()
libceph: replace BUG_ON with bounds check for map->max_osd
mm: swap: remove duplicate nr_swap_pages decrement in get_swap_page_of_type()
usb: udc: Add trace event for usb_gadget_set_state
usb: gadget: udc: fix use-after-free in usb_gadget_state_work
Revert "ACPI: Suppress misleading SPCR console message when SPCR table is absent"
spi: cadence-quadspi: Fix cqspi_probe() error handling for runtime pm
Linux 6.17.11
UBUNTU: Upstream stable to v6.17.11
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2138824/+subscriptions
[Bug 2144584] Re: Multiple PM Regressions on ASUS Z790/RTX 4070 Ti: Suspend freeze, UCSI (INT3515) IRQ failure, and Display recovery hang
Status changed to 'Confirmed' because the bug affects multiple users.
** 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/2144584
Title:
Multiple PM Regressions on ASUS Z790/RTX 4070 Ti: Suspend freeze, UCSI
(INT3515) IRQ failure, and Display recovery hang
Status in linux package in Ubuntu:
Confirmed
Bug description:
SUMMARY: Hard freeze on Suspend, DP link loss after monitor power
cycle, and non-functional USB-C (INT3515 IRQ error) on ASUS Z790 + RTX
4070 Ti and display recovery failure
Environment:
OS: Ubuntu 26.04 "Resolute Raccoon" (Development Branch)
Kernel: 6.19.0-9-generic
Motherboard: ASUS ROG MAXIMUS Z790 HERO (BIOS 3001)
GPU: NVIDIA GeForce RTX 4070 Ti (Driver: 580.126.09)
Secure Boot: Enabled (Kernel Lockdown active)
Symptoms:
Hard Lockup: System freezes instantly when attempting to Suspend
or Hibernate. Requires physical hard reset.
Display Recovery Failure: If the monitor is manually turned OFF
and back ON (or switched to another input), the screen remains black.
SSH access remains functional, confirming a GPU/Driver hang rather
than a kernel panic.
USB-C Failure: All USB Type-C ports are non-functional in Ubuntu.
UI Regression: The 'Suspend' option is often missing or
unresponsive in the GNOME power menu.
Technical Root Causes Found:
UCSI / IRQ Conflict: The kernel log shows a critical failure in the serial bus driver:
Serial bus multi instantiate pseudo device driver INT3515:00: error -ENXIO: IRQ index 1 not found.
This appears to be the root cause, as the UCSI (USB Type-C Connector System Software Interface) is tied to the system's power state transitions.
EDID Mismatch: While the monitor is active, cat
/sys/class/drm/card1-DP-1/edid returns 0 bytes. However, valid EDID
data (384 bytes) was found on card1-DP-3. This suggests a mapping
regression between physical ports and logical DRM outputs.
Lockdown Interference: Kernel Lockdown restricts hibernation, but
the system fails to handle this restriction gracefully, leading to a
freeze instead of a denied request.
Evidence of Regression:
Dual-Boot Verification: All hardware (USB-C ports, Suspend/Resume,
DisplayPort link) works perfectly on Windows on the same machine. This
confirms the hardware is functional and the issue is strictly a Linux
kernel/driver regression.
NVIDIA Tooling Failure: nvidia-settings is non-functional under
Wayland/Kernel 6.19, returning multiple "Bad handle" errors,
preventing standard diagnostic procedures.
Steps to Reproduce:
Boot into Ubuntu with Secure Boot active.
Turn the monitor OFF and then ON via the physical power button
(causes Black Screen).
OR attempt to Suspend via terminal/UI (causes Hard Freeze).
Attached Logs:
nvidia-bug-report.log.gz (Detailed GPU/Driver state)
acpidump.txt (ACPI tables for ASUS Z790)
/proc/interrupts (Showing the IRQ 1 conflict)
Scenario A: Immediate Hard Freeze (Suspend/Hibernate)
Ensure Secure Boot is enabled in BIOS (Kernel Lockdown active).
Attempt to trigger a power state transition by running:
sudo systemctl suspend (or use the GNOME Power Menu).
Actual Result: The system freezes instantly. No disk activity, no
keyboard response (Caps Lock doesn't toggle). A hard reset is
required.
Expected Result: The system should enter a low-power state or
gracefully deny the request if Lockdown prevents it.
Scenario B: Permanent Black Screen (Display Link Loss)
Boot into a Wayland session with the monitor connected via
DisplayPort.
Turn the monitor OFF using its physical power button.
Wait 10 seconds and turn the monitor ON.
Actual Result: The screen remains black. No signal is detected by
the monitor.
Verification via SSH: From a remote machine, run nvidia-smi. The
GPU is still reported as "On" and processes are running, but the
display link is broken.
Expected Result: The monitor should re-initialize and show the
desktop immediately.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144584/+subscriptions
** 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/2144584
Title:
Multiple PM Regressions on ASUS Z790/RTX 4070 Ti: Suspend freeze, UCSI
(INT3515) IRQ failure, and Display recovery hang
Status in linux package in Ubuntu:
Confirmed
Bug description:
SUMMARY: Hard freeze on Suspend, DP link loss after monitor power
cycle, and non-functional USB-C (INT3515 IRQ error) on ASUS Z790 + RTX
4070 Ti and display recovery failure
Environment:
OS: Ubuntu 26.04 "Resolute Raccoon" (Development Branch)
Kernel: 6.19.0-9-generic
Motherboard: ASUS ROG MAXIMUS Z790 HERO (BIOS 3001)
GPU: NVIDIA GeForce RTX 4070 Ti (Driver: 580.126.09)
Secure Boot: Enabled (Kernel Lockdown active)
Symptoms:
Hard Lockup: System freezes instantly when attempting to Suspend
or Hibernate. Requires physical hard reset.
Display Recovery Failure: If the monitor is manually turned OFF
and back ON (or switched to another input), the screen remains black.
SSH access remains functional, confirming a GPU/Driver hang rather
than a kernel panic.
USB-C Failure: All USB Type-C ports are non-functional in Ubuntu.
UI Regression: The 'Suspend' option is often missing or
unresponsive in the GNOME power menu.
Technical Root Causes Found:
UCSI / IRQ Conflict: The kernel log shows a critical failure in the serial bus driver:
Serial bus multi instantiate pseudo device driver INT3515:00: error -ENXIO: IRQ index 1 not found.
This appears to be the root cause, as the UCSI (USB Type-C Connector System Software Interface) is tied to the system's power state transitions.
EDID Mismatch: While the monitor is active, cat
/sys/class/drm/card1-DP-1/edid returns 0 bytes. However, valid EDID
data (384 bytes) was found on card1-DP-3. This suggests a mapping
regression between physical ports and logical DRM outputs.
Lockdown Interference: Kernel Lockdown restricts hibernation, but
the system fails to handle this restriction gracefully, leading to a
freeze instead of a denied request.
Evidence of Regression:
Dual-Boot Verification: All hardware (USB-C ports, Suspend/Resume,
DisplayPort link) works perfectly on Windows on the same machine. This
confirms the hardware is functional and the issue is strictly a Linux
kernel/driver regression.
NVIDIA Tooling Failure: nvidia-settings is non-functional under
Wayland/Kernel 6.19, returning multiple "Bad handle" errors,
preventing standard diagnostic procedures.
Steps to Reproduce:
Boot into Ubuntu with Secure Boot active.
Turn the monitor OFF and then ON via the physical power button
(causes Black Screen).
OR attempt to Suspend via terminal/UI (causes Hard Freeze).
Attached Logs:
nvidia-bug-report.log.gz (Detailed GPU/Driver state)
acpidump.txt (ACPI tables for ASUS Z790)
/proc/interrupts (Showing the IRQ 1 conflict)
Scenario A: Immediate Hard Freeze (Suspend/Hibernate)
Ensure Secure Boot is enabled in BIOS (Kernel Lockdown active).
Attempt to trigger a power state transition by running:
sudo systemctl suspend (or use the GNOME Power Menu).
Actual Result: The system freezes instantly. No disk activity, no
keyboard response (Caps Lock doesn't toggle). A hard reset is
required.
Expected Result: The system should enter a low-power state or
gracefully deny the request if Lockdown prevents it.
Scenario B: Permanent Black Screen (Display Link Loss)
Boot into a Wayland session with the monitor connected via
DisplayPort.
Turn the monitor OFF using its physical power button.
Wait 10 seconds and turn the monitor ON.
Actual Result: The screen remains black. No signal is detected by
the monitor.
Verification via SSH: From a remote machine, run nvidia-smi. The
GPU is still reported as "On" and processes are running, but the
display link is broken.
Expected Result: The monitor should re-initialize and show the
desktop immediately.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144584/+subscriptions
[Bug 2144602] Re: Ubuntu 26.04: Screen Freeze Caused by amdgpu Crash
Status changed to 'Confirmed' because the bug affects multiple users.
** 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/2144602
Title:
Ubuntu 26.04: Screen Freeze Caused by amdgpu Crash
Status in linux package in Ubuntu:
Confirmed
Bug description:
The screen freezes during both live and installed system boot when the
amdgpu GPU driver initializes.
As a workaround, using the nomodeset boot parameter or blacklisting
the amdgpu module resolves the freeze, though this results in a very
low resolution.
The dmesg output indicates a firmware loading issue:
[ 288.124542] amdgpu 0000:03:00.0: amdgpu: failed to load ucode SMC(0x32)
[ 288.124546] amdgpu 0000:03:00.0: amdgpu: psp gfx command LOAD_IP_FW(0x6) failed and response status is (0x0)
[ 288.124548] amdgpu 0000:03:00.0: amdgpu: PSP load smu failed!
[ 288.299894] amdgpu 0000:03:00.0: amdgpu: psp reg (0x16080) wait timed out, mask: 8000ffff, read: 30000 exp: 80000000
[ 288.299901] [drm:psp_v11_0_ring_destroy [amdgpu]] *ERROR* Fail to stop psp ring
[ 288.300320] amdgpu 0000:03:00.0: amdgpu: PSP firmware loading failed
[ 288.300326] amdgpu 0000:03:00.0: amdgpu: hw_init of IP block <psp> failed -22
[ 288.300329] amdgpu 0000:03:00.0: amdgpu: amdgpu_device_ip_init failed
[ 288.300332] amdgpu 0000:03:00.0: amdgpu: Fatal error during GPU init
[ 288.300335] amdgpu 0000:03:00.0: amdgpu: amdgpu: finishing device.
I've tried not only the linux-firmware package but also downloaded and
installed the very latest version (commit
57303edc4101c1003ec45e91652f281ebd2f41b2) from git.kernel.org without
success.
The issue also persists with the following mainline Ubuntu kernel:
linux-image-
unsigned-7.0.0-070000rc3-generic_7.0.0-070000rc3.202603090038_amd64.
I'm reporting this for Ubuntu 26.04, but Ubuntu 25.10 is also
affected. However, older releases are unaffected, everything works as
expected from 22.04 to 25.04.
Interestingly, I have a Gentoo running kernels 6.19 and 7.0-rc4, and
it works flawlessly. No firmware loading issues or any amdgpu-related
problems have been observed.
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/controlC0: lacyc3 2025 F.... wireplumber
/dev/snd/controlC1: lacyc3 2025 F.... wireplumber
/dev/snd/seq: lacyc3 2003 F.... pipewire
CasperMD5CheckResult: pass
Date: Mon Mar 16 21:29:38 2026
InstallationDate: Installed on 2026-03-14 (2 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20260313)
MachineType: ASUS All Series
ProcEnviron:
LANG=hu_HU.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.19.0-9-generic root=UUID=ccdc3ee1-a8b4-4af0-a947-a2c2749058c0 ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2015
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2702
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
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.:bvr2702:bd10/27/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuAll:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
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/2144602/+subscriptions
** 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/2144602
Title:
Ubuntu 26.04: Screen Freeze Caused by amdgpu Crash
Status in linux package in Ubuntu:
Confirmed
Bug description:
The screen freezes during both live and installed system boot when the
amdgpu GPU driver initializes.
As a workaround, using the nomodeset boot parameter or blacklisting
the amdgpu module resolves the freeze, though this results in a very
low resolution.
The dmesg output indicates a firmware loading issue:
[ 288.124542] amdgpu 0000:03:00.0: amdgpu: failed to load ucode SMC(0x32)
[ 288.124546] amdgpu 0000:03:00.0: amdgpu: psp gfx command LOAD_IP_FW(0x6) failed and response status is (0x0)
[ 288.124548] amdgpu 0000:03:00.0: amdgpu: PSP load smu failed!
[ 288.299894] amdgpu 0000:03:00.0: amdgpu: psp reg (0x16080) wait timed out, mask: 8000ffff, read: 30000 exp: 80000000
[ 288.299901] [drm:psp_v11_0_ring_destroy [amdgpu]] *ERROR* Fail to stop psp ring
[ 288.300320] amdgpu 0000:03:00.0: amdgpu: PSP firmware loading failed
[ 288.300326] amdgpu 0000:03:00.0: amdgpu: hw_init of IP block <psp> failed -22
[ 288.300329] amdgpu 0000:03:00.0: amdgpu: amdgpu_device_ip_init failed
[ 288.300332] amdgpu 0000:03:00.0: amdgpu: Fatal error during GPU init
[ 288.300335] amdgpu 0000:03:00.0: amdgpu: amdgpu: finishing device.
I've tried not only the linux-firmware package but also downloaded and
installed the very latest version (commit
57303edc4101c1003ec45e91652f281ebd2f41b2) from git.kernel.org without
success.
The issue also persists with the following mainline Ubuntu kernel:
linux-image-
unsigned-7.0.0-070000rc3-generic_7.0.0-070000rc3.202603090038_amd64.
I'm reporting this for Ubuntu 26.04, but Ubuntu 25.10 is also
affected. However, older releases are unaffected, everything works as
expected from 22.04 to 25.04.
Interestingly, I have a Gentoo running kernels 6.19 and 7.0-rc4, and
it works flawlessly. No firmware loading issues or any amdgpu-related
problems have been observed.
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/controlC0: lacyc3 2025 F.... wireplumber
/dev/snd/controlC1: lacyc3 2025 F.... wireplumber
/dev/snd/seq: lacyc3 2003 F.... pipewire
CasperMD5CheckResult: pass
Date: Mon Mar 16 21:29:38 2026
InstallationDate: Installed on 2026-03-14 (2 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20260313)
MachineType: ASUS All Series
ProcEnviron:
LANG=hu_HU.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.19.0-9-generic root=UUID=ccdc3ee1-a8b4-4af0-a947-a2c2749058c0 ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2015
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2702
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z97-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
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.:bvr2702:bd10/27/2015:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuAll:
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
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/2144602/+subscriptions
[Bug 2144953] Re: hangup while suspend
Status changed to 'Confirmed' because the bug affects multiple users.
** 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/2144953
Title:
hangup while suspend
Status in linux package in Ubuntu:
Confirmed
Bug description:
During resume kernel warnings and panic.
Thinkpad X1 Extreme Gen5
$ uname -a
Linux TP-X1X-G5 7.0.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 12 11:34:39 UTC 2026 x86_64 GNU/Linux
Old kernel (linux-6.17.0-14-generic) is working, 6.19 not.
root@TP-X1X-G5:/boot/efi/EFI/Linux# lspci -nnk |grep -A3 -i vga
00:02.0 VGA compatible controller [0300]: Intel Corporation Alder Lake-P GT2 [Iris Xe Graphics] [8086:46a6] (rev 0c)
Subsystem: Lenovo Device [17aa:22f8]
Kernel driver in use: i915
Kernel modules: i915, xe
--
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA103M [GeForce RTX 3080 Ti Mobile] [10de:2420] (rev a1)
Subsystem: Lenovo Device [17aa:22f8]
Kernel driver in use: nouveau
Kernel modules: nvidiafb, nouveau, nova_core
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-image-7.0.0-7-generic 7.0.0-7.7
ProcVersionSignature: Ubuntu 7.0.0-7.7-generic 7.0.0-rc3
Uname: Linux 7.0.0-7-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: hans 9372 F.... pipewire
hans 9386 F.... wireplumber
/dev/snd/controlC0: hans 9386 F.... wireplumber
/dev/snd/seq: hans 9372 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 19 22:21:54 2026
MachineType: LENOVO 21DE001EUS
ProcFB:
0 i915drmfb
1 nouveaudrmfb
ProcKernelCmdLine: root=/dev/mapper/cryptlinux rootfstype=btrfs rootflags=rw,noatime,compress=zstd:6,ssd,space_cache=v2,subvol=@ resume=/dev/mapper/cryptlinux resume_offset=20243660 sysrq_always_enabled=1 panic=100
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
SourcePackage: linux
UpgradeStatus: Upgraded to resolute on 2026-02-11 (36 days ago)
WifiSyslog:
dmi.bios.date: 12/09/2025
dmi.bios.release: 1.30
dmi.bios.vendor: LENOVO
dmi.bios.version: N3JET46W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21DE001EUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76528 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.15
dmi.modalias: dmi:bvnLENOVO:bvrN3JET46W(1.30):bd12/09/2025:br1.30:efr1.15:svnLENOVO:pn21DE001EUS:pvrThinkPadX1ExtremeGen5:rvnLENOVO:rn21DE001EUS:rvrSDK0T76528WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21DE_BU_Think_FM_ThinkPadX1ExtremeGen5:pfaThinkPadX1ExtremeGen5:
dmi.product.family: ThinkPad X1 Extreme Gen 5
dmi.product.name: 21DE001EUS
dmi.product.sku: LENOVO_MT_21DE_BU_Think_FM_ThinkPad X1 Extreme Gen 5
dmi.product.version: ThinkPad X1 Extreme Gen 5
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144953/+subscriptions
** 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/2144953
Title:
hangup while suspend
Status in linux package in Ubuntu:
Confirmed
Bug description:
During resume kernel warnings and panic.
Thinkpad X1 Extreme Gen5
$ uname -a
Linux TP-X1X-G5 7.0.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 12 11:34:39 UTC 2026 x86_64 GNU/Linux
Old kernel (linux-6.17.0-14-generic) is working, 6.19 not.
root@TP-X1X-G5:/boot/efi/EFI/Linux# lspci -nnk |grep -A3 -i vga
00:02.0 VGA compatible controller [0300]: Intel Corporation Alder Lake-P GT2 [Iris Xe Graphics] [8086:46a6] (rev 0c)
Subsystem: Lenovo Device [17aa:22f8]
Kernel driver in use: i915
Kernel modules: i915, xe
--
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA103M [GeForce RTX 3080 Ti Mobile] [10de:2420] (rev a1)
Subsystem: Lenovo Device [17aa:22f8]
Kernel driver in use: nouveau
Kernel modules: nvidiafb, nouveau, nova_core
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: linux-image-7.0.0-7-generic 7.0.0-7.7
ProcVersionSignature: Ubuntu 7.0.0-7.7-generic 7.0.0-rc3
Uname: Linux 7.0.0-7-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: hans 9372 F.... pipewire
hans 9386 F.... wireplumber
/dev/snd/controlC0: hans 9386 F.... wireplumber
/dev/snd/seq: hans 9372 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 19 22:21:54 2026
MachineType: LENOVO 21DE001EUS
ProcFB:
0 i915drmfb
1 nouveaudrmfb
ProcKernelCmdLine: root=/dev/mapper/cryptlinux rootfstype=btrfs rootflags=rw,noatime,compress=zstd:6,ssd,space_cache=v2,subvol=@ resume=/dev/mapper/cryptlinux resume_offset=20243660 sysrq_always_enabled=1 panic=100
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
SourcePackage: linux
UpgradeStatus: Upgraded to resolute on 2026-02-11 (36 days ago)
WifiSyslog:
dmi.bios.date: 12/09/2025
dmi.bios.release: 1.30
dmi.bios.vendor: LENOVO
dmi.bios.version: N3JET46W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21DE001EUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76528 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.15
dmi.modalias: dmi:bvnLENOVO:bvrN3JET46W(1.30):bd12/09/2025:br1.30:efr1.15:svnLENOVO:pn21DE001EUS:pvrThinkPadX1ExtremeGen5:rvnLENOVO:rn21DE001EUS:rvrSDK0T76528WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21DE_BU_Think_FM_ThinkPadX1ExtremeGen5:pfaThinkPadX1ExtremeGen5:
dmi.product.family: ThinkPad X1 Extreme Gen 5
dmi.product.name: 21DE001EUS
dmi.product.sku: LENOVO_MT_21DE_BU_Think_FM_ThinkPad X1 Extreme Gen 5
dmi.product.version: ThinkPad X1 Extreme Gen 5
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144953/+subscriptions
[Bug 2144957] Re: compatibly issue between 6.17.0-19-generic and ROCm 7.2.0
** 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/2144957
Title:
compatibly issue between 6.17.0-19-generic and ROCm 7.2.0
Status in linux package in Ubuntu:
New
Bug description:
After updating to kernel 6.17.0-19-generic, I faced issue in lunching
Ollama: failure in loading GPU driver. I'm running Ubuntu on Framework
desktop AMD Ryazen AI MAX 395 with ROCm 7.2.0.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-19-generic 6.17.0-19.19
ProcVersionSignature: Ubuntu 6.17.0-14.14-generic 6.17.9
Uname: Linux 6.17.0-14-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.17.0-14-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CasperMD5CheckResult: pass
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted
Date: Thu Mar 19 22:58:48 2026
InstallationDate: Installed on 2026-01-06 (72 days ago)
InstallationMedia: Ubuntu-Server 25.10 "Questing Quokka" - Release amd64 (20251007.1)
MachineType: Framework Desktop (AMD Ryzen AI Max 300 Series)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.17.0-14-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
dmi.bios.date: 11/19/2025
dmi.bios.release: 3.4
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.04
dmi.board.asset.tag: *
dmi.board.name: FRANMFCP06
dmi.board.vendor: Framework
dmi.board.version: A6
dmi.chassis.asset.tag: FRAMDACPA65332001Z
dmi.chassis.type: 35
dmi.chassis.vendor: Framework
dmi.chassis.version: A6
dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd11/19/2025:br3.4:svnFramework:pnDesktop(AMDRyzenAIMax300Series):pvrA6:rvnFramework:rnFRANMFCP06:rvrA6:cvnFramework:ct35:cvrA6:skuFRAMDACP06:
dmi.product.family: Desktop
dmi.product.name: Desktop (AMD Ryzen AI Max 300 Series)
dmi.product.sku: FRAMDACP06
dmi.product.version: A6
dmi.sys.vendor: Framework
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144957/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2144957
Title:
compatibly issue between 6.17.0-19-generic and ROCm 7.2.0
Status in linux package in Ubuntu:
New
Bug description:
After updating to kernel 6.17.0-19-generic, I faced issue in lunching
Ollama: failure in loading GPU driver. I'm running Ubuntu on Framework
desktop AMD Ryazen AI MAX 395 with ROCm 7.2.0.
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-19-generic 6.17.0-19.19
ProcVersionSignature: Ubuntu 6.17.0-14.14-generic 6.17.9
Uname: Linux 6.17.0-14-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version k6.17.0-14-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CasperMD5CheckResult: pass
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted
Date: Thu Mar 19 22:58:48 2026
InstallationDate: Installed on 2026-01-06 (72 days ago)
InstallationMedia: Ubuntu-Server 25.10 "Questing Quokka" - Release amd64 (20251007.1)
MachineType: Framework Desktop (AMD Ryzen AI Max 300 Series)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.17.0-14-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
dmi.bios.date: 11/19/2025
dmi.bios.release: 3.4
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.04
dmi.board.asset.tag: *
dmi.board.name: FRANMFCP06
dmi.board.vendor: Framework
dmi.board.version: A6
dmi.chassis.asset.tag: FRAMDACPA65332001Z
dmi.chassis.type: 35
dmi.chassis.vendor: Framework
dmi.chassis.version: A6
dmi.modalias: dmi:bvnINSYDECorp.:bvr03.04:bd11/19/2025:br3.4:svnFramework:pnDesktop(AMDRyzenAIMax300Series):pvrA6:rvnFramework:rnFRANMFCP06:rvrA6:cvnFramework:ct35:cvrA6:skuFRAMDACP06:
dmi.product.family: Desktop
dmi.product.name: Desktop (AMD Ryzen AI Max 300 Series)
dmi.product.sku: FRAMDACP06
dmi.product.version: A6
dmi.sys.vendor: Framework
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144957/+subscriptions
[Bug 2144854] Re: Charging, Samsung Galaxy Book4 (NP750XGK). regression?
** 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/2144854
Title:
Charging, Samsung Galaxy Book4 (NP750XGK). regression?
Status in linux package in Ubuntu:
New
Bug description:
================================================================================
CANONICAL BUG REPORT
USB-C Power Delivery Regression on Samsung Galaxy Book4 (NP750XGK)
Kernel 6.17.0-19-generic / Ubuntu 25.10 (Questing)
================================================================================
Date: 2026-03-18
Reporter: Dr. Brian King
System: Samsung Galaxy Book4, NP750XGK-KS2US
OS: Ubuntu 25.10 (Questing)
Kernel: 6.17.0-19-generic
Last known good kernel: 6.17.0-12-generic
--------------------------------------------------------------------------------
EXECUTIVE SUMMARY
--------------------------------------------------------------------------------
USB-C Power Delivery (PD) negotiation is severely degraded under kernel
6.17.0-19-generic on the Samsung Galaxy Book4 (NP750XGK). The system charges
at approximately 27W instead of the rated 45W minimum, and the UCSI power
supply sysfs node reports VOLTAGE_NOW=0, VOLTAGE_MAX=0, and CURRENT_MAX=0.
The UCSI command/response cycle returns all zeros via debugfs. The regression
was introduced between kernel 6.17.0-12 and 6.17.0-19.
Extensive investigation revealed two separate bugs contributing to this
regression, both with identified patches. A third deeper issue — the UCSI
command/response cycle returning all zeros — remains unresolved and is the
primary blocker for full PD negotiation.
--------------------------------------------------------------------------------
HARDWARE
--------------------------------------------------------------------------------
System manufacturer: SAMSUNG ELECTRONICS CO., LTD.
Product name: 750XGK
Product family: Galaxy Book4
System version: P02CFP
BIOS: P02CFP.015.240409.HQ (04/09/2024)
Battery: SAMSUNG Electronics SR Real Battery
Design capacity: 3530 mAh / 54 Wh
Chemistry: Li-ion, Nominal voltage: 15.4V
Charger: Samsung OEM USB-C (65W rated, 20V/3.25A)
Charging port: USB-C (UCSI, PD and PPS capable)
--------------------------------------------------------------------------------
KERNEL VERSIONS
--------------------------------------------------------------------------------
Affected: 6.17.0-19-generic (installed 2026-03-16)
Not affected: 6.17.0-12-generic (removed 2026-03-18, no longer available)
--------------------------------------------------------------------------------
SYMPTOMS
--------------------------------------------------------------------------------
1. USB-C charging voltage negotiates to ~15.8V instead of 20V
- Actual power delivery: ~27W (observed: 1.7A x 15.8V)
- Expected power delivery: 45W minimum (20V x 2.25A)
2. UCSI power supply sysfs reports zeroed voltage data:
POWER_SUPPLY_VOLTAGE_MAX=0
POWER_SUPPLY_VOLTAGE_MIN=0
POWER_SUPPLY_VOLTAGE_NOW=0
POWER_SUPPLY_CURRENT_MAX=0
(Despite POWER_SUPPLY_CURRENT_NOW=2250000 and USB_TYPE=C [PD] PD_PPS)
3. UCSI debugfs interface returns all zeros:
/sys/kernel/debug/usb/ucsi/USBC000:00/vbus_voltage = 0 mV
/sys/kernel/debug/usb/ucsi/USBC000:00/avg_current = 0 mA
/sys/kernel/debug/usb/ucsi/USBC000:00/response = 0x0000...0000
4. Zero UCSI/typec messages in dmesg at boot — PD negotiation events are
not logged, indicating silent failure in the UCSI initialization path.
5. Slower-than-expected charging when system is powered off, suggesting
the embedded controller (EC) charging profile is not properly initialized
during shutdown/handoff.
6. samsung-galaxybook platform driver logs repeated unknown ACPI
notification events:
samsung-galaxybook SAM0430:00: unknown ACPI notification event: 0x71
(firing approximately every 60-90 seconds)
--------------------------------------------------------------------------------
ROOT CAUSE ANALYSIS
--------------------------------------------------------------------------------
The Samsung Galaxy Book4 uses a non-standard UCSI implementation that routes
all communication through the Embedded Controller (EC) via ACPI _DSM methods
(UUID: 6f8398c2-7ca4-11e4-ad36-631042b5008f). The DSDT defines a UBTC device
at \_SB.UBTC with:
- A shared memory region at physical address 0x40238E18
- DSM Case 1: OPM write (kernel -> EC via MGO registers)
- DSM Case 2: OPM read (EC -> kernel via MGI/CCI registers)
- A UCEV method that reads EC state and fires Notify(UBTC, 0x80)
Three issues were identified:
ISSUE 1: Missing Samsung DMI quirk in ucsi_acpi.c
The ucsi_acpi driver contains a quirk table for LG gram laptops
(ucsi_gram_ops) that handles bogus PDOS_CHANGE events after GET_PDOS.
Samsung Galaxy Book4 uses the identical EC-routed UCSI architecture and
exhibits the same bogus event behavior, but is absent from the quirk table.
Without ucsi_gram_ops, spurious POWER_LEVEL_CHANGE | PDOS_CHANGE events
after GET_PDOS cause the kernel to re-trigger connector status checks that
interfere with PDO data population.
FILE: drivers/usb/typec/ucsi/ucsi_acpi.c
FIX: Add Samsung Galaxy Book4 to ucsi_acpi_quirks[] DMI table
ISSUE 2: Unhandled ACPI notification event 0x71 in samsung-galaxybook driver
The samsung-galaxybook platform driver (SAM0430) handles ACPI notification
events 0x61, 0x6c, 0x6d, and 0x70, but does not handle 0x71. This event
fires repeatedly (~every 60-90 seconds) and appears to be a USB-C PD power
state change notification. When unhandled, the UCEV ACPI method (which
triggers UCSI connector status refresh) is never called in response to
charger state changes.
FILE: drivers/platform/x86/samsung-galaxybook.c
FIX: Add case for 0x71 that calls acpi_evaluate_object(UCEV)
ISSUE 3: UCSI command/response cycle returning all zeros (PRIMARY BUG)
Even with the above patches applied, the UCSI debugfs interface returns
all zeros for vbus_voltage, avg_current, and response. GET_CONNECTOR_STATUS
commands return no data. This indicates the DSM read path (Case 2) is not
functioning correctly — the EC response is either not being requested or
not being read back at the right time. This is the primary regression
between -12 and -19 and the root cause of src_pdos never being populated.
The likely location is in how ucsi_acpi_poll_cci() vs ucsi_acpi_read_cci()
are called, or a timing change in how the driver waits for EC responses
via the DSM interface. Without the -12 kernel source for comparison,
the exact commit introducing this regression could not be identified.
--------------------------------------------------------------------------------
PATCHES DEVELOPED
--------------------------------------------------------------------------------
PATCH 1: drivers/usb/typec/ucsi/ucsi_acpi.c
Add Samsung Galaxy Book4 to ucsi_acpi_quirks DMI table.
--- a/drivers/usb/typec/ucsi/ucsi_acpi.c
+++ b/drivers/usb/typec/ucsi/ucsi_acpi.c
@@ -146,6 +146,14 @@ static const struct dmi_system_id ucsi_acpi_quirks[] = {
.driver_data = (void *)&ucsi_gram_ops,
},
+ {
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "SAMSUNG ELECTRONICS CO., LTD."),
+ DMI_MATCH(DMI_PRODUCT_FAMILY, "Galaxy Book4"),
+ DMI_MATCH(DMI_PRODUCT_NAME, "750XGK"),
+ },
+ .driver_data = (void *)&ucsi_gram_ops,
+ },
{ }
};
PATCH 2: drivers/platform/x86/samsung-galaxybook.c
Add handling for ACPI notification event 0x71 (USB-C PD state change).
--- a/drivers/platform/x86/samsung-galaxybook.c
+++ b/drivers/platform/x86/samsung-galaxybook.c
@@ -199,6 +199,7 @@ static const struct dmi_system_id ucsi_acpi_quirks[] = {
#define GB_ACPI_NOTIFY_HOTKEY_PERFORMANCE_MODE 0x70
+#define GB_ACPI_NOTIFY_USB_PD_STATE_CHANGED 0x71
@@ -1256,6 +1256,13 @@ static void galaxybook_acpi_notify(...)
case GB_ACPI_NOTIFY_HOTKEY_PERFORMANCE_MODE:
if (galaxybook->has_performance_mode)
platform_profile_cycle();
break;
+ case GB_ACPI_NOTIFY_USB_PD_STATE_CHANGED:
+ {
+ acpi_handle ubtc_handle;
+ if (ACPI_SUCCESS(acpi_get_handle(NULL, "\\_SB.UBTC", &ubtc_handle)))
+ acpi_evaluate_object(ubtc_handle, "UCEV", NULL, NULL);
+ break;
+ }
default:
--------------------------------------------------------------------------------
WORKAROUND
--------------------------------------------------------------------------------
Reloading the ucsi_acpi module after boot partially restores charging:
sudo modprobe -r ucsi_acpi && sudo modprobe ucsi_acpi
This brings charging to approximately 27W. It does not fully restore rated
wattage but is better than the initial degraded state. A systemd oneshot
service can automate this at boot:
[Unit]
Description=Reset UCSI ACPI for USB-C PD negotiation
After=multi-user.target
[Service]
Type=oneshot
ExecStart=/bin/sh -c 'modprobe -r ucsi_acpi && modprobe ucsi_acpi'
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target
--------------------------------------------------------------------------------
KEY SYSFS DATA
--------------------------------------------------------------------------------
BAT1 uevent (while charging):
POWER_SUPPLY_STATUS=Charging
POWER_SUPPLY_VOLTAGE_NOW=16316000 (16.3V — should be ~20V under PD)
POWER_SUPPLY_CURRENT_NOW=1668000 (1.67A)
Calculated actual wattage: ~27.2W
Expected wattage: 45W minimum
ucsi-source-psy-USBC000:002 uevent:
POWER_SUPPLY_CHARGE_TYPE=Standard (should be Fast)
POWER_SUPPLY_ONLINE=1
POWER_SUPPLY_VOLTAGE_MAX=0 (BUG)
POWER_SUPPLY_VOLTAGE_MIN=0 (BUG)
POWER_SUPPLY_VOLTAGE_NOW=0 (BUG)
POWER_SUPPLY_CURRENT_MAX=0 (BUG)
POWER_SUPPLY_CURRENT_NOW=2250000 (correct — 2.25A rated)
POWER_SUPPLY_USB_TYPE=C [PD] PD_PPS (correct — PD/PPS supported)
Power supply nodes present:
ADP1 BAT1 ucsi-source-psy-USBC000:001 ucsi-source-psy-USBC000:002
UCSI debugfs (USBC000:00):
vbus_voltage = 0 mV
avg_current = 0 mA
response = 0x00000000000000000000000000000000
--------------------------------------------------------------------------------
DSDT ANALYSIS
--------------------------------------------------------------------------------
The UCSI device (\_SB.UBTC) uses HID USBC000 / CID PNP0CA0 and communicates
via a Samsung-specific _DSM (UUID 6f8398c2-7ca4-11e4-ad36-631042b5008f):
- Case 0: Capabilities (returns 0x0F)
- Case 1: OPM write — copies MGO/CTL registers to EC, sets UCIT=1
- Case 2: OPM read — copies MGI/CCI registers from EC to shared memory
The UCEV method reads EC state (MGI/CCI) and fires Notify(UBTC, 0x80),
which is the standard mechanism to trigger UCSI connector status refresh.
This method is currently never called because the 0x71 notification that
should trigger it is unhandled.
--------------------------------------------------------------------------------
SUGGESTED BISECT RANGE
--------------------------------------------------------------------------------
Good: 6.17.0-12-generic (Ubuntu package: 6.17.0-12.12)
Bad: 6.17.0-19-generic (Ubuntu package: 6.17.0-19.19)
Primary suspects:
drivers/usb/typec/ucsi/ucsi_acpi.c — DSM read/write sequencing
drivers/usb/typec/ucsi/ucsi.c — poll_cci vs read_cci usage
drivers/platform/x86/samsung-galaxybook.c — missing 0x71 handler
Upstream maintainer:
Heikki Krogerus <heikki.krogerus@linux.intel.com> (UCSI)
Joshua Grisham <josh@joshuagrisham.com> (samsung-galaxybook)
--------------------------------------------------------------------------------
HOW TO REPRODUCE
--------------------------------------------------------------------------------
1. Install kernel 6.17.0-19-generic on Ubuntu 25.10
2. Boot Samsung Galaxy Book4 NP750XGK with Samsung OEM 65W USB-C charger
3. Check:
cat /sys/class/power_supply/ucsi-source-psy-USBC000:002/voltage_now
# Returns 0 (expected: ~20000000)
cat /sys/kernel/debug/usb/ucsi/USBC000:00/response
# Returns all zeros (expected: connector status data)
4. Observe charging voltage ~15.8V instead of 20V via:
cat /sys/class/power_supply/BAT1/voltage_now
cat /sys/class/power_supply/BAT1/current_now
# Multiply: should be ~45W, actual ~27W
--------------------------------------------------------------------------------
ADDITIONAL CONTEXT
--------------------------------------------------------------------------------
- TLP 1.8.0 installed but charge thresholds unconfigured (not the cause)
- Battery health: 91.2% capacity at 258 cycles (not a factor)
- Secure Boot: enabled (patched modules require MOK signing)
- The samsung-galaxybook driver was new/significantly updated for this
hardware class — interactions between it and ucsi_acpi may not have
been fully tested on kernel -19
- Reporter is available to test patches, provide additional diagnostics,
or run bisect builds
--------------------------------------------------------------------------------
FILING INSTRUCTIONS
--------------------------------------------------------------------------------
Ubuntu Launchpad: ubuntu-bug linux (auto-collects system info)
Tag: regression, usb-c, charging, ucsi, samsung
Kernel bugzilla: https://bugzilla.kernel.org
Product: Drivers / Component: USB
CC: heikki.krogerus@linux.intel.com
CC: josh@joshuagrisham.com
================================================================================
END OF REPORT
================================================================================
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-19-generic 6.17.0-19.19
ProcVersionSignature: Ubuntu 6.17.0-19.19-generic 6.17.13
Uname: Linux 6.17.0-19-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: brian 3875 F.... pipewire
brian 3897 F.... wireplumber
/dev/snd/seq: brian 3875 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 18 23:03:53 2026
InstallationDate: Installed on 2025-05-23 (299 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 750XGK
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-19-generic root=UUID=67cdc73c-425b-47f6-a88c-636207de0da4 ro quiet splash lockdown=none resume=UUID=67cdc73c-425b-47f6-a88c-636207de0da4 resume_offset=103645184 i915.enable_dc=0 i915.enable_psr=0 i915.enable_fbc=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/09/2024
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: P02CFP.015.240409.HQ
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP750XGK-KS2US
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SAMSUNG_SW_REVISION_12345+10.0.22631
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP02CFP.015.240409.HQ:bd04/09/2024:br5.27:svnSAMSUNGELECTRONICSCO.,LTD.:pn750XGK:pvrP02CFP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP750XGK-KS2US:rvrSAMSUNG_SW_REVISION_12345+10.0.22631:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-RPLU-PCFP:
dmi.product.family: Galaxy Book4
dmi.product.name: 750XGK
dmi.product.sku: SCAI-A5A5-A5A5-RPLU-PCFP
dmi.product.version: P02CFP
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144854/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2144854
Title:
Charging, Samsung Galaxy Book4 (NP750XGK). regression?
Status in linux package in Ubuntu:
New
Bug description:
================================================================================
CANONICAL BUG REPORT
USB-C Power Delivery Regression on Samsung Galaxy Book4 (NP750XGK)
Kernel 6.17.0-19-generic / Ubuntu 25.10 (Questing)
================================================================================
Date: 2026-03-18
Reporter: Dr. Brian King
System: Samsung Galaxy Book4, NP750XGK-KS2US
OS: Ubuntu 25.10 (Questing)
Kernel: 6.17.0-19-generic
Last known good kernel: 6.17.0-12-generic
--------------------------------------------------------------------------------
EXECUTIVE SUMMARY
--------------------------------------------------------------------------------
USB-C Power Delivery (PD) negotiation is severely degraded under kernel
6.17.0-19-generic on the Samsung Galaxy Book4 (NP750XGK). The system charges
at approximately 27W instead of the rated 45W minimum, and the UCSI power
supply sysfs node reports VOLTAGE_NOW=0, VOLTAGE_MAX=0, and CURRENT_MAX=0.
The UCSI command/response cycle returns all zeros via debugfs. The regression
was introduced between kernel 6.17.0-12 and 6.17.0-19.
Extensive investigation revealed two separate bugs contributing to this
regression, both with identified patches. A third deeper issue — the UCSI
command/response cycle returning all zeros — remains unresolved and is the
primary blocker for full PD negotiation.
--------------------------------------------------------------------------------
HARDWARE
--------------------------------------------------------------------------------
System manufacturer: SAMSUNG ELECTRONICS CO., LTD.
Product name: 750XGK
Product family: Galaxy Book4
System version: P02CFP
BIOS: P02CFP.015.240409.HQ (04/09/2024)
Battery: SAMSUNG Electronics SR Real Battery
Design capacity: 3530 mAh / 54 Wh
Chemistry: Li-ion, Nominal voltage: 15.4V
Charger: Samsung OEM USB-C (65W rated, 20V/3.25A)
Charging port: USB-C (UCSI, PD and PPS capable)
--------------------------------------------------------------------------------
KERNEL VERSIONS
--------------------------------------------------------------------------------
Affected: 6.17.0-19-generic (installed 2026-03-16)
Not affected: 6.17.0-12-generic (removed 2026-03-18, no longer available)
--------------------------------------------------------------------------------
SYMPTOMS
--------------------------------------------------------------------------------
1. USB-C charging voltage negotiates to ~15.8V instead of 20V
- Actual power delivery: ~27W (observed: 1.7A x 15.8V)
- Expected power delivery: 45W minimum (20V x 2.25A)
2. UCSI power supply sysfs reports zeroed voltage data:
POWER_SUPPLY_VOLTAGE_MAX=0
POWER_SUPPLY_VOLTAGE_MIN=0
POWER_SUPPLY_VOLTAGE_NOW=0
POWER_SUPPLY_CURRENT_MAX=0
(Despite POWER_SUPPLY_CURRENT_NOW=2250000 and USB_TYPE=C [PD] PD_PPS)
3. UCSI debugfs interface returns all zeros:
/sys/kernel/debug/usb/ucsi/USBC000:00/vbus_voltage = 0 mV
/sys/kernel/debug/usb/ucsi/USBC000:00/avg_current = 0 mA
/sys/kernel/debug/usb/ucsi/USBC000:00/response = 0x0000...0000
4. Zero UCSI/typec messages in dmesg at boot — PD negotiation events are
not logged, indicating silent failure in the UCSI initialization path.
5. Slower-than-expected charging when system is powered off, suggesting
the embedded controller (EC) charging profile is not properly initialized
during shutdown/handoff.
6. samsung-galaxybook platform driver logs repeated unknown ACPI
notification events:
samsung-galaxybook SAM0430:00: unknown ACPI notification event: 0x71
(firing approximately every 60-90 seconds)
--------------------------------------------------------------------------------
ROOT CAUSE ANALYSIS
--------------------------------------------------------------------------------
The Samsung Galaxy Book4 uses a non-standard UCSI implementation that routes
all communication through the Embedded Controller (EC) via ACPI _DSM methods
(UUID: 6f8398c2-7ca4-11e4-ad36-631042b5008f). The DSDT defines a UBTC device
at \_SB.UBTC with:
- A shared memory region at physical address 0x40238E18
- DSM Case 1: OPM write (kernel -> EC via MGO registers)
- DSM Case 2: OPM read (EC -> kernel via MGI/CCI registers)
- A UCEV method that reads EC state and fires Notify(UBTC, 0x80)
Three issues were identified:
ISSUE 1: Missing Samsung DMI quirk in ucsi_acpi.c
The ucsi_acpi driver contains a quirk table for LG gram laptops
(ucsi_gram_ops) that handles bogus PDOS_CHANGE events after GET_PDOS.
Samsung Galaxy Book4 uses the identical EC-routed UCSI architecture and
exhibits the same bogus event behavior, but is absent from the quirk table.
Without ucsi_gram_ops, spurious POWER_LEVEL_CHANGE | PDOS_CHANGE events
after GET_PDOS cause the kernel to re-trigger connector status checks that
interfere with PDO data population.
FILE: drivers/usb/typec/ucsi/ucsi_acpi.c
FIX: Add Samsung Galaxy Book4 to ucsi_acpi_quirks[] DMI table
ISSUE 2: Unhandled ACPI notification event 0x71 in samsung-galaxybook driver
The samsung-galaxybook platform driver (SAM0430) handles ACPI notification
events 0x61, 0x6c, 0x6d, and 0x70, but does not handle 0x71. This event
fires repeatedly (~every 60-90 seconds) and appears to be a USB-C PD power
state change notification. When unhandled, the UCEV ACPI method (which
triggers UCSI connector status refresh) is never called in response to
charger state changes.
FILE: drivers/platform/x86/samsung-galaxybook.c
FIX: Add case for 0x71 that calls acpi_evaluate_object(UCEV)
ISSUE 3: UCSI command/response cycle returning all zeros (PRIMARY BUG)
Even with the above patches applied, the UCSI debugfs interface returns
all zeros for vbus_voltage, avg_current, and response. GET_CONNECTOR_STATUS
commands return no data. This indicates the DSM read path (Case 2) is not
functioning correctly — the EC response is either not being requested or
not being read back at the right time. This is the primary regression
between -12 and -19 and the root cause of src_pdos never being populated.
The likely location is in how ucsi_acpi_poll_cci() vs ucsi_acpi_read_cci()
are called, or a timing change in how the driver waits for EC responses
via the DSM interface. Without the -12 kernel source for comparison,
the exact commit introducing this regression could not be identified.
--------------------------------------------------------------------------------
PATCHES DEVELOPED
--------------------------------------------------------------------------------
PATCH 1: drivers/usb/typec/ucsi/ucsi_acpi.c
Add Samsung Galaxy Book4 to ucsi_acpi_quirks DMI table.
--- a/drivers/usb/typec/ucsi/ucsi_acpi.c
+++ b/drivers/usb/typec/ucsi/ucsi_acpi.c
@@ -146,6 +146,14 @@ static const struct dmi_system_id ucsi_acpi_quirks[] = {
.driver_data = (void *)&ucsi_gram_ops,
},
+ {
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "SAMSUNG ELECTRONICS CO., LTD."),
+ DMI_MATCH(DMI_PRODUCT_FAMILY, "Galaxy Book4"),
+ DMI_MATCH(DMI_PRODUCT_NAME, "750XGK"),
+ },
+ .driver_data = (void *)&ucsi_gram_ops,
+ },
{ }
};
PATCH 2: drivers/platform/x86/samsung-galaxybook.c
Add handling for ACPI notification event 0x71 (USB-C PD state change).
--- a/drivers/platform/x86/samsung-galaxybook.c
+++ b/drivers/platform/x86/samsung-galaxybook.c
@@ -199,6 +199,7 @@ static const struct dmi_system_id ucsi_acpi_quirks[] = {
#define GB_ACPI_NOTIFY_HOTKEY_PERFORMANCE_MODE 0x70
+#define GB_ACPI_NOTIFY_USB_PD_STATE_CHANGED 0x71
@@ -1256,6 +1256,13 @@ static void galaxybook_acpi_notify(...)
case GB_ACPI_NOTIFY_HOTKEY_PERFORMANCE_MODE:
if (galaxybook->has_performance_mode)
platform_profile_cycle();
break;
+ case GB_ACPI_NOTIFY_USB_PD_STATE_CHANGED:
+ {
+ acpi_handle ubtc_handle;
+ if (ACPI_SUCCESS(acpi_get_handle(NULL, "\\_SB.UBTC", &ubtc_handle)))
+ acpi_evaluate_object(ubtc_handle, "UCEV", NULL, NULL);
+ break;
+ }
default:
--------------------------------------------------------------------------------
WORKAROUND
--------------------------------------------------------------------------------
Reloading the ucsi_acpi module after boot partially restores charging:
sudo modprobe -r ucsi_acpi && sudo modprobe ucsi_acpi
This brings charging to approximately 27W. It does not fully restore rated
wattage but is better than the initial degraded state. A systemd oneshot
service can automate this at boot:
[Unit]
Description=Reset UCSI ACPI for USB-C PD negotiation
After=multi-user.target
[Service]
Type=oneshot
ExecStart=/bin/sh -c 'modprobe -r ucsi_acpi && modprobe ucsi_acpi'
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target
--------------------------------------------------------------------------------
KEY SYSFS DATA
--------------------------------------------------------------------------------
BAT1 uevent (while charging):
POWER_SUPPLY_STATUS=Charging
POWER_SUPPLY_VOLTAGE_NOW=16316000 (16.3V — should be ~20V under PD)
POWER_SUPPLY_CURRENT_NOW=1668000 (1.67A)
Calculated actual wattage: ~27.2W
Expected wattage: 45W minimum
ucsi-source-psy-USBC000:002 uevent:
POWER_SUPPLY_CHARGE_TYPE=Standard (should be Fast)
POWER_SUPPLY_ONLINE=1
POWER_SUPPLY_VOLTAGE_MAX=0 (BUG)
POWER_SUPPLY_VOLTAGE_MIN=0 (BUG)
POWER_SUPPLY_VOLTAGE_NOW=0 (BUG)
POWER_SUPPLY_CURRENT_MAX=0 (BUG)
POWER_SUPPLY_CURRENT_NOW=2250000 (correct — 2.25A rated)
POWER_SUPPLY_USB_TYPE=C [PD] PD_PPS (correct — PD/PPS supported)
Power supply nodes present:
ADP1 BAT1 ucsi-source-psy-USBC000:001 ucsi-source-psy-USBC000:002
UCSI debugfs (USBC000:00):
vbus_voltage = 0 mV
avg_current = 0 mA
response = 0x00000000000000000000000000000000
--------------------------------------------------------------------------------
DSDT ANALYSIS
--------------------------------------------------------------------------------
The UCSI device (\_SB.UBTC) uses HID USBC000 / CID PNP0CA0 and communicates
via a Samsung-specific _DSM (UUID 6f8398c2-7ca4-11e4-ad36-631042b5008f):
- Case 0: Capabilities (returns 0x0F)
- Case 1: OPM write — copies MGO/CTL registers to EC, sets UCIT=1
- Case 2: OPM read — copies MGI/CCI registers from EC to shared memory
The UCEV method reads EC state (MGI/CCI) and fires Notify(UBTC, 0x80),
which is the standard mechanism to trigger UCSI connector status refresh.
This method is currently never called because the 0x71 notification that
should trigger it is unhandled.
--------------------------------------------------------------------------------
SUGGESTED BISECT RANGE
--------------------------------------------------------------------------------
Good: 6.17.0-12-generic (Ubuntu package: 6.17.0-12.12)
Bad: 6.17.0-19-generic (Ubuntu package: 6.17.0-19.19)
Primary suspects:
drivers/usb/typec/ucsi/ucsi_acpi.c — DSM read/write sequencing
drivers/usb/typec/ucsi/ucsi.c — poll_cci vs read_cci usage
drivers/platform/x86/samsung-galaxybook.c — missing 0x71 handler
Upstream maintainer:
Heikki Krogerus <heikki.krogerus@linux.intel.com> (UCSI)
Joshua Grisham <josh@joshuagrisham.com> (samsung-galaxybook)
--------------------------------------------------------------------------------
HOW TO REPRODUCE
--------------------------------------------------------------------------------
1. Install kernel 6.17.0-19-generic on Ubuntu 25.10
2. Boot Samsung Galaxy Book4 NP750XGK with Samsung OEM 65W USB-C charger
3. Check:
cat /sys/class/power_supply/ucsi-source-psy-USBC000:002/voltage_now
# Returns 0 (expected: ~20000000)
cat /sys/kernel/debug/usb/ucsi/USBC000:00/response
# Returns all zeros (expected: connector status data)
4. Observe charging voltage ~15.8V instead of 20V via:
cat /sys/class/power_supply/BAT1/voltage_now
cat /sys/class/power_supply/BAT1/current_now
# Multiply: should be ~45W, actual ~27W
--------------------------------------------------------------------------------
ADDITIONAL CONTEXT
--------------------------------------------------------------------------------
- TLP 1.8.0 installed but charge thresholds unconfigured (not the cause)
- Battery health: 91.2% capacity at 258 cycles (not a factor)
- Secure Boot: enabled (patched modules require MOK signing)
- The samsung-galaxybook driver was new/significantly updated for this
hardware class — interactions between it and ucsi_acpi may not have
been fully tested on kernel -19
- Reporter is available to test patches, provide additional diagnostics,
or run bisect builds
--------------------------------------------------------------------------------
FILING INSTRUCTIONS
--------------------------------------------------------------------------------
Ubuntu Launchpad: ubuntu-bug linux (auto-collects system info)
Tag: regression, usb-c, charging, ucsi, samsung
Kernel bugzilla: https://bugzilla.kernel.org
Product: Drivers / Component: USB
CC: heikki.krogerus@linux.intel.com
CC: josh@joshuagrisham.com
================================================================================
END OF REPORT
================================================================================
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: linux-image-6.17.0-19-generic 6.17.0-19.19
ProcVersionSignature: Ubuntu 6.17.0-19.19-generic 6.17.13
Uname: Linux 6.17.0-19-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: brian 3875 F.... pipewire
brian 3897 F.... wireplumber
/dev/snd/seq: brian 3875 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 18 23:03:53 2026
InstallationDate: Installed on 2025-05-23 (299 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 750XGK
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/zsh
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-19-generic root=UUID=67cdc73c-425b-47f6-a88c-636207de0da4 ro quiet splash lockdown=none resume=UUID=67cdc73c-425b-47f6-a88c-636207de0da4 resume_offset=103645184 i915.enable_dc=0 i915.enable_psr=0 i915.enable_fbc=0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
firmware-sof N/A
linux-firmware 20250901.git993ff19b-0ubuntu1.9
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/09/2024
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: P02CFP.015.240409.HQ
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP750XGK-KS2US
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SAMSUNG_SW_REVISION_12345+10.0.22631
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP02CFP.015.240409.HQ:bd04/09/2024:br5.27:svnSAMSUNGELECTRONICSCO.,LTD.:pn750XGK:pvrP02CFP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP750XGK-KS2US:rvrSAMSUNG_SW_REVISION_12345+10.0.22631:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-RPLU-PCFP:
dmi.product.family: Galaxy Book4
dmi.product.name: 750XGK
dmi.product.sku: SCAI-A5A5-A5A5-RPLU-PCFP
dmi.product.version: P02CFP
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2144854/+subscriptions
Подписаться на:
Комментарии (Atom)