I did some reading up on the ambient light sensor and LCD backlight
control in Linux and found out the following:
1. The ambient light sensor is present:
> cat sys/bus/iio/devices/iio:device0/name
> acpi-als
2. watch cat sys/bus/iio/devices/iio.device0/in_illuminance_raw shows
changing values as expected
3. The LCD backlight can be controlled with F1 and F2
4. The LCD backlight can be controlled from the quick settings
5. The LCD backlight can be controlled with the debian package
brightnessctl
So what's happening is that the "Automatic Screen Brightness", when
toggled on in the power settings, has no apparent effect on the LCD
brightness even if the ALS is working fine.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2131555
Title:
[Macbook Pro 11,5] Ambient Light sensor regression
Status in linux package in Ubuntu:
New
Bug description:
In Kernel 6.14 the ambient light sensor on the Macbook Pro 11,5 (2015
15" A1398) model works as expected
In Kernel 6.17 the ambient light sensor no longer works
This appears to be a regression
ProblemType: Bug
DistroRelease: Ubuntu 25.10
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 6.17.0-6.6-generic 6.17.1
Uname: Linux 6.17.0-6-generic x86_64
ApportVersion: 2.33.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 14 14:41:30 2025
InstallationDate: Installed on 2025-09-06 (70 days ago)
InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=<set>
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to questing on 2025-09-25 (50 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2131555/+subscriptions
понедельник
[Bug 2128729] Re: Black screen when booting 5.15.0-160 (on AMD Lucienne / Cezanne / Navi / Renoir / Rembrandt)
Kernels including this fix (-generic and derivatives, including FIPS)
can only be released with the next planned kernel update cycle. I'm
expecting this patch to be included in the security cycle s2025.11.17
which will release in the week of 26-Jan. Please find the current
schedule of cycles here: https://kernel.ubuntu.com/
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2128729
Title:
Black screen when booting 5.15.0-160 (on AMD Lucienne / Cezanne / Navi
/ Renoir / Rembrandt)
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
In Progress
Bug description:
SRU Justification:
[Impact]
The Ubuntu backport of e6a7df96facdc ("drm/amd/display: Fix MST Null Ptr
for RV") to fix CVE-2024-26700 does not consider that
compute_mst_dsc_configs_for_state() returns a boolean to
indicate success or failure in 5.15, while it returns an integer
in later kernel versions with 0 indicating success. This means
we need to flip the error condition when checking whether the
call succeeded when backporting this to 5.15 and older.
Currently, the error path is taken even though the call to
compute_mst_dsc_configs_for_state() succeeds which causes some systems
to have no video output or a black screen while the system is running.
This is causing loss of video output to screens on affected amdgpu
hardware.
[Fix]
Check the return value of compute_mst_dsc_configs_for_state() in
amdgpu_dm_atomic_check() correctly.
[Test Plan]
Without the fix, there will be no video output to the screen and the
following messages can be found in the kernel log if the kernel is
booted with drm.debug=0x2:
kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] compute_mst_dsc_configs_for_state() failed
kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] Atomic check failed with err: -22
With the fix applied, video output should return to normal and the
kernel warnings will disappear from the log.
[Where problems could occur]
Problems would be observed in odd behavior of the amdgpu driver,
particularly for hardware with DSC support.
[Original Bug Report]
Updated to Kernel 5.15.0-160 from Kernel 5.15.0-157, System seemed to boot but I never got the usual splash logo while booting. Eventually the fans stop and the system sits idle with no video output. I updated the kernel using the system update tool. This system is down stream on Mint, so I can't use the instructions as written in the submission form. But I will do my best. I had to roll back to -157 to write this report. Hope this helps. Logs attached.
_____
[code]
System:
Kernel: 5.15.0-157-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 6.0.4
tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia
base: Ubuntu 22.04 jammy
Machine:
Type: Desktop System: Gigabyte product: X570S AERO G v: -CF serial: <superuser required>
Mobo: Gigabyte model: X570S AERO G v: x.x serial: <superuser required>
UEFI: American Megatrends LLC. v: F3 date: 01/04/2022
CPU:
Info: 8-core model: AMD Ryzen 7 5800X bits: 64 type: MT MCP smt: enabled arch: Zen 3 rev: 0
cache: L1: 512 KiB L2: 4 MiB L3: 32 MiB
Speed (MHz): avg: 4017 high: 4850 min/max: 2200/3800 boost: enabled cores: 1: 4850 2: 3879
3: 3884 4: 3876 5: 3879 6: 3879 7: 3879 8: 3878 9: 4840 10: 3880 11: 3900 12: 3879 13: 3878
14: 3880 15: 3878 16: 4140 bogomips: 121593
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] vendor: Sapphire driver: amdgpu
v: kernel pcie: speed: 16 GT/s lanes: 16 ports: active: DP-2 empty: DP-1,DP-3,HDMI-A-1
bus-ID: 0f:00.0 chip-ID: 1002:73bf class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1080 s-dpi: 96 s-size: 677x285mm (26.7x11.2") s-diag: 735mm (28.9")
Monitor-1: DisplayPort-1 mapped: DP-2 model: LG (GoldStar) 34UC89G serial: <filter>
res: 2560x1080 dpi: 81 size: 798x335mm (31.4x13.2") diag: 865mm (34.1") modes: max: 2560x1080
min: 640x480
OpenGL: renderer: AMD Radeon RX 6900 XT (navi21 LLVM 15.0.7 DRM 3.42 5.15.0-157-generic)
v: 4.6 Mesa 23.2.1-1ubuntu3.1~22.04.3 direct render: Yes
Audio:
Device-1: AMD Navi 21 HDMI Audio [Radeon RX 6800/6800 XT / 6900 XT] driver: snd_hda_intel
v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 0f:00.1 chip-ID: 1002:ab28 class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel pcie:
speed: 16 GT/s lanes: 16 bus-ID: 11:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: HP HyperX Cloud Alpha Wireless type: USB
driver: cdc_acm,hid-generic,snd-usb-audio,usbhid bus-ID: 5-2:2 chip-ID: 03f0:098d class-ID: 0a00
serial: <filter>
Sound Server-1: ALSA v: k5.15.0-157-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: speed: 5 GT/s lanes: 1
bus-ID: 08:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlp8s0 state: up mac: <filter>
Device-2: Intel Ethernet I225-V vendor: Gigabyte driver: igc v: kernel pcie: speed: 5 GT/s
lanes: 1 port: N/A bus-ID: 09:00.0 chip-ID: 8086:15f3 class-ID: 0200
IF: enp9s0 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 5-5:3 chip-ID: 8087:0029
class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
sub-v: 2184 hci-v: 5.2 rev: 2184
Drives:
Local Storage: total: 3.18 TiB used: 1.77 TiB (55.5%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 500GB size: 465.76 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 1B4QFXO7 temp: 34.9 C scheme: GPT
ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 3B4QFXO7 temp: 35.9 C scheme: GPT
ID-3: /dev/nvme2n1 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 2B4QFXO7 temp: 37.9 C
ID-4: /dev/nvme3n1 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 2B4QFXO7 temp: 52.9 C scheme: GPT
Partition:
ID-1: / size: 915.32 GiB used: 640.68 GiB (70.0%) fs: ext4 dev: /dev/nvme3n1p2
ID-2: /boot/efi size: 96 MiB used: 31.4 MiB (32.7%) fs: vfat dev: /dev/nvme0n1p1
Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
USB:
Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Hub-2: 2-0:1 info: Super-speed hub ports: 1 rev: 3.1 speed: 20 Gb/s chip-ID: 1d6b:0003
class-ID: 0900
Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 6 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 3-1:2 info: Integrated Express ITE Device type: HID driver: hid-generic,usbhid
interfaces: 1 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 048d:5702 class-ID: 0300
Hub-4: 3-5:3 info: Genesys Logic Hub ports: 4 rev: 2.1 speed: 480 Mb/s power: 100mA
chip-ID: 05e3:0610 class-ID: 0900
Device-1: 3-5.1:5 info: Mad Catz Catz C.A.T. 9 type: HID driver: hid-generic,usbhid
interfaces: 1 rev: 2.0 speed: 12 Mb/s power: 400mA chip-ID: 0738:0309 class-ID: 0300
Hub-5: 3-6:4 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s power: 100mA
chip-ID: 05e3:0608 class-ID: 0900
Device-1: 3-6.1:6 info: DEXIN MADCATZ R.A.T. 8+ gaming mouse type: Mouse,Keyboard
driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 50mA chip-ID: 12cf:0c05
class-ID: 0300
Hub-6: 4-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
class-ID: 0900
Hub-7: 4-3:2 info: Genesys Logic USB3.1 Hub ports: 4 rev: 3.2 speed: 5 Gb/s chip-ID: 05e3:0626
class-ID: 0900
Hub-8: 5-0:1 info: Hi-speed hub with single TT ports: 6 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 5-2:2 info: HP HyperX Cloud Alpha Wireless
type: Audio,Keyboard,Abstract (modem),CDC-Data driver: cdc_acm,hid-generic,snd-usb-audio,usbhid
interfaces: 6 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 03f0:098d class-ID: 0a00
serial: <filter>
Device-2: 5-5:3 info: Intel AX200 Bluetooth type: Bluetooth driver: btusb interfaces: 2
rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 8087:0029 class-ID: e001
Hub-9: 5-6:4 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s power: 100mA
chip-ID: 05e3:0608 class-ID: 0900
Device-1: 5-6.1:5 info: Logitech G910 Orion Spark Mechanical Keyboard type: Keyboard,HID
driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 500mA chip-ID: 046d:c32b
class-ID: 0300 serial: <filter>
Hub-10: 6-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
class-ID: 0900
Hub-11: 7-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 7-1:2 info: Elan Micro Gaming KB type: Keyboard driver: hid-generic,usbhid
interfaces: 2 rev: 1.1 speed: 1.5 Mb/s power: 100mA chip-ID: 04f3:152e class-ID: 0301
Device-2: 7-2:3 info: SiGma Micro USB HANDLE type: Keyboard,HID driver: hid-generic,usbhid
interfaces: 2 rev: 1.1 speed: 12 Mb/s power: 100mA chip-ID: 1c4f:007c class-ID: 0300
serial: <filter>
Hub-12: 8-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
class-ID: 0900
Device-1: 8-4:2 info: Pioneer Blu-ray Drive type: Mass Storage driver: usb-storage
interfaces: 1 rev: 3.0 speed: 5 Gb/s power: 8mA chip-ID: 08e4:017a class-ID: 0802
serial: <filter>
Sensors:
System Temperatures: cpu: 16.8 C mobo: 16.8 C gpu: amdgpu temp: 43.0 C mem: 46.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Repos:
Packages: 3131 apt: 3092 flatpak: 39
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https: //brave-browser-apt-release.s3.brave.com/ stable main
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http: //packages.linuxmint.com virginia main upstream import backport
2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Info:
Processes: 456 Uptime: 24m wakeups: 0 Memory: 62.69 GiB used: 4.52 GiB (7.2%) Init: systemd
v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Unknown python3.10 client
inxi: 3.3.13
[/code]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2128729/+subscriptions
can only be released with the next planned kernel update cycle. I'm
expecting this patch to be included in the security cycle s2025.11.17
which will release in the week of 26-Jan. Please find the current
schedule of cycles here: https://kernel.ubuntu.com/
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2128729
Title:
Black screen when booting 5.15.0-160 (on AMD Lucienne / Cezanne / Navi
/ Renoir / Rembrandt)
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
In Progress
Bug description:
SRU Justification:
[Impact]
The Ubuntu backport of e6a7df96facdc ("drm/amd/display: Fix MST Null Ptr
for RV") to fix CVE-2024-26700 does not consider that
compute_mst_dsc_configs_for_state() returns a boolean to
indicate success or failure in 5.15, while it returns an integer
in later kernel versions with 0 indicating success. This means
we need to flip the error condition when checking whether the
call succeeded when backporting this to 5.15 and older.
Currently, the error path is taken even though the call to
compute_mst_dsc_configs_for_state() succeeds which causes some systems
to have no video output or a black screen while the system is running.
This is causing loss of video output to screens on affected amdgpu
hardware.
[Fix]
Check the return value of compute_mst_dsc_configs_for_state() in
amdgpu_dm_atomic_check() correctly.
[Test Plan]
Without the fix, there will be no video output to the screen and the
following messages can be found in the kernel log if the kernel is
booted with drm.debug=0x2:
kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] compute_mst_dsc_configs_for_state() failed
kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] Atomic check failed with err: -22
With the fix applied, video output should return to normal and the
kernel warnings will disappear from the log.
[Where problems could occur]
Problems would be observed in odd behavior of the amdgpu driver,
particularly for hardware with DSC support.
[Original Bug Report]
Updated to Kernel 5.15.0-160 from Kernel 5.15.0-157, System seemed to boot but I never got the usual splash logo while booting. Eventually the fans stop and the system sits idle with no video output. I updated the kernel using the system update tool. This system is down stream on Mint, so I can't use the instructions as written in the submission form. But I will do my best. I had to roll back to -157 to write this report. Hope this helps. Logs attached.
_____
[code]
System:
Kernel: 5.15.0-157-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 6.0.4
tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia
base: Ubuntu 22.04 jammy
Machine:
Type: Desktop System: Gigabyte product: X570S AERO G v: -CF serial: <superuser required>
Mobo: Gigabyte model: X570S AERO G v: x.x serial: <superuser required>
UEFI: American Megatrends LLC. v: F3 date: 01/04/2022
CPU:
Info: 8-core model: AMD Ryzen 7 5800X bits: 64 type: MT MCP smt: enabled arch: Zen 3 rev: 0
cache: L1: 512 KiB L2: 4 MiB L3: 32 MiB
Speed (MHz): avg: 4017 high: 4850 min/max: 2200/3800 boost: enabled cores: 1: 4850 2: 3879
3: 3884 4: 3876 5: 3879 6: 3879 7: 3879 8: 3878 9: 4840 10: 3880 11: 3900 12: 3879 13: 3878
14: 3880 15: 3878 16: 4140 bogomips: 121593
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] vendor: Sapphire driver: amdgpu
v: kernel pcie: speed: 16 GT/s lanes: 16 ports: active: DP-2 empty: DP-1,DP-3,HDMI-A-1
bus-ID: 0f:00.0 chip-ID: 1002:73bf class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1080 s-dpi: 96 s-size: 677x285mm (26.7x11.2") s-diag: 735mm (28.9")
Monitor-1: DisplayPort-1 mapped: DP-2 model: LG (GoldStar) 34UC89G serial: <filter>
res: 2560x1080 dpi: 81 size: 798x335mm (31.4x13.2") diag: 865mm (34.1") modes: max: 2560x1080
min: 640x480
OpenGL: renderer: AMD Radeon RX 6900 XT (navi21 LLVM 15.0.7 DRM 3.42 5.15.0-157-generic)
v: 4.6 Mesa 23.2.1-1ubuntu3.1~22.04.3 direct render: Yes
Audio:
Device-1: AMD Navi 21 HDMI Audio [Radeon RX 6800/6800 XT / 6900 XT] driver: snd_hda_intel
v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 0f:00.1 chip-ID: 1002:ab28 class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel pcie:
speed: 16 GT/s lanes: 16 bus-ID: 11:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: HP HyperX Cloud Alpha Wireless type: USB
driver: cdc_acm,hid-generic,snd-usb-audio,usbhid bus-ID: 5-2:2 chip-ID: 03f0:098d class-ID: 0a00
serial: <filter>
Sound Server-1: ALSA v: k5.15.0-157-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: speed: 5 GT/s lanes: 1
bus-ID: 08:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlp8s0 state: up mac: <filter>
Device-2: Intel Ethernet I225-V vendor: Gigabyte driver: igc v: kernel pcie: speed: 5 GT/s
lanes: 1 port: N/A bus-ID: 09:00.0 chip-ID: 8086:15f3 class-ID: 0200
IF: enp9s0 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 5-5:3 chip-ID: 8087:0029
class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
sub-v: 2184 hci-v: 5.2 rev: 2184
Drives:
Local Storage: total: 3.18 TiB used: 1.77 TiB (55.5%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 500GB size: 465.76 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 1B4QFXO7 temp: 34.9 C scheme: GPT
ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 3B4QFXO7 temp: 35.9 C scheme: GPT
ID-3: /dev/nvme2n1 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 2B4QFXO7 temp: 37.9 C
ID-4: /dev/nvme3n1 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 2B4QFXO7 temp: 52.9 C scheme: GPT
Partition:
ID-1: / size: 915.32 GiB used: 640.68 GiB (70.0%) fs: ext4 dev: /dev/nvme3n1p2
ID-2: /boot/efi size: 96 MiB used: 31.4 MiB (32.7%) fs: vfat dev: /dev/nvme0n1p1
Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
USB:
Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Hub-2: 2-0:1 info: Super-speed hub ports: 1 rev: 3.1 speed: 20 Gb/s chip-ID: 1d6b:0003
class-ID: 0900
Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 6 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 3-1:2 info: Integrated Express ITE Device type: HID driver: hid-generic,usbhid
interfaces: 1 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 048d:5702 class-ID: 0300
Hub-4: 3-5:3 info: Genesys Logic Hub ports: 4 rev: 2.1 speed: 480 Mb/s power: 100mA
chip-ID: 05e3:0610 class-ID: 0900
Device-1: 3-5.1:5 info: Mad Catz Catz C.A.T. 9 type: HID driver: hid-generic,usbhid
interfaces: 1 rev: 2.0 speed: 12 Mb/s power: 400mA chip-ID: 0738:0309 class-ID: 0300
Hub-5: 3-6:4 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s power: 100mA
chip-ID: 05e3:0608 class-ID: 0900
Device-1: 3-6.1:6 info: DEXIN MADCATZ R.A.T. 8+ gaming mouse type: Mouse,Keyboard
driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 50mA chip-ID: 12cf:0c05
class-ID: 0300
Hub-6: 4-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
class-ID: 0900
Hub-7: 4-3:2 info: Genesys Logic USB3.1 Hub ports: 4 rev: 3.2 speed: 5 Gb/s chip-ID: 05e3:0626
class-ID: 0900
Hub-8: 5-0:1 info: Hi-speed hub with single TT ports: 6 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 5-2:2 info: HP HyperX Cloud Alpha Wireless
type: Audio,Keyboard,Abstract (modem),CDC-Data driver: cdc_acm,hid-generic,snd-usb-audio,usbhid
interfaces: 6 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 03f0:098d class-ID: 0a00
serial: <filter>
Device-2: 5-5:3 info: Intel AX200 Bluetooth type: Bluetooth driver: btusb interfaces: 2
rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 8087:0029 class-ID: e001
Hub-9: 5-6:4 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s power: 100mA
chip-ID: 05e3:0608 class-ID: 0900
Device-1: 5-6.1:5 info: Logitech G910 Orion Spark Mechanical Keyboard type: Keyboard,HID
driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 500mA chip-ID: 046d:c32b
class-ID: 0300 serial: <filter>
Hub-10: 6-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
class-ID: 0900
Hub-11: 7-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 7-1:2 info: Elan Micro Gaming KB type: Keyboard driver: hid-generic,usbhid
interfaces: 2 rev: 1.1 speed: 1.5 Mb/s power: 100mA chip-ID: 04f3:152e class-ID: 0301
Device-2: 7-2:3 info: SiGma Micro USB HANDLE type: Keyboard,HID driver: hid-generic,usbhid
interfaces: 2 rev: 1.1 speed: 12 Mb/s power: 100mA chip-ID: 1c4f:007c class-ID: 0300
serial: <filter>
Hub-12: 8-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
class-ID: 0900
Device-1: 8-4:2 info: Pioneer Blu-ray Drive type: Mass Storage driver: usb-storage
interfaces: 1 rev: 3.0 speed: 5 Gb/s power: 8mA chip-ID: 08e4:017a class-ID: 0802
serial: <filter>
Sensors:
System Temperatures: cpu: 16.8 C mobo: 16.8 C gpu: amdgpu temp: 43.0 C mem: 46.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Repos:
Packages: 3131 apt: 3092 flatpak: 39
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https: //brave-browser-apt-release.s3.brave.com/ stable main
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http: //packages.linuxmint.com virginia main upstream import backport
2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Info:
Processes: 456 Uptime: 24m wakeups: 0 Memory: 62.69 GiB used: 4.52 GiB (7.2%) Init: systemd
v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Unknown python3.10 client
inxi: 3.3.13
[/code]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2128729/+subscriptions
[Bug 1996068] Re: i915 0000:00:02.0: Block 42 min_size is zero | WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915]
The problem was gone after installing kernel 6.8.
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1996068
Title:
i915 0000:00:02.0: Block 42 min_size is zero | WARNING: CPU: 2 PID:
254 at drivers/gpu/drm/i915/display/intel_bios.c:476
init_bdb_block+0x29a/0x460 [i915]
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen.
Nov 5 09:46:42 shusaku kernel: [ 2.209937] ------------[ cut here ]------------
Nov 5 09:46:42 shusaku kernel: [ 2.209938] i915 0000:00:02.0: Block 42 min_size is zero
Nov 5 09:46:42 shusaku kernel: [ 2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915]
Nov 5 09:46:42 shusaku kernel: [ 2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c
lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin
ctrl_tigerlake
Nov 5 09:46:42 shusaku kernel: [ 2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu
Nov 5 09:46:42 shusaku kernel: [ 2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022
Nov 5 09:46:42 shusaku kernel: [ 2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915]
Nov 5 09:46:42 shusaku kernel: [ 2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6
48 c7 c7
Nov 5 09:46:42 shusaku kernel: [ 2.210168] RSP: 0018:ffffabb9c0953888 EFLAGS: 00010246
Nov 5 09:46:42 shusaku kernel: [ 2.210170] RAX: 0000000000000000 RBX: ffff8ca1a1108000 RCX: 0000000000000000
Nov 5 09:46:42 shusaku kernel: [ 2.210171] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
Nov 5 09:46:42 shusaku kernel: [ 2.210172] RBP: ffffabb9c09538d8 R08: 0000000000000000 R09: 0000000000000000
Nov 5 09:46:42 shusaku kernel: [ 2.210173] R10: 0000000000000000 R11: 0000000000000000 R12: 000000000000002a
Nov 5 09:46:42 shusaku kernel: [ 2.210174] R13: 0000000000000000 R14: ffff8ca1826ad170 R15: ffff8ca1a1109328
Nov 5 09:46:42 shusaku kernel: [ 2.210175] FS: 00007f21d34178c0(0000) GS:ffff8ca8bf480000(0000) knlGS:0000000000000000
Nov 5 09:46:42 shusaku kernel: [ 2.210176] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 5 09:46:42 shusaku kernel: [ 2.210177] CR2: 000055a99a0511d8 CR3: 000000011d202003 CR4: 0000000000770ee0
Nov 5 09:46:42 shusaku kernel: [ 2.210179] PKRU: 55555554
Nov 5 09:46:42 shusaku kernel: [ 2.210179] Call Trace:
Nov 5 09:46:42 shusaku kernel: [ 2.210181] <TASK>
Nov 5 09:46:42 shusaku kernel: [ 2.210183] intel_bios_init+0x171/0x7c0 [i915]
Nov 5 09:46:42 shusaku kernel: [ 2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm]
Nov 5 09:46:42 shusaku kernel: [ 2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915]
Nov 5 09:46:42 shusaku kernel: [ 2.210594] i915_driver_probe+0x1ae/0x490 [i915]
Nov 5 09:46:42 shusaku kernel: [ 2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm]
Nov 5 09:46:42 shusaku kernel: [ 2.210833] ? acpi_dev_found+0x64/0x80
Nov 5 09:46:42 shusaku kernel: [ 2.210842] i915_pci_probe+0x56/0x150 [i915]
Nov 5 09:46:42 shusaku kernel: [ 2.210935] local_pci_probe+0x44/0x90
Nov 5 09:46:42 shusaku kernel: [ 2.210939] pci_call_probe+0x55/0x190
Nov 5 09:46:42 shusaku kernel: [ 2.210940] pci_device_probe+0x84/0x120
Nov 5 09:46:42 shusaku kernel: [ 2.210941] really_probe+0x1dc/0x3b0
Nov 5 09:46:42 shusaku kernel: [ 2.210945] __driver_probe_device+0x12c/0x1b0
Nov 5 09:46:42 shusaku kernel: [ 2.210946] driver_probe_device+0x24/0xd0
Nov 5 09:46:42 shusaku kernel: [ 2.210948] __driver_attach+0xe0/0x210
Nov 5 09:46:42 shusaku kernel: [ 2.210949] ? __device_attach_driver+0x130/0x130
Nov 5 09:46:42 shusaku kernel: [ 2.210951] bus_for_each_dev+0x8d/0xe0
Nov 5 09:46:42 shusaku kernel: [ 2.210952] driver_attach+0x1e/0x30
Nov 5 09:46:42 shusaku kernel: [ 2.210953] bus_add_driver+0x187/0x230
Nov 5 09:46:42 shusaku kernel: [ 2.210955] driver_register+0x8f/0x100
Nov 5 09:46:42 shusaku kernel: [ 2.210956] __pci_register_driver+0x62/0x70
Nov 5 09:46:42 shusaku kernel: [ 2.210958] i915_pci_register_driver+0x23/0x30 [i915]
Nov 5 09:46:42 shusaku kernel: [ 2.210993] i915_init+0x3b/0xf2 [i915]
Nov 5 09:46:42 shusaku kernel: [ 2.211045] ? 0xffffffffc098b000
Nov 5 09:46:42 shusaku kernel: [ 2.211046] do_one_initcall+0x5b/0x240
Nov 5 09:46:42 shusaku kernel: [ 2.211049] do_init_module+0x50/0x210
Nov 5 09:46:42 shusaku kernel: [ 2.211051] load_module+0xb7d/0xcd0
Nov 5 09:46:42 shusaku kernel: [ 2.211053] __do_sys_finit_module+0xc4/0x140
Nov 5 09:46:42 shusaku kernel: [ 2.211054] ? __do_sys_finit_module+0xc4/0x140
Nov 5 09:46:42 shusaku kernel: [ 2.211056] __x64_sys_finit_module+0x18/0x30
Nov 5 09:46:42 shusaku kernel: [ 2.211057] do_syscall_64+0x58/0x90
Nov 5 09:46:42 shusaku kernel: [ 2.211059] ? do_syscall_64+0x67/0x90
Nov 5 09:46:42 shusaku kernel: [ 2.211060] ? sysvec_call_function+0x4b/0xd0
Nov 5 09:46:42 shusaku kernel: [ 2.211062] entry_SYSCALL_64_after_hwframe+0x63/0xcd
Nov 5 09:46:42 shusaku kernel: [ 2.211064] RIP: 0033:0x7f21d3af7c4d
Nov 5 09:46:42 shusaku kernel: [ 2.211065] Code: 5d c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 83 f1 0d 00 f7 d8 64 89 01 48
Nov 5 09:46:42 shusaku kernel: [ 2.211066] RSP: 002b:00007ffdaf1f6398 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
Nov 5 09:46:42 shusaku kernel: [ 2.211067] RAX: ffffffffffffffda RBX: 000055a99a04cd90 RCX: 00007f21d3af7c4d
Nov 5 09:46:42 shusaku kernel: [ 2.211070] RDX: 0000000000000000 RSI: 00007f21d3c79458 RDI: 0000000000000017
Nov 5 09:46:42 shusaku kernel: [ 2.211071] RBP: 00007f21d3c79458 R08: 0000000000000000 R09: 00007ffdaf1f64c0
Nov 5 09:46:42 shusaku kernel: [ 2.211071] R10: 0000000000000017 R11: 0000000000000246 R12: 0000000000020000
Nov 5 09:46:42 shusaku kernel: [ 2.211072] R13: 000055a99a04b610 R14: 0000000000000000 R15: 000055a99a04f420
Nov 5 09:46:42 shusaku kernel: [ 2.211073] </TASK>
Nov 5 09:46:42 shusaku kernel: [ 2.211074] ---[ end trace 0000000000000000 ]---
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: gpoo 2430 F.... pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
DistroRelease: Ubuntu 22.10
InstallationDate: Installed on 2015-04-07 (2772 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Beta amd64 (20150326)
MachineType: LENOVO 21CBCTO1WW
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-oem root=UUID=bdc1e1f1-542f-4263-9d93-ea65aefb5f89 ro quiet splash
ProcVersionSignature: Ubuntu 5.17.0-1003.3-oem 5.17.0
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.17.0-1003-oem N/A
linux-backports-modules-5.17.0-1003-oem N/A
linux-firmware 20220923.gitf09bebf3-0ubuntu1
Tags: wayland-session kinetic wayland-session
Uname: Linux 5.17.0-1003-oem x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: Upgraded to kinetic on 2022-10-21 (18 days ago)
UserGroups: adm audio cdrom dip docker lpadmin plugdev render sambashare sudo
_MarkForUpload: False
dmi.bios.date: 09/27/2022
dmi.bios.release: 1.32
dmi.bios.vendor: LENOVO
dmi.bios.version: N3AET67W (1.32 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CBCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.15
dmi.modalias: dmi:bvnLENOVO:bvrN3AET67W(1.32):bd09/27/2022:br1.32:efr1.15:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10:
dmi.product.family: ThinkPad X1 Carbon Gen 10
dmi.product.name: 21CBCTO1WW
dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10
dmi.product.version: ThinkPad X1 Carbon Gen 10
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996068/+subscriptions
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1996068
Title:
i915 0000:00:02.0: Block 42 min_size is zero | WARNING: CPU: 2 PID:
254 at drivers/gpu/drm/i915/display/intel_bios.c:476
init_bdb_block+0x29a/0x460 [i915]
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is using kernel 5.19 on a Lenovo X1 Carbon 10th Gen.
Nov 5 09:46:42 shusaku kernel: [ 2.209937] ------------[ cut here ]------------
Nov 5 09:46:42 shusaku kernel: [ 2.209938] i915 0000:00:02.0: Block 42 min_size is zero
Nov 5 09:46:42 shusaku kernel: [ 2.209953] WARNING: CPU: 2 PID: 254 at drivers/gpu/drm/i915/display/intel_bios.c:476 init_bdb_block+0x29a/0x460 [i915]
Nov 5 09:46:42 shusaku kernel: [ 2.210068] Modules linked in: fjes(+) i915(+) drm_buddy i2c_algo_bit ttm drm_display_helper hid_generic cec rc_core drm_kms_helper syscopyarea sysfillrect sysimgblt crct10dif_pclmul crc32_pclmul ghash_c
lmulni_intel fb_sys_fops aesni_intel i2c_hid_acpi crypto_simd intel_lpss_pci nvme cryptd spi_intel_pci psmouse drm i2c_i801 i2c_hid xhci_pci intel_lpss thunderbolt(+) spi_intel i2c_smbus nvme_core idma64 xhci_pci_renesas wmi hid video pin
ctrl_tigerlake
Nov 5 09:46:42 shusaku kernel: [ 2.210087] CPU: 2 PID: 254 Comm: systemd-udevd Not tainted 5.19.0-23-generic #24-Ubuntu
Nov 5 09:46:42 shusaku kernel: [ 2.210089] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET65W (1.30 ) 08/02/2022
Nov 5 09:46:42 shusaku kernel: [ 2.210091] RIP: 0010:init_bdb_block+0x29a/0x460 [i915]
Nov 5 09:46:42 shusaku kernel: [ 2.210166] Code: 8b 7b 08 4c 8b 77 50 4d 85 f6 74 29 4c 89 4d c8 e8 bb cc 41 e3 44 89 e1 4c 89 f2 48 c7 c7 f0 42 8b c0 48 89 c6 e8 eb 96 8f e3 <0f> 0b 4c 8b 4d c8 e9 b7 fd ff ff 4c 8b 37 eb d2 4c 89 e6
48 c7 c7
Nov 5 09:46:42 shusaku kernel: [ 2.210168] RSP: 0018:ffffabb9c0953888 EFLAGS: 00010246
Nov 5 09:46:42 shusaku kernel: [ 2.210170] RAX: 0000000000000000 RBX: ffff8ca1a1108000 RCX: 0000000000000000
Nov 5 09:46:42 shusaku kernel: [ 2.210171] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
Nov 5 09:46:42 shusaku kernel: [ 2.210172] RBP: ffffabb9c09538d8 R08: 0000000000000000 R09: 0000000000000000
Nov 5 09:46:42 shusaku kernel: [ 2.210173] R10: 0000000000000000 R11: 0000000000000000 R12: 000000000000002a
Nov 5 09:46:42 shusaku kernel: [ 2.210174] R13: 0000000000000000 R14: ffff8ca1826ad170 R15: ffff8ca1a1109328
Nov 5 09:46:42 shusaku kernel: [ 2.210175] FS: 00007f21d34178c0(0000) GS:ffff8ca8bf480000(0000) knlGS:0000000000000000
Nov 5 09:46:42 shusaku kernel: [ 2.210176] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Nov 5 09:46:42 shusaku kernel: [ 2.210177] CR2: 000055a99a0511d8 CR3: 000000011d202003 CR4: 0000000000770ee0
Nov 5 09:46:42 shusaku kernel: [ 2.210179] PKRU: 55555554
Nov 5 09:46:42 shusaku kernel: [ 2.210179] Call Trace:
Nov 5 09:46:42 shusaku kernel: [ 2.210181] <TASK>
Nov 5 09:46:42 shusaku kernel: [ 2.210183] intel_bios_init+0x171/0x7c0 [i915]
Nov 5 09:46:42 shusaku kernel: [ 2.210312] ? drm_vblank_worker_init+0x68/0x80 [drm]
Nov 5 09:46:42 shusaku kernel: [ 2.210391] intel_modeset_init_noirq+0x3b/0x250 [i915]
Nov 5 09:46:42 shusaku kernel: [ 2.210594] i915_driver_probe+0x1ae/0x490 [i915]
Nov 5 09:46:42 shusaku kernel: [ 2.210765] ? drm_privacy_screen_get+0x16d/0x190 [drm]
Nov 5 09:46:42 shusaku kernel: [ 2.210833] ? acpi_dev_found+0x64/0x80
Nov 5 09:46:42 shusaku kernel: [ 2.210842] i915_pci_probe+0x56/0x150 [i915]
Nov 5 09:46:42 shusaku kernel: [ 2.210935] local_pci_probe+0x44/0x90
Nov 5 09:46:42 shusaku kernel: [ 2.210939] pci_call_probe+0x55/0x190
Nov 5 09:46:42 shusaku kernel: [ 2.210940] pci_device_probe+0x84/0x120
Nov 5 09:46:42 shusaku kernel: [ 2.210941] really_probe+0x1dc/0x3b0
Nov 5 09:46:42 shusaku kernel: [ 2.210945] __driver_probe_device+0x12c/0x1b0
Nov 5 09:46:42 shusaku kernel: [ 2.210946] driver_probe_device+0x24/0xd0
Nov 5 09:46:42 shusaku kernel: [ 2.210948] __driver_attach+0xe0/0x210
Nov 5 09:46:42 shusaku kernel: [ 2.210949] ? __device_attach_driver+0x130/0x130
Nov 5 09:46:42 shusaku kernel: [ 2.210951] bus_for_each_dev+0x8d/0xe0
Nov 5 09:46:42 shusaku kernel: [ 2.210952] driver_attach+0x1e/0x30
Nov 5 09:46:42 shusaku kernel: [ 2.210953] bus_add_driver+0x187/0x230
Nov 5 09:46:42 shusaku kernel: [ 2.210955] driver_register+0x8f/0x100
Nov 5 09:46:42 shusaku kernel: [ 2.210956] __pci_register_driver+0x62/0x70
Nov 5 09:46:42 shusaku kernel: [ 2.210958] i915_pci_register_driver+0x23/0x30 [i915]
Nov 5 09:46:42 shusaku kernel: [ 2.210993] i915_init+0x3b/0xf2 [i915]
Nov 5 09:46:42 shusaku kernel: [ 2.211045] ? 0xffffffffc098b000
Nov 5 09:46:42 shusaku kernel: [ 2.211046] do_one_initcall+0x5b/0x240
Nov 5 09:46:42 shusaku kernel: [ 2.211049] do_init_module+0x50/0x210
Nov 5 09:46:42 shusaku kernel: [ 2.211051] load_module+0xb7d/0xcd0
Nov 5 09:46:42 shusaku kernel: [ 2.211053] __do_sys_finit_module+0xc4/0x140
Nov 5 09:46:42 shusaku kernel: [ 2.211054] ? __do_sys_finit_module+0xc4/0x140
Nov 5 09:46:42 shusaku kernel: [ 2.211056] __x64_sys_finit_module+0x18/0x30
Nov 5 09:46:42 shusaku kernel: [ 2.211057] do_syscall_64+0x58/0x90
Nov 5 09:46:42 shusaku kernel: [ 2.211059] ? do_syscall_64+0x67/0x90
Nov 5 09:46:42 shusaku kernel: [ 2.211060] ? sysvec_call_function+0x4b/0xd0
Nov 5 09:46:42 shusaku kernel: [ 2.211062] entry_SYSCALL_64_after_hwframe+0x63/0xcd
Nov 5 09:46:42 shusaku kernel: [ 2.211064] RIP: 0033:0x7f21d3af7c4d
Nov 5 09:46:42 shusaku kernel: [ 2.211065] Code: 5d c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 83 f1 0d 00 f7 d8 64 89 01 48
Nov 5 09:46:42 shusaku kernel: [ 2.211066] RSP: 002b:00007ffdaf1f6398 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
Nov 5 09:46:42 shusaku kernel: [ 2.211067] RAX: ffffffffffffffda RBX: 000055a99a04cd90 RCX: 00007f21d3af7c4d
Nov 5 09:46:42 shusaku kernel: [ 2.211070] RDX: 0000000000000000 RSI: 00007f21d3c79458 RDI: 0000000000000017
Nov 5 09:46:42 shusaku kernel: [ 2.211071] RBP: 00007f21d3c79458 R08: 0000000000000000 R09: 00007ffdaf1f64c0
Nov 5 09:46:42 shusaku kernel: [ 2.211071] R10: 0000000000000017 R11: 0000000000000246 R12: 0000000000020000
Nov 5 09:46:42 shusaku kernel: [ 2.211072] R13: 000055a99a04b610 R14: 0000000000000000 R15: 000055a99a04f420
Nov 5 09:46:42 shusaku kernel: [ 2.211073] </TASK>
Nov 5 09:46:42 shusaku kernel: [ 2.211074] ---[ end trace 0000000000000000 ]---
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: gpoo 2430 F.... pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
DistroRelease: Ubuntu 22.10
InstallationDate: Installed on 2015-04-07 (2772 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Beta amd64 (20150326)
MachineType: LENOVO 21CBCTO1WW
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.17.0-1003-oem root=UUID=bdc1e1f1-542f-4263-9d93-ea65aefb5f89 ro quiet splash
ProcVersionSignature: Ubuntu 5.17.0-1003.3-oem 5.17.0
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.17.0-1003-oem N/A
linux-backports-modules-5.17.0-1003-oem N/A
linux-firmware 20220923.gitf09bebf3-0ubuntu1
Tags: wayland-session kinetic wayland-session
Uname: Linux 5.17.0-1003-oem x86_64
UnreportableReason: This report is about a package that is not installed.
UpgradeStatus: Upgraded to kinetic on 2022-10-21 (18 days ago)
UserGroups: adm audio cdrom dip docker lpadmin plugdev render sambashare sudo
_MarkForUpload: False
dmi.bios.date: 09/27/2022
dmi.bios.release: 1.32
dmi.bios.vendor: LENOVO
dmi.bios.version: N3AET67W (1.32 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CBCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.15
dmi.modalias: dmi:bvnLENOVO:bvrN3AET67W(1.32):bd09/27/2022:br1.32:efr1.15:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10:
dmi.product.family: ThinkPad X1 Carbon Gen 10
dmi.product.name: 21CBCTO1WW
dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10
dmi.product.version: ThinkPad X1 Carbon Gen 10
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996068/+subscriptions
[Bug 2128729] Re: Black screen when booting 5.15.0-160 (on AMD Lucienne / Cezanne / Navi / Renoir / Rembrandt)
I tested a clean install today with 5.15.0-164-fips #174+fips1-Ubuntu
and this bug is still present. I'm guessing this isn't new information
to those of you who were working on the bug, but still waiting on the
fix to get incorporated into the FIPS kernel as well. Thanks for
debugging / fixing this one!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2128729
Title:
Black screen when booting 5.15.0-160 (on AMD Lucienne / Cezanne / Navi
/ Renoir / Rembrandt)
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
In Progress
Bug description:
SRU Justification:
[Impact]
The Ubuntu backport of e6a7df96facdc ("drm/amd/display: Fix MST Null Ptr
for RV") to fix CVE-2024-26700 does not consider that
compute_mst_dsc_configs_for_state() returns a boolean to
indicate success or failure in 5.15, while it returns an integer
in later kernel versions with 0 indicating success. This means
we need to flip the error condition when checking whether the
call succeeded when backporting this to 5.15 and older.
Currently, the error path is taken even though the call to
compute_mst_dsc_configs_for_state() succeeds which causes some systems
to have no video output or a black screen while the system is running.
This is causing loss of video output to screens on affected amdgpu
hardware.
[Fix]
Check the return value of compute_mst_dsc_configs_for_state() in
amdgpu_dm_atomic_check() correctly.
[Test Plan]
Without the fix, there will be no video output to the screen and the
following messages can be found in the kernel log if the kernel is
booted with drm.debug=0x2:
kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] compute_mst_dsc_configs_for_state() failed
kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] Atomic check failed with err: -22
With the fix applied, video output should return to normal and the
kernel warnings will disappear from the log.
[Where problems could occur]
Problems would be observed in odd behavior of the amdgpu driver,
particularly for hardware with DSC support.
[Original Bug Report]
Updated to Kernel 5.15.0-160 from Kernel 5.15.0-157, System seemed to boot but I never got the usual splash logo while booting. Eventually the fans stop and the system sits idle with no video output. I updated the kernel using the system update tool. This system is down stream on Mint, so I can't use the instructions as written in the submission form. But I will do my best. I had to roll back to -157 to write this report. Hope this helps. Logs attached.
_____
[code]
System:
Kernel: 5.15.0-157-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 6.0.4
tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia
base: Ubuntu 22.04 jammy
Machine:
Type: Desktop System: Gigabyte product: X570S AERO G v: -CF serial: <superuser required>
Mobo: Gigabyte model: X570S AERO G v: x.x serial: <superuser required>
UEFI: American Megatrends LLC. v: F3 date: 01/04/2022
CPU:
Info: 8-core model: AMD Ryzen 7 5800X bits: 64 type: MT MCP smt: enabled arch: Zen 3 rev: 0
cache: L1: 512 KiB L2: 4 MiB L3: 32 MiB
Speed (MHz): avg: 4017 high: 4850 min/max: 2200/3800 boost: enabled cores: 1: 4850 2: 3879
3: 3884 4: 3876 5: 3879 6: 3879 7: 3879 8: 3878 9: 4840 10: 3880 11: 3900 12: 3879 13: 3878
14: 3880 15: 3878 16: 4140 bogomips: 121593
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] vendor: Sapphire driver: amdgpu
v: kernel pcie: speed: 16 GT/s lanes: 16 ports: active: DP-2 empty: DP-1,DP-3,HDMI-A-1
bus-ID: 0f:00.0 chip-ID: 1002:73bf class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1080 s-dpi: 96 s-size: 677x285mm (26.7x11.2") s-diag: 735mm (28.9")
Monitor-1: DisplayPort-1 mapped: DP-2 model: LG (GoldStar) 34UC89G serial: <filter>
res: 2560x1080 dpi: 81 size: 798x335mm (31.4x13.2") diag: 865mm (34.1") modes: max: 2560x1080
min: 640x480
OpenGL: renderer: AMD Radeon RX 6900 XT (navi21 LLVM 15.0.7 DRM 3.42 5.15.0-157-generic)
v: 4.6 Mesa 23.2.1-1ubuntu3.1~22.04.3 direct render: Yes
Audio:
Device-1: AMD Navi 21 HDMI Audio [Radeon RX 6800/6800 XT / 6900 XT] driver: snd_hda_intel
v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 0f:00.1 chip-ID: 1002:ab28 class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel pcie:
speed: 16 GT/s lanes: 16 bus-ID: 11:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: HP HyperX Cloud Alpha Wireless type: USB
driver: cdc_acm,hid-generic,snd-usb-audio,usbhid bus-ID: 5-2:2 chip-ID: 03f0:098d class-ID: 0a00
serial: <filter>
Sound Server-1: ALSA v: k5.15.0-157-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: speed: 5 GT/s lanes: 1
bus-ID: 08:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlp8s0 state: up mac: <filter>
Device-2: Intel Ethernet I225-V vendor: Gigabyte driver: igc v: kernel pcie: speed: 5 GT/s
lanes: 1 port: N/A bus-ID: 09:00.0 chip-ID: 8086:15f3 class-ID: 0200
IF: enp9s0 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 5-5:3 chip-ID: 8087:0029
class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
sub-v: 2184 hci-v: 5.2 rev: 2184
Drives:
Local Storage: total: 3.18 TiB used: 1.77 TiB (55.5%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 500GB size: 465.76 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 1B4QFXO7 temp: 34.9 C scheme: GPT
ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 3B4QFXO7 temp: 35.9 C scheme: GPT
ID-3: /dev/nvme2n1 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 2B4QFXO7 temp: 37.9 C
ID-4: /dev/nvme3n1 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 2B4QFXO7 temp: 52.9 C scheme: GPT
Partition:
ID-1: / size: 915.32 GiB used: 640.68 GiB (70.0%) fs: ext4 dev: /dev/nvme3n1p2
ID-2: /boot/efi size: 96 MiB used: 31.4 MiB (32.7%) fs: vfat dev: /dev/nvme0n1p1
Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
USB:
Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Hub-2: 2-0:1 info: Super-speed hub ports: 1 rev: 3.1 speed: 20 Gb/s chip-ID: 1d6b:0003
class-ID: 0900
Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 6 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 3-1:2 info: Integrated Express ITE Device type: HID driver: hid-generic,usbhid
interfaces: 1 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 048d:5702 class-ID: 0300
Hub-4: 3-5:3 info: Genesys Logic Hub ports: 4 rev: 2.1 speed: 480 Mb/s power: 100mA
chip-ID: 05e3:0610 class-ID: 0900
Device-1: 3-5.1:5 info: Mad Catz Catz C.A.T. 9 type: HID driver: hid-generic,usbhid
interfaces: 1 rev: 2.0 speed: 12 Mb/s power: 400mA chip-ID: 0738:0309 class-ID: 0300
Hub-5: 3-6:4 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s power: 100mA
chip-ID: 05e3:0608 class-ID: 0900
Device-1: 3-6.1:6 info: DEXIN MADCATZ R.A.T. 8+ gaming mouse type: Mouse,Keyboard
driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 50mA chip-ID: 12cf:0c05
class-ID: 0300
Hub-6: 4-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
class-ID: 0900
Hub-7: 4-3:2 info: Genesys Logic USB3.1 Hub ports: 4 rev: 3.2 speed: 5 Gb/s chip-ID: 05e3:0626
class-ID: 0900
Hub-8: 5-0:1 info: Hi-speed hub with single TT ports: 6 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 5-2:2 info: HP HyperX Cloud Alpha Wireless
type: Audio,Keyboard,Abstract (modem),CDC-Data driver: cdc_acm,hid-generic,snd-usb-audio,usbhid
interfaces: 6 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 03f0:098d class-ID: 0a00
serial: <filter>
Device-2: 5-5:3 info: Intel AX200 Bluetooth type: Bluetooth driver: btusb interfaces: 2
rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 8087:0029 class-ID: e001
Hub-9: 5-6:4 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s power: 100mA
chip-ID: 05e3:0608 class-ID: 0900
Device-1: 5-6.1:5 info: Logitech G910 Orion Spark Mechanical Keyboard type: Keyboard,HID
driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 500mA chip-ID: 046d:c32b
class-ID: 0300 serial: <filter>
Hub-10: 6-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
class-ID: 0900
Hub-11: 7-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 7-1:2 info: Elan Micro Gaming KB type: Keyboard driver: hid-generic,usbhid
interfaces: 2 rev: 1.1 speed: 1.5 Mb/s power: 100mA chip-ID: 04f3:152e class-ID: 0301
Device-2: 7-2:3 info: SiGma Micro USB HANDLE type: Keyboard,HID driver: hid-generic,usbhid
interfaces: 2 rev: 1.1 speed: 12 Mb/s power: 100mA chip-ID: 1c4f:007c class-ID: 0300
serial: <filter>
Hub-12: 8-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
class-ID: 0900
Device-1: 8-4:2 info: Pioneer Blu-ray Drive type: Mass Storage driver: usb-storage
interfaces: 1 rev: 3.0 speed: 5 Gb/s power: 8mA chip-ID: 08e4:017a class-ID: 0802
serial: <filter>
Sensors:
System Temperatures: cpu: 16.8 C mobo: 16.8 C gpu: amdgpu temp: 43.0 C mem: 46.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Repos:
Packages: 3131 apt: 3092 flatpak: 39
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https: //brave-browser-apt-release.s3.brave.com/ stable main
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http: //packages.linuxmint.com virginia main upstream import backport
2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Info:
Processes: 456 Uptime: 24m wakeups: 0 Memory: 62.69 GiB used: 4.52 GiB (7.2%) Init: systemd
v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Unknown python3.10 client
inxi: 3.3.13
[/code]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2128729/+subscriptions
and this bug is still present. I'm guessing this isn't new information
to those of you who were working on the bug, but still waiting on the
fix to get incorporated into the FIPS kernel as well. Thanks for
debugging / fixing this one!
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2128729
Title:
Black screen when booting 5.15.0-160 (on AMD Lucienne / Cezanne / Navi
/ Renoir / Rembrandt)
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Jammy:
In Progress
Bug description:
SRU Justification:
[Impact]
The Ubuntu backport of e6a7df96facdc ("drm/amd/display: Fix MST Null Ptr
for RV") to fix CVE-2024-26700 does not consider that
compute_mst_dsc_configs_for_state() returns a boolean to
indicate success or failure in 5.15, while it returns an integer
in later kernel versions with 0 indicating success. This means
we need to flip the error condition when checking whether the
call succeeded when backporting this to 5.15 and older.
Currently, the error path is taken even though the call to
compute_mst_dsc_configs_for_state() succeeds which causes some systems
to have no video output or a black screen while the system is running.
This is causing loss of video output to screens on affected amdgpu
hardware.
[Fix]
Check the return value of compute_mst_dsc_configs_for_state() in
amdgpu_dm_atomic_check() correctly.
[Test Plan]
Without the fix, there will be no video output to the screen and the
following messages can be found in the kernel log if the kernel is
booted with drm.debug=0x2:
kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] compute_mst_dsc_configs_for_state() failed
kernel: [drm:amdgpu_dm_atomic_check [amdgpu]] Atomic check failed with err: -22
With the fix applied, video output should return to normal and the
kernel warnings will disappear from the log.
[Where problems could occur]
Problems would be observed in odd behavior of the amdgpu driver,
particularly for hardware with DSC support.
[Original Bug Report]
Updated to Kernel 5.15.0-160 from Kernel 5.15.0-157, System seemed to boot but I never got the usual splash logo while booting. Eventually the fans stop and the system sits idle with no video output. I updated the kernel using the system update tool. This system is down stream on Mint, so I can't use the instructions as written in the submission form. But I will do my best. I had to roll back to -157 to write this report. Hope this helps. Logs attached.
_____
[code]
System:
Kernel: 5.15.0-157-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Cinnamon 6.0.4
tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia
base: Ubuntu 22.04 jammy
Machine:
Type: Desktop System: Gigabyte product: X570S AERO G v: -CF serial: <superuser required>
Mobo: Gigabyte model: X570S AERO G v: x.x serial: <superuser required>
UEFI: American Megatrends LLC. v: F3 date: 01/04/2022
CPU:
Info: 8-core model: AMD Ryzen 7 5800X bits: 64 type: MT MCP smt: enabled arch: Zen 3 rev: 0
cache: L1: 512 KiB L2: 4 MiB L3: 32 MiB
Speed (MHz): avg: 4017 high: 4850 min/max: 2200/3800 boost: enabled cores: 1: 4850 2: 3879
3: 3884 4: 3876 5: 3879 6: 3879 7: 3879 8: 3878 9: 4840 10: 3880 11: 3900 12: 3879 13: 3878
14: 3880 15: 3878 16: 4140 bogomips: 121593
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] vendor: Sapphire driver: amdgpu
v: kernel pcie: speed: 16 GT/s lanes: 16 ports: active: DP-2 empty: DP-1,DP-3,HDMI-A-1
bus-ID: 0f:00.0 chip-ID: 1002:73bf class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa gpu: amdgpu display-ID: :0 screens: 1
Screen-1: 0 s-res: 2560x1080 s-dpi: 96 s-size: 677x285mm (26.7x11.2") s-diag: 735mm (28.9")
Monitor-1: DisplayPort-1 mapped: DP-2 model: LG (GoldStar) 34UC89G serial: <filter>
res: 2560x1080 dpi: 81 size: 798x335mm (31.4x13.2") diag: 865mm (34.1") modes: max: 2560x1080
min: 640x480
OpenGL: renderer: AMD Radeon RX 6900 XT (navi21 LLVM 15.0.7 DRM 3.42 5.15.0-157-generic)
v: 4.6 Mesa 23.2.1-1ubuntu3.1~22.04.3 direct render: Yes
Audio:
Device-1: AMD Navi 21 HDMI Audio [Radeon RX 6800/6800 XT / 6900 XT] driver: snd_hda_intel
v: kernel pcie: speed: 16 GT/s lanes: 16 bus-ID: 0f:00.1 chip-ID: 1002:ab28 class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel pcie:
speed: 16 GT/s lanes: 16 bus-ID: 11:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: HP HyperX Cloud Alpha Wireless type: USB
driver: cdc_acm,hid-generic,snd-usb-audio,usbhid bus-ID: 5-2:2 chip-ID: 03f0:098d class-ID: 0a00
serial: <filter>
Sound Server-1: ALSA v: k5.15.0-157-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel pcie: speed: 5 GT/s lanes: 1
bus-ID: 08:00.0 chip-ID: 8086:2723 class-ID: 0280
IF: wlp8s0 state: up mac: <filter>
Device-2: Intel Ethernet I225-V vendor: Gigabyte driver: igc v: kernel pcie: speed: 5 GT/s
lanes: 1 port: N/A bus-ID: 09:00.0 chip-ID: 8086:15f3 class-ID: 0200
IF: enp9s0 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 5-5:3 chip-ID: 8087:0029
class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 3.0 lmp-v: 5.2
sub-v: 2184 hci-v: 5.2 rev: 2184
Drives:
Local Storage: total: 3.18 TiB used: 1.77 TiB (55.5%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 980 500GB size: 465.76 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 1B4QFXO7 temp: 34.9 C scheme: GPT
ID-2: /dev/nvme1n1 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 3B4QFXO7 temp: 35.9 C scheme: GPT
ID-3: /dev/nvme2n1 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 2B4QFXO7 temp: 37.9 C
ID-4: /dev/nvme3n1 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB speed: 31.6 Gb/s
lanes: 4 type: SSD serial: <filter> rev: 2B4QFXO7 temp: 52.9 C scheme: GPT
Partition:
ID-1: / size: 915.32 GiB used: 640.68 GiB (70.0%) fs: ext4 dev: /dev/nvme3n1p2
ID-2: /boot/efi size: 96 MiB used: 31.4 MiB (32.7%) fs: vfat dev: /dev/nvme0n1p1
Swap:
ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
USB:
Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 1 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Hub-2: 2-0:1 info: Super-speed hub ports: 1 rev: 3.1 speed: 20 Gb/s chip-ID: 1d6b:0003
class-ID: 0900
Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 6 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 3-1:2 info: Integrated Express ITE Device type: HID driver: hid-generic,usbhid
interfaces: 1 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 048d:5702 class-ID: 0300
Hub-4: 3-5:3 info: Genesys Logic Hub ports: 4 rev: 2.1 speed: 480 Mb/s power: 100mA
chip-ID: 05e3:0610 class-ID: 0900
Device-1: 3-5.1:5 info: Mad Catz Catz C.A.T. 9 type: HID driver: hid-generic,usbhid
interfaces: 1 rev: 2.0 speed: 12 Mb/s power: 400mA chip-ID: 0738:0309 class-ID: 0300
Hub-5: 3-6:4 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s power: 100mA
chip-ID: 05e3:0608 class-ID: 0900
Device-1: 3-6.1:6 info: DEXIN MADCATZ R.A.T. 8+ gaming mouse type: Mouse,Keyboard
driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 50mA chip-ID: 12cf:0c05
class-ID: 0300
Hub-6: 4-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
class-ID: 0900
Hub-7: 4-3:2 info: Genesys Logic USB3.1 Hub ports: 4 rev: 3.2 speed: 5 Gb/s chip-ID: 05e3:0626
class-ID: 0900
Hub-8: 5-0:1 info: Hi-speed hub with single TT ports: 6 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 5-2:2 info: HP HyperX Cloud Alpha Wireless
type: Audio,Keyboard,Abstract (modem),CDC-Data driver: cdc_acm,hid-generic,snd-usb-audio,usbhid
interfaces: 6 rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 03f0:098d class-ID: 0a00
serial: <filter>
Device-2: 5-5:3 info: Intel AX200 Bluetooth type: Bluetooth driver: btusb interfaces: 2
rev: 2.0 speed: 12 Mb/s power: 100mA chip-ID: 8087:0029 class-ID: e001
Hub-9: 5-6:4 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s power: 100mA
chip-ID: 05e3:0608 class-ID: 0900
Device-1: 5-6.1:5 info: Logitech G910 Orion Spark Mechanical Keyboard type: Keyboard,HID
driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 500mA chip-ID: 046d:c32b
class-ID: 0300 serial: <filter>
Hub-10: 6-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
class-ID: 0900
Hub-11: 7-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s
chip-ID: 1d6b:0002 class-ID: 0900
Device-1: 7-1:2 info: Elan Micro Gaming KB type: Keyboard driver: hid-generic,usbhid
interfaces: 2 rev: 1.1 speed: 1.5 Mb/s power: 100mA chip-ID: 04f3:152e class-ID: 0301
Device-2: 7-2:3 info: SiGma Micro USB HANDLE type: Keyboard,HID driver: hid-generic,usbhid
interfaces: 2 rev: 1.1 speed: 12 Mb/s power: 100mA chip-ID: 1c4f:007c class-ID: 0300
serial: <filter>
Hub-12: 8-0:1 info: Super-speed hub ports: 4 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
class-ID: 0900
Device-1: 8-4:2 info: Pioneer Blu-ray Drive type: Mass Storage driver: usb-storage
interfaces: 1 rev: 3.0 speed: 5 Gb/s power: 8mA chip-ID: 08e4:017a class-ID: 0802
serial: <filter>
Sensors:
System Temperatures: cpu: 16.8 C mobo: 16.8 C gpu: amdgpu temp: 43.0 C mem: 46.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Repos:
Packages: 3131 apt: 3092 flatpak: 39
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
1: deb [signed-by=/usr/share/keyrings/brave-browser-archive-keyring.gpg] https: //brave-browser-apt-release.s3.brave.com/ stable main
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http: //packages.linuxmint.com virginia main upstream import backport
2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Info:
Processes: 456 Uptime: 24m wakeups: 0 Memory: 62.69 GiB used: 4.52 GiB (7.2%) Init: systemd
v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Unknown python3.10 client
inxi: 3.3.13
[/code]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2128729/+subscriptions
[Bug 2133143] Re: Could not output video from type-c to VGA adapter
This bug was fixed in the package linux-oem-6.14 - 6.14.0-1018.18
---------------
linux-oem-6.14 (6.14.0-1018.18) noble; urgency=medium
* noble/linux-oem-6.14: 6.14.0-1018.18 -proposed tracker (LP:
#2134520)
* Export CWSR size to userspace (LP: #2134491)
- SAUCE: drm/amdkfd: Export the cwsr_size and ctl_stack_size to userspace
- SAUCE: drm/amdkfd: bump minimum vgpr size for gfx1151
* Seamless boot doesn't work on Strix or Strix Halo (LP: #2134488)
- SAUCE: drm/amd/display: Fix scratch registers offsets for DCN35
- SAUCE: drm/amd/display: Fix scratch registers offsets for DCN351
* Fix speaker mute and mic mute leds on more HP 200 G2a platforms
(LP: #2133922)
- ALSA: hda/realtek: fix mute/micmute LEDs don't work for HP 200 G2i
- ALSA: hda/realtek: fix mute/micmute LEDs don't work for more HP laptops
* Enable RTL ASPM for more new Dell platforms (LP: #2133144)
- SAUCE: r8169: Add more Dell platforms to enable ASPM
* Could not output video from type-c to VGA adapter (LP: #2133143)
- SAUCE: drm/i915/dp: Add byte-by-byte fallback for broken USB-C adapters
-- Kuan-Ying Lee <kuan-ying.lee@canonical.com> Wed, 10 Dec 2025
14:43:27 +0800
** Changed in: linux-oem-6.14 (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/2133143
Title:
Could not output video from type-c to VGA adapter
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux-oem-6.17 source package in Noble:
Fix Committed
Status in linux source package in Plucky:
In Progress
Status in linux-oem-6.14 source package in Plucky:
Invalid
Status in linux-oem-6.17 source package in Plucky:
Invalid
Status in linux source package in Questing:
In Progress
Status in linux-oem-6.14 source package in Questing:
Invalid
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
In Progress
Status in linux-oem-6.14 source package in Resolute:
Invalid
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[Impact]
Plugged the Lenovo USB-C to VGA adapter or Dell DA310 hub to thunderbolt 5 port, the communication through AUX timed out, and there is no video output to the VGA monitor
i915 0000:00:02.0: [drm:drm_dp_dpcd_read [drm_display_helper]] AUX
USBC4/DDI TC4/PHY TC4: 0x00000 AUX -> (ret=-110)
[Fix]
https://lkml.org/lkml/2025/11/27/193
v2 - https://lore.kernel.org/lkml/20251204024647.1462866-1-acelan.kao@canonical.com/T/#u
[Test]
1. Find a device with TB5 port
2. Plug a VGA monitor to Lenovo USB-C to VGA adapter[17ef:7217] or Dell DA310[413c:c010]
3. Plug the adapter/hub to the TB5 port
4. The external monitor should work as expected.
[Where problems could occur]
It handles the fail case and doesn't affect the code path if it already works. No regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2133143/+subscriptions
---------------
linux-oem-6.14 (6.14.0-1018.18) noble; urgency=medium
* noble/linux-oem-6.14: 6.14.0-1018.18 -proposed tracker (LP:
#2134520)
* Export CWSR size to userspace (LP: #2134491)
- SAUCE: drm/amdkfd: Export the cwsr_size and ctl_stack_size to userspace
- SAUCE: drm/amdkfd: bump minimum vgpr size for gfx1151
* Seamless boot doesn't work on Strix or Strix Halo (LP: #2134488)
- SAUCE: drm/amd/display: Fix scratch registers offsets for DCN35
- SAUCE: drm/amd/display: Fix scratch registers offsets for DCN351
* Fix speaker mute and mic mute leds on more HP 200 G2a platforms
(LP: #2133922)
- ALSA: hda/realtek: fix mute/micmute LEDs don't work for HP 200 G2i
- ALSA: hda/realtek: fix mute/micmute LEDs don't work for more HP laptops
* Enable RTL ASPM for more new Dell platforms (LP: #2133144)
- SAUCE: r8169: Add more Dell platforms to enable ASPM
* Could not output video from type-c to VGA adapter (LP: #2133143)
- SAUCE: drm/i915/dp: Add byte-by-byte fallback for broken USB-C adapters
-- Kuan-Ying Lee <kuan-ying.lee@canonical.com> Wed, 10 Dec 2025
14:43:27 +0800
** Changed in: linux-oem-6.14 (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/2133143
Title:
Could not output video from type-c to VGA adapter
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux-oem-6.17 source package in Noble:
Fix Committed
Status in linux source package in Plucky:
In Progress
Status in linux-oem-6.14 source package in Plucky:
Invalid
Status in linux-oem-6.17 source package in Plucky:
Invalid
Status in linux source package in Questing:
In Progress
Status in linux-oem-6.14 source package in Questing:
Invalid
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
In Progress
Status in linux-oem-6.14 source package in Resolute:
Invalid
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[Impact]
Plugged the Lenovo USB-C to VGA adapter or Dell DA310 hub to thunderbolt 5 port, the communication through AUX timed out, and there is no video output to the VGA monitor
i915 0000:00:02.0: [drm:drm_dp_dpcd_read [drm_display_helper]] AUX
USBC4/DDI TC4/PHY TC4: 0x00000 AUX -> (ret=-110)
[Fix]
https://lkml.org/lkml/2025/11/27/193
v2 - https://lore.kernel.org/lkml/20251204024647.1462866-1-acelan.kao@canonical.com/T/#u
[Test]
1. Find a device with TB5 port
2. Plug a VGA monitor to Lenovo USB-C to VGA adapter[17ef:7217] or Dell DA310[413c:c010]
3. Plug the adapter/hub to the TB5 port
4. The external monitor should work as expected.
[Where problems could occur]
It handles the fail case and doesn't affect the code path if it already works. No regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2133143/+subscriptions
[Bug 2133144] Re: Enable RTL ASPM for more new Dell platforms
This bug was fixed in the package linux-oem-6.14 - 6.14.0-1018.18
---------------
linux-oem-6.14 (6.14.0-1018.18) noble; urgency=medium
* noble/linux-oem-6.14: 6.14.0-1018.18 -proposed tracker (LP:
#2134520)
* Export CWSR size to userspace (LP: #2134491)
- SAUCE: drm/amdkfd: Export the cwsr_size and ctl_stack_size to userspace
- SAUCE: drm/amdkfd: bump minimum vgpr size for gfx1151
* Seamless boot doesn't work on Strix or Strix Halo (LP: #2134488)
- SAUCE: drm/amd/display: Fix scratch registers offsets for DCN35
- SAUCE: drm/amd/display: Fix scratch registers offsets for DCN351
* Fix speaker mute and mic mute leds on more HP 200 G2a platforms
(LP: #2133922)
- ALSA: hda/realtek: fix mute/micmute LEDs don't work for HP 200 G2i
- ALSA: hda/realtek: fix mute/micmute LEDs don't work for more HP laptops
* Enable RTL ASPM for more new Dell platforms (LP: #2133144)
- SAUCE: r8169: Add more Dell platforms to enable ASPM
* Could not output video from type-c to VGA adapter (LP: #2133143)
- SAUCE: drm/i915/dp: Add byte-by-byte fallback for broken USB-C adapters
-- Kuan-Ying Lee <kuan-ying.lee@canonical.com> Wed, 10 Dec 2025
14:43:27 +0800
** Changed in: linux-oem-6.14 (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/2133144
Title:
Enable RTL ASPM for more new Dell platforms
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux-oem-6.17 source package in Noble:
Fix Committed
Status in linux source package in Plucky:
In Progress
Status in linux-oem-6.14 source package in Plucky:
Invalid
Status in linux-oem-6.17 source package in Plucky:
Invalid
Status in linux source package in Questing:
In Progress
Status in linux-oem-6.14 source package in Questing:
Invalid
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
In Progress
Status in linux-oem-6.14 source package in Resolute:
Invalid
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[Impact]
To pass the energy star cert, the ASPM feature on RTL NIC should be enabled.
[Fix]
Enable the ASPM feature on more new Dell platforms, the family names are used on the new Dell platforms.
[Test]
1. check the value of /sys/power/suspend_stats/total_hw_sleep
2. suspend and resume the system
3. the value of /sys/power/suspend_stats/total_hw_sleep increases
[Where problems could occur]
The listed family names are used in the new Dell platforms, so should not impact the existing platforms. And Dell will push Realtek to fix the ASPM issue found on RTL NIC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2133144/+subscriptions
---------------
linux-oem-6.14 (6.14.0-1018.18) noble; urgency=medium
* noble/linux-oem-6.14: 6.14.0-1018.18 -proposed tracker (LP:
#2134520)
* Export CWSR size to userspace (LP: #2134491)
- SAUCE: drm/amdkfd: Export the cwsr_size and ctl_stack_size to userspace
- SAUCE: drm/amdkfd: bump minimum vgpr size for gfx1151
* Seamless boot doesn't work on Strix or Strix Halo (LP: #2134488)
- SAUCE: drm/amd/display: Fix scratch registers offsets for DCN35
- SAUCE: drm/amd/display: Fix scratch registers offsets for DCN351
* Fix speaker mute and mic mute leds on more HP 200 G2a platforms
(LP: #2133922)
- ALSA: hda/realtek: fix mute/micmute LEDs don't work for HP 200 G2i
- ALSA: hda/realtek: fix mute/micmute LEDs don't work for more HP laptops
* Enable RTL ASPM for more new Dell platforms (LP: #2133144)
- SAUCE: r8169: Add more Dell platforms to enable ASPM
* Could not output video from type-c to VGA adapter (LP: #2133143)
- SAUCE: drm/i915/dp: Add byte-by-byte fallback for broken USB-C adapters
-- Kuan-Ying Lee <kuan-ying.lee@canonical.com> Wed, 10 Dec 2025
14:43:27 +0800
** Changed in: linux-oem-6.14 (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/2133144
Title:
Enable RTL ASPM for more new Dell platforms
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux-oem-6.17 source package in Noble:
Fix Committed
Status in linux source package in Plucky:
In Progress
Status in linux-oem-6.14 source package in Plucky:
Invalid
Status in linux-oem-6.17 source package in Plucky:
Invalid
Status in linux source package in Questing:
In Progress
Status in linux-oem-6.14 source package in Questing:
Invalid
Status in linux-oem-6.17 source package in Questing:
Invalid
Status in linux source package in Resolute:
In Progress
Status in linux-oem-6.14 source package in Resolute:
Invalid
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[Impact]
To pass the energy star cert, the ASPM feature on RTL NIC should be enabled.
[Fix]
Enable the ASPM feature on more new Dell platforms, the family names are used on the new Dell platforms.
[Test]
1. check the value of /sys/power/suspend_stats/total_hw_sleep
2. suspend and resume the system
3. the value of /sys/power/suspend_stats/total_hw_sleep increases
[Where problems could occur]
The listed family names are used in the new Dell platforms, so should not impact the existing platforms. And Dell will push Realtek to fix the ASPM issue found on RTL NIC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2133144/+subscriptions
[Bug 2133922] Re: Fix speaker mute and mic mute leds on more HP 200 G2a platforms
This bug was fixed in the package linux-oem-6.14 - 6.14.0-1018.18
---------------
linux-oem-6.14 (6.14.0-1018.18) noble; urgency=medium
* noble/linux-oem-6.14: 6.14.0-1018.18 -proposed tracker (LP:
#2134520)
* Export CWSR size to userspace (LP: #2134491)
- SAUCE: drm/amdkfd: Export the cwsr_size and ctl_stack_size to userspace
- SAUCE: drm/amdkfd: bump minimum vgpr size for gfx1151
* Seamless boot doesn't work on Strix or Strix Halo (LP: #2134488)
- SAUCE: drm/amd/display: Fix scratch registers offsets for DCN35
- SAUCE: drm/amd/display: Fix scratch registers offsets for DCN351
* Fix speaker mute and mic mute leds on more HP 200 G2a platforms
(LP: #2133922)
- ALSA: hda/realtek: fix mute/micmute LEDs don't work for HP 200 G2i
- ALSA: hda/realtek: fix mute/micmute LEDs don't work for more HP laptops
* Enable RTL ASPM for more new Dell platforms (LP: #2133144)
- SAUCE: r8169: Add more Dell platforms to enable ASPM
* Could not output video from type-c to VGA adapter (LP: #2133143)
- SAUCE: drm/i915/dp: Add byte-by-byte fallback for broken USB-C adapters
-- Kuan-Ying Lee <kuan-ying.lee@canonical.com> Wed, 10 Dec 2025
14:43:27 +0800
** Changed in: linux-oem-6.14 (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/2133922
Title:
Fix speaker mute and mic mute leds on more HP 200 G2a platforms
Status in HWE Next:
New
Status in linux package in Ubuntu:
New
Status in linux-oem-6.14 package in Ubuntu:
New
Status in linux-oem-6.17 package in Ubuntu:
New
Status in linux source package in Noble:
New
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux-oem-6.17 source package in Noble:
Fix Committed
Status in linux source package in Questing:
New
Status in linux-oem-6.14 source package in Questing:
New
Status in linux-oem-6.17 source package in Questing:
New
Status in linux source package in Resolute:
New
Status in linux-oem-6.14 source package in Resolute:
New
Status in linux-oem-6.17 source package in Resolute:
New
Bug description:
SRU Justification:
[Impact]
New HP platform with Realtek ALC3247 audio solution fail to toggle the speaker/mic mute led accordingly while the speaker/mic mute function work w/o problem. This SRU includes fix for the following platforms
BantieI6U: 8EC1 (RPL-UR/HR+dGPM), 8EC5 (TWL+on board SSD), 8EC4 (TWL+plug SSD)
AbeI6U: 8ECE(TWL+plug SSD), 8ECF(TWL+on board SSD), 8ED2(RPL-UR ), 8ED3(RPL-HR)
BantieA6U: 8EE4(MDC), 8EE5(HPT)
AbeA6U: 8EB8(MDC), 8EB6( HPT), 8EE7( HPT-H)
[Fix]
Backport the upstream fix: b72a6ddf6af2("ALSA: hda/realtek: fix mute/micmute LEDs don't work for HP 200 G2i") and a30fa8122222 ("ALSA: hda/realtek: fix mute/micmute LEDs don't work for more HP laptops")
[Test Case]
1. Boot up the machine of new HP platforms w/ the listed SSIDs
2. Press Fn+F9 for mic-mute function Fn+F6 for speaker mute function
3. Click led lights up/down in according with the speaker/mic mute functions.
[Where problems could occur]
It adds the quirk for particular SSIDs of the audio solution. No regression expected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2133922/+subscriptions
---------------
linux-oem-6.14 (6.14.0-1018.18) noble; urgency=medium
* noble/linux-oem-6.14: 6.14.0-1018.18 -proposed tracker (LP:
#2134520)
* Export CWSR size to userspace (LP: #2134491)
- SAUCE: drm/amdkfd: Export the cwsr_size and ctl_stack_size to userspace
- SAUCE: drm/amdkfd: bump minimum vgpr size for gfx1151
* Seamless boot doesn't work on Strix or Strix Halo (LP: #2134488)
- SAUCE: drm/amd/display: Fix scratch registers offsets for DCN35
- SAUCE: drm/amd/display: Fix scratch registers offsets for DCN351
* Fix speaker mute and mic mute leds on more HP 200 G2a platforms
(LP: #2133922)
- ALSA: hda/realtek: fix mute/micmute LEDs don't work for HP 200 G2i
- ALSA: hda/realtek: fix mute/micmute LEDs don't work for more HP laptops
* Enable RTL ASPM for more new Dell platforms (LP: #2133144)
- SAUCE: r8169: Add more Dell platforms to enable ASPM
* Could not output video from type-c to VGA adapter (LP: #2133143)
- SAUCE: drm/i915/dp: Add byte-by-byte fallback for broken USB-C adapters
-- Kuan-Ying Lee <kuan-ying.lee@canonical.com> Wed, 10 Dec 2025
14:43:27 +0800
** Changed in: linux-oem-6.14 (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/2133922
Title:
Fix speaker mute and mic mute leds on more HP 200 G2a platforms
Status in HWE Next:
New
Status in linux package in Ubuntu:
New
Status in linux-oem-6.14 package in Ubuntu:
New
Status in linux-oem-6.17 package in Ubuntu:
New
Status in linux source package in Noble:
New
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux-oem-6.17 source package in Noble:
Fix Committed
Status in linux source package in Questing:
New
Status in linux-oem-6.14 source package in Questing:
New
Status in linux-oem-6.17 source package in Questing:
New
Status in linux source package in Resolute:
New
Status in linux-oem-6.14 source package in Resolute:
New
Status in linux-oem-6.17 source package in Resolute:
New
Bug description:
SRU Justification:
[Impact]
New HP platform with Realtek ALC3247 audio solution fail to toggle the speaker/mic mute led accordingly while the speaker/mic mute function work w/o problem. This SRU includes fix for the following platforms
BantieI6U: 8EC1 (RPL-UR/HR+dGPM), 8EC5 (TWL+on board SSD), 8EC4 (TWL+plug SSD)
AbeI6U: 8ECE(TWL+plug SSD), 8ECF(TWL+on board SSD), 8ED2(RPL-UR ), 8ED3(RPL-HR)
BantieA6U: 8EE4(MDC), 8EE5(HPT)
AbeA6U: 8EB8(MDC), 8EB6( HPT), 8EE7( HPT-H)
[Fix]
Backport the upstream fix: b72a6ddf6af2("ALSA: hda/realtek: fix mute/micmute LEDs don't work for HP 200 G2i") and a30fa8122222 ("ALSA: hda/realtek: fix mute/micmute LEDs don't work for more HP laptops")
[Test Case]
1. Boot up the machine of new HP platforms w/ the listed SSIDs
2. Press Fn+F9 for mic-mute function Fn+F6 for speaker mute function
3. Click led lights up/down in according with the speaker/mic mute functions.
[Where problems could occur]
It adds the quirk for particular SSIDs of the audio solution. No regression expected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2133922/+subscriptions
[Bug 2134488] Re: Seamless boot doesn't work on Strix or Strix Halo
This bug was fixed in the package linux-oem-6.14 - 6.14.0-1018.18
---------------
linux-oem-6.14 (6.14.0-1018.18) noble; urgency=medium
* noble/linux-oem-6.14: 6.14.0-1018.18 -proposed tracker (LP:
#2134520)
* Export CWSR size to userspace (LP: #2134491)
- SAUCE: drm/amdkfd: Export the cwsr_size and ctl_stack_size to userspace
- SAUCE: drm/amdkfd: bump minimum vgpr size for gfx1151
* Seamless boot doesn't work on Strix or Strix Halo (LP: #2134488)
- SAUCE: drm/amd/display: Fix scratch registers offsets for DCN35
- SAUCE: drm/amd/display: Fix scratch registers offsets for DCN351
* Fix speaker mute and mic mute leds on more HP 200 G2a platforms
(LP: #2133922)
- ALSA: hda/realtek: fix mute/micmute LEDs don't work for HP 200 G2i
- ALSA: hda/realtek: fix mute/micmute LEDs don't work for more HP laptops
* Enable RTL ASPM for more new Dell platforms (LP: #2133144)
- SAUCE: r8169: Add more Dell platforms to enable ASPM
* Could not output video from type-c to VGA adapter (LP: #2133143)
- SAUCE: drm/i915/dp: Add byte-by-byte fallback for broken USB-C adapters
-- Kuan-Ying Lee <kuan-ying.lee@canonical.com> Wed, 10 Dec 2025
14:43:27 +0800
** Changed in: linux-oem-6.14 (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/2134488
Title:
Seamless boot doesn't work on Strix or Strix Halo
Status in linux package in Ubuntu:
New
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux-oem-6.17 source package in Noble:
Fix Committed
Status in linux source package in Resolute:
New
Status in linux-oem-6.14 source package in Resolute:
Invalid
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[Impact]
During bootup sequence there is a black screen when it's intended that BGRT logo continues through bootup.
This is because the stream hasn't been marked for seamless boot and so the amdgpu kernel module does a modeset which leaves a black screen until next drawing.
[Test Plan]
Obtain Strix or Strix Halo design that has eDP panel that doesn't
support DSC. (DSC is incompatible with seamless boot).
Turn on drm.debug=0x106.
Verify that message "Marked stream for seamless boot optimization" is
viewed in logs.
NOTE: There are other reasons a black screen could occur during
bootup. The key point here is the new message which indicates that
amdgpu has adopted the seamless boot process.
[ Where problems could occur ]
AMD Strix or Strix Halo designs.
[Upstream changes]
These are to be merged for 6.19-rc for fixing this issue.
https://lore.kernel.org/amd-gfx/20251209085702.293682-3-chen-yu.chen@amd.com/T/#u
https://lore.kernel.org/amd-gfx/20251209085702.293682-4-chen-yu.chen@amd.com/T/#u
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2134488/+subscriptions
---------------
linux-oem-6.14 (6.14.0-1018.18) noble; urgency=medium
* noble/linux-oem-6.14: 6.14.0-1018.18 -proposed tracker (LP:
#2134520)
* Export CWSR size to userspace (LP: #2134491)
- SAUCE: drm/amdkfd: Export the cwsr_size and ctl_stack_size to userspace
- SAUCE: drm/amdkfd: bump minimum vgpr size for gfx1151
* Seamless boot doesn't work on Strix or Strix Halo (LP: #2134488)
- SAUCE: drm/amd/display: Fix scratch registers offsets for DCN35
- SAUCE: drm/amd/display: Fix scratch registers offsets for DCN351
* Fix speaker mute and mic mute leds on more HP 200 G2a platforms
(LP: #2133922)
- ALSA: hda/realtek: fix mute/micmute LEDs don't work for HP 200 G2i
- ALSA: hda/realtek: fix mute/micmute LEDs don't work for more HP laptops
* Enable RTL ASPM for more new Dell platforms (LP: #2133144)
- SAUCE: r8169: Add more Dell platforms to enable ASPM
* Could not output video from type-c to VGA adapter (LP: #2133143)
- SAUCE: drm/i915/dp: Add byte-by-byte fallback for broken USB-C adapters
-- Kuan-Ying Lee <kuan-ying.lee@canonical.com> Wed, 10 Dec 2025
14:43:27 +0800
** Changed in: linux-oem-6.14 (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/2134488
Title:
Seamless boot doesn't work on Strix or Strix Halo
Status in linux package in Ubuntu:
New
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux-oem-6.17 source package in Noble:
Fix Committed
Status in linux source package in Resolute:
New
Status in linux-oem-6.14 source package in Resolute:
Invalid
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[Impact]
During bootup sequence there is a black screen when it's intended that BGRT logo continues through bootup.
This is because the stream hasn't been marked for seamless boot and so the amdgpu kernel module does a modeset which leaves a black screen until next drawing.
[Test Plan]
Obtain Strix or Strix Halo design that has eDP panel that doesn't
support DSC. (DSC is incompatible with seamless boot).
Turn on drm.debug=0x106.
Verify that message "Marked stream for seamless boot optimization" is
viewed in logs.
NOTE: There are other reasons a black screen could occur during
bootup. The key point here is the new message which indicates that
amdgpu has adopted the seamless boot process.
[ Where problems could occur ]
AMD Strix or Strix Halo designs.
[Upstream changes]
These are to be merged for 6.19-rc for fixing this issue.
https://lore.kernel.org/amd-gfx/20251209085702.293682-3-chen-yu.chen@amd.com/T/#u
https://lore.kernel.org/amd-gfx/20251209085702.293682-4-chen-yu.chen@amd.com/T/#u
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2134488/+subscriptions
[Bug 2134491] Re: Export CWSR size to userspace
This bug was fixed in the package linux-oem-6.14 - 6.14.0-1018.18
---------------
linux-oem-6.14 (6.14.0-1018.18) noble; urgency=medium
* noble/linux-oem-6.14: 6.14.0-1018.18 -proposed tracker (LP:
#2134520)
* Export CWSR size to userspace (LP: #2134491)
- SAUCE: drm/amdkfd: Export the cwsr_size and ctl_stack_size to userspace
- SAUCE: drm/amdkfd: bump minimum vgpr size for gfx1151
* Seamless boot doesn't work on Strix or Strix Halo (LP: #2134488)
- SAUCE: drm/amd/display: Fix scratch registers offsets for DCN35
- SAUCE: drm/amd/display: Fix scratch registers offsets for DCN351
* Fix speaker mute and mic mute leds on more HP 200 G2a platforms
(LP: #2133922)
- ALSA: hda/realtek: fix mute/micmute LEDs don't work for HP 200 G2i
- ALSA: hda/realtek: fix mute/micmute LEDs don't work for more HP laptops
* Enable RTL ASPM for more new Dell platforms (LP: #2133144)
- SAUCE: r8169: Add more Dell platforms to enable ASPM
* Could not output video from type-c to VGA adapter (LP: #2133143)
- SAUCE: drm/i915/dp: Add byte-by-byte fallback for broken USB-C adapters
-- Kuan-Ying Lee <kuan-ying.lee@canonical.com> Wed, 10 Dec 2025
14:43:27 +0800
** Changed in: linux-oem-6.14 (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/2134491
Title:
Export CWSR size to userspace
Status in linux package in Ubuntu:
New
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux-oem-6.17 source package in Noble:
Fix Committed
Status in linux source package in Resolute:
New
Status in linux-oem-6.14 source package in Resolute:
Invalid
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[Impact]
Legacy ROCm releases (7.2 or earlier) hardcode per-program VGPR size which is used to calculate context switch area. Kernel also hardcodes this information.
ROCm 7.10 and later releases are switching away from hardcoded information and need the kernel to be source of truth and advertise.
[Test Plan]
Verify that kfd properties include cwsr size.
❯ cat /sys/class/kfd/kfd/topology/nodes/1/properties | grep cwsr_size
[ Where problems could occur ]
Strix Halo designs with ROCm
[Upstream changes]
These are to be merged for 6.19-rc for fixing this issue.
https://lore.kernel.org/amd-gfx/20251205184158.2261400-1-mario.limonciello@amd.com/
https://lore.kernel.org/amd-gfx/20251205195730.1266877-1-jonathan.kim@amd.com/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2134491/+subscriptions
---------------
linux-oem-6.14 (6.14.0-1018.18) noble; urgency=medium
* noble/linux-oem-6.14: 6.14.0-1018.18 -proposed tracker (LP:
#2134520)
* Export CWSR size to userspace (LP: #2134491)
- SAUCE: drm/amdkfd: Export the cwsr_size and ctl_stack_size to userspace
- SAUCE: drm/amdkfd: bump minimum vgpr size for gfx1151
* Seamless boot doesn't work on Strix or Strix Halo (LP: #2134488)
- SAUCE: drm/amd/display: Fix scratch registers offsets for DCN35
- SAUCE: drm/amd/display: Fix scratch registers offsets for DCN351
* Fix speaker mute and mic mute leds on more HP 200 G2a platforms
(LP: #2133922)
- ALSA: hda/realtek: fix mute/micmute LEDs don't work for HP 200 G2i
- ALSA: hda/realtek: fix mute/micmute LEDs don't work for more HP laptops
* Enable RTL ASPM for more new Dell platforms (LP: #2133144)
- SAUCE: r8169: Add more Dell platforms to enable ASPM
* Could not output video from type-c to VGA adapter (LP: #2133143)
- SAUCE: drm/i915/dp: Add byte-by-byte fallback for broken USB-C adapters
-- Kuan-Ying Lee <kuan-ying.lee@canonical.com> Wed, 10 Dec 2025
14:43:27 +0800
** Changed in: linux-oem-6.14 (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/2134491
Title:
Export CWSR size to userspace
Status in linux package in Ubuntu:
New
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux-oem-6.17 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux-oem-6.17 source package in Noble:
Fix Committed
Status in linux source package in Resolute:
New
Status in linux-oem-6.14 source package in Resolute:
Invalid
Status in linux-oem-6.17 source package in Resolute:
Invalid
Bug description:
[Impact]
Legacy ROCm releases (7.2 or earlier) hardcode per-program VGPR size which is used to calculate context switch area. Kernel also hardcodes this information.
ROCm 7.10 and later releases are switching away from hardcoded information and need the kernel to be source of truth and advertise.
[Test Plan]
Verify that kfd properties include cwsr size.
❯ cat /sys/class/kfd/kfd/topology/nodes/1/properties | grep cwsr_size
[ Where problems could occur ]
Strix Halo designs with ROCm
[Upstream changes]
These are to be merged for 6.19-rc for fixing this issue.
https://lore.kernel.org/amd-gfx/20251205184158.2261400-1-mario.limonciello@amd.com/
https://lore.kernel.org/amd-gfx/20251205195730.1266877-1-jonathan.kim@amd.com/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2134491/+subscriptions
[Bug 2132086] Re: Bluetooth Fails on Ubuntu 24.04 with AMD Ryzen AI CPUs
** Package changed: linux (Ubuntu) => linux-hwe-6.14 (Ubuntu)
** Summary changed:
- Bluetooth Fails on Ubuntu 24.04 with AMD Ryzen AI CPUs
+ [mt7925e] Bluetooth Fails on Ubuntu 24.04 with AMD Ryzen AI CPUs
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2132086
Title:
[mt7925e] Bluetooth Fails on Ubuntu 24.04 with AMD Ryzen AI CPUs
Status in bluez package in Ubuntu:
New
Status in linux-hwe-6.14 package in Ubuntu:
New
Bug description:
Bluetooth does not work on Ubuntu 24.04 machines running with AMD
Ryzen AI processors. The only workaround is booting into BIOS,
disabling Bluetooth, rebooting, booting back into BIOS, and re-
enabling Bluetooth in BIOS. All other troubleshooting methods fail to
work.
Currently 4 systems have been affected:
2 computers with AMD Ryzen AI 9 HX PRO 370 w/ Radeon 890M
&
2 computers with AMD Ryzen AI 7 PRO 350 w/ Radeon 860M
After a few hours/days of use with a fresh install of Ubuntu 24.04 the
Bluetooth toggle grays out and is unable to be turned on or used
despite rebooting or restarting the Bluetooth service.
Ubuntu release: Ubuntu 24.04.3 LTS
Package version: Bluez 5.72-0ubuntu5.5 (I'm not confident this package is responsible for the bug)
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2025-10-14 (41 days ago)
InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. Dell Pro 16 Plus PB16255
NonfreeKernelModules: zfs
Package: linux
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.14.0-1015-oem root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.14.0-1015.15-oem 6.14.11
Tags: noble wayland-session
Uname: Linux 6.14.0-1015-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom lxd plugdev sudo users video
_MarkForUpload: True
dmi.bios.date: 07/15/2025
dmi.bios.release: 1.5
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.2
dmi.board.name: 0NV2T5
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 1.4
dmi.modalias: dmi:bvnDellInc.:bvr1.5.2:bd07/15/2025:br1.5:efr1.4:svnDellInc.:pnDellPro16PlusPB16255:pvr:rvnDellInc.:rn0NV2T5:rvrA00:cvnDellInc.:ct10:cvr:sku0D4F:
dmi.product.family: Dell Pro Laptops
dmi.product.name: Dell Pro 16 Plus PB16255
dmi.product.sku: 0D4F
dmi.sys.vendor: Dell Inc.
hciconfig:
hci0: Type: Primary Bus: USB
BD Address: 48:45:E6:0F:93:48 ACL MTU: 1021:8 SCO MTU: 240:8
UP RUNNING PSCAN
RX bytes:17443 acl:33 sco:0 events:2238 errors:0
TX bytes:525966 acl:36 sco:0 commands:2192 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2132086/+subscriptions
** Summary changed:
- Bluetooth Fails on Ubuntu 24.04 with AMD Ryzen AI CPUs
+ [mt7925e] Bluetooth Fails on Ubuntu 24.04 with AMD Ryzen AI CPUs
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2132086
Title:
[mt7925e] Bluetooth Fails on Ubuntu 24.04 with AMD Ryzen AI CPUs
Status in bluez package in Ubuntu:
New
Status in linux-hwe-6.14 package in Ubuntu:
New
Bug description:
Bluetooth does not work on Ubuntu 24.04 machines running with AMD
Ryzen AI processors. The only workaround is booting into BIOS,
disabling Bluetooth, rebooting, booting back into BIOS, and re-
enabling Bluetooth in BIOS. All other troubleshooting methods fail to
work.
Currently 4 systems have been affected:
2 computers with AMD Ryzen AI 9 HX PRO 370 w/ Radeon 890M
&
2 computers with AMD Ryzen AI 7 PRO 350 w/ Radeon 860M
After a few hours/days of use with a fresh install of Ubuntu 24.04 the
Bluetooth toggle grays out and is unable to be turned on or used
despite rebooting or restarting the Bluetooth service.
Ubuntu release: Ubuntu 24.04.3 LTS
Package version: Bluez 5.72-0ubuntu5.5 (I'm not confident this package is responsible for the bug)
---
ProblemType: Bug
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 24.04
InstallationDate: Installed on 2025-10-14 (41 days ago)
InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. Dell Pro 16 Plus PB16255
NonfreeKernelModules: zfs
Package: linux
PackageArchitecture: amd64
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/usr/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.14.0-1015-oem root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.14.0-1015.15-oem 6.14.11
Tags: noble wayland-session
Uname: Linux 6.14.0-1015-oem x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom lxd plugdev sudo users video
_MarkForUpload: True
dmi.bios.date: 07/15/2025
dmi.bios.release: 1.5
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.2
dmi.board.name: 0NV2T5
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.ec.firmware.release: 1.4
dmi.modalias: dmi:bvnDellInc.:bvr1.5.2:bd07/15/2025:br1.5:efr1.4:svnDellInc.:pnDellPro16PlusPB16255:pvr:rvnDellInc.:rn0NV2T5:rvrA00:cvnDellInc.:ct10:cvr:sku0D4F:
dmi.product.family: Dell Pro Laptops
dmi.product.name: Dell Pro 16 Plus PB16255
dmi.product.sku: 0D4F
dmi.sys.vendor: Dell Inc.
hciconfig:
hci0: Type: Primary Bus: USB
BD Address: 48:45:E6:0F:93:48 ACL MTU: 1021:8 SCO MTU: 240:8
UP RUNNING PSCAN
RX bytes:17443 acl:33 sco:0 events:2238 errors:0
TX bytes:525966 acl:36 sco:0 commands:2192 errors:0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2132086/+subscriptions
[Bug 2131710] Re: Locked computer screen and walked away, upron return computer was unresponsive and unable to log in. Required REISUB to reboot computer.
** Package changed: linux (Ubuntu) => linux-hwe-6.14 (Ubuntu)
** Changed in: linux-hwe-6.14 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2131710
Title:
Locked computer screen and walked away, upron return computer was
unresponsive and unable to log in. Required REISUB to reboot computer.
Status in linux-hwe-6.14 package in Ubuntu:
New
Bug description:
A short while after booting the laptop, I locked my session and walked
away to deal with an issue. Upon return, the screen was black and non-
responsive. Unplugging and re-plugging my USB C external monitors did
eventually restore the desktop image/lock screen (with system time),
but the keyboard and mouse input was not reflected on the screen. ALT
SYS-REQ and REISUB to reboot.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gdm3 46.2-1ubuntu1~24.04.4
ProcVersionSignature: Ubuntu 6.14.0-35.35~24.04.1-generic 6.14.11
Uname: Linux 6.14.0-35-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 17 18:32:45 2025
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.14/+bug/2131710/+subscriptions
** Changed in: linux-hwe-6.14 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2131710
Title:
Locked computer screen and walked away, upron return computer was
unresponsive and unable to log in. Required REISUB to reboot computer.
Status in linux-hwe-6.14 package in Ubuntu:
New
Bug description:
A short while after booting the laptop, I locked my session and walked
away to deal with an issue. Upon return, the screen was black and non-
responsive. Unplugging and re-plugging my USB C external monitors did
eventually restore the desktop image/lock screen (with system time),
but the keyboard and mouse input was not reflected on the screen. ALT
SYS-REQ and REISUB to reboot.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gdm3 46.2-1ubuntu1~24.04.4
ProcVersionSignature: Ubuntu 6.14.0-35.35~24.04.1-generic 6.14.11
Uname: Linux 6.14.0-35-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.1-0ubuntu3.8
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 17 18:32:45 2025
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.14/+bug/2131710/+subscriptions
[Bug 2119479] Re: [SRU][Q/P/N:hwe-6.14] mt7925: Add MBSS support
This bug was fixed in the package linux - 6.17.0-8.8
---------------
linux (6.17.0-8.8) questing; urgency=medium
* questing/linux: 6.17.0-8.8 -proposed tracker (LP: #2131554)
* crash when reading from /sys/kernel/tracing/rv/enabled_monitors
(LP: #2131136)
- rv: Fully convert enabled_monitors to use list_head as iterator
* i40e driver is triggering VF resets on every link state change
(LP: #2130552)
- i40e: avoid redundant VF link state updates
* kernel crash on bootup for some arm64 machines (LP: #2129770)
- KVM: arm64: Guard PMSCR_EL1 initialization with SPE presence check
* CVE-2025-40018
- ipvs: Defer ip_vs_ftp unregister during netns cleanup
-- Manuel Diewald <manuel.diewald@canonical.com> Fri, 14 Nov 2025
17:53:03 +0100
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
** CVE added: https://cve.org/CVERecord?id=CVE-2025-40018
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2119479
Title:
[SRU][Q/P/N:hwe-6.14] mt7925: Add MBSS support
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-hwe-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-hwe-6.14 source package in Noble:
Fix Released
Status in linux source package in Plucky:
Fix Released
Status in linux-firmware source package in Plucky:
Fix Released
Status in linux-hwe-6.14 source package in Plucky:
Invalid
Status in linux source package in Questing:
Fix Released
Status in linux-firmware source package in Questing:
Fix Released
Status in linux-hwe-6.14 source package in Questing:
Invalid
Bug description:
[SRU Justfication]
BugLink: https://bugs.launchpad.net/bugs/2119479
These binary firmware changes are required to fix the following issues
(provided by vendor):
Release Note:
- Fix "PCIE AER: RxErr" issue
- Fix "probe request Supported Rates Listed twice" issue
- with driver patch: https://patchwork.kernel.org/project/linux-wireless/patch/20250616063649.1100503-1-mingyen.hsieh@mediatek.com/
- Send Beacon frame (with MBSS IE) to driver directly for mac80211.
- with driver patch: https://patchwork.kernel.org/project/linux-wireless/patch/20250729084932.264155-1-mingyen.hsieh@mediatek.com/
This driver change is also required:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/mediatek/mt76?id=74e756b9e28af3ee94a7ea480bb39694be5fbd96
(applied from https://patchwork.kernel.org/project/linux-
wireless/patch/20250729084932.264155-1-mingyen.hsieh@mediatek.com/)
[Impact]
Addresses lack of some WiFi and Bluetooth functionality on mt7925
device and undefined behavior / unreliability when connecting to some
APs. Specifically, this update changes how the beacon frame with MBSS
IE is delivered to the driver, in conjunction with this kernel change:
https://patchwork.kernel.org/project/linux-
wireless/patch/20250729084932.264155-1-mingyen.hsieh@mediatek.com/
[Fix]
Apply the following vendor-proposed patches from upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/mediatek/mt7925?id=2ccae12c4f73bf130143ab7cc9c8546d25faac47
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/mediatek/mt7925?id=ebf45cd0f8d0e98d08e7ecfc10342735425677b1
[Test Case]
Verify that Wifi and BT connections can still be established with the
updated blobs, and verify that MBSS functionality works as expected
[Where problems could occur]
Without these patches, affected wireless adapters connecting to 6GHz
APs that broadcast MBSSID have undefined behavior. In various tests,
it was observed that there were frequent disconnections in cases where
the host was closer in proximity to the AP, but that there were
instances where a connection could be maintained if they were farther
away.
If this firmware is used without
https://patchwork.kernel.org/project/linux-
wireless/patch/20250729084932.264155-1-mingyen.hsieh@mediatek.com/
being present in the running kernel, the firmware patch can cause some
such devices to be unable to detect their APs regardless of distance.
This could be perceived as a regression for users who did not observe
this issue due to device positioning (which would be resolved once
they update their kernel to include the related driver patch, which I
will SRU into noble-generic and derivatives).
However, given that the best case behavior for impacted devices
without these patches is undefined behavior at best, I believe they
are necessary/appropriate to SRU.
Regarding the kernel patch - this only adds the required handlers for
MBSS support. If any issues exist in the implementation of those new
functions, the user could experience unexpected behavior when
attempting to use MBSS functionality.
[Other Info]
This update originates from a support request by Nvidia
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2119479/+subscriptions
---------------
linux (6.17.0-8.8) questing; urgency=medium
* questing/linux: 6.17.0-8.8 -proposed tracker (LP: #2131554)
* crash when reading from /sys/kernel/tracing/rv/enabled_monitors
(LP: #2131136)
- rv: Fully convert enabled_monitors to use list_head as iterator
* i40e driver is triggering VF resets on every link state change
(LP: #2130552)
- i40e: avoid redundant VF link state updates
* kernel crash on bootup for some arm64 machines (LP: #2129770)
- KVM: arm64: Guard PMSCR_EL1 initialization with SPE presence check
* CVE-2025-40018
- ipvs: Defer ip_vs_ftp unregister during netns cleanup
-- Manuel Diewald <manuel.diewald@canonical.com> Fri, 14 Nov 2025
17:53:03 +0100
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
** CVE added: https://cve.org/CVERecord?id=CVE-2025-40018
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2119479
Title:
[SRU][Q/P/N:hwe-6.14] mt7925: Add MBSS support
Status in linux package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-hwe-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-hwe-6.14 source package in Noble:
Fix Released
Status in linux source package in Plucky:
Fix Released
Status in linux-firmware source package in Plucky:
Fix Released
Status in linux-hwe-6.14 source package in Plucky:
Invalid
Status in linux source package in Questing:
Fix Released
Status in linux-firmware source package in Questing:
Fix Released
Status in linux-hwe-6.14 source package in Questing:
Invalid
Bug description:
[SRU Justfication]
BugLink: https://bugs.launchpad.net/bugs/2119479
These binary firmware changes are required to fix the following issues
(provided by vendor):
Release Note:
- Fix "PCIE AER: RxErr" issue
- Fix "probe request Supported Rates Listed twice" issue
- with driver patch: https://patchwork.kernel.org/project/linux-wireless/patch/20250616063649.1100503-1-mingyen.hsieh@mediatek.com/
- Send Beacon frame (with MBSS IE) to driver directly for mac80211.
- with driver patch: https://patchwork.kernel.org/project/linux-wireless/patch/20250729084932.264155-1-mingyen.hsieh@mediatek.com/
This driver change is also required:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/wireless/mediatek/mt76?id=74e756b9e28af3ee94a7ea480bb39694be5fbd96
(applied from https://patchwork.kernel.org/project/linux-
wireless/patch/20250729084932.264155-1-mingyen.hsieh@mediatek.com/)
[Impact]
Addresses lack of some WiFi and Bluetooth functionality on mt7925
device and undefined behavior / unreliability when connecting to some
APs. Specifically, this update changes how the beacon frame with MBSS
IE is delivered to the driver, in conjunction with this kernel change:
https://patchwork.kernel.org/project/linux-
wireless/patch/20250729084932.264155-1-mingyen.hsieh@mediatek.com/
[Fix]
Apply the following vendor-proposed patches from upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/mediatek/mt7925?id=2ccae12c4f73bf130143ab7cc9c8546d25faac47
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/mediatek/mt7925?id=ebf45cd0f8d0e98d08e7ecfc10342735425677b1
[Test Case]
Verify that Wifi and BT connections can still be established with the
updated blobs, and verify that MBSS functionality works as expected
[Where problems could occur]
Without these patches, affected wireless adapters connecting to 6GHz
APs that broadcast MBSSID have undefined behavior. In various tests,
it was observed that there were frequent disconnections in cases where
the host was closer in proximity to the AP, but that there were
instances where a connection could be maintained if they were farther
away.
If this firmware is used without
https://patchwork.kernel.org/project/linux-
wireless/patch/20250729084932.264155-1-mingyen.hsieh@mediatek.com/
being present in the running kernel, the firmware patch can cause some
such devices to be unable to detect their APs regardless of distance.
This could be perceived as a regression for users who did not observe
this issue due to device positioning (which would be resolved once
they update their kernel to include the related driver patch, which I
will SRU into noble-generic and derivatives).
However, given that the best case behavior for impacted devices
without these patches is undefined behavior at best, I believe they
are necessary/appropriate to SRU.
Regarding the kernel patch - this only adds the required handlers for
MBSS support. If any issues exist in the implementation of those new
functions, the user could experience unexpected behavior when
attempting to use MBSS functionality.
[Other Info]
This update originates from a support request by Nvidia
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2119479/+subscriptions
[Bug 2123901] Re: r8169 can not wake on LAN via SFP moudule
This bug was fixed in the package linux - 6.17.0-8.8
---------------
linux (6.17.0-8.8) questing; urgency=medium
* questing/linux: 6.17.0-8.8 -proposed tracker (LP: #2131554)
* crash when reading from /sys/kernel/tracing/rv/enabled_monitors
(LP: #2131136)
- rv: Fully convert enabled_monitors to use list_head as iterator
* i40e driver is triggering VF resets on every link state change
(LP: #2130552)
- i40e: avoid redundant VF link state updates
* kernel crash on bootup for some arm64 machines (LP: #2129770)
- KVM: arm64: Guard PMSCR_EL1 initialization with SPE presence check
* CVE-2025-40018
- ipvs: Defer ip_vs_ftp unregister during netns cleanup
-- Manuel Diewald <manuel.diewald@canonical.com> Fri, 14 Nov 2025
17:53:03 +0100
** Changed in: linux (Ubuntu)
Status: Invalid => Fix Released
** CVE added: https://cve.org/CVERecord?id=CVE-2025-40018
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2123901
Title:
r8169 can not wake on LAN via SFP moudule
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux source package in Plucky:
Fix Released
Status in linux-oem-6.14 source package in Plucky:
Invalid
Status in linux source package in Questing:
Fix Released
Status in linux-oem-6.14 source package in Questing:
Invalid
Bug description:
[Impact]
Can not wake on LAN via Realtek SFP moudule.
[Fix]
Realtek provides a patch to fix this issue
https://patchew.org/linux/20250904021123.5734-1-hau@realtek.com/
Which is included in linux-next
bf7154ffb1c65 r8169: set EEE speed down ratio to 1
[Test]
1. On the machine with Realtek SFP module, enable Wake-On-Lan
$ sudo ethtool --change <your interface name> wol g
2. To power on the machine from remote
$ wakeonlan -i <ip address> <MAC address>
[Where problems could occur]
This patch reduce the value of EEE speed down ratio. From the commit message, it may only affect the power consumption a little bit.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2123901/+subscriptions
---------------
linux (6.17.0-8.8) questing; urgency=medium
* questing/linux: 6.17.0-8.8 -proposed tracker (LP: #2131554)
* crash when reading from /sys/kernel/tracing/rv/enabled_monitors
(LP: #2131136)
- rv: Fully convert enabled_monitors to use list_head as iterator
* i40e driver is triggering VF resets on every link state change
(LP: #2130552)
- i40e: avoid redundant VF link state updates
* kernel crash on bootup for some arm64 machines (LP: #2129770)
- KVM: arm64: Guard PMSCR_EL1 initialization with SPE presence check
* CVE-2025-40018
- ipvs: Defer ip_vs_ftp unregister during netns cleanup
-- Manuel Diewald <manuel.diewald@canonical.com> Fri, 14 Nov 2025
17:53:03 +0100
** Changed in: linux (Ubuntu)
Status: Invalid => Fix Released
** CVE added: https://cve.org/CVERecord?id=CVE-2025-40018
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2123901
Title:
r8169 can not wake on LAN via SFP moudule
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-6.14 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.14 source package in Noble:
Fix Released
Status in linux source package in Plucky:
Fix Released
Status in linux-oem-6.14 source package in Plucky:
Invalid
Status in linux source package in Questing:
Fix Released
Status in linux-oem-6.14 source package in Questing:
Invalid
Bug description:
[Impact]
Can not wake on LAN via Realtek SFP moudule.
[Fix]
Realtek provides a patch to fix this issue
https://patchew.org/linux/20250904021123.5734-1-hau@realtek.com/
Which is included in linux-next
bf7154ffb1c65 r8169: set EEE speed down ratio to 1
[Test]
1. On the machine with Realtek SFP module, enable Wake-On-Lan
$ sudo ethtool --change <your interface name> wol g
2. To power on the machine from remote
$ wakeonlan -i <ip address> <MAC address>
[Where problems could occur]
This patch reduce the value of EEE speed down ratio. From the commit message, it may only affect the power consumption a little bit.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2123901/+subscriptions
Подписаться на:
Комментарии (Atom)