Thank you for reporting this and helping make Ubuntu better. This bug
report is missing kernel log files. Please boot into the Ubuntu kernel
and run the following command in a terminal, which will collect
debugging information and attach it to this bug report:
$ sudo apport-collect 2142293
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142293
Title:
WCN7850 / FastConnect 7800 Wi-Fi 7 not working — ath12k_pci module
missing
Status in linux package in Ubuntu:
Incomplete
Bug description:
The Qualcomm FastConnect 7800 (WCN7850) Wi-Fi 7 adapter is detected and the ath12k_pci module loads, but probe fails due to an unrecognized hardware revision.
Commands and output:
lspci -nn | grep -i qualcomm
uname -r
lsmod | grep ath
sudo dmesg | grep -i ath12k
ls /lib/firmware/ath12k/
09:00.0 Network controller [0280]: Qualcomm Technologies, Inc WCN785x Wi-Fi 7(802.11be) 320MHz 2x2 [FastConnect 7800] [17cb:1107] (rev 01)
6.17.0-14-generic
ath12k 987136 0
qmi_helpers 28672 1 ath12k
mac80211 1884160 1 ath12k
cfg80211 1478656 2 ath12k,mac80211
qcom_scm 53248 1 ath12k
mhi 139264 1 ath12k
[ 4.547060] ath12k_pci 0000:09:00.0: BAR 0 [mem 0xf6200000-0xf63fffff 64bit]: assigned
[ 4.547084] ath12k_pci 0000:09:00.0: enabling device (0000 -> 0002)
[ 5.005891] ath12k_pci 0000:09:00.0: Unknown hardware version found for WCN7850: 0xf
[ 5.005949] ath12k_pci 0000:09:00.0: probe with driver ath12k_pci failed with error -95
QCN9274 WCN7850
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142293/+subscriptions
вторник
[Bug 2141377] Re: [SRU]Fix xe GPU suspend/resume crash on Battlemage
This bug is awaiting verification that the linux-oem-6.17/6.17.0-1013.13
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-oem-6.17' to 'verification-done-
noble-linux-oem-6.17'. If the problem still exists, change the tag
'verification-needed-noble-linux-oem-6.17' to 'verification-failed-
noble-linux-oem-6.17'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-noble-linux-oem-6.17-v2 verification-needed-noble-linux-oem-6.17
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141377
Title:
[SRU]Fix xe GPU suspend/resume crash on Battlemage
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-oem-6.17 source package in Noble:
Fix Committed
Status in linux source package in Questing:
In Progress
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Fix Released
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[ Impact ]
Intel Battlemage xe GPU (8086:e212) crashes during system resume with
NULL pointer dereference in xe_guc_ads_populate_post_load(), making
suspend/resume non-functional on affected systems.
Root cause: Noble 6.17 kernels have commit 59cebf0bdff48 but are missing
its prerequisite commit 1313351e71181. Without proper forcewake handling,
MMIO register access causes hardware corruption.
[ Fix ]
Cherry-pick upstream commit from v6.18-rc1:
- 1313351e71181 ("drm/xe: make xe_gt_idle_disable_c6() handle the forcewake internally")
[ Test Plan ]
1. System: Lenovo ThinkStation P3 Ultra G2 with Battlemage dGPU (8086:e212)
2. Reproduce: rtcwake -m mem -s 10
3. Verify: System resumes successfully without crashes
[ Where problems could occur ]
It may break xe driver GT idle/power management, affects suspend/resume path. Commit is from mainline v6.18-rc1.
The dGPU is not fully certified on v6.8 kernel, so SRU for questing
and oem-6.17.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2141377/+subscriptions
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-noble-linux-oem-6.17' to 'verification-done-
noble-linux-oem-6.17'. If the problem still exists, change the tag
'verification-needed-noble-linux-oem-6.17' to 'verification-failed-
noble-linux-oem-6.17'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-noble-linux-oem-6.17-v2 verification-needed-noble-linux-oem-6.17
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2141377
Title:
[SRU]Fix xe GPU suspend/resume crash on Battlemage
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-oem-6.17 source package in Noble:
Fix Committed
Status in linux source package in Questing:
In Progress
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Fix Released
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[ Impact ]
Intel Battlemage xe GPU (8086:e212) crashes during system resume with
NULL pointer dereference in xe_guc_ads_populate_post_load(), making
suspend/resume non-functional on affected systems.
Root cause: Noble 6.17 kernels have commit 59cebf0bdff48 but are missing
its prerequisite commit 1313351e71181. Without proper forcewake handling,
MMIO register access causes hardware corruption.
[ Fix ]
Cherry-pick upstream commit from v6.18-rc1:
- 1313351e71181 ("drm/xe: make xe_gt_idle_disable_c6() handle the forcewake internally")
[ Test Plan ]
1. System: Lenovo ThinkStation P3 Ultra G2 with Battlemage dGPU (8086:e212)
2. Reproduce: rtcwake -m mem -s 10
3. Verify: System resumes successfully without crashes
[ Where problems could occur ]
It may break xe driver GT idle/power management, affects suspend/resume path. Commit is from mainline v6.18-rc1.
The dGPU is not fully certified on v6.8 kernel, so SRU for questing
and oem-6.17.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2141377/+subscriptions
[Bug 2142443] Re: [resolute] Installed an Nvidia driver and now booting to a frozen black screen
** Changed in: nvidia-graphics-drivers-590 (Ubuntu)
Status: Confirmed => In Progress
** Changed in: nvidia-graphics-drivers-580 (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142443
Title:
[resolute] Installed an Nvidia driver and now booting to a frozen
black screen
Status in linux package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-580 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-590 package in Ubuntu:
In Progress
Bug description:
I installed the latest Nvidia driver in Resolute:
ubuntu-drivers list
sudo ubuntu-drivers install nvidia-driver-590-open
sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 4131
Kernel driver in use: NovaCore
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142443/+subscriptions
Status: Confirmed => In Progress
** Changed in: nvidia-graphics-drivers-580 (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142443
Title:
[resolute] Installed an Nvidia driver and now booting to a frozen
black screen
Status in linux package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-580 package in Ubuntu:
In Progress
Status in nvidia-graphics-drivers-590 package in Ubuntu:
In Progress
Bug description:
I installed the latest Nvidia driver in Resolute:
ubuntu-drivers list
sudo ubuntu-drivers install nvidia-driver-590-open
sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 4131
Kernel driver in use: NovaCore
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142443/+subscriptions
[Bug 2142443] Re: [resolute] Installed an Nvidia driver and now booting to a frozen black screen
https://github.com/canonical/nvidia-graphics-drivers/pull/83
** Changed in: nvidia-graphics-drivers-590 (Ubuntu)
Assignee: (unassigned) => Alessandro Astone (aleasto)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142443
Title:
[resolute] Installed an Nvidia driver and now booting to a frozen
black screen
Status in linux package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-580 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-590 package in Ubuntu:
Confirmed
Bug description:
I installed the latest Nvidia driver in Resolute:
ubuntu-drivers list
sudo ubuntu-drivers install nvidia-driver-590-open
sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 4131
Kernel driver in use: NovaCore
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142443/+subscriptions
** Changed in: nvidia-graphics-drivers-590 (Ubuntu)
Assignee: (unassigned) => Alessandro Astone (aleasto)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2142443
Title:
[resolute] Installed an Nvidia driver and now booting to a frozen
black screen
Status in linux package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-580 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-590 package in Ubuntu:
Confirmed
Bug description:
I installed the latest Nvidia driver in Resolute:
ubuntu-drivers list
sudo ubuntu-drivers install nvidia-driver-590-open
sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 4131
Kernel driver in use: NovaCore
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142443/+subscriptions
[Bug 2142510] Re: Regression: ip route get intermittently returns broadcast … for public IPs on 6.8.0-100 (breaks outbound TCP/Docker pulls)
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/2142510
Title:
Regression: ip route get intermittently returns broadcast …
<local,brd> for public IPs on 6.8.0-100 (breaks outbound TCP/Docker
pulls)
Status in linux package in Ubuntu:
Confirmed
Bug description:
Summary / Regression
This is a regression between Ubuntu kernels on an Ubuntu VM (Proxmox/QEMU/KVM, bridged networking, DHCP reservation). With 6.8.0-100-generic, ip -details route get <public-ip> intermittently returns an invalid cached result marking public IPs as broadcast/local (cache <local,brd>). When it enters this state, outbound TCP fails with "Network is unreachable" and Docker/Portainer pulls fail. Booting 6.8.0-90-generic on the same VM fixes it (route lookups remain unicast).
Environment
Ubuntu VM on Proxmox VE (QEMU/KVM), bridge vmbr0, DHCP reservation.
Reproduced across configuration changes: virtio/e1000 NIC, cpu
host/kvm64, cloud-init disabled; persists specifically with 6.8.0-100
and disappears with 6.8.0-90.
Evidence (6.8.0-100-generic)
Running repeatedly:
ip -details route get 1.1.1.1
shows flapping between correct unicast and incorrect broadcast classification:
unicast 1.1.1.1 via 192.168.1.1 dev ens18 table main src 192.168.1.72
cache
broadcast 1.1.1.1 via 192.168.1.1 dev ens18 table main src 192.168.1.72
cache <local,brd>
broadcast 1.1.1.1 via 192.168.1.1 dev ens18 table main src 192.168.1.72
cache <local,brd>
When the broadcast … <local,brd> state appears, outbound TCP
connections to public IPs fail ("Network is unreachable"), and ubuntu-
bug linux upload also sometimes fails with urlopen error [Errno 101]
Network is unreachable.
Expected
Public IPs should never be classified as broadcast … <local,brd> in route lookup; outbound TCP should stay stable.
Workaround
Boot kernel 6.8.0-90-generic (issue disappears). Flushing caches (ip route flush cache and ip neigh flush dev ens18) temporarily restores correct behavior on 6.8.0-100.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-100-generic 6.8.0-100.100
ProcVersionSignature: Ubuntu 6.8.0-100.100-generic 6.8.12
Uname: Linux 6.8.0-100-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
Date: Mon Feb 23 19:39:48 2026
InstallationDate: Installed on 2025-03-13 (347 days ago)
InstallationMedia: Ubuntu-Server 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm
ProcFB: 0 bochs-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-100-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro usbcore.autosuspend=-1
RelatedPackageVersions:
linux-restricted-modules-6.8.0-100-generic N/A
linux-backports-modules-6.8.0-100-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.22
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-9.2
dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-9.2:cvnQEMU:ct1:cvrpc-i440fx-9.2:sku:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-9.2
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142510/+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/2142510
Title:
Regression: ip route get intermittently returns broadcast …
<local,brd> for public IPs on 6.8.0-100 (breaks outbound TCP/Docker
pulls)
Status in linux package in Ubuntu:
Confirmed
Bug description:
Summary / Regression
This is a regression between Ubuntu kernels on an Ubuntu VM (Proxmox/QEMU/KVM, bridged networking, DHCP reservation). With 6.8.0-100-generic, ip -details route get <public-ip> intermittently returns an invalid cached result marking public IPs as broadcast/local (cache <local,brd>). When it enters this state, outbound TCP fails with "Network is unreachable" and Docker/Portainer pulls fail. Booting 6.8.0-90-generic on the same VM fixes it (route lookups remain unicast).
Environment
Ubuntu VM on Proxmox VE (QEMU/KVM), bridge vmbr0, DHCP reservation.
Reproduced across configuration changes: virtio/e1000 NIC, cpu
host/kvm64, cloud-init disabled; persists specifically with 6.8.0-100
and disappears with 6.8.0-90.
Evidence (6.8.0-100-generic)
Running repeatedly:
ip -details route get 1.1.1.1
shows flapping between correct unicast and incorrect broadcast classification:
unicast 1.1.1.1 via 192.168.1.1 dev ens18 table main src 192.168.1.72
cache
broadcast 1.1.1.1 via 192.168.1.1 dev ens18 table main src 192.168.1.72
cache <local,brd>
broadcast 1.1.1.1 via 192.168.1.1 dev ens18 table main src 192.168.1.72
cache <local,brd>
When the broadcast … <local,brd> state appears, outbound TCP
connections to public IPs fail ("Network is unreachable"), and ubuntu-
bug linux upload also sometimes fails with urlopen error [Errno 101]
Network is unreachable.
Expected
Public IPs should never be classified as broadcast … <local,brd> in route lookup; outbound TCP should stay stable.
Workaround
Boot kernel 6.8.0-90-generic (issue disappears). Flushing caches (ip route flush cache and ip neigh flush dev ens18) temporarily restores correct behavior on 6.8.0-100.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-100-generic 6.8.0-100.100
ProcVersionSignature: Ubuntu 6.8.0-100.100-generic 6.8.12
Uname: Linux 6.8.0-100-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
Date: Mon Feb 23 19:39:48 2026
InstallationDate: Installed on 2025-03-13 (347 days ago)
InstallationMedia: Ubuntu-Server 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm
ProcFB: 0 bochs-drmdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.8.0-100-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro usbcore.autosuspend=-1
RelatedPackageVersions:
linux-restricted-modules-6.8.0-100-generic N/A
linux-backports-modules-6.8.0-100-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.22
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.release: 0.0
dmi.bios.vendor: SeaBIOS
dmi.bios.version: rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-9.2
dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-9.2:cvnQEMU:ct1:cvrpc-i440fx-9.2:sku:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-9.2
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142510/+subscriptions
[Bug 2142443] Re: [resolute] Installed an Nvidia driver and now booting to a frozen black screen
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-590 (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/2142443
Title:
[resolute] Installed an Nvidia driver and now booting to a frozen
black screen
Status in linux package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-580 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-590 package in Ubuntu:
Confirmed
Bug description:
I installed the latest Nvidia driver in Resolute:
ubuntu-drivers list
sudo ubuntu-drivers install nvidia-driver-590-open
sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 4131
Kernel driver in use: NovaCore
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142443/+subscriptions
** Changed in: nvidia-graphics-drivers-590 (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/2142443
Title:
[resolute] Installed an Nvidia driver and now booting to a frozen
black screen
Status in linux package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-580 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-590 package in Ubuntu:
Confirmed
Bug description:
I installed the latest Nvidia driver in Resolute:
ubuntu-drivers list
sudo ubuntu-drivers install nvidia-driver-590-open
sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 4131
Kernel driver in use: NovaCore
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142443/+subscriptions
[Bug 2142443] Re: [resolute] Installed an Nvidia driver and now booting to a frozen black screen
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-580 (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/2142443
Title:
[resolute] Installed an Nvidia driver and now booting to a frozen
black screen
Status in linux package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-580 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-590 package in Ubuntu:
Confirmed
Bug description:
I installed the latest Nvidia driver in Resolute:
ubuntu-drivers list
sudo ubuntu-drivers install nvidia-driver-590-open
sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 4131
Kernel driver in use: NovaCore
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142443/+subscriptions
** Changed in: nvidia-graphics-drivers-580 (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/2142443
Title:
[resolute] Installed an Nvidia driver and now booting to a frozen
black screen
Status in linux package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-580 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-590 package in Ubuntu:
Confirmed
Bug description:
I installed the latest Nvidia driver in Resolute:
ubuntu-drivers list
sudo ubuntu-drivers install nvidia-driver-590-open
sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 4131
Kernel driver in use: NovaCore
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142443/+subscriptions
[Bug 2142443] Re: [resolute] Installed an Nvidia driver and now booting to a frozen black screen
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/2142443
Title:
[resolute] Installed an Nvidia driver and now booting to a frozen
black screen
Status in linux package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-580 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-590 package in Ubuntu:
Confirmed
Bug description:
I installed the latest Nvidia driver in Resolute:
ubuntu-drivers list
sudo ubuntu-drivers install nvidia-driver-590-open
sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 4131
Kernel driver in use: NovaCore
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142443/+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/2142443
Title:
[resolute] Installed an Nvidia driver and now booting to a frozen
black screen
Status in linux package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-580 package in Ubuntu:
Confirmed
Status in nvidia-graphics-drivers-590 package in Ubuntu:
Confirmed
Bug description:
I installed the latest Nvidia driver in Resolute:
ubuntu-drivers list
sudo ubuntu-drivers install nvidia-driver-590-open
sudo reboot
but the system now boots to a frozen black screen.
An SSH login reveals the wrong kernel driver in use:
$ lspci -k -d::300
01:00.0 VGA compatible controller: NVIDIA Corporation GA107 [GeForce RTX 3050 6GB] (rev a1)
Subsystem: Gigabyte Technology Co., Ltd Device 4131
Kernel driver in use: NovaCore
Kernel modules: nvidiafb, nouveau, nova_core, nvidia_drm, nvidia
ProblemType: Bug
DistroRelease: Ubuntu 26.04
Package: nvidia-driver-590-open 590.48.01-0ubuntu5
ProcVersionSignature: Ubuntu 6.19.0-6.6-generic 6.19.2
Uname: Linux 6.19.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon Feb 23 16:33:28 2026
InstallationDate: Installed on 2025-12-17 (68 days ago)
InstallationMedia: Ubuntu 26.04 LTS "Resolute Raccoon" - Daily amd64 (20251209)
SourcePackage: nvidia-graphics-drivers-590
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2142443/+subscriptions
[Bug 2134400] Re: Questing preinstalled server fails to boot on QCS8300 based boards
Hi @Stefan Bader(smb),
Can you please update when this patch will be merged to mainline?
Thanks,
Anurag
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2134400
Title:
Questing preinstalled server fails to boot on QCS8300 based boards
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Questing:
Triaged
Bug description:
For successful boot of Ubuntu Linux Distro on Qualcomm QCS8300 based
boards, kernel CONFIGs for QCS8300 interconnect, pinctrl and global
clock controllers must be built in (statically compiled).
In current Questing kernel, the CONFIGs, CONFIG_PINCTRL_QCS8300,
CONFIG_INTERCONNECT_QCOM_QCS8300 and CONFIG_QCS_GCC_8300 are set as
modules.
Board: Monaco-evk.
Will be posting a change to make these SOC specific as static.
reference BUG for CONFIGs enabled as static on other Qualcomm boards:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2106681
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2121347
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2134400/+subscriptions
Can you please update when this patch will be merged to mainline?
Thanks,
Anurag
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2134400
Title:
Questing preinstalled server fails to boot on QCS8300 based boards
Status in linux package in Ubuntu:
Triaged
Status in linux source package in Questing:
Triaged
Bug description:
For successful boot of Ubuntu Linux Distro on Qualcomm QCS8300 based
boards, kernel CONFIGs for QCS8300 interconnect, pinctrl and global
clock controllers must be built in (statically compiled).
In current Questing kernel, the CONFIGs, CONFIG_PINCTRL_QCS8300,
CONFIG_INTERCONNECT_QCOM_QCS8300 and CONFIG_QCS_GCC_8300 are set as
modules.
Board: Monaco-evk.
Will be posting a change to make these SOC specific as static.
reference BUG for CONFIGs enabled as static on other Qualcomm boards:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2106681
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2121347
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2134400/+subscriptions
[Bug 2139596] Re: Enable GSC loading and PXP for PTL
This bug was fixed in the package linux-oem-6.17 - 6.17.0-1012.12
---------------
linux-oem-6.17 (6.17.0-1012.12) noble; urgency=medium
* noble/linux-oem-6.17: 6.17.0-1012.12 -proposed tracker (LP:
#2141290)
* Fix no built-in audio input device on HP 200 G2a (LP: #2141366)
- ASoC: amd: yc: Add quirk for HP 200 G2a 16
* [SRU] Fix USB4 hotplug on certain Lenovo Platforms (LP: #2141283)
- PCI/ERR: Ensure error recoverability at all times
- treewide: Drop pci_save_state() after pci_restore_state()
* [SRU] Fix ice PTP crash on suspend/resume (LP: #2140514)
- SAUCE: ice: Fix PTP NULL pointer dereference during VSI rebuild
* dma-buf filesystem flags fix (LP: #2139656)
- SAUCE: dma-buf: set SB_I_NOEXEC and SB_I_NODEV on dmabuf filesystem
* Enable GSC loading and PXP for PTL (LP: #2139596)
- drm/xe/gsc: Make GSC FW load optional for newer platforms
- drm/xe/ptl: Define GSC for PTL
- drm/xe/ptl: Enable PXP for PTL
* The second tbt storage plugged on the dock will not be recognized
(LP: #2139572)
- PCI: Always claim bridge window before its setup
- PCI: Disable non-claimed bridge window
- PCI: Use pci_release_resource() instead of release_resource()
- PCI: Enable bridge even if bridge window fails to assign
- PCI: Fix pdev_resources_assignable() disparity
- PCI: Preserve bridge window resource type flags
- SAUCE: thunderbolt: Fix PCIe device enumeration with delayed rescan
-- Kuan-Ying Lee <kuan-ying.lee@canonical.com> Tue, 10 Feb 2026
10:49:35 +0800
** Changed in: linux-oem-6.17 (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2139596
Title:
Enable GSC loading and PXP for PTL
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-firmware source package in Noble:
Fix Committed
Status in linux-oem-6.17 source package in Noble:
Fix Released
Status in linux source package in Questing:
In Progress
Status in linux-firmware source package in Questing:
Fix Committed
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
In Progress
Status in linux-firmware source package in Resolute:
Fix Released
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
SRU Justification:
[Impact]
On newer platforms GSC FW is only required for content protection
features, so the core driver features work perfectly fine without it.
GSC was previously made optional for PTL.
[Fix]
Proposed fixes:
* kernel: (currently in linux-next only)
* b1dcec9bd8a1d drm/xe/ptl: Enable PXP for PTL
* 6d24027d555e4 drm/xe/ptl: Define GSC for PTL
* 65b65ffcf669c drm/xe/gsc: Make GSC FW load optional for newer platforms
* firmware: (main branch only)
* 05a6a40bb xe: Add GSC 105.0.2.1301 for PTL
[Test Plan]
With GSC firmware loaded:
```
$ sudo dmesg|grep -i gsc
[ 6.925262] xe 0000:00:02.0: [drm] GT1: Using GSC firmware from xe/ptl_gsc_1.bin version 105.0.2.1301
[ 6.925766] mei_gsc_proxy 0000:00:16.0-0f73db04-97ab-4125-b893-e904ad0d5464: bound 0000:00:02.0 (ops xe_gsc_proxy_component_ops [xe])
[ 7.097263] xe 0000:00:02.0: [drm] GT1: found GSC cv105.1.0
```
[Where problems could occur]
Opaque firmware. Expect maybe stability updates.
[Other Info]
While PTL was scheduled for v6.17 kernels, nominate fix for R, Q and
linux-oem-6.17/noble.
========== original bug report ==========
On newer platforms GSC FW is only required for content protection
features, so the core driver features work perfectly fine without it.
GSC was previously made optional for PTL.
Proposed fixes:
* kernel: (currently in linux-next only)
* b1dcec9bd8a1d drm/xe/ptl: Enable PXP for PTL
* 6d24027d555e4 drm/xe/ptl: Define GSC for PTL
* 65b65ffcf669c drm/xe/gsc: Make GSC FW load optional for newer platforms
* firmware: (main branch only)
* 05a6a40bb xe: Add GSC 105.0.2.1301 for PTL
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: u 2397 F.... pipewire
u 2402 F.... wireplumber
/dev/snd/seq: u 2397 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
Dependencies: firmware-sof-signed 2023.12.1-1ubuntu1.10
DistributionChannelDescriptor:
# This is the distribution channel descriptor for Ubuntu 24.04 for Dell
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-noble-oem-24.04d-edge-20260115-68
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2026-01-19 (14 days ago)
InstallationMedia: Ubuntu OEM 24.04.3 LTS "Noble Numbat" - Release amd64 (20260112)
IwConfig:
lo no wireless extensions.
wlp0s20f3 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 06cb:0701 Synaptics, Inc. SVP7500
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/3p, 20000M/x2
/: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/10p, 480M
|__ Port 003: Dev 002, If 0, Class=Vendor Specific Class, Driver=usbio-bridge, 12M
/: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 20000M/x2
MachineType: Dell Inc. XPS 14 DA14260
Package: linux-firmware
PackageArchitecture: amd64
ProcFB: 0 xedrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-1011-oem root=UUID=13504ba9-5519-4427-ac38-1f7a78fff0f3 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.17.0-1011.11-oem 6.17.9
RelatedPackageVersions:
linux-restricted-modules-6.17.0-1011-oem N/A
linux-backports-modules-6.17.0-1011-oem N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.23
Tags: noble
Uname: Linux 6.17.0-1011-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 01/09/2026
dmi.bios.release: 1.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.1
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 1.0
dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd01/09/2026:br1.2:efr1.0:svnDellInc.:pnXPS14DA14260:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0DB9:
dmi.product.family: Dell Laptops
dmi.product.name: XPS 14 DA14260
dmi.product.sku: 0DB9
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2139596/+subscriptions
---------------
linux-oem-6.17 (6.17.0-1012.12) noble; urgency=medium
* noble/linux-oem-6.17: 6.17.0-1012.12 -proposed tracker (LP:
#2141290)
* Fix no built-in audio input device on HP 200 G2a (LP: #2141366)
- ASoC: amd: yc: Add quirk for HP 200 G2a 16
* [SRU] Fix USB4 hotplug on certain Lenovo Platforms (LP: #2141283)
- PCI/ERR: Ensure error recoverability at all times
- treewide: Drop pci_save_state() after pci_restore_state()
* [SRU] Fix ice PTP crash on suspend/resume (LP: #2140514)
- SAUCE: ice: Fix PTP NULL pointer dereference during VSI rebuild
* dma-buf filesystem flags fix (LP: #2139656)
- SAUCE: dma-buf: set SB_I_NOEXEC and SB_I_NODEV on dmabuf filesystem
* Enable GSC loading and PXP for PTL (LP: #2139596)
- drm/xe/gsc: Make GSC FW load optional for newer platforms
- drm/xe/ptl: Define GSC for PTL
- drm/xe/ptl: Enable PXP for PTL
* The second tbt storage plugged on the dock will not be recognized
(LP: #2139572)
- PCI: Always claim bridge window before its setup
- PCI: Disable non-claimed bridge window
- PCI: Use pci_release_resource() instead of release_resource()
- PCI: Enable bridge even if bridge window fails to assign
- PCI: Fix pdev_resources_assignable() disparity
- PCI: Preserve bridge window resource type flags
- SAUCE: thunderbolt: Fix PCIe device enumeration with delayed rescan
-- Kuan-Ying Lee <kuan-ying.lee@canonical.com> Tue, 10 Feb 2026
10:49:35 +0800
** Changed in: linux-oem-6.17 (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2139596
Title:
Enable GSC loading and PXP for PTL
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-firmware source package in Noble:
Fix Committed
Status in linux-oem-6.17 source package in Noble:
Fix Released
Status in linux source package in Questing:
In Progress
Status in linux-firmware source package in Questing:
Fix Committed
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
In Progress
Status in linux-firmware source package in Resolute:
Fix Released
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
SRU Justification:
[Impact]
On newer platforms GSC FW is only required for content protection
features, so the core driver features work perfectly fine without it.
GSC was previously made optional for PTL.
[Fix]
Proposed fixes:
* kernel: (currently in linux-next only)
* b1dcec9bd8a1d drm/xe/ptl: Enable PXP for PTL
* 6d24027d555e4 drm/xe/ptl: Define GSC for PTL
* 65b65ffcf669c drm/xe/gsc: Make GSC FW load optional for newer platforms
* firmware: (main branch only)
* 05a6a40bb xe: Add GSC 105.0.2.1301 for PTL
[Test Plan]
With GSC firmware loaded:
```
$ sudo dmesg|grep -i gsc
[ 6.925262] xe 0000:00:02.0: [drm] GT1: Using GSC firmware from xe/ptl_gsc_1.bin version 105.0.2.1301
[ 6.925766] mei_gsc_proxy 0000:00:16.0-0f73db04-97ab-4125-b893-e904ad0d5464: bound 0000:00:02.0 (ops xe_gsc_proxy_component_ops [xe])
[ 7.097263] xe 0000:00:02.0: [drm] GT1: found GSC cv105.1.0
```
[Where problems could occur]
Opaque firmware. Expect maybe stability updates.
[Other Info]
While PTL was scheduled for v6.17 kernels, nominate fix for R, Q and
linux-oem-6.17/noble.
========== original bug report ==========
On newer platforms GSC FW is only required for content protection
features, so the core driver features work perfectly fine without it.
GSC was previously made optional for PTL.
Proposed fixes:
* kernel: (currently in linux-next only)
* b1dcec9bd8a1d drm/xe/ptl: Enable PXP for PTL
* 6d24027d555e4 drm/xe/ptl: Define GSC for PTL
* 65b65ffcf669c drm/xe/gsc: Make GSC FW load optional for newer platforms
* firmware: (main branch only)
* 05a6a40bb xe: Add GSC 105.0.2.1301 for PTL
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: u 2397 F.... pipewire
u 2402 F.... wireplumber
/dev/snd/seq: u 2397 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: unknown
Dependencies: firmware-sof-signed 2023.12.1-1ubuntu1.10
DistributionChannelDescriptor:
# This is the distribution channel descriptor for Ubuntu 24.04 for Dell
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-noble-oem-24.04d-edge-20260115-68
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2026-01-19 (14 days ago)
InstallationMedia: Ubuntu OEM 24.04.3 LTS "Noble Numbat" - Release amd64 (20260112)
IwConfig:
lo no wireless extensions.
wlp0s20f3 no wireless extensions.
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 06cb:0701 Synaptics, Inc. SVP7500
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Lsusb-t:
/: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/1p, 480M
/: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/3p, 20000M/x2
/: Bus 003.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/10p, 480M
|__ Port 003: Dev 002, If 0, Class=Vendor Specific Class, Driver=usbio-bridge, 12M
/: Bus 004.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/2p, 20000M/x2
MachineType: Dell Inc. XPS 14 DA14260
Package: linux-firmware
PackageArchitecture: amd64
ProcFB: 0 xedrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.17.0-1011-oem root=UUID=13504ba9-5519-4427-ac38-1f7a78fff0f3 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.17.0-1011.11-oem 6.17.9
RelatedPackageVersions:
linux-restricted-modules-6.17.0-1011-oem N/A
linux-backports-modules-6.17.0-1011-oem N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.23
Tags: noble
Uname: Linux 6.17.0-1011-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 01/09/2026
dmi.bios.release: 1.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.1
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 1.0
dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd01/09/2026:br1.2:efr1.0:svnDellInc.:pnXPS14DA14260:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0DB9:
dmi.product.family: Dell Laptops
dmi.product.name: XPS 14 DA14260
dmi.product.sku: 0DB9
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2139596/+subscriptions
[Bug 2140514] Re: [SRU] Fix ice PTP crash on suspend/resume
This bug was fixed in the package linux-oem-6.17 - 6.17.0-1012.12
---------------
linux-oem-6.17 (6.17.0-1012.12) noble; urgency=medium
* noble/linux-oem-6.17: 6.17.0-1012.12 -proposed tracker (LP:
#2141290)
* Fix no built-in audio input device on HP 200 G2a (LP: #2141366)
- ASoC: amd: yc: Add quirk for HP 200 G2a 16
* [SRU] Fix USB4 hotplug on certain Lenovo Platforms (LP: #2141283)
- PCI/ERR: Ensure error recoverability at all times
- treewide: Drop pci_save_state() after pci_restore_state()
* [SRU] Fix ice PTP crash on suspend/resume (LP: #2140514)
- SAUCE: ice: Fix PTP NULL pointer dereference during VSI rebuild
* dma-buf filesystem flags fix (LP: #2139656)
- SAUCE: dma-buf: set SB_I_NOEXEC and SB_I_NODEV on dmabuf filesystem
* Enable GSC loading and PXP for PTL (LP: #2139596)
- drm/xe/gsc: Make GSC FW load optional for newer platforms
- drm/xe/ptl: Define GSC for PTL
- drm/xe/ptl: Enable PXP for PTL
* The second tbt storage plugged on the dock will not be recognized
(LP: #2139572)
- PCI: Always claim bridge window before its setup
- PCI: Disable non-claimed bridge window
- PCI: Use pci_release_resource() instead of release_resource()
- PCI: Enable bridge even if bridge window fails to assign
- PCI: Fix pdev_resources_assignable() disparity
- PCI: Preserve bridge window resource type flags
- SAUCE: thunderbolt: Fix PCIe device enumeration with delayed rescan
-- Kuan-Ying Lee <kuan-ying.lee@canonical.com> Tue, 10 Feb 2026
10:49:35 +0800
** Changed in: linux-oem-6.17 (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2140514
Title:
[SRU] Fix ice PTP crash on suspend/resume
Status in HWE Next:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Confirmed
Status in linux-oem-6.17 source package in Noble:
Fix Released
Status in linux source package in Questing:
Confirmed
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Fix Released
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
SRU Justification:
[ Impact ]
Intel E810 network adapters experience kernel NULL pointer dereference
crashes during system resume when PTP is enabled. This occurs due to a
race condition where PTP periodic work attempts to access vsi->rx_rings
while VSI structures are being rebuilt, causing system instability and
potential data loss during suspend/resume cycles.
The crash occurs in this sequence:
1. System suspend triggers ice_ptp_prepare_for_reset() which cancels PTP work
2. ice_ptp_rebuild() immediately queues PTP work before VSI rebuild
3. PTP work executes and accesses NULL vsi->rx_rings
4. System crashes with NULL pointer dereference
[ Fix ]
Cherry-pick upstream commit:
- 8be3a229a6112 ("ice: Fix PTP NULL pointer dereference during VSI rebuild")
from https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git dev-queue
The fix keeps PTP work cancelled during rebuild and only queues it after
VSI rebuild completes. Adds ice_ptp_queue_work() helper function to
encapsulate proper timing of PTP work queue.
[ Test Plan ]
1. System with Intel E810 network adapter (ice driver)
2. Enable PTP: ptp4l -i <interface> -m
3. Suspend system: systemctl suspend
4. Resume system
5. Verify no kernel crash in dmesg (check for NULL pointer dereference in ice_ptp_update_cached_phctime)
6. Verify network connectivity restored: ping <target>
7. Verify PTP synchronization working: ptp4l shows proper sync
8. Repeat suspend/resume cycle multiple times to ensure stability
[ Where problems could occur ]
The patch changes when PTP work is queued during VSI rebuild. If there's
an error in the timing logic, PTP synchronization might be delayed after
resume, though the delay would be minimal (sub-second).
Risk is very low because:
- The fix only affects the suspend/resume path, not normal operation
- PTP work is still queued, just at the correct time (after VSI rebuild)
- The helper function includes proper state checking (ICE_PTP_READY)
- Change is isolated to PTP subsystem
[ Other Info ]
This issue affects systems using Intel E810 NICs with PTP enabled,
particularly in environments requiring frequent suspend/resume cycles
(laptops, power-managed servers).
The upstream commit is in the Intel Wired LAN maintainer's tree
(next-queue) and expected to be merged to mainline in the next cycle.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2140514/+subscriptions
---------------
linux-oem-6.17 (6.17.0-1012.12) noble; urgency=medium
* noble/linux-oem-6.17: 6.17.0-1012.12 -proposed tracker (LP:
#2141290)
* Fix no built-in audio input device on HP 200 G2a (LP: #2141366)
- ASoC: amd: yc: Add quirk for HP 200 G2a 16
* [SRU] Fix USB4 hotplug on certain Lenovo Platforms (LP: #2141283)
- PCI/ERR: Ensure error recoverability at all times
- treewide: Drop pci_save_state() after pci_restore_state()
* [SRU] Fix ice PTP crash on suspend/resume (LP: #2140514)
- SAUCE: ice: Fix PTP NULL pointer dereference during VSI rebuild
* dma-buf filesystem flags fix (LP: #2139656)
- SAUCE: dma-buf: set SB_I_NOEXEC and SB_I_NODEV on dmabuf filesystem
* Enable GSC loading and PXP for PTL (LP: #2139596)
- drm/xe/gsc: Make GSC FW load optional for newer platforms
- drm/xe/ptl: Define GSC for PTL
- drm/xe/ptl: Enable PXP for PTL
* The second tbt storage plugged on the dock will not be recognized
(LP: #2139572)
- PCI: Always claim bridge window before its setup
- PCI: Disable non-claimed bridge window
- PCI: Use pci_release_resource() instead of release_resource()
- PCI: Enable bridge even if bridge window fails to assign
- PCI: Fix pdev_resources_assignable() disparity
- PCI: Preserve bridge window resource type flags
- SAUCE: thunderbolt: Fix PCIe device enumeration with delayed rescan
-- Kuan-Ying Lee <kuan-ying.lee@canonical.com> Tue, 10 Feb 2026
10:49:35 +0800
** Changed in: linux-oem-6.17 (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2140514
Title:
[SRU] Fix ice PTP crash on suspend/resume
Status in HWE Next:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Confirmed
Status in linux-oem-6.17 source package in Noble:
Fix Released
Status in linux source package in Questing:
Confirmed
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
Fix Released
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
SRU Justification:
[ Impact ]
Intel E810 network adapters experience kernel NULL pointer dereference
crashes during system resume when PTP is enabled. This occurs due to a
race condition where PTP periodic work attempts to access vsi->rx_rings
while VSI structures are being rebuilt, causing system instability and
potential data loss during suspend/resume cycles.
The crash occurs in this sequence:
1. System suspend triggers ice_ptp_prepare_for_reset() which cancels PTP work
2. ice_ptp_rebuild() immediately queues PTP work before VSI rebuild
3. PTP work executes and accesses NULL vsi->rx_rings
4. System crashes with NULL pointer dereference
[ Fix ]
Cherry-pick upstream commit:
- 8be3a229a6112 ("ice: Fix PTP NULL pointer dereference during VSI rebuild")
from https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git dev-queue
The fix keeps PTP work cancelled during rebuild and only queues it after
VSI rebuild completes. Adds ice_ptp_queue_work() helper function to
encapsulate proper timing of PTP work queue.
[ Test Plan ]
1. System with Intel E810 network adapter (ice driver)
2. Enable PTP: ptp4l -i <interface> -m
3. Suspend system: systemctl suspend
4. Resume system
5. Verify no kernel crash in dmesg (check for NULL pointer dereference in ice_ptp_update_cached_phctime)
6. Verify network connectivity restored: ping <target>
7. Verify PTP synchronization working: ptp4l shows proper sync
8. Repeat suspend/resume cycle multiple times to ensure stability
[ Where problems could occur ]
The patch changes when PTP work is queued during VSI rebuild. If there's
an error in the timing logic, PTP synchronization might be delayed after
resume, though the delay would be minimal (sub-second).
Risk is very low because:
- The fix only affects the suspend/resume path, not normal operation
- PTP work is still queued, just at the correct time (after VSI rebuild)
- The helper function includes proper state checking (ICE_PTP_READY)
- Change is isolated to PTP subsystem
[ Other Info ]
This issue affects systems using Intel E810 NICs with PTP enabled,
particularly in environments requiring frequent suspend/resume cycles
(laptops, power-managed servers).
The upstream commit is in the Intel Wired LAN maintainer's tree
(next-queue) and expected to be merged to mainline in the next cycle.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2140514/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-meta-gcp/6.8.0-1050.53)
All autopkgtests for the newly accepted linux-meta-gcp (6.8.0-1050.53) for noble have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/255.4-1ubuntu8.12 (amd64, arm64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#linux-meta-gcp
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
The following regressions have been reported in tests triggered by the package:
systemd/255.4-1ubuntu8.12 (amd64, arm64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/noble/update_excuses.html#linux-meta-gcp
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-meta-gcp-6.8/6.8.0-1050.53~22.04.1)
All autopkgtests for the newly accepted linux-meta-gcp-6.8 (6.8.0-1050.53~22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
linux-gcp-6.8/6.8.0-1050.53~22.04.1 (amd64, arm64)
systemd/249.11-0ubuntu3.17 (amd64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-gcp-6.8
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
The following regressions have been reported in tests triggered by the package:
linux-gcp-6.8/6.8.0-1050.53~22.04.1 (amd64, arm64)
systemd/249.11-0ubuntu3.17 (amd64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#linux-meta-gcp-6.8
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1786013
Title:
Packaging resync
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-edge package in Ubuntu:
Fix Released
Status in linux source package in Precise:
Fix Released
Status in linux-azure source package in Precise:
Won't Fix
Status in linux-azure-edge source package in Precise:
Won't Fix
Status in linux source package in Trusty:
Fix Released
Status in linux-azure source package in Trusty:
Fix Released
Status in linux-azure-edge source package in Trusty:
Won't Fix
Status in linux source package in Xenial:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-edge source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Fix Released
Status in linux-azure-edge source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux-azure source package in Cosmic:
Fix Released
Status in linux-azure-edge source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Fix Released
Status in linux-azure-edge source package in Disco:
Won't Fix
Bug description:
Ongoing packaging resyncs.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
Подписаться на:
Комментарии (Atom)