test13 boots OK, dmesg attached
** Attachment added: "LP2111521-dmesg-test13.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2111521/+attachment/5887410/+files/LP2111521-dmesg-test13.txt
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2111521
Title:
nvme no longer detected on boot after upgrade to 6.8.0-60
Status in linux package in Ubuntu:
Triaged
Bug description:
Short version: booting 6.8.0-59-generic or any earlier version from
the grub menu works; 6.8.0-60-generic dumps me at the initramfs prompt
with no disks.
We have some servers running Ubuntu 24.04.2 LTS. They have NVME
solid-state disks which (in a working kernel) are detected as follows:
[ 3.537968] nvme nvme0: pci function 10000:01:00.0
[ 3.539285] nvme 10000:01:00.0: PCI INT A: no GSI
[ 5.897819] nvme nvme0: 32/0/0 default/read/poll queues
[ 5.905451] nvme nvme0: Ignoring bogus Namespace Identifiers
[ 5.909057] nvme0n1: p1 p2 p3
On the PCI bus they look like this:
10000:01:00.0 Non-Volatile memory controller [0108]: Intel Corporation NVMe Datacenter SSD [3DNAND, Beta Rock Controller] [8086:0a54]
$ ls -l /sys/class/nvme/nvme0
lrwxrwxrwx 1 root root 0 May 22 16:56 /sys/class/nvme/nvme0 -> ../../devices/pci0000:d7/0000:d7:05.5/pci10000:00/10000:00:02.0/10000:01:00.0/nvme/nvme0
Four identical servers updated their kernel this morning to:
ii linux-image-6.8.0-60-generic 6.8.0-60.63 amd64 Signed kernel image generic
...and rebooted. All four failed to come up and ended up at the
(initramfs) prompt. Rebooting and selecting 6.8.0-59-generic from the
grub menu allowed them to boot as normal.
There is no sign that the initramfs generation went wrong (on all four
servers) and the initramfs does contain all the same nvme modules for
-60 that the one for -59 does. I am at a loss to explain this, and
the initramfs environment is a bit limited for debugging.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2111521/+subscriptions
среда
[Bug 2110891] Re: System freeze on release upgrade 24.10 oneiric to 25.04 plucky with root fs on ZFS
benbuntu: I will try that. The data pool is only for my personal
development use so it should not be a problem.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2110891
Title:
System freeze on release upgrade 24.10 oneiric to 25.04 plucky with
root fs on ZFS
Status in linux package in Ubuntu:
Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
Deferred
Status in zfs-linux package in Ubuntu:
Confirmed
Status in linux source package in Plucky:
Confirmed
Status in ubuntu-release-upgrader source package in Plucky:
Fix Released
Status in zfs-linux source package in Plucky:
Confirmed
Bug description:
[Impact]
Upgrades to 25.10 (and newer) fail as the ZFS userspace modules are newer than the kernel modules and there is some incompatibility that can cause the kernel to hang, particularly the bug observes a problem with iterating over the snapshots of the root file system freezing it.
[Test plan: ubuntu-release-upgrader]
1. Create a vm
2. Check that the upgrade doesn't trigger the screen
(no zpool exists)
3. Install zfsutils-linux
4. Check that the upgrade doesn't trigger the screen
(zpool list -H will be empty)
5. Create a zpool, for example in a file
# fallocate /swap -l 2G
# zpool create foo /swap
# zpool list
NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
foo 1.88G 134K 1.87G - - 0% 0% 1.00x ONLINE -
# zpool list -H
foo 1.88G 110K 1.87G - - 0% 0% 1.00x ONLINE -
6. Check that the upgrade aborts
[Where problems could occur: ubuntu-release-upgrader]
The change disables upgrades for all systems with a zpool, regardless of snapshots existing or zpool being on root, this also may include systems that could upgrade successfully.
If the code is wrong it could inadvertently block systems without ZFS
from upgrading, however this seems reasonably mitigated by the test
plan.
[Original bug report]
SUMMARY:
I'm running Ubuntu 24.10 on a ZFS root fs on LUKS which also has snapshots. As part of the release upgrade process ubuntu-release-upgrader is triggering a bug in ZFS triggered by the update-grub steps which executes ls /.zfs/snapshot/… via 10_linux_zfs and eventually causes a kernel deadlock on mount.zfs.
As the `ls` statement in question works flawlessly before the upgrade
process, I assume the hang is caused due to ZoL been replaced by apt
previously? That's why I feel this is a ubuntu-release-upgrader
package bug.
I've reported this bug also upstream at ZoL:
https://github.com/openzfs/zfs/issues/17337
DETAILED DESCRIPTION:
I've failed now 7 time to upgrade my Ubuntu 24.10 to 25.04 (Beta, RC, First Release, Today). In all cases the upgrade runs into a complete system freeze deadlock. `zfs rollback` for the rescue. Today, only using text console with screen & running `dmesg -Hxw`, `htop -d 5` and `do-release-upgrade` in parallel I finally was able to pinpoint the problem:
1. `do-release-upgrade` downloads & install all updated .deb
packages
2. Eventually, the upgrade tries to run `upgrade-grub`
3. The grub script executes the hook `10_linux_zfs` to identify the
available kernel versions for the grub boot menu
4. As part of this discovery an `ls /.zfs/snapshot/[snapshot]/etc`
is executed which causes a system freeze
5. Eventually, after a long pause the kernel reports `task ls:…
blocked for more than 122 seconds.`
6. Only option left for me is to shutdown server and revert to ZFS
snapshot I did before the upgrade
REMARKS:
* Executing "ls /.zfs/snapshot/[snapshot]/etc" and "update-grub" works successfully BEFORE upgrade
* Rebooting into the partial upgraded system, running "strace update-grub" reproduces the problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2110891/+subscriptions
development use so it should not be a problem.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2110891
Title:
System freeze on release upgrade 24.10 oneiric to 25.04 plucky with
root fs on ZFS
Status in linux package in Ubuntu:
Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
Deferred
Status in zfs-linux package in Ubuntu:
Confirmed
Status in linux source package in Plucky:
Confirmed
Status in ubuntu-release-upgrader source package in Plucky:
Fix Released
Status in zfs-linux source package in Plucky:
Confirmed
Bug description:
[Impact]
Upgrades to 25.10 (and newer) fail as the ZFS userspace modules are newer than the kernel modules and there is some incompatibility that can cause the kernel to hang, particularly the bug observes a problem with iterating over the snapshots of the root file system freezing it.
[Test plan: ubuntu-release-upgrader]
1. Create a vm
2. Check that the upgrade doesn't trigger the screen
(no zpool exists)
3. Install zfsutils-linux
4. Check that the upgrade doesn't trigger the screen
(zpool list -H will be empty)
5. Create a zpool, for example in a file
# fallocate /swap -l 2G
# zpool create foo /swap
# zpool list
NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
foo 1.88G 134K 1.87G - - 0% 0% 1.00x ONLINE -
# zpool list -H
foo 1.88G 110K 1.87G - - 0% 0% 1.00x ONLINE -
6. Check that the upgrade aborts
[Where problems could occur: ubuntu-release-upgrader]
The change disables upgrades for all systems with a zpool, regardless of snapshots existing or zpool being on root, this also may include systems that could upgrade successfully.
If the code is wrong it could inadvertently block systems without ZFS
from upgrading, however this seems reasonably mitigated by the test
plan.
[Original bug report]
SUMMARY:
I'm running Ubuntu 24.10 on a ZFS root fs on LUKS which also has snapshots. As part of the release upgrade process ubuntu-release-upgrader is triggering a bug in ZFS triggered by the update-grub steps which executes ls /.zfs/snapshot/… via 10_linux_zfs and eventually causes a kernel deadlock on mount.zfs.
As the `ls` statement in question works flawlessly before the upgrade
process, I assume the hang is caused due to ZoL been replaced by apt
previously? That's why I feel this is a ubuntu-release-upgrader
package bug.
I've reported this bug also upstream at ZoL:
https://github.com/openzfs/zfs/issues/17337
DETAILED DESCRIPTION:
I've failed now 7 time to upgrade my Ubuntu 24.10 to 25.04 (Beta, RC, First Release, Today). In all cases the upgrade runs into a complete system freeze deadlock. `zfs rollback` for the rescue. Today, only using text console with screen & running `dmesg -Hxw`, `htop -d 5` and `do-release-upgrade` in parallel I finally was able to pinpoint the problem:
1. `do-release-upgrade` downloads & install all updated .deb
packages
2. Eventually, the upgrade tries to run `upgrade-grub`
3. The grub script executes the hook `10_linux_zfs` to identify the
available kernel versions for the grub boot menu
4. As part of this discovery an `ls /.zfs/snapshot/[snapshot]/etc`
is executed which causes a system freeze
5. Eventually, after a long pause the kernel reports `task ls:…
blocked for more than 122 seconds.`
6. Only option left for me is to shutdown server and revert to ZFS
snapshot I did before the upgrade
REMARKS:
* Executing "ls /.zfs/snapshot/[snapshot]/etc" and "update-grub" works successfully BEFORE upgrade
* Rebooting into the partial upgraded system, running "strace update-grub" reproduces the problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2110891/+subscriptions
[Bug 2100924] Re: There is a error log for i915 in dmesg and syslog in Ubuntu 24.04.2
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux-firmware (Ubuntu)
Status: Incomplete => 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/2100924
Title:
There is a error log for i915 in dmesg and syslog in Ubuntu 24.04.2
Status in linux package in Ubuntu:
Invalid
Status in linux-firmware package in Ubuntu:
Fix Released
Bug description:
There is a error log for i915 in dmesg and /var/log/syslog:
"""""""""""""""""""""""""""""""""""""""""""""""""""
[ 4.825006] i915 0000:00:02.0: [drm] Found METEORLAKE (device ID 7d51) display version 14.00 stepping D0
[ 4.826686] i915 0000:00:02.0: [drm] VT-d active for gfx access
[ 4.826748] i915 0000:00:02.0: [drm] Using Transparent Hugepages
[ 4.839375] i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=io+mem
[ 4.850434] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/mtl_dmc.bin (v2.21)
[ 4.860494] i915 0000:00:02.0: [drm] GT1: GSC firmware too old for ARL, got 102.0.10.1878 but need at least 102.1.15.1926
[ 4.860503] i915 0000:00:02.0: [drm] *ERROR* GT1: GSC firmware i915/mtl_gsc_1.bin: fetch failed -EINVAL
[ 4.860524] i915 0000:00:02.0: [drm] GT1: GSC firmware(s) can be downloaded from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
[ 4.865190] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/mtl_guc_70.bin version 70.20.0
[ 4.875218] i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
[ 4.875224] i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
[ 4.875445] i915 0000:00:02.0: [drm] GT0: GUC: RC enabled
[ 4.882507] i915 0000:00:02.0: [drm] GT1: GuC firmware i915/mtl_guc_70.bin version 70.20.0
[ 4.882513] i915 0000:00:02.0: [drm] GT1: HuC firmware i915/mtl_huc_gsc.bin version 8.5.4
[ 4.905284] i915 0000:00:02.0: [drm] GT1: HuC: authenticated for clear media
[ 4.905680] i915 0000:00:02.0: [drm] GT1: GUC: submission enabled
[ 4.905682] i915 0000:00:02.0: [drm] GT1: GUC: SLPC enabled
[ 4.905807] i915 0000:00:02.0: [drm] GT1: GUC: RC enabled
[ 4.932807] [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor
"""""""""""""""""""""""""""""""""""""""""""""""""""
After get newer fw pack from https://web.git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/ and get the newer version of "mtl_gsc_1.bin:, it seems like no error on dmesg now:
"""""""""""""""""""""""""""""""""""""""""""""""""""
[ 4.027837] i915 0000:00:02.0: [drm] Found METEORLAKE (device ID 7dd1) display version 14.00 stepping D0
[ 4.029317] i915 0000:00:02.0: [drm] VT-d active for gfx access
[ 4.029356] i915 0000:00:02.0: [drm] Using Transparent Hugepages
[ 4.042454] i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=io+mem
[ 4.051728] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/mtl_dmc.bin (v2.21)
[ 5.935281] i915 0000:00:02.0: [drm] [ENCODER:240:DDI A/PHY A] failed to retrieve link info, disabling eDP
[ 5.952549] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/mtl_guc_70.bin version 70.20.0
[ 5.961933] i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
[ 5.961941] i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
[ 5.962275] i915 0000:00:02.0: [drm] GT0: GUC: RC enabled
[ 5.973946] mei_gsc_proxy 0000:00:16.0-0f73db04-97ab-4125-b893-e904ad0d5464: bound 0000:00:02.0 (ops i915_gsc_proxy_component_ops [i915])
[ 5.974446] i915 0000:00:02.0: [drm] GT1: GuC firmware i915/mtl_guc_70.bin version 70.20.0
[ 5.974451] i915 0000:00:02.0: [drm] GT1: HuC firmware i915/mtl_huc_gsc.bin version 8.5.4
[ 5.997362] i915 0000:00:02.0: [drm] GT1: HuC: authenticated for clear media
[ 5.998714] i915 0000:00:02.0: [drm] GT1: GUC: submission enabled
[ 5.998716] i915 0000:00:02.0: [drm] GT1: GUC: SLPC enabled
[ 5.998927] i915 0000:00:02.0: [drm] GT1: GUC: RC enabled
[ 6.002902] i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initialized
[ 6.011549] [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor 1
[ 6.024290] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
[ 6.045282] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
[ 6.056408] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
[ 6.143809] i915 0000:00:02.0: [drm] GT1: Loaded GSC firmware i915/mtl_gsc_1.bin (cv1.0, r102.1.15.1926, svn 1)
[ 6.164174] i915 0000:00:02.0: [drm] GT1: HuC: authenticated for all workloads
"""""""""""""""""""""""""""""""""""""""""""""""""""
With above test, should i915 use a newer version fw?
If there any info needed, please let me know, thanks.
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw----+ 1 root audio 116, 1 Mar 5 08:33 seq
crw-rw----+ 1 root audio 116, 33 Mar 5 08:33 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2025-03-05 (1 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: Lenovo ThinkEdge SE100 Planar
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-19-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
ProcVersionSignature: Ubuntu 6.11.0-19.19~24.04.1-generic 6.11.11
RelatedPackageVersions:
linux-restricted-modules-6.11.0-19-generic N/A
linux-backports-modules-6.11.0-19-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.9
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
Tags: noble
Uname: Linux 6.11.0-19-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 01/13/2025
dmi.bios.release: 1.10
dmi.bios.vendor: Lenovo
dmi.bios.version: DZE103H-1.10
dmi.board.name: SB27B84847
dmi.board.vendor: Lenovo
dmi.board.version: 04
dmi.chassis.type: 1
dmi.chassis.vendor: Lenovo
dmi.chassis.version: None
dmi.ec.firmware.release: 1.10
dmi.modalias: dmi:bvnLenovo:bvrDZE103H-1.10:bd01/13/2025:br1.10:efr1.10:svnLenovo:pnThinkEdgeSE100Planar:pvr04:rvnLenovo:rnSB27B84847:rvr04:cvnLenovo:ct1:cvrNone:sku7DGRCTO1WW:
dmi.product.family: ThinkSystem
dmi.product.name: ThinkEdge SE100 Planar
dmi.product.sku: 7DGRCTO1WW
dmi.product.version: 04
dmi.sys.vendor: Lenovo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100924/+subscriptions
Status: Confirmed => Invalid
** Changed in: linux-firmware (Ubuntu)
Status: Incomplete => 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/2100924
Title:
There is a error log for i915 in dmesg and syslog in Ubuntu 24.04.2
Status in linux package in Ubuntu:
Invalid
Status in linux-firmware package in Ubuntu:
Fix Released
Bug description:
There is a error log for i915 in dmesg and /var/log/syslog:
"""""""""""""""""""""""""""""""""""""""""""""""""""
[ 4.825006] i915 0000:00:02.0: [drm] Found METEORLAKE (device ID 7d51) display version 14.00 stepping D0
[ 4.826686] i915 0000:00:02.0: [drm] VT-d active for gfx access
[ 4.826748] i915 0000:00:02.0: [drm] Using Transparent Hugepages
[ 4.839375] i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=io+mem
[ 4.850434] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/mtl_dmc.bin (v2.21)
[ 4.860494] i915 0000:00:02.0: [drm] GT1: GSC firmware too old for ARL, got 102.0.10.1878 but need at least 102.1.15.1926
[ 4.860503] i915 0000:00:02.0: [drm] *ERROR* GT1: GSC firmware i915/mtl_gsc_1.bin: fetch failed -EINVAL
[ 4.860524] i915 0000:00:02.0: [drm] GT1: GSC firmware(s) can be downloaded from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
[ 4.865190] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/mtl_guc_70.bin version 70.20.0
[ 4.875218] i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
[ 4.875224] i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
[ 4.875445] i915 0000:00:02.0: [drm] GT0: GUC: RC enabled
[ 4.882507] i915 0000:00:02.0: [drm] GT1: GuC firmware i915/mtl_guc_70.bin version 70.20.0
[ 4.882513] i915 0000:00:02.0: [drm] GT1: HuC firmware i915/mtl_huc_gsc.bin version 8.5.4
[ 4.905284] i915 0000:00:02.0: [drm] GT1: HuC: authenticated for clear media
[ 4.905680] i915 0000:00:02.0: [drm] GT1: GUC: submission enabled
[ 4.905682] i915 0000:00:02.0: [drm] GT1: GUC: SLPC enabled
[ 4.905807] i915 0000:00:02.0: [drm] GT1: GUC: RC enabled
[ 4.932807] [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor
"""""""""""""""""""""""""""""""""""""""""""""""""""
After get newer fw pack from https://web.git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/ and get the newer version of "mtl_gsc_1.bin:, it seems like no error on dmesg now:
"""""""""""""""""""""""""""""""""""""""""""""""""""
[ 4.027837] i915 0000:00:02.0: [drm] Found METEORLAKE (device ID 7dd1) display version 14.00 stepping D0
[ 4.029317] i915 0000:00:02.0: [drm] VT-d active for gfx access
[ 4.029356] i915 0000:00:02.0: [drm] Using Transparent Hugepages
[ 4.042454] i915 0000:00:02.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=io+mem
[ 4.051728] i915 0000:00:02.0: [drm] Finished loading DMC firmware i915/mtl_dmc.bin (v2.21)
[ 5.935281] i915 0000:00:02.0: [drm] [ENCODER:240:DDI A/PHY A] failed to retrieve link info, disabling eDP
[ 5.952549] i915 0000:00:02.0: [drm] GT0: GuC firmware i915/mtl_guc_70.bin version 70.20.0
[ 5.961933] i915 0000:00:02.0: [drm] GT0: GUC: submission enabled
[ 5.961941] i915 0000:00:02.0: [drm] GT0: GUC: SLPC enabled
[ 5.962275] i915 0000:00:02.0: [drm] GT0: GUC: RC enabled
[ 5.973946] mei_gsc_proxy 0000:00:16.0-0f73db04-97ab-4125-b893-e904ad0d5464: bound 0000:00:02.0 (ops i915_gsc_proxy_component_ops [i915])
[ 5.974446] i915 0000:00:02.0: [drm] GT1: GuC firmware i915/mtl_guc_70.bin version 70.20.0
[ 5.974451] i915 0000:00:02.0: [drm] GT1: HuC firmware i915/mtl_huc_gsc.bin version 8.5.4
[ 5.997362] i915 0000:00:02.0: [drm] GT1: HuC: authenticated for clear media
[ 5.998714] i915 0000:00:02.0: [drm] GT1: GUC: submission enabled
[ 5.998716] i915 0000:00:02.0: [drm] GT1: GUC: SLPC enabled
[ 5.998927] i915 0000:00:02.0: [drm] GT1: GUC: RC enabled
[ 6.002902] i915 0000:00:02.0: [drm] Protected Xe Path (PXP) protected content support initialized
[ 6.011549] [drm] Initialized i915 1.6.0 for 0000:00:02.0 on minor 1
[ 6.024290] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
[ 6.045282] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
[ 6.056408] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes
[ 6.143809] i915 0000:00:02.0: [drm] GT1: Loaded GSC firmware i915/mtl_gsc_1.bin (cv1.0, r102.1.15.1926, svn 1)
[ 6.164174] i915 0000:00:02.0: [drm] GT1: HuC: authenticated for all workloads
"""""""""""""""""""""""""""""""""""""""""""""""""""
With above test, should i915 use a newer version fw?
If there any info needed, please let me know, thanks.
---
ProblemType: Bug
AlsaDevices:
total 0
crw-rw----+ 1 root audio 116, 1 Mar 5 08:33 seq
crw-rw----+ 1 root audio 116, 33 Mar 5 08:33 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.28.1-0ubuntu3.3
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer', '/dev/snd/seq'] failed with exit code 1:
CRDA: N/A
CasperMD5CheckResult: pass
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2025-03-05 (1 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: Lenovo ThinkEdge SE100 Planar
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm
ProcFB: 0 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-19-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
ProcVersionSignature: Ubuntu 6.11.0-19.19~24.04.1-generic 6.11.11
RelatedPackageVersions:
linux-restricted-modules-6.11.0-19-generic N/A
linux-backports-modules-6.11.0-19-generic N/A
linux-firmware 20240318.git3b128b60-0ubuntu2.9
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
Tags: noble
Uname: Linux 6.11.0-19-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 01/13/2025
dmi.bios.release: 1.10
dmi.bios.vendor: Lenovo
dmi.bios.version: DZE103H-1.10
dmi.board.name: SB27B84847
dmi.board.vendor: Lenovo
dmi.board.version: 04
dmi.chassis.type: 1
dmi.chassis.vendor: Lenovo
dmi.chassis.version: None
dmi.ec.firmware.release: 1.10
dmi.modalias: dmi:bvnLenovo:bvrDZE103H-1.10:bd01/13/2025:br1.10:efr1.10:svnLenovo:pnThinkEdgeSE100Planar:pvr04:rvnLenovo:rnSB27B84847:rvr04:cvnLenovo:ct1:cvrNone:sku7DGRCTO1WW:
dmi.product.family: ThinkSystem
dmi.product.name: ThinkEdge SE100 Planar
dmi.product.sku: 7DGRCTO1WW
dmi.product.version: 04
dmi.sys.vendor: Lenovo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2100924/+subscriptions
[Bug 2109343] Re: Intel(R) Wireless-AC 9461 doesnt load in 6.14
I'm going to close this bug as invalid for linux-firmware. Please reopen
it if you're still seeing issues.
** Changed in: linux-firmware (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux-firmware (Ubuntu Plucky)
Status: Confirmed => Invalid
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2109343
Title:
Intel(R) Wireless-AC 9461 doesnt load in 6.14
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux source package in Plucky:
Fix Released
Status in linux-firmware source package in Plucky:
Invalid
Bug description:
iwlwifi driver not loading
it works fine in kernel 6.12
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: linux-modules-6.14.0-1002-realtime 6.14.0-1002.2
ProcVersionSignature: Ubuntu 6.14.0-1002.2-realtime 6.14.0
Uname: Linux 6.14.0-1002-realtime x86_64
ApportVersion: 2.32.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: bret 1786 F.... wireplumber
/dev/snd/seq: bret 1783 F.... pipewire
CasperMD5CheckMismatches: ./pool/main/l/linux/linux-modules-extra-6.12.0-16-generic_6.12.0-16.16_amd64.deb
CasperMD5CheckResult: fail
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 25 12:44:17 2025
Dependencies:
InstallationDate: Installed on 2025-03-03 (53 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Daily amd64 (20250302)
MachineType: Crusaders Corporate (Pty) Ltd DNLP1502
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-1002-realtime root=UUID=8b090781-9885-42ec-b482-42b1b1c61005 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.14.0-1002-realtime N/A
linux-backports-modules-6.14.0-1002-realtime N/A
linux-firmware 20250317.git1d4c88ee-0ubuntu1
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux-realtime
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/10/2023
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: HQ-BI-15.6-T140ANR100-034-B
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: Shenzhen WEIBU Information Co.,Ltd
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.ec.firmware.release: 1.2
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrHQ-BI-15.6-T140ANR100-034-B:bd08/10/2023:br5.27:efr1.2:svnCrusadersCorporate(Pty)Ltd:pnDNLP1502:pvrDefaultstring:rvnShenzhenWEIBUInformationCo.,Ltd:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuAlderLake-N:
dmi.product.family: Alder Lake
dmi.product.name: DNLP1502
dmi.product.sku: AlderLake-N
dmi.product.version: Default string
dmi.sys.vendor: Crusaders Corporate (Pty) Ltd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2109343/+subscriptions
it if you're still seeing issues.
** Changed in: linux-firmware (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux-firmware (Ubuntu Plucky)
Status: Confirmed => Invalid
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2109343
Title:
Intel(R) Wireless-AC 9461 doesnt load in 6.14
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux source package in Plucky:
Fix Released
Status in linux-firmware source package in Plucky:
Invalid
Bug description:
iwlwifi driver not loading
it works fine in kernel 6.12
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: linux-modules-6.14.0-1002-realtime 6.14.0-1002.2
ProcVersionSignature: Ubuntu 6.14.0-1002.2-realtime 6.14.0
Uname: Linux 6.14.0-1002-realtime x86_64
ApportVersion: 2.32.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: bret 1786 F.... wireplumber
/dev/snd/seq: bret 1783 F.... pipewire
CasperMD5CheckMismatches: ./pool/main/l/linux/linux-modules-extra-6.12.0-16-generic_6.12.0-16.16_amd64.deb
CasperMD5CheckResult: fail
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 25 12:44:17 2025
Dependencies:
InstallationDate: Installed on 2025-03-03 (53 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Daily amd64 (20250302)
MachineType: Crusaders Corporate (Pty) Ltd DNLP1502
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-1002-realtime root=UUID=8b090781-9885-42ec-b482-42b1b1c61005 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.14.0-1002-realtime N/A
linux-backports-modules-6.14.0-1002-realtime N/A
linux-firmware 20250317.git1d4c88ee-0ubuntu1
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux-realtime
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/10/2023
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: HQ-BI-15.6-T140ANR100-034-B
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: Shenzhen WEIBU Information Co.,Ltd
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.ec.firmware.release: 1.2
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrHQ-BI-15.6-T140ANR100-034-B:bd08/10/2023:br5.27:efr1.2:svnCrusadersCorporate(Pty)Ltd:pnDNLP1502:pvrDefaultstring:rvnShenzhenWEIBUInformationCo.,Ltd:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuAlderLake-N:
dmi.product.family: Alder Lake
dmi.product.name: DNLP1502
dmi.product.sku: AlderLake-N
dmi.product.version: Default string
dmi.sys.vendor: Crusaders Corporate (Pty) Ltd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2109343/+subscriptions
[Bug 2098457] Re: Enable AMD ACP70/ACP71 and relevant soundwire support
Tested on the following platforms, on 6.14-oem -1016, with the steps in
the description. Confirmed that audio is functional:
1. TRD4-DVT-A2X-HP1
2. TRD6-DVT-A2
3. TRD6-DVT-A3
** Tags removed: verification-needed-noble-linux-oem-6.14
** Tags added: verification-done-noble-linux-oem-6.14
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2098457
Title:
Enable AMD ACP70/ACP71 and relevant soundwire support
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.11 package in Ubuntu:
New
Status in linux-oem-6.14 package in Ubuntu:
New
Status in linux source package in Noble:
Won't Fix
Status in linux-oem-6.11 source package in Noble:
Fix Released
Status in linux-oem-6.14 source package in Noble:
Fix Committed
Status in linux source package in Oracular:
Won't Fix
Status in linux-oem-6.11 source package in Oracular:
New
Status in linux-oem-6.14 source package in Oracular:
New
Status in linux source package in Plucky:
In Progress
Status in linux-oem-6.11 source package in Plucky:
New
Status in linux-oem-6.14 source package in Plucky:
New
Bug description:
[ Impact ]
This introduces support for the ACP70/ACP71 audio co-processors, as
well as soundwire related integration. The main patchesets are:
1. [PATCH V3 00/25] ASoC: amd: Add support for ACP7.0 & ACP7.1 platforms[1]
2. [PATCH V4 0/6] soundwire: amd: code improvements and new platform support[2]
3. [PATCH] ASoC: amd: ps: use switch statements for acp pci revision id check[3]
As well as their dependent patches.
[1] https://lore.kernel.org/alsa-devel/173946420611.270661.6294707599627839150.b4-ty@kernel.org/T/#mc726945cf0e97d7cbbc5a9dda3b33d42779ed3af
[2] https://lore.kernel.org/alsa-devel/173920500520.65690.5365981028345549480.b4-ty@kernel.org/T/#m2d7a2b3b128813a2ee5fc45c8d31982c5f2d709c
[3] https://lore.kernel.org/alsa-devel/173945697146.151957.15841988796176463409.b4-ty@kernel.org/T/#m778380541979c1bb1f8bf5863e8a30015289b067
[ Test ]
1. Test record/playback of built-in mic and speakers by, say, recording and playing the speaker test sound in the gnome control center.
2. Connect to headphones and test playback and recording.
3. Suspend the machine and test 1. and 2. again.
4. Test the above 3 on a ACP63 machine.
[ Where the problems could occur ]
Most of the codes are AMD-specific. However, those patches contain
refactors to the existing ACP63 codes. Errors in those refactoring may
impact existing ACP63 platforms.
The patch "[PATCH V3 19/25] ASoC: amd: ps: update file description and
copyright year"[3] didn't get backported, because it conflicted due to
the recent MODULE_IMPORT_NS() API change in cdd30ebb1b9f (module:
Convert symbol namespace to string literal). This patch only change
the module description and doesn't have real functional impact, so was
not pulled in.
[3] https://lore.kernel.org/alsa-
devel/173920500520.65690.5365981028345549480.b4-ty@kernel.org/T/#m39948f8b75ae43055b55a0ccc4dbec66de1eb269
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2098457/+subscriptions
the description. Confirmed that audio is functional:
1. TRD4-DVT-A2X-HP1
2. TRD6-DVT-A2
3. TRD6-DVT-A3
** Tags removed: verification-needed-noble-linux-oem-6.14
** Tags added: verification-done-noble-linux-oem-6.14
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2098457
Title:
Enable AMD ACP70/ACP71 and relevant soundwire support
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.11 package in Ubuntu:
New
Status in linux-oem-6.14 package in Ubuntu:
New
Status in linux source package in Noble:
Won't Fix
Status in linux-oem-6.11 source package in Noble:
Fix Released
Status in linux-oem-6.14 source package in Noble:
Fix Committed
Status in linux source package in Oracular:
Won't Fix
Status in linux-oem-6.11 source package in Oracular:
New
Status in linux-oem-6.14 source package in Oracular:
New
Status in linux source package in Plucky:
In Progress
Status in linux-oem-6.11 source package in Plucky:
New
Status in linux-oem-6.14 source package in Plucky:
New
Bug description:
[ Impact ]
This introduces support for the ACP70/ACP71 audio co-processors, as
well as soundwire related integration. The main patchesets are:
1. [PATCH V3 00/25] ASoC: amd: Add support for ACP7.0 & ACP7.1 platforms[1]
2. [PATCH V4 0/6] soundwire: amd: code improvements and new platform support[2]
3. [PATCH] ASoC: amd: ps: use switch statements for acp pci revision id check[3]
As well as their dependent patches.
[1] https://lore.kernel.org/alsa-devel/173946420611.270661.6294707599627839150.b4-ty@kernel.org/T/#mc726945cf0e97d7cbbc5a9dda3b33d42779ed3af
[2] https://lore.kernel.org/alsa-devel/173920500520.65690.5365981028345549480.b4-ty@kernel.org/T/#m2d7a2b3b128813a2ee5fc45c8d31982c5f2d709c
[3] https://lore.kernel.org/alsa-devel/173945697146.151957.15841988796176463409.b4-ty@kernel.org/T/#m778380541979c1bb1f8bf5863e8a30015289b067
[ Test ]
1. Test record/playback of built-in mic and speakers by, say, recording and playing the speaker test sound in the gnome control center.
2. Connect to headphones and test playback and recording.
3. Suspend the machine and test 1. and 2. again.
4. Test the above 3 on a ACP63 machine.
[ Where the problems could occur ]
Most of the codes are AMD-specific. However, those patches contain
refactors to the existing ACP63 codes. Errors in those refactoring may
impact existing ACP63 platforms.
The patch "[PATCH V3 19/25] ASoC: amd: ps: update file description and
copyright year"[3] didn't get backported, because it conflicted due to
the recent MODULE_IMPORT_NS() API change in cdd30ebb1b9f (module:
Convert symbol namespace to string literal). This patch only change
the module description and doesn't have real functional impact, so was
not pulled in.
[3] https://lore.kernel.org/alsa-
devel/173920500520.65690.5365981028345549480.b4-ty@kernel.org/T/#m39948f8b75ae43055b55a0ccc4dbec66de1eb269
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2098457/+subscriptions
[Bug 2111521] Re: nvme no longer detected on boot after upgrade to 6.8.0-60
@Marks,
Could you help test a new kernel, the kernel applied the patch below as
requested by community, and help collect dmesg with "dyndbg="file
drivers/pci/* +p", thanks.
https://people.canonical.com/~hwang4/lp2111521/test13/
diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
index 9e42090fb108..86012399597e 100644
--- a/drivers/pci/pci.c
+++ b/drivers/pci/pci.c
@@ -1264,10 +1264,13 @@ void pci_resume_bus(struct pci_bus *bus)
static int pci_dev_wait(struct pci_dev *dev, char *reset_type, int timeout)
{
- int delay = 1;
+ int delay = 10;
bool retrain = false;
struct pci_dev *root, *bridge;
+ u16 devctl, devsta;
+ pci_info(dev, "%s: VF%c %s timeout %d\n", __func__,
+ dev->is_virtfn ? '+' : '-', reset_type, timeout);
root = pcie_find_root_port(dev);
if (pci_is_pcie(dev)) {
@@ -1276,6 +1279,19 @@ static int pci_dev_wait(struct pci_dev *dev, char *reset_type, int timeout)
retrain = true;
}
+ if (root) {
+ pcie_capability_read_word(root, PCI_EXP_DEVCTL, &devctl);
+ if (!(devctl & PCI_EXP_DEVCTL_URRE))
+ pcie_capability_write_word(root, PCI_EXP_DEVCTL,
+ devctl | PCI_EXP_DEVCTL_URRE);
+ pcie_capability_read_word(root, PCI_EXP_DEVSTA, &devsta);
+ if (devsta & PCI_EXP_DEVSTA_URD)
+ pcie_capability_write_word(root, PCI_EXP_DEVSTA,
+ PCI_EXP_DEVSTA_URD);
+ pci_info(root, "%s: DEVCTL %#06x DEVSTA %#06x\n", __func__,
+ devctl, devsta);
+ }
+
/*
* The caller has already waited long enough after a reset that the
* device should respond to config requests, but it may respond
@@ -1305,14 +1321,33 @@ static int pci_dev_wait(struct pci_dev *dev, char *reset_type, int timeout)
if (root && root->config_rrs_sv) {
pci_read_config_dword(dev, PCI_VENDOR_ID, &id);
- if (!pci_bus_rrs_vendor_id(id))
- break;
+
+ if (pci_bus_rrs_vendor_id(id)) {
+ pci_info(dev, "%s: read %#06x (RRS)\n",
+ __func__, id);
+ goto retry;
+ }
+
+ if (PCI_POSSIBLE_ERROR(id)) {
+ pcie_capability_read_word(root, PCI_EXP_DEVSTA,
+ &devsta);
+ if (devsta & PCI_EXP_DEVSTA_URD)
+ pcie_capability_write_word(root,
+ PCI_EXP_DEVSTA,
+ PCI_EXP_DEVSTA_URD);
+ pci_info(root, "%s: read %#06x DEVSTA %#06x\n",
+ __func__, id, devsta);
+ goto retry;
+ }
+
+ break;
} else {
pci_read_config_dword(dev, PCI_COMMAND, &id);
if (!PCI_POSSIBLE_ERROR(id))
break;
}
+retry:
if (delay > timeout) {
pci_warn(dev, "not ready %dms after %s; giving up\n",
delay - 1, reset_type);
@@ -1332,7 +1367,6 @@ static int pci_dev_wait(struct pci_dev *dev, char *reset_type, int timeout)
}
msleep(delay);
- delay *= 2;
}
if (delay > PCI_RESET_WAIT)
@@ -4671,8 +4705,10 @@ static int pcie_wait_for_link_status(struct pci_dev *pdev,
end_jiffies = jiffies + msecs_to_jiffies(PCIE_LINK_RETRAIN_TIMEOUT_MS);
do {
pcie_capability_read_word(pdev, PCI_EXP_LNKSTA, &lnksta);
- if ((lnksta & lnksta_mask) == lnksta_match)
+ if ((lnksta & lnksta_mask) == lnksta_match) {
+ pci_info(pdev, "%s: LNKSTA %#06x\n", __func__, lnksta);
return 0;
+ }
msleep(1);
} while (time_before(jiffies, end_jiffies));
@@ -4761,6 +4797,8 @@ static bool pcie_wait_for_link_delay(struct pci_dev *pdev, bool active,
* Some controllers might not implement link active reporting. In this
* case, we wait for 1000 ms + any delay requested by the caller.
*/
+ pci_info(pdev, "%s: active %d delay %d link_active_reporting %d\n",
+ __func__, active, delay, pdev->link_active_reporting);
if (!pdev->link_active_reporting) {
msleep(PCIE_LINK_RETRAIN_TIMEOUT_MS + delay);
return true;
@@ -4785,6 +4823,7 @@ static bool pcie_wait_for_link_delay(struct pci_dev *pdev, bool active,
return false;
msleep(delay);
+ pci_info(pdev, "%s: waited %dms\n", __func__, delay);
return true;
}
@@ -4961,6 +5000,7 @@ void pci_reset_secondary_bus(struct pci_dev *dev)
ctrl &= ~PCI_BRIDGE_CTL_BUS_RESET;
pci_write_config_word(dev, PCI_BRIDGE_CONTROL, ctrl);
+ pci_info(dev, "%s: PCI_BRIDGE_CTL_BUS_RESET deasserted\n", __func__);
}
void __weak pcibios_reset_secondary_bus(struct pci_dev *dev)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2111521
Title:
nvme no longer detected on boot after upgrade to 6.8.0-60
Status in linux package in Ubuntu:
Triaged
Bug description:
Short version: booting 6.8.0-59-generic or any earlier version from
the grub menu works; 6.8.0-60-generic dumps me at the initramfs prompt
with no disks.
We have some servers running Ubuntu 24.04.2 LTS. They have NVME
solid-state disks which (in a working kernel) are detected as follows:
[ 3.537968] nvme nvme0: pci function 10000:01:00.0
[ 3.539285] nvme 10000:01:00.0: PCI INT A: no GSI
[ 5.897819] nvme nvme0: 32/0/0 default/read/poll queues
[ 5.905451] nvme nvme0: Ignoring bogus Namespace Identifiers
[ 5.909057] nvme0n1: p1 p2 p3
On the PCI bus they look like this:
10000:01:00.0 Non-Volatile memory controller [0108]: Intel Corporation NVMe Datacenter SSD [3DNAND, Beta Rock Controller] [8086:0a54]
$ ls -l /sys/class/nvme/nvme0
lrwxrwxrwx 1 root root 0 May 22 16:56 /sys/class/nvme/nvme0 -> ../../devices/pci0000:d7/0000:d7:05.5/pci10000:00/10000:00:02.0/10000:01:00.0/nvme/nvme0
Four identical servers updated their kernel this morning to:
ii linux-image-6.8.0-60-generic 6.8.0-60.63 amd64 Signed kernel image generic
...and rebooted. All four failed to come up and ended up at the
(initramfs) prompt. Rebooting and selecting 6.8.0-59-generic from the
grub menu allowed them to boot as normal.
There is no sign that the initramfs generation went wrong (on all four
servers) and the initramfs does contain all the same nvme modules for
-60 that the one for -59 does. I am at a loss to explain this, and
the initramfs environment is a bit limited for debugging.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2111521/+subscriptions
Could you help test a new kernel, the kernel applied the patch below as
requested by community, and help collect dmesg with "dyndbg="file
drivers/pci/* +p", thanks.
https://people.canonical.com/~hwang4/lp2111521/test13/
diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
index 9e42090fb108..86012399597e 100644
--- a/drivers/pci/pci.c
+++ b/drivers/pci/pci.c
@@ -1264,10 +1264,13 @@ void pci_resume_bus(struct pci_bus *bus)
static int pci_dev_wait(struct pci_dev *dev, char *reset_type, int timeout)
{
- int delay = 1;
+ int delay = 10;
bool retrain = false;
struct pci_dev *root, *bridge;
+ u16 devctl, devsta;
+ pci_info(dev, "%s: VF%c %s timeout %d\n", __func__,
+ dev->is_virtfn ? '+' : '-', reset_type, timeout);
root = pcie_find_root_port(dev);
if (pci_is_pcie(dev)) {
@@ -1276,6 +1279,19 @@ static int pci_dev_wait(struct pci_dev *dev, char *reset_type, int timeout)
retrain = true;
}
+ if (root) {
+ pcie_capability_read_word(root, PCI_EXP_DEVCTL, &devctl);
+ if (!(devctl & PCI_EXP_DEVCTL_URRE))
+ pcie_capability_write_word(root, PCI_EXP_DEVCTL,
+ devctl | PCI_EXP_DEVCTL_URRE);
+ pcie_capability_read_word(root, PCI_EXP_DEVSTA, &devsta);
+ if (devsta & PCI_EXP_DEVSTA_URD)
+ pcie_capability_write_word(root, PCI_EXP_DEVSTA,
+ PCI_EXP_DEVSTA_URD);
+ pci_info(root, "%s: DEVCTL %#06x DEVSTA %#06x\n", __func__,
+ devctl, devsta);
+ }
+
/*
* The caller has already waited long enough after a reset that the
* device should respond to config requests, but it may respond
@@ -1305,14 +1321,33 @@ static int pci_dev_wait(struct pci_dev *dev, char *reset_type, int timeout)
if (root && root->config_rrs_sv) {
pci_read_config_dword(dev, PCI_VENDOR_ID, &id);
- if (!pci_bus_rrs_vendor_id(id))
- break;
+
+ if (pci_bus_rrs_vendor_id(id)) {
+ pci_info(dev, "%s: read %#06x (RRS)\n",
+ __func__, id);
+ goto retry;
+ }
+
+ if (PCI_POSSIBLE_ERROR(id)) {
+ pcie_capability_read_word(root, PCI_EXP_DEVSTA,
+ &devsta);
+ if (devsta & PCI_EXP_DEVSTA_URD)
+ pcie_capability_write_word(root,
+ PCI_EXP_DEVSTA,
+ PCI_EXP_DEVSTA_URD);
+ pci_info(root, "%s: read %#06x DEVSTA %#06x\n",
+ __func__, id, devsta);
+ goto retry;
+ }
+
+ break;
} else {
pci_read_config_dword(dev, PCI_COMMAND, &id);
if (!PCI_POSSIBLE_ERROR(id))
break;
}
+retry:
if (delay > timeout) {
pci_warn(dev, "not ready %dms after %s; giving up\n",
delay - 1, reset_type);
@@ -1332,7 +1367,6 @@ static int pci_dev_wait(struct pci_dev *dev, char *reset_type, int timeout)
}
msleep(delay);
- delay *= 2;
}
if (delay > PCI_RESET_WAIT)
@@ -4671,8 +4705,10 @@ static int pcie_wait_for_link_status(struct pci_dev *pdev,
end_jiffies = jiffies + msecs_to_jiffies(PCIE_LINK_RETRAIN_TIMEOUT_MS);
do {
pcie_capability_read_word(pdev, PCI_EXP_LNKSTA, &lnksta);
- if ((lnksta & lnksta_mask) == lnksta_match)
+ if ((lnksta & lnksta_mask) == lnksta_match) {
+ pci_info(pdev, "%s: LNKSTA %#06x\n", __func__, lnksta);
return 0;
+ }
msleep(1);
} while (time_before(jiffies, end_jiffies));
@@ -4761,6 +4797,8 @@ static bool pcie_wait_for_link_delay(struct pci_dev *pdev, bool active,
* Some controllers might not implement link active reporting. In this
* case, we wait for 1000 ms + any delay requested by the caller.
*/
+ pci_info(pdev, "%s: active %d delay %d link_active_reporting %d\n",
+ __func__, active, delay, pdev->link_active_reporting);
if (!pdev->link_active_reporting) {
msleep(PCIE_LINK_RETRAIN_TIMEOUT_MS + delay);
return true;
@@ -4785,6 +4823,7 @@ static bool pcie_wait_for_link_delay(struct pci_dev *pdev, bool active,
return false;
msleep(delay);
+ pci_info(pdev, "%s: waited %dms\n", __func__, delay);
return true;
}
@@ -4961,6 +5000,7 @@ void pci_reset_secondary_bus(struct pci_dev *dev)
ctrl &= ~PCI_BRIDGE_CTL_BUS_RESET;
pci_write_config_word(dev, PCI_BRIDGE_CONTROL, ctrl);
+ pci_info(dev, "%s: PCI_BRIDGE_CTL_BUS_RESET deasserted\n", __func__);
}
void __weak pcibios_reset_secondary_bus(struct pci_dev *dev)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2111521
Title:
nvme no longer detected on boot after upgrade to 6.8.0-60
Status in linux package in Ubuntu:
Triaged
Bug description:
Short version: booting 6.8.0-59-generic or any earlier version from
the grub menu works; 6.8.0-60-generic dumps me at the initramfs prompt
with no disks.
We have some servers running Ubuntu 24.04.2 LTS. They have NVME
solid-state disks which (in a working kernel) are detected as follows:
[ 3.537968] nvme nvme0: pci function 10000:01:00.0
[ 3.539285] nvme 10000:01:00.0: PCI INT A: no GSI
[ 5.897819] nvme nvme0: 32/0/0 default/read/poll queues
[ 5.905451] nvme nvme0: Ignoring bogus Namespace Identifiers
[ 5.909057] nvme0n1: p1 p2 p3
On the PCI bus they look like this:
10000:01:00.0 Non-Volatile memory controller [0108]: Intel Corporation NVMe Datacenter SSD [3DNAND, Beta Rock Controller] [8086:0a54]
$ ls -l /sys/class/nvme/nvme0
lrwxrwxrwx 1 root root 0 May 22 16:56 /sys/class/nvme/nvme0 -> ../../devices/pci0000:d7/0000:d7:05.5/pci10000:00/10000:00:02.0/10000:01:00.0/nvme/nvme0
Four identical servers updated their kernel this morning to:
ii linux-image-6.8.0-60-generic 6.8.0-60.63 amd64 Signed kernel image generic
...and rebooted. All four failed to come up and ended up at the
(initramfs) prompt. Rebooting and selecting 6.8.0-59-generic from the
grub menu allowed them to boot as normal.
There is no sign that the initramfs generation went wrong (on all four
servers) and the initramfs does contain all the same nvme modules for
-60 that the one for -59 does. I am at a loss to explain this, and
the initramfs environment is a bit limited for debugging.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2111521/+subscriptions
[Bug 2112518] Re: [AMDGPU] No display during boot on AMDGPU system with Thunderbolt-connected monitor
This bug was fixed in the package linux-firmware -
20240318.git3b128b60-0ubuntu2.14
---------------
linux-firmware (20240318.git3b128b60-0ubuntu2.14) noble; urgency=medium
* Miscellaneous Ubuntu changes
- [Workflow] Switch to pull_request and clean up
* [AMDGPU] No display during boot on AMDGPU system with Thunderbolt-connected monitor (LP: #2112518)
- amdgpu: DMCUB updates for various AMDGPU ASICs
- amdgpu: DMCUB updates for various ASICs
- amdgpu: DMCUB updates for various ASICs
- amdgpu: DMCUB updates for various ASICs
- amdgpu: update dcn 3.5 firmware to 0.1.0.0
- amdgpu: update dcn 3.5 and dcn 3.5.1 firmware to 9.0.27.0
- amdgpu: DMCUB updates for various ASICs
- amdgpu: DMCUB updates for various ASICs
* glxgears -fullscreen has noises on the gear edges on AMD Hawk Point platforms with QHD panel (LP: #2114157)
- amdgpu: DMCUB updates for various AMDGPU ASICs
- amdgpu: DMCUB updates for various AMDGPU ASICs
- amdgpu: update DMCUB to v0.0.222.0 for DCN314
- amdgpu: update DMCUB to v0.0.225.0 for Various AMDGPU Asics
- amdgpu: DMCUB updates for DCN314
- amdgpu: DMCUB updates for various AMDGPU ASICs
- amdgpu: DMCUB updates forvarious AMDGPU ASICs
- amdgpu: update DMCUB to v0.0.232.0 for DCN314 and DCN351
- amdgpu: DMCUB updates forvarious AMDGPU ASICs
- amdgpu: update DMCUB to v9.0.10.0 for DCN351
- amdgpu: update DMCUB to v9.0.10.0 for DCN314
- amdgpu: update dmcub 0.0.246.0 firmware
- amdgpu: DMCUB updates for various AMDGPU ASICs
- amdgpu: revert DMCUB 3.1.4 firmware
- amdgpu: DMCUB updates for various ASICs
- amdgpu: DMCUB updates for various ASICs
- amdgpu: update dcn 3.1.4 firmware to 8.0.78.0
- amdgpu: DMCUB updates for various ASICs
-- Juerg Haefliger <juerg.haefliger@canonical.com> Mon, 16 Jun 2025
10:56:09 +0200
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2112518
Title:
[AMDGPU] No display during boot on AMDGPU system with Thunderbolt-
connected monitor
Status in HWE Next:
New
Status in linux package in Ubuntu:
Won't Fix
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-firmware source package in Noble:
Fix Released
Status in linux-oem-6.14 source package in Noble:
Fix Committed
Status in linux source package in Oracular:
Won't Fix
Status in linux-firmware source package in Oracular:
Won't Fix
Status in linux-oem-6.14 source package in Oracular:
Invalid
Status in linux source package in Plucky:
Won't Fix
Status in linux-firmware source package in Plucky:
Fix Released
Status in linux-oem-6.14 source package in Plucky:
Invalid
Bug description:
SRU Justification:
[Impact]
On HP AMDGPU platform running the 6.14.0-1005-oem kernel, the monitor screen never appeared when booting the system with a Thunderbolt cable connected. However, we were still able to SSH into the system, suggesting that it had booted successfully.
For the Noble and Plucky generic kernels, they have been classified as
"won't fix" since the bug only occurrs on a specific platform. For
users on that platform, we recommend using our Noble 6.14-OEM kernel,
which includes the appropriate fix.
[Fix]
Updates are required for both the Linux AMDGPU driver and the linux-firmware package.
- Linux AMDGPU driver: cherry-pick the following commit from the Linux
mainline:
59510792baa drm/amd/display: Assign preferred stream encoder instance
to dpia
- linux-firmware: backport the following commits from the upstream
linux-firmware repository:
1. b3049665a5d amdgpu: DMCUB updates for various AMDGPU ASICs
2. 61d257d5a8b amdgpu: DMCUB updates for various ASICs
3. 5602c7293e6 amdgpu: DMCUB updates for various ASICs
4. b0e96674082 amdgpu: DMCUB updates for various ASICs
5. a2aaefe5a59 amdgpu: update dcn 3.5 firmware to 0.1.0.0
6. a80a8bd73e0 amdgpu: update dcn 3.5 and dcn 3.5.1 firmware to 9.0.27.0
7. 25750add9b7 amdgpu: DMCUB updates for various ASICs
8. 5ac6303062 amdgpu: DMCUB updates for various ASICs
Be aware that only amdgpu/dcn_3_5_1_dmcub.bin and amdgpu/dcn_3_5_dmcub.bin are updated by the above commits.
Updates to other files were intentionally omitted.
[Test Plan]
========= On Noble 6.14-OEM ==================
- Prerequisites:
1. Install the linux-oem-6.14 version 6.14.0-1006.6 kernel from -proposed [1]
2. Install the linux-firmware version 20240318.git3b128b60-0ubuntu2.14 from -proposed [1]
- Test instructions:
1. Connect the machine to an external monitor using a Thunderbolt cable before booting.
2. Boot the system using the Noble 6.14.0-1005-oem kernel
3. Verify that the display output appears on the monitor and the GNOME desktop environment is visible.
========= On Noble/Plucky generic ==================
- Prerequisites:
1. Install the Noble or Plucky generic kernel
2. If you will be running the Noble generic kernel, please install the linux-firmware version 20240318.git3b128b60-0ubuntu2.14 from -proposed [1]. Otherwise, please install the linux-firmware version 20250317.git1d4c88ee-0ubuntu1.3 from -proposed[1].
- Test instructions:
1. Boot the system using the Noble or Plucky generic kernel
2. Since this bug was intended to be fixed only in the Noble 6.14-OEM kernel, it is expected to still reproduce on the Noble and Plucky generic kernels. Please
test all other functionalities to verify whether there are any regressions.
[Where problems could occur]
We updated the firmware to the latest version, while the Linux AMDGPU driver remains behind the mainline. As a consequence, a mismatch might occur between the Linux AMDGPU driver and the firmware.
[1] See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2112518/+subscriptions
20240318.git3b128b60-0ubuntu2.14
---------------
linux-firmware (20240318.git3b128b60-0ubuntu2.14) noble; urgency=medium
* Miscellaneous Ubuntu changes
- [Workflow] Switch to pull_request and clean up
* [AMDGPU] No display during boot on AMDGPU system with Thunderbolt-connected monitor (LP: #2112518)
- amdgpu: DMCUB updates for various AMDGPU ASICs
- amdgpu: DMCUB updates for various ASICs
- amdgpu: DMCUB updates for various ASICs
- amdgpu: DMCUB updates for various ASICs
- amdgpu: update dcn 3.5 firmware to 0.1.0.0
- amdgpu: update dcn 3.5 and dcn 3.5.1 firmware to 9.0.27.0
- amdgpu: DMCUB updates for various ASICs
- amdgpu: DMCUB updates for various ASICs
* glxgears -fullscreen has noises on the gear edges on AMD Hawk Point platforms with QHD panel (LP: #2114157)
- amdgpu: DMCUB updates for various AMDGPU ASICs
- amdgpu: DMCUB updates for various AMDGPU ASICs
- amdgpu: update DMCUB to v0.0.222.0 for DCN314
- amdgpu: update DMCUB to v0.0.225.0 for Various AMDGPU Asics
- amdgpu: DMCUB updates for DCN314
- amdgpu: DMCUB updates for various AMDGPU ASICs
- amdgpu: DMCUB updates forvarious AMDGPU ASICs
- amdgpu: update DMCUB to v0.0.232.0 for DCN314 and DCN351
- amdgpu: DMCUB updates forvarious AMDGPU ASICs
- amdgpu: update DMCUB to v9.0.10.0 for DCN351
- amdgpu: update DMCUB to v9.0.10.0 for DCN314
- amdgpu: update dmcub 0.0.246.0 firmware
- amdgpu: DMCUB updates for various AMDGPU ASICs
- amdgpu: revert DMCUB 3.1.4 firmware
- amdgpu: DMCUB updates for various ASICs
- amdgpu: DMCUB updates for various ASICs
- amdgpu: update dcn 3.1.4 firmware to 8.0.78.0
- amdgpu: DMCUB updates for various ASICs
-- Juerg Haefliger <juerg.haefliger@canonical.com> Mon, 16 Jun 2025
10:56:09 +0200
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2112518
Title:
[AMDGPU] No display during boot on AMDGPU system with Thunderbolt-
connected monitor
Status in HWE Next:
New
Status in linux package in Ubuntu:
Won't Fix
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-firmware source package in Noble:
Fix Released
Status in linux-oem-6.14 source package in Noble:
Fix Committed
Status in linux source package in Oracular:
Won't Fix
Status in linux-firmware source package in Oracular:
Won't Fix
Status in linux-oem-6.14 source package in Oracular:
Invalid
Status in linux source package in Plucky:
Won't Fix
Status in linux-firmware source package in Plucky:
Fix Released
Status in linux-oem-6.14 source package in Plucky:
Invalid
Bug description:
SRU Justification:
[Impact]
On HP AMDGPU platform running the 6.14.0-1005-oem kernel, the monitor screen never appeared when booting the system with a Thunderbolt cable connected. However, we were still able to SSH into the system, suggesting that it had booted successfully.
For the Noble and Plucky generic kernels, they have been classified as
"won't fix" since the bug only occurrs on a specific platform. For
users on that platform, we recommend using our Noble 6.14-OEM kernel,
which includes the appropriate fix.
[Fix]
Updates are required for both the Linux AMDGPU driver and the linux-firmware package.
- Linux AMDGPU driver: cherry-pick the following commit from the Linux
mainline:
59510792baa drm/amd/display: Assign preferred stream encoder instance
to dpia
- linux-firmware: backport the following commits from the upstream
linux-firmware repository:
1. b3049665a5d amdgpu: DMCUB updates for various AMDGPU ASICs
2. 61d257d5a8b amdgpu: DMCUB updates for various ASICs
3. 5602c7293e6 amdgpu: DMCUB updates for various ASICs
4. b0e96674082 amdgpu: DMCUB updates for various ASICs
5. a2aaefe5a59 amdgpu: update dcn 3.5 firmware to 0.1.0.0
6. a80a8bd73e0 amdgpu: update dcn 3.5 and dcn 3.5.1 firmware to 9.0.27.0
7. 25750add9b7 amdgpu: DMCUB updates for various ASICs
8. 5ac6303062 amdgpu: DMCUB updates for various ASICs
Be aware that only amdgpu/dcn_3_5_1_dmcub.bin and amdgpu/dcn_3_5_dmcub.bin are updated by the above commits.
Updates to other files were intentionally omitted.
[Test Plan]
========= On Noble 6.14-OEM ==================
- Prerequisites:
1. Install the linux-oem-6.14 version 6.14.0-1006.6 kernel from -proposed [1]
2. Install the linux-firmware version 20240318.git3b128b60-0ubuntu2.14 from -proposed [1]
- Test instructions:
1. Connect the machine to an external monitor using a Thunderbolt cable before booting.
2. Boot the system using the Noble 6.14.0-1005-oem kernel
3. Verify that the display output appears on the monitor and the GNOME desktop environment is visible.
========= On Noble/Plucky generic ==================
- Prerequisites:
1. Install the Noble or Plucky generic kernel
2. If you will be running the Noble generic kernel, please install the linux-firmware version 20240318.git3b128b60-0ubuntu2.14 from -proposed [1]. Otherwise, please install the linux-firmware version 20250317.git1d4c88ee-0ubuntu1.3 from -proposed[1].
- Test instructions:
1. Boot the system using the Noble or Plucky generic kernel
2. Since this bug was intended to be fixed only in the Noble 6.14-OEM kernel, it is expected to still reproduce on the Noble and Plucky generic kernels. Please
test all other functionalities to verify whether there are any regressions.
[Where problems could occur]
We updated the firmware to the latest version, while the Linux AMDGPU driver remains behind the mainline. As a consequence, a mismatch might occur between the Linux AMDGPU driver and the firmware.
[1] See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2112518/+subscriptions
[Bug 2112518] Re: [AMDGPU] No display during boot on AMDGPU system with Thunderbolt-connected monitor
This bug was fixed in the package linux-firmware -
20250317.git1d4c88ee-0ubuntu1.3
---------------
linux-firmware (20250317.git1d4c88ee-0ubuntu1.3) plucky; urgency=medium
* Miscellaneous Ubuntu changes
- [Workflow] Switch to pull_request and clean up
* [AMDGPU] No display during boot on AMDGPU system with Thunderbolt-connected monitor (LP: #2112518)
- amdgpu: DMCUB updates for various ASICs
- amdgpu: update dcn 3.5 firmware to 0.1.0.0
- amdgpu: update dcn 3.5 and dcn 3.5.1 firmware to 9.0.27.0
- amdgpu: DMCUB updates for various ASICs
- amdgpu: DMCUB updates for various ASICs
* glxgears -fullscreen has noises on the gear edges on AMD Hawk Point platforms with QHD panel (LP: #2114157)
- amdgpu: update dcn 3.1.4 firmware to 8.0.78.0
- amdgpu: DMCUB updates for various ASICs
-- Juerg Haefliger <juerg.haefliger@canonical.com> Mon, 16 Jun 2025
10:49:14 +0200
** Changed in: linux-firmware (Ubuntu Plucky)
Status: Fix Committed => Fix Released
** Changed in: linux-firmware (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/2112518
Title:
[AMDGPU] No display during boot on AMDGPU system with Thunderbolt-
connected monitor
Status in HWE Next:
New
Status in linux package in Ubuntu:
Won't Fix
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-firmware source package in Noble:
Fix Released
Status in linux-oem-6.14 source package in Noble:
Fix Committed
Status in linux source package in Oracular:
Won't Fix
Status in linux-firmware source package in Oracular:
Won't Fix
Status in linux-oem-6.14 source package in Oracular:
Invalid
Status in linux source package in Plucky:
Won't Fix
Status in linux-firmware source package in Plucky:
Fix Released
Status in linux-oem-6.14 source package in Plucky:
Invalid
Bug description:
SRU Justification:
[Impact]
On HP AMDGPU platform running the 6.14.0-1005-oem kernel, the monitor screen never appeared when booting the system with a Thunderbolt cable connected. However, we were still able to SSH into the system, suggesting that it had booted successfully.
For the Noble and Plucky generic kernels, they have been classified as
"won't fix" since the bug only occurrs on a specific platform. For
users on that platform, we recommend using our Noble 6.14-OEM kernel,
which includes the appropriate fix.
[Fix]
Updates are required for both the Linux AMDGPU driver and the linux-firmware package.
- Linux AMDGPU driver: cherry-pick the following commit from the Linux
mainline:
59510792baa drm/amd/display: Assign preferred stream encoder instance
to dpia
- linux-firmware: backport the following commits from the upstream
linux-firmware repository:
1. b3049665a5d amdgpu: DMCUB updates for various AMDGPU ASICs
2. 61d257d5a8b amdgpu: DMCUB updates for various ASICs
3. 5602c7293e6 amdgpu: DMCUB updates for various ASICs
4. b0e96674082 amdgpu: DMCUB updates for various ASICs
5. a2aaefe5a59 amdgpu: update dcn 3.5 firmware to 0.1.0.0
6. a80a8bd73e0 amdgpu: update dcn 3.5 and dcn 3.5.1 firmware to 9.0.27.0
7. 25750add9b7 amdgpu: DMCUB updates for various ASICs
8. 5ac6303062 amdgpu: DMCUB updates for various ASICs
Be aware that only amdgpu/dcn_3_5_1_dmcub.bin and amdgpu/dcn_3_5_dmcub.bin are updated by the above commits.
Updates to other files were intentionally omitted.
[Test Plan]
========= On Noble 6.14-OEM ==================
- Prerequisites:
1. Install the linux-oem-6.14 version 6.14.0-1006.6 kernel from -proposed [1]
2. Install the linux-firmware version 20240318.git3b128b60-0ubuntu2.14 from -proposed [1]
- Test instructions:
1. Connect the machine to an external monitor using a Thunderbolt cable before booting.
2. Boot the system using the Noble 6.14.0-1005-oem kernel
3. Verify that the display output appears on the monitor and the GNOME desktop environment is visible.
========= On Noble/Plucky generic ==================
- Prerequisites:
1. Install the Noble or Plucky generic kernel
2. If you will be running the Noble generic kernel, please install the linux-firmware version 20240318.git3b128b60-0ubuntu2.14 from -proposed [1]. Otherwise, please install the linux-firmware version 20250317.git1d4c88ee-0ubuntu1.3 from -proposed[1].
- Test instructions:
1. Boot the system using the Noble or Plucky generic kernel
2. Since this bug was intended to be fixed only in the Noble 6.14-OEM kernel, it is expected to still reproduce on the Noble and Plucky generic kernels. Please
test all other functionalities to verify whether there are any regressions.
[Where problems could occur]
We updated the firmware to the latest version, while the Linux AMDGPU driver remains behind the mainline. As a consequence, a mismatch might occur between the Linux AMDGPU driver and the firmware.
[1] See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2112518/+subscriptions
20250317.git1d4c88ee-0ubuntu1.3
---------------
linux-firmware (20250317.git1d4c88ee-0ubuntu1.3) plucky; urgency=medium
* Miscellaneous Ubuntu changes
- [Workflow] Switch to pull_request and clean up
* [AMDGPU] No display during boot on AMDGPU system with Thunderbolt-connected monitor (LP: #2112518)
- amdgpu: DMCUB updates for various ASICs
- amdgpu: update dcn 3.5 firmware to 0.1.0.0
- amdgpu: update dcn 3.5 and dcn 3.5.1 firmware to 9.0.27.0
- amdgpu: DMCUB updates for various ASICs
- amdgpu: DMCUB updates for various ASICs
* glxgears -fullscreen has noises on the gear edges on AMD Hawk Point platforms with QHD panel (LP: #2114157)
- amdgpu: update dcn 3.1.4 firmware to 8.0.78.0
- amdgpu: DMCUB updates for various ASICs
-- Juerg Haefliger <juerg.haefliger@canonical.com> Mon, 16 Jun 2025
10:49:14 +0200
** Changed in: linux-firmware (Ubuntu Plucky)
Status: Fix Committed => Fix Released
** Changed in: linux-firmware (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/2112518
Title:
[AMDGPU] No display during boot on AMDGPU system with Thunderbolt-
connected monitor
Status in HWE Next:
New
Status in linux package in Ubuntu:
Won't Fix
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-firmware source package in Noble:
Fix Released
Status in linux-oem-6.14 source package in Noble:
Fix Committed
Status in linux source package in Oracular:
Won't Fix
Status in linux-firmware source package in Oracular:
Won't Fix
Status in linux-oem-6.14 source package in Oracular:
Invalid
Status in linux source package in Plucky:
Won't Fix
Status in linux-firmware source package in Plucky:
Fix Released
Status in linux-oem-6.14 source package in Plucky:
Invalid
Bug description:
SRU Justification:
[Impact]
On HP AMDGPU platform running the 6.14.0-1005-oem kernel, the monitor screen never appeared when booting the system with a Thunderbolt cable connected. However, we were still able to SSH into the system, suggesting that it had booted successfully.
For the Noble and Plucky generic kernels, they have been classified as
"won't fix" since the bug only occurrs on a specific platform. For
users on that platform, we recommend using our Noble 6.14-OEM kernel,
which includes the appropriate fix.
[Fix]
Updates are required for both the Linux AMDGPU driver and the linux-firmware package.
- Linux AMDGPU driver: cherry-pick the following commit from the Linux
mainline:
59510792baa drm/amd/display: Assign preferred stream encoder instance
to dpia
- linux-firmware: backport the following commits from the upstream
linux-firmware repository:
1. b3049665a5d amdgpu: DMCUB updates for various AMDGPU ASICs
2. 61d257d5a8b amdgpu: DMCUB updates for various ASICs
3. 5602c7293e6 amdgpu: DMCUB updates for various ASICs
4. b0e96674082 amdgpu: DMCUB updates for various ASICs
5. a2aaefe5a59 amdgpu: update dcn 3.5 firmware to 0.1.0.0
6. a80a8bd73e0 amdgpu: update dcn 3.5 and dcn 3.5.1 firmware to 9.0.27.0
7. 25750add9b7 amdgpu: DMCUB updates for various ASICs
8. 5ac6303062 amdgpu: DMCUB updates for various ASICs
Be aware that only amdgpu/dcn_3_5_1_dmcub.bin and amdgpu/dcn_3_5_dmcub.bin are updated by the above commits.
Updates to other files were intentionally omitted.
[Test Plan]
========= On Noble 6.14-OEM ==================
- Prerequisites:
1. Install the linux-oem-6.14 version 6.14.0-1006.6 kernel from -proposed [1]
2. Install the linux-firmware version 20240318.git3b128b60-0ubuntu2.14 from -proposed [1]
- Test instructions:
1. Connect the machine to an external monitor using a Thunderbolt cable before booting.
2. Boot the system using the Noble 6.14.0-1005-oem kernel
3. Verify that the display output appears on the monitor and the GNOME desktop environment is visible.
========= On Noble/Plucky generic ==================
- Prerequisites:
1. Install the Noble or Plucky generic kernel
2. If you will be running the Noble generic kernel, please install the linux-firmware version 20240318.git3b128b60-0ubuntu2.14 from -proposed [1]. Otherwise, please install the linux-firmware version 20250317.git1d4c88ee-0ubuntu1.3 from -proposed[1].
- Test instructions:
1. Boot the system using the Noble or Plucky generic kernel
2. Since this bug was intended to be fixed only in the Noble 6.14-OEM kernel, it is expected to still reproduce on the Noble and Plucky generic kernels. Please
test all other functionalities to verify whether there are any regressions.
[Where problems could occur]
We updated the firmware to the latest version, while the Linux AMDGPU driver remains behind the mainline. As a consequence, a mismatch might occur between the Linux AMDGPU driver and the firmware.
[1] See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2112518/+subscriptions
[Bug 2112518] Update Released
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2112518
Title:
[AMDGPU] No display during boot on AMDGPU system with Thunderbolt-
connected monitor
Status in HWE Next:
New
Status in linux package in Ubuntu:
Won't Fix
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-firmware source package in Noble:
Fix Released
Status in linux-oem-6.14 source package in Noble:
Fix Committed
Status in linux source package in Oracular:
Won't Fix
Status in linux-firmware source package in Oracular:
Won't Fix
Status in linux-oem-6.14 source package in Oracular:
Invalid
Status in linux source package in Plucky:
Won't Fix
Status in linux-firmware source package in Plucky:
Fix Released
Status in linux-oem-6.14 source package in Plucky:
Invalid
Bug description:
SRU Justification:
[Impact]
On HP AMDGPU platform running the 6.14.0-1005-oem kernel, the monitor screen never appeared when booting the system with a Thunderbolt cable connected. However, we were still able to SSH into the system, suggesting that it had booted successfully.
For the Noble and Plucky generic kernels, they have been classified as
"won't fix" since the bug only occurrs on a specific platform. For
users on that platform, we recommend using our Noble 6.14-OEM kernel,
which includes the appropriate fix.
[Fix]
Updates are required for both the Linux AMDGPU driver and the linux-firmware package.
- Linux AMDGPU driver: cherry-pick the following commit from the Linux
mainline:
59510792baa drm/amd/display: Assign preferred stream encoder instance
to dpia
- linux-firmware: backport the following commits from the upstream
linux-firmware repository:
1. b3049665a5d amdgpu: DMCUB updates for various AMDGPU ASICs
2. 61d257d5a8b amdgpu: DMCUB updates for various ASICs
3. 5602c7293e6 amdgpu: DMCUB updates for various ASICs
4. b0e96674082 amdgpu: DMCUB updates for various ASICs
5. a2aaefe5a59 amdgpu: update dcn 3.5 firmware to 0.1.0.0
6. a80a8bd73e0 amdgpu: update dcn 3.5 and dcn 3.5.1 firmware to 9.0.27.0
7. 25750add9b7 amdgpu: DMCUB updates for various ASICs
8. 5ac6303062 amdgpu: DMCUB updates for various ASICs
Be aware that only amdgpu/dcn_3_5_1_dmcub.bin and amdgpu/dcn_3_5_dmcub.bin are updated by the above commits.
Updates to other files were intentionally omitted.
[Test Plan]
========= On Noble 6.14-OEM ==================
- Prerequisites:
1. Install the linux-oem-6.14 version 6.14.0-1006.6 kernel from -proposed [1]
2. Install the linux-firmware version 20240318.git3b128b60-0ubuntu2.14 from -proposed [1]
- Test instructions:
1. Connect the machine to an external monitor using a Thunderbolt cable before booting.
2. Boot the system using the Noble 6.14.0-1005-oem kernel
3. Verify that the display output appears on the monitor and the GNOME desktop environment is visible.
========= On Noble/Plucky generic ==================
- Prerequisites:
1. Install the Noble or Plucky generic kernel
2. If you will be running the Noble generic kernel, please install the linux-firmware version 20240318.git3b128b60-0ubuntu2.14 from -proposed [1]. Otherwise, please install the linux-firmware version 20250317.git1d4c88ee-0ubuntu1.3 from -proposed[1].
- Test instructions:
1. Boot the system using the Noble or Plucky generic kernel
2. Since this bug was intended to be fixed only in the Noble 6.14-OEM kernel, it is expected to still reproduce on the Noble and Plucky generic kernels. Please
test all other functionalities to verify whether there are any regressions.
[Where problems could occur]
We updated the firmware to the latest version, while the Linux AMDGPU driver remains behind the mainline. As a consequence, a mismatch might occur between the Linux AMDGPU driver and the firmware.
[1] See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2112518/+subscriptions
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2112518
Title:
[AMDGPU] No display during boot on AMDGPU system with Thunderbolt-
connected monitor
Status in HWE Next:
New
Status in linux package in Ubuntu:
Won't Fix
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-firmware source package in Noble:
Fix Released
Status in linux-oem-6.14 source package in Noble:
Fix Committed
Status in linux source package in Oracular:
Won't Fix
Status in linux-firmware source package in Oracular:
Won't Fix
Status in linux-oem-6.14 source package in Oracular:
Invalid
Status in linux source package in Plucky:
Won't Fix
Status in linux-firmware source package in Plucky:
Fix Released
Status in linux-oem-6.14 source package in Plucky:
Invalid
Bug description:
SRU Justification:
[Impact]
On HP AMDGPU platform running the 6.14.0-1005-oem kernel, the monitor screen never appeared when booting the system with a Thunderbolt cable connected. However, we were still able to SSH into the system, suggesting that it had booted successfully.
For the Noble and Plucky generic kernels, they have been classified as
"won't fix" since the bug only occurrs on a specific platform. For
users on that platform, we recommend using our Noble 6.14-OEM kernel,
which includes the appropriate fix.
[Fix]
Updates are required for both the Linux AMDGPU driver and the linux-firmware package.
- Linux AMDGPU driver: cherry-pick the following commit from the Linux
mainline:
59510792baa drm/amd/display: Assign preferred stream encoder instance
to dpia
- linux-firmware: backport the following commits from the upstream
linux-firmware repository:
1. b3049665a5d amdgpu: DMCUB updates for various AMDGPU ASICs
2. 61d257d5a8b amdgpu: DMCUB updates for various ASICs
3. 5602c7293e6 amdgpu: DMCUB updates for various ASICs
4. b0e96674082 amdgpu: DMCUB updates for various ASICs
5. a2aaefe5a59 amdgpu: update dcn 3.5 firmware to 0.1.0.0
6. a80a8bd73e0 amdgpu: update dcn 3.5 and dcn 3.5.1 firmware to 9.0.27.0
7. 25750add9b7 amdgpu: DMCUB updates for various ASICs
8. 5ac6303062 amdgpu: DMCUB updates for various ASICs
Be aware that only amdgpu/dcn_3_5_1_dmcub.bin and amdgpu/dcn_3_5_dmcub.bin are updated by the above commits.
Updates to other files were intentionally omitted.
[Test Plan]
========= On Noble 6.14-OEM ==================
- Prerequisites:
1. Install the linux-oem-6.14 version 6.14.0-1006.6 kernel from -proposed [1]
2. Install the linux-firmware version 20240318.git3b128b60-0ubuntu2.14 from -proposed [1]
- Test instructions:
1. Connect the machine to an external monitor using a Thunderbolt cable before booting.
2. Boot the system using the Noble 6.14.0-1005-oem kernel
3. Verify that the display output appears on the monitor and the GNOME desktop environment is visible.
========= On Noble/Plucky generic ==================
- Prerequisites:
1. Install the Noble or Plucky generic kernel
2. If you will be running the Noble generic kernel, please install the linux-firmware version 20240318.git3b128b60-0ubuntu2.14 from -proposed [1]. Otherwise, please install the linux-firmware version 20250317.git1d4c88ee-0ubuntu1.3 from -proposed[1].
- Test instructions:
1. Boot the system using the Noble or Plucky generic kernel
2. Since this bug was intended to be fixed only in the Noble 6.14-OEM kernel, it is expected to still reproduce on the Noble and Plucky generic kernels. Please
test all other functionalities to verify whether there are any regressions.
[Where problems could occur]
We updated the firmware to the latest version, while the Linux AMDGPU driver remains behind the mainline. As a consequence, a mismatch might occur between the Linux AMDGPU driver and the firmware.
[1] See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2112518/+subscriptions
[Bug 2112518] Re: [AMDGPU] No display during boot on AMDGPU system with Thunderbolt-connected monitor
Hi @juliank, thank you for the heads-up.
I just ran a test using Plucky linux-image-6.14.0-24-generic and linux-
firmware 20250317.git1d4c88ee-0ubuntu1.3, there is no regression. Update
the tag to verification-done-plucky accordingly.
** Tags removed: verification-needed-plucky
** Tags added: verification-done-plucky
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2112518
Title:
[AMDGPU] No display during boot on AMDGPU system with Thunderbolt-
connected monitor
Status in HWE Next:
New
Status in linux package in Ubuntu:
Won't Fix
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-oem-6.14 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.14 source package in Noble:
Fix Committed
Status in linux source package in Oracular:
Won't Fix
Status in linux-firmware source package in Oracular:
Won't Fix
Status in linux-oem-6.14 source package in Oracular:
Invalid
Status in linux source package in Plucky:
Won't Fix
Status in linux-firmware source package in Plucky:
Fix Committed
Status in linux-oem-6.14 source package in Plucky:
Invalid
Bug description:
SRU Justification:
[Impact]
On HP AMDGPU platform running the 6.14.0-1005-oem kernel, the monitor screen never appeared when booting the system with a Thunderbolt cable connected. However, we were still able to SSH into the system, suggesting that it had booted successfully.
For the Noble and Plucky generic kernels, they have been classified as
"won't fix" since the bug only occurrs on a specific platform. For
users on that platform, we recommend using our Noble 6.14-OEM kernel,
which includes the appropriate fix.
[Fix]
Updates are required for both the Linux AMDGPU driver and the linux-firmware package.
- Linux AMDGPU driver: cherry-pick the following commit from the Linux
mainline:
59510792baa drm/amd/display: Assign preferred stream encoder instance
to dpia
- linux-firmware: backport the following commits from the upstream
linux-firmware repository:
1. b3049665a5d amdgpu: DMCUB updates for various AMDGPU ASICs
2. 61d257d5a8b amdgpu: DMCUB updates for various ASICs
3. 5602c7293e6 amdgpu: DMCUB updates for various ASICs
4. b0e96674082 amdgpu: DMCUB updates for various ASICs
5. a2aaefe5a59 amdgpu: update dcn 3.5 firmware to 0.1.0.0
6. a80a8bd73e0 amdgpu: update dcn 3.5 and dcn 3.5.1 firmware to 9.0.27.0
7. 25750add9b7 amdgpu: DMCUB updates for various ASICs
8. 5ac6303062 amdgpu: DMCUB updates for various ASICs
Be aware that only amdgpu/dcn_3_5_1_dmcub.bin and amdgpu/dcn_3_5_dmcub.bin are updated by the above commits.
Updates to other files were intentionally omitted.
[Test Plan]
========= On Noble 6.14-OEM ==================
- Prerequisites:
1. Install the linux-oem-6.14 version 6.14.0-1006.6 kernel from -proposed [1]
2. Install the linux-firmware version 20240318.git3b128b60-0ubuntu2.14 from -proposed [1]
- Test instructions:
1. Connect the machine to an external monitor using a Thunderbolt cable before booting.
2. Boot the system using the Noble 6.14.0-1005-oem kernel
3. Verify that the display output appears on the monitor and the GNOME desktop environment is visible.
========= On Noble/Plucky generic ==================
- Prerequisites:
1. Install the Noble or Plucky generic kernel
2. If you will be running the Noble generic kernel, please install the linux-firmware version 20240318.git3b128b60-0ubuntu2.14 from -proposed [1]. Otherwise, please install the linux-firmware version 20250317.git1d4c88ee-0ubuntu1.3 from -proposed[1].
- Test instructions:
1. Boot the system using the Noble or Plucky generic kernel
2. Since this bug was intended to be fixed only in the Noble 6.14-OEM kernel, it is expected to still reproduce on the Noble and Plucky generic kernels. Please
test all other functionalities to verify whether there are any regressions.
[Where problems could occur]
We updated the firmware to the latest version, while the Linux AMDGPU driver remains behind the mainline. As a consequence, a mismatch might occur between the Linux AMDGPU driver and the firmware.
[1] See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2112518/+subscriptions
I just ran a test using Plucky linux-image-6.14.0-24-generic and linux-
firmware 20250317.git1d4c88ee-0ubuntu1.3, there is no regression. Update
the tag to verification-done-plucky accordingly.
** Tags removed: verification-needed-plucky
** Tags added: verification-done-plucky
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2112518
Title:
[AMDGPU] No display during boot on AMDGPU system with Thunderbolt-
connected monitor
Status in HWE Next:
New
Status in linux package in Ubuntu:
Won't Fix
Status in linux-firmware package in Ubuntu:
In Progress
Status in linux-oem-6.14 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.14 source package in Noble:
Fix Committed
Status in linux source package in Oracular:
Won't Fix
Status in linux-firmware source package in Oracular:
Won't Fix
Status in linux-oem-6.14 source package in Oracular:
Invalid
Status in linux source package in Plucky:
Won't Fix
Status in linux-firmware source package in Plucky:
Fix Committed
Status in linux-oem-6.14 source package in Plucky:
Invalid
Bug description:
SRU Justification:
[Impact]
On HP AMDGPU platform running the 6.14.0-1005-oem kernel, the monitor screen never appeared when booting the system with a Thunderbolt cable connected. However, we were still able to SSH into the system, suggesting that it had booted successfully.
For the Noble and Plucky generic kernels, they have been classified as
"won't fix" since the bug only occurrs on a specific platform. For
users on that platform, we recommend using our Noble 6.14-OEM kernel,
which includes the appropriate fix.
[Fix]
Updates are required for both the Linux AMDGPU driver and the linux-firmware package.
- Linux AMDGPU driver: cherry-pick the following commit from the Linux
mainline:
59510792baa drm/amd/display: Assign preferred stream encoder instance
to dpia
- linux-firmware: backport the following commits from the upstream
linux-firmware repository:
1. b3049665a5d amdgpu: DMCUB updates for various AMDGPU ASICs
2. 61d257d5a8b amdgpu: DMCUB updates for various ASICs
3. 5602c7293e6 amdgpu: DMCUB updates for various ASICs
4. b0e96674082 amdgpu: DMCUB updates for various ASICs
5. a2aaefe5a59 amdgpu: update dcn 3.5 firmware to 0.1.0.0
6. a80a8bd73e0 amdgpu: update dcn 3.5 and dcn 3.5.1 firmware to 9.0.27.0
7. 25750add9b7 amdgpu: DMCUB updates for various ASICs
8. 5ac6303062 amdgpu: DMCUB updates for various ASICs
Be aware that only amdgpu/dcn_3_5_1_dmcub.bin and amdgpu/dcn_3_5_dmcub.bin are updated by the above commits.
Updates to other files were intentionally omitted.
[Test Plan]
========= On Noble 6.14-OEM ==================
- Prerequisites:
1. Install the linux-oem-6.14 version 6.14.0-1006.6 kernel from -proposed [1]
2. Install the linux-firmware version 20240318.git3b128b60-0ubuntu2.14 from -proposed [1]
- Test instructions:
1. Connect the machine to an external monitor using a Thunderbolt cable before booting.
2. Boot the system using the Noble 6.14.0-1005-oem kernel
3. Verify that the display output appears on the monitor and the GNOME desktop environment is visible.
========= On Noble/Plucky generic ==================
- Prerequisites:
1. Install the Noble or Plucky generic kernel
2. If you will be running the Noble generic kernel, please install the linux-firmware version 20240318.git3b128b60-0ubuntu2.14 from -proposed [1]. Otherwise, please install the linux-firmware version 20250317.git1d4c88ee-0ubuntu1.3 from -proposed[1].
- Test instructions:
1. Boot the system using the Noble or Plucky generic kernel
2. Since this bug was intended to be fixed only in the Noble 6.14-OEM kernel, it is expected to still reproduce on the Noble and Plucky generic kernels. Please
test all other functionalities to verify whether there are any regressions.
[Where problems could occur]
We updated the firmware to the latest version, while the Linux AMDGPU driver remains behind the mainline. As a consequence, a mismatch might occur between the Linux AMDGPU driver and the firmware.
[1] See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2112518/+subscriptions
[Bug 2101931] Re: Dell machine cannot wake up from suspend via KB
Verified on JA4DTL-DVT-A2 with 6.14-oem -1006 kernel. The system can be
woken up by both keyboard and power button.
** Tags removed: verification-needed-noble-linux-oem-6.14
** Tags added: verification-done-noble-linux-oem-6.14
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2101931
Title:
Dell machine cannot wake up from suspend via KB
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.11 package in Ubuntu:
Invalid
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.11 source package in Noble:
Fix Released
Status in linux-oem-6.14 source package in Noble:
Fix Committed
Status in linux source package in Oracular:
In Progress
Status in linux-oem-6.11 source package in Oracular:
Invalid
Status in linux-oem-6.14 source package in Oracular:
Invalid
Status in linux source package in Plucky:
In Progress
Status in linux-oem-6.11 source package in Plucky:
Invalid
Status in linux-oem-6.14 source package in Plucky:
Invalid
Bug description:
[Impact]
On some systems when the system is put to sleep pressing the ACPI power
button will cause the EC SCI to try to wake the system by a Notify(DEV, 0x2)
with an intention to wake the system up from suspend.
This behavior matches the ACPI specification in ACPI 6.4 section
4.8.3.1.1.2 which describes that the AML handler would generate a Notify()
with a code of 0x2 to indicate it was responsible for waking the system.
This currently doesn't work because acpi_button_add() only configured
`ACPI_DEVICE_NOTIFY` which means that device handler notifications
0x80 through 0xFF are handled.
[Fix]
To fix the wakeups on such systems, adjust the ACPI button handler to
use `ACPI_ALL_NOTIFY` which will handle all events 0x00 through 0x7F.
https://patchwork.kernel.org/project/linux-acpi/patch/20250303212719.4153485-1-superm1@kernel.org/
Included in linux-next
39bc24ceb09d ACPI: button: Install notifier for system events as well
[Test]
The issue could be found on Dell Pro 14 notebook.
Verify the system could be waken up by the power button.
[Where problems could occur]
ACPI button driver submit more events to wake up the system, it could lead to unexpected wake up if the BIOS sends unexpected events during suspend.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2101931/+subscriptions
woken up by both keyboard and power button.
** Tags removed: verification-needed-noble-linux-oem-6.14
** Tags added: verification-done-noble-linux-oem-6.14
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2101931
Title:
Dell machine cannot wake up from suspend via KB
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.11 package in Ubuntu:
Invalid
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.11 source package in Noble:
Fix Released
Status in linux-oem-6.14 source package in Noble:
Fix Committed
Status in linux source package in Oracular:
In Progress
Status in linux-oem-6.11 source package in Oracular:
Invalid
Status in linux-oem-6.14 source package in Oracular:
Invalid
Status in linux source package in Plucky:
In Progress
Status in linux-oem-6.11 source package in Plucky:
Invalid
Status in linux-oem-6.14 source package in Plucky:
Invalid
Bug description:
[Impact]
On some systems when the system is put to sleep pressing the ACPI power
button will cause the EC SCI to try to wake the system by a Notify(DEV, 0x2)
with an intention to wake the system up from suspend.
This behavior matches the ACPI specification in ACPI 6.4 section
4.8.3.1.1.2 which describes that the AML handler would generate a Notify()
with a code of 0x2 to indicate it was responsible for waking the system.
This currently doesn't work because acpi_button_add() only configured
`ACPI_DEVICE_NOTIFY` which means that device handler notifications
0x80 through 0xFF are handled.
[Fix]
To fix the wakeups on such systems, adjust the ACPI button handler to
use `ACPI_ALL_NOTIFY` which will handle all events 0x00 through 0x7F.
https://patchwork.kernel.org/project/linux-acpi/patch/20250303212719.4153485-1-superm1@kernel.org/
Included in linux-next
39bc24ceb09d ACPI: button: Install notifier for system events as well
[Test]
The issue could be found on Dell Pro 14 notebook.
Verify the system could be waken up by the power button.
[Where problems could occur]
ACPI button driver submit more events to wake up the system, it could lead to unexpected wake up if the BIOS sends unexpected events during suspend.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2101931/+subscriptions
вторник
[Bug 2109343] Re: Intel(R) Wireless-AC 9461 doesnt load in 6.14
** Changed in: linux (Ubuntu Plucky)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu)
Status: In Progress => 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/2109343
Title:
Intel(R) Wireless-AC 9461 doesnt load in 6.14
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Confirmed
Status in linux source package in Plucky:
Fix Released
Status in linux-firmware source package in Plucky:
Confirmed
Bug description:
iwlwifi driver not loading
it works fine in kernel 6.12
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: linux-modules-6.14.0-1002-realtime 6.14.0-1002.2
ProcVersionSignature: Ubuntu 6.14.0-1002.2-realtime 6.14.0
Uname: Linux 6.14.0-1002-realtime x86_64
ApportVersion: 2.32.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: bret 1786 F.... wireplumber
/dev/snd/seq: bret 1783 F.... pipewire
CasperMD5CheckMismatches: ./pool/main/l/linux/linux-modules-extra-6.12.0-16-generic_6.12.0-16.16_amd64.deb
CasperMD5CheckResult: fail
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 25 12:44:17 2025
Dependencies:
InstallationDate: Installed on 2025-03-03 (53 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Daily amd64 (20250302)
MachineType: Crusaders Corporate (Pty) Ltd DNLP1502
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-1002-realtime root=UUID=8b090781-9885-42ec-b482-42b1b1c61005 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.14.0-1002-realtime N/A
linux-backports-modules-6.14.0-1002-realtime N/A
linux-firmware 20250317.git1d4c88ee-0ubuntu1
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux-realtime
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/10/2023
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: HQ-BI-15.6-T140ANR100-034-B
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: Shenzhen WEIBU Information Co.,Ltd
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.ec.firmware.release: 1.2
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrHQ-BI-15.6-T140ANR100-034-B:bd08/10/2023:br5.27:efr1.2:svnCrusadersCorporate(Pty)Ltd:pnDNLP1502:pvrDefaultstring:rvnShenzhenWEIBUInformationCo.,Ltd:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuAlderLake-N:
dmi.product.family: Alder Lake
dmi.product.name: DNLP1502
dmi.product.sku: AlderLake-N
dmi.product.version: Default string
dmi.sys.vendor: Crusaders Corporate (Pty) Ltd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2109343/+subscriptions
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu)
Status: In Progress => 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/2109343
Title:
Intel(R) Wireless-AC 9461 doesnt load in 6.14
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Confirmed
Status in linux source package in Plucky:
Fix Released
Status in linux-firmware source package in Plucky:
Confirmed
Bug description:
iwlwifi driver not loading
it works fine in kernel 6.12
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: linux-modules-6.14.0-1002-realtime 6.14.0-1002.2
ProcVersionSignature: Ubuntu 6.14.0-1002.2-realtime 6.14.0
Uname: Linux 6.14.0-1002-realtime x86_64
ApportVersion: 2.32.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: bret 1786 F.... wireplumber
/dev/snd/seq: bret 1783 F.... pipewire
CasperMD5CheckMismatches: ./pool/main/l/linux/linux-modules-extra-6.12.0-16-generic_6.12.0-16.16_amd64.deb
CasperMD5CheckResult: fail
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 25 12:44:17 2025
Dependencies:
InstallationDate: Installed on 2025-03-03 (53 days ago)
InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Daily amd64 (20250302)
MachineType: Crusaders Corporate (Pty) Ltd DNLP1502
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-1002-realtime root=UUID=8b090781-9885-42ec-b482-42b1b1c61005 ro quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-6.14.0-1002-realtime N/A
linux-backports-modules-6.14.0-1002-realtime N/A
linux-firmware 20250317.git1d4c88ee-0ubuntu1
RfKill:
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux-realtime
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/10/2023
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: HQ-BI-15.6-T140ANR100-034-B
dmi.board.asset.tag: Default string
dmi.board.name: Default string
dmi.board.vendor: Shenzhen WEIBU Information Co.,Ltd
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.ec.firmware.release: 1.2
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrHQ-BI-15.6-T140ANR100-034-B:bd08/10/2023:br5.27:efr1.2:svnCrusadersCorporate(Pty)Ltd:pnDNLP1502:pvrDefaultstring:rvnShenzhenWEIBUInformationCo.,Ltd:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuAlderLake-N:
dmi.product.family: Alder Lake
dmi.product.name: DNLP1502
dmi.product.sku: AlderLake-N
dmi.product.version: Default string
dmi.sys.vendor: Crusaders Corporate (Pty) Ltd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2109343/+subscriptions
[Bug 2115512] Re: MacBook Pro USB 3.0 Devices Unrecognized
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Juerg Haefliger (juergh)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2115512
Title:
MacBook Pro USB 3.0 Devices Unrecognized
Status in linux package in Ubuntu:
Incomplete
Bug description:
If my MacBook Pro boots with a USB 3.0/3.2 device (e.g., thumb drive)
connected, then those devices are recognized. But if the thumb drive
is not connected when the computer boots then the Linux kernel doesn't
see it or access it. This holds true whether the thumb drive is
directly connected to a USB-C port or via a USB 3.0 USB hub. If the
thumb drive is connected to a non-USB 3.0 port on the USB hub, then it
is seen and recognized and operates correctly (albeit more slowly).
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: linux-image-6.14.0-24-generic 6.14.0-24.24
ProcVersionSignature: Ubuntu 6.14.0-24.24-generic 6.14.6
Uname: Linux 6.14.0-24-generic x86_64
ApportVersion: 2.32.0-0ubuntu5.2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: bill 2275 F.... wireplumber
/dev/snd/seq: bill 2270 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 27 08:02:03 2025
InstallationDate: Installed on 2025-03-17 (102 days ago)
InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1)
MachineType: Apple Inc. MacBookPro14,1
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-24-generic root=UUID=4e84a7fa-65d0-4d81-933b-3edfdbbb5285 ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
RelatedPackageVersions:
linux-restricted-modules-6.14.0-24-generic N/A
linux-backports-modules-6.14.0-24-generic N/A
linux-firmware 20250317.git1d4c88ee-0ubuntu1.2
SourcePackage: linux
UpgradeStatus: Upgraded to plucky on 2025-05-30 (28 days ago)
dmi.bios.date: 06/16/2020
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 428.0.0.0.0
dmi.board.name: Mac-B4831CEBD52A0C4C
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro14,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-B4831CEBD52A0C4C
dmi.modalias: dmi:bvnAppleInc.:bvr428.0.0.0.0:bd06/16/2020:br0.1:svnAppleInc.:pnMacBookPro14,1:pvr1.0:rvnAppleInc.:rnMac-B4831CEBD52A0C4C:rvrMacBookPro14,1:cvnAppleInc.:ct9:cvrMac-B4831CEBD52A0C4C:sku:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro14,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2115512/+subscriptions
Assignee: (unassigned) => Juerg Haefliger (juergh)
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2115512
Title:
MacBook Pro USB 3.0 Devices Unrecognized
Status in linux package in Ubuntu:
Incomplete
Bug description:
If my MacBook Pro boots with a USB 3.0/3.2 device (e.g., thumb drive)
connected, then those devices are recognized. But if the thumb drive
is not connected when the computer boots then the Linux kernel doesn't
see it or access it. This holds true whether the thumb drive is
directly connected to a USB-C port or via a USB 3.0 USB hub. If the
thumb drive is connected to a non-USB 3.0 port on the USB hub, then it
is seen and recognized and operates correctly (albeit more slowly).
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: linux-image-6.14.0-24-generic 6.14.0-24.24
ProcVersionSignature: Ubuntu 6.14.0-24.24-generic 6.14.6
Uname: Linux 6.14.0-24-generic x86_64
ApportVersion: 2.32.0-0ubuntu5.2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: bill 2275 F.... wireplumber
/dev/snd/seq: bill 2270 F.... pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 27 08:02:03 2025
InstallationDate: Installed on 2025-03-17 (102 days ago)
InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1)
MachineType: Apple Inc. MacBookPro14,1
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.14.0-24-generic root=UUID=4e84a7fa-65d0-4d81-933b-3edfdbbb5285 ro crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
RelatedPackageVersions:
linux-restricted-modules-6.14.0-24-generic N/A
linux-backports-modules-6.14.0-24-generic N/A
linux-firmware 20250317.git1d4c88ee-0ubuntu1.2
SourcePackage: linux
UpgradeStatus: Upgraded to plucky on 2025-05-30 (28 days ago)
dmi.bios.date: 06/16/2020
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 428.0.0.0.0
dmi.board.name: Mac-B4831CEBD52A0C4C
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro14,1
dmi.chassis.type: 9
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-B4831CEBD52A0C4C
dmi.modalias: dmi:bvnAppleInc.:bvr428.0.0.0.0:bd06/16/2020:br0.1:svnAppleInc.:pnMacBookPro14,1:pvr1.0:rvnAppleInc.:rnMac-B4831CEBD52A0C4C:rvrMacBookPro14,1:cvnAppleInc.:ct9:cvrMac-B4831CEBD52A0C4C:sku:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro14,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2115512/+subscriptions
Подписаться на:
Сообщения (Atom)