Black Screen on Boot kernel 6.9.8 and 6.9.9

Ask Fedora
, , , , ,
1

After upgrade kernel to 6.9.8 my workstation wont boot. I have LUKS encrypted disks and I believe the issue happens when I usually gets the graphical interface to enter my passphrase.

Below is the output I get and from there it freezes and I need to reboot and choose kernel version 6.9.7 to get it behave normally.

[stack]

ffffffffff600000-ffffffffff601000-xp 00000000 00:00 0

[vsysca

111

backtrace:

/lib64/libc.so.6(+0x40d80) [0x7f5a2d1b0d001
/lib64/libply-splash-core.so.5(ply_input_device_get_keymap+0x28)[8x7f5a2d37a5281
/usr/lib64/plymouth/renderers/drm.so(+0xc0e8)[8x7f5a2cfb90e01 /lib64/libply-splash-graphics.so.5(ply_keymap_icon_new+8x6e) [8x7f5a2cf77aee1
/usr/lib64/plymouth/two-step.so(+0xb834)[8x7f5a2cf8d8341 /lib64/libply-splash-core.so.5(+0x151f9)[0x7f5a2d37e1f91
Qusr/sbin/plymouthd(+8xfcbc) [0x55c20f22acbc]
Qusr/sbin/plymouthd(+0x1149a) [0x55c20f22c49al @usr/sbin/plymouthd(+0x15668) [0x55c20f2306681
/lib64/libply-splash-core.so.5(+0x1a45d) [0x7f5a2d38345d]
/lib64/libply-splash-core.so.5(+0x1b4b7) [0x7f5a2d3844b7] /lib64/libply-splash-core.so.5(+8x26655) [0x7f5a2d38f655]
/lib64/libply-splash-core.so.5(+8x1a6cb) [0x7f5a2d3836cb]
/lib64/libply-splash-core.so.5(+0x1aa1f) [0x7f5a2d383a1f ]
/lib64/libply.so.5(ply_event_loop_process_pending_events+0x2e9)[0x7f5a2d3ad1791
/lib64/libply.so.5(ply_event_loop_run+0x28) [0x7f5a2d3ad678]
Qusr/sbin/plymouthd (main+0x9ca) [0x55c20f22243a] /lib64/libc.so.6(+8x2a888)10x7f5a2d1a2088]
/lib64/libc.so.6(libc_start main+0x8b) [0x7f5a2d1a214b]
@usr/sbin/plymouthd(_start+8x25) [0x55c20f223fe5]

Below is my Inxi output.

System:
  Kernel: 6.9.7-200.fc40.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.41-37.fc40
  Desktop: GNOME v: 46.3.1 tk: GTK v: 3.24.42 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 40 (Workstation Edition)
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: <superuser required>
  Mobo: ASUSTeK model: ROG STRIX Z690-G GAMING WIFI v: Rev 1.xx
    serial: <superuser required> part-nu: SKU UEFI: American Megatrends v: 3603
    date: 05/27/2024
Battery:
  Device-1: hid-34:b1:eb:ed:3e:df-battery model: Magic Trackpad serial: N/A
    charge: N/A status: discharging
CPU:
  Info: 24-core (8-mt/16-st) model: 13th Gen Intel Core i9-13900KF bits: 64
    type: MST AMCP arch: Raptor Lake rev: 1 cache: L1: 2.1 MiB L2: 32 MiB
    L3: 36 MiB
  Speed (MHz): avg: 854 high: 1100 min/max: 800/5500:5800:4300 cores:
    1: 1035 2: 800 3: 1085 4: 800 5: 1039 6: 800 7: 1034 8: 800 9: 800 10: 800
    11: 1100 12: 800 13: 1100 14: 952 15: 800 16: 800 17: 800 18: 800 19: 800
    20: 800 21: 800 22: 800 23: 800 24: 800 25: 800 26: 800 27: 800 28: 800
    29: 800 30: 800 31: 800 32: 800 bogomips: 191692
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel DG2 [Arc A750] driver: i915 v: kernel arch: Gen-12.7 ports:
    active: DP-3 empty: DP-1, DP-2, DP-4, HDMI-A-1, HDMI-A-2, HDMI-A-3
    bus-ID: 0000:03:00.0 chip-ID: 8086:56a1
  Device-2: MacroSilicon USB Video
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 1-6.2:5 chip-ID: 534d:2109
  Device-3: Logitech MX Brio
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 3.2
    speed: 5 Gb/s lanes: 1 bus-ID: 2-4:2 chip-ID: 046d:0944
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 24.1.1
    compositor: gnome-shell driver: gpu: i915 display-ID: 0
  Monitor-1: DP-3 model: Samsung LC49G95T res: 3840x1080 dpi: 82
    diag: 1239mm (48.8")
  API: OpenGL v: 4.6 vendor: intel mesa v: 24.1.2 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: Mesa Intel Arc A750 Graphics (DG2)
    device-ID: 8086:56a1 display-ID: :0.0
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: Intel Alder Lake-S HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel bus-ID: 0000:00:1f.3 chip-ID: 8086:7ad0
  Device-2: Intel DG2 Audio driver: snd_hda_intel v: kernel
    bus-ID: 0000:04:00.0 chip-ID: 8086:4f90
  Device-3: ASUSTek USB Audio driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-4:2 chip-ID: 0b05:1996
  Device-4: MacroSilicon USB Video
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 bus-ID: 1-6.2:5 chip-ID: 534d:2109
  Device-5: C-Media Audio Adapter (Unitek Y-247A)
    driver: cmedia_hs100b,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
    lanes: 1 bus-ID: 1-6.3.3:16 chip-ID: 0d8c:0014
  Device-6: XMOS AVA AnyCo A3 driver: hid-generic,snd-usb-audio,usbhid
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 bus-ID: 1-6.4.1.3:21
    chip-ID: 20b1:0104
  Device-7: Logitech MX Brio
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 3.2
    speed: 5 Gb/s lanes: 1 bus-ID: 2-4:2 chip-ID: 046d:0944
  API: ALSA v: k6.9.7-200.fc40.x86_64 status: kernel-api
  Server-1: JACK v: 1.9.22 status: off
  Server-2: PipeWire v: 1.0.7 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
  Device-1: Intel Alder Lake-S PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 0000:00:14.3 chip-ID: 8086:7af0
  IF: wlo1 state: up mac: <filter>
  Device-2: Intel Ethernet I225-V vendor: ASUSTeK driver: igc v: kernel
    port: N/A bus-ID: 0000:09:00.0 chip-ID: 8086:15f3
  IF: enp9s0 state: down mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
  IF-ID-2: wg-CH-NZ-1 state: unknown speed: N/A duplex: N/A mac: N/A
Bluetooth:
  Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 bus-ID: 1-14:8 chip-ID: 8087:0033
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
    lmp-v: 12
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller Intel
    driver: vmd v: 0.6 bus-ID: 0000:00:0e.0 chip-ID: 8086:a77f
Drives:
  Local Storage: total: 13.65 TiB used: 1.34 TiB (9.8%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 990 PRO 1TB size: 931.51 GiB
    speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 42.9 C
  ID-2: /dev/sda vendor: Samsung model: SSD 870 QVO 8TB size: 7.28 TiB
    speed: 6.0 Gb/s serial: <filter>
  ID-3: /dev/sdb vendor: Western Digital model: WDS400T1R0A-68A4W0
    size: 3.64 TiB speed: 6.0 Gb/s serial: <filter>
  ID-4: /dev/sdc vendor: Samsung model: SSD 870 EVO 2TB size: 1.82 TiB
    speed: 6.0 Gb/s serial: <filter>
Partition:
  ID-1: / size: 913.92 GiB used: 24.51 GiB (2.7%) fs: ext4 dev: /dev/dm-0
    mapped: luks-3cd67b52-ff8b-402a-9477-d6f0c2c8675a
  ID-2: /boot size: 942.8 MiB used: 282.5 MiB (30.0%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 974.6 MiB used: 19 MiB (2.0%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 3.64 TiB used: 57.2 GiB (1.5%) fs: btrfs dev: /dev/dm-2
    mapped: luks-6e32ffe2-070d-4265-9cdb-9872971e1671
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 32.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 128 GiB available: 125.6 GiB used: 5.72 GiB (4.6%)
  Processes: 614 Power: uptime: 12m wakeups: 0 Init: systemd v: 255
    target: graphical (5) default: graphical
  Packages: pm: flatpak pkgs: 37 Compilers: clang: 18.1.6 gcc: 14.1.1
    Shell: Bash v: 5.2.26 running-in: zellij inxi: 3.3.34
2

You could also try boot parameters rd.debug and single. If you can get to the root prompt, you could save the boot log. If it’s a problem with graphical interface, that should be possible. If it’s not that, it could be hanging before you can get to root prompt, but I wouldn’t assume that. Even if not, rd.debug will put up text on the screen, which is better than nothing.

Also, did you try to see if anything from the hangs made it into the journal? If it is getting far enough in the boot process, the boot logs will get put in the journal, so it could be there, even if you have to hard rest.

4

Oh, my issue happens before entering the password. So not the same issue. I’ll look for another thread if any, and best of luck solving this threads issue :slight_smile:

5

I’ll move your post so you have your own thread.

1 Like
6

Please provide details of your issue.

7

Thanks, I’ve edited my first post to include the details.

1 Like
8

Is this correct? The more recent kernel is 6.9.x Why do you need kernel 6.7.8

9

I don’t need version 6.9.8. It was the release that introduced the issue for me, and current release has inherited it.

10

ah, misspell. sorry

11

Can you provide some logs for us?

Go ahead a try the new kernels, if it does not boot, then boot with older kernel and run this command

journalctl -b 1 paste the info here.

if it is too long journalctl -b 1 | fpaste --raw-url

12

Added asus, boot, kernel, plymouth, workstation

13

That should be journalctl -b -1 for the previous boot. Also, journalctl makes very long lines. You can use journalctl --no-hostname -b -1 |cat (we don’t need the hostname, and |cat will wrap long lines)
.

1 Like
14

Will do :+1:t5: :fedora:

15

This is strange, the logs from suggested journalctl command yields a lot of logs, but they make no sense to me as the timestamps are on either a wrong day or completely off.

I have done a test where I shutdown my computer for 20 min and then booted on the failing kernel. I left it there in this state for 10 min before Ctr+Alt+Del.

I then examined the log and I can see a time gap between my shoutdown and the boot from Ctrl+Alt+Del, meaning, the failing boot is not shown at all in the logs.

The only thing are the output from the screen I took a photo of are what I can provide unless there are other logs I can fetch or generate, any suggestions?

16

Here’s a snippet of the log, between the Journal stopped and the boot on 6.9.7-200 was the boot on the failing kernel and my Ctr+Alt+Del.

jul 18 09:38:16 systemd-shutdown[1]: Syncing filesystems and block devices.
jul 18 09:38:16 systemd-shutdown[1]: Sending SIGTERM to remaining processes...
jul 18 09:38:16 systemd-journald[1463]: Received SIGTERM from PID 1 (systemd-shutdow).
jul 18 09:38:16 systemd-journald[1463]: Journal stopped
-- Boot 0ab17828efa94a30978be0b397b2bfdd --
jul 18 10:11:10 kernel: Linux version 6.9.7-200.fc40.x86_64 (mockbuild@8d858239ee7c403c892e8a84096b3ce3) (gcc (GCC) 14.1.1 20240620 (Red Hat 14.1.1-6), GNU ld version 2.41-37.fc40) #1 SMP PREEMPT_DYNAMIC Thu Jun 27 18:11:45 UTC 2024
jul 18 10:11:10 kernel: Command line: BOOT_IMAGE=(hd2,gpt2)/vmlinuz-6.9.7-200.fc40.x86_64 root=UUID=9452dc01-6eb4-4fac-829d-c7cb599dd125 ro rd.luks.uuid=luks-3cd67b52-ff8b-402a-9477-d6f0c2c8675a rhgb quiet intel_iommu=on iommu=pt ipv6.disable=1
jul 18 10:11:10 kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
jul 18 10:11:10 kernel: BIOS-provided physical RAM map:
17

So the problem comes before journaling is enabled. Boot without the rhgb quiet to see early messages. For my personal systems I prefer to remove these from the grub configuration so I see right away when something has broken.

1 Like
18

Thanks for the tip, I have some logs to show now, see snipped below.
It hangs at jul 18 13:01:56 kernel: i915 0000:03:00.0: [drm] GT0: HuC: timed out waiting for MEI GSC. A few minutes later 13:04:55 I just hit a key and the LUKS passphrase prompt showed up. Entering my passphrase, and the boot continues successfully on 6.9.9 kernel.

jul 18 13:01:51 kernel: input: Kinesis Corporation Adv360 Pro Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6.3/1-6.3.1/1-6.3.1.3/1-6.3.1.3.4/1-6.3.1.3.4:1.0/0003:29EA:0362.000E/input/input13
jul 18 13:01:51 kernel: hid-generic 0003:29EA:0362.000E: input,hidraw13: USB HID v1.10 Keyboard [Kinesis Corporation Adv360 Pro] on usb-0000:00:14.0-6.3.1.3.4/input0
jul 18 13:01:51 systemd-journald[457]: Journal started
jul 18 13:01:51 systemd-journald[457]: Runtime Journal (/run/log/journal/945795b2b3dc420c9ee5260ab3cac40b) is 8.0M, max 2.5G, 2.5G free.
jul 18 13:01:45 systemd-modules-load[459]: Inserted module 'i2c_dev'
jul 18 13:01:45 systemd-modules-load[459]: Module 'msr' is built in
jul 18 13:01:45 systemd-modules-load[459]: Inserted module 'fuse'
jul 18 13:01:45 systemd-modules-load[459]: Inserted module 'ip_tables'
jul 18 13:01:45 systemd-modules-load[459]: Inserted module 'ip6_tables'
jul 18 13:01:45 systemd-escape[565]: Input 'luks-3cd67b52-ff8b-402a-9477-d6f0c2c8675a' is not an absolute file system path, escaping is likely not going to be reversible.
jul 18 13:01:45 systemd-udevd[587]: Using default interface naming scheme 'v255'.
jul 18 13:01:51 dracut-cmdline[480]: dracut-101-1.fc40
jul 18 13:01:51 dracut-cmdline[480]: Using kernel command line parameters:    BOOT_IMAGE=(hd2,gpt2)/vmlinuz-6.9.9-200.fc40.x86_64 root=UUID=9452dc01-6eb4-4fac-829d-c7cb599dd125 ro rd.luks.uuid=luks-3cd67b52-ff8b-402a-9477-d6f0c2c8675a intel_iommu=on iommu=pt ipv6.disable=1
jul 18 13:01:51 systemd[1]: Started systemd-journald.service - Journal Service.
jul 18 13:01:51 systemd[1]: Starting systemd-tmpfiles-setup.service - Create System Files and Directories...
jul 18 13:01:51 systemd[1]: Finished systemd-tmpfiles-setup.service - Create System Files and Directories.
jul 18 13:01:56 kernel: i915 0000:03:00.0: [drm] GT0: HuC: timed out waiting for MEI GSC
jul 18 13:04:55 systemd-cryptsetup[802]: Set cipher aes, mode xts-plain64, key size 512 bits for device /dev/disk/by-uuid/3cd67b52-ff8b-402a-9477-d6f0c2c8675a.
19

Just speculating from my end, it looks to be some issue with the Intel driver causing it to halt during boot.

kmod list | grep -E 'mei_gsc|i915'
mei_gsc                12288  2
mei_me                 57344  1 mei_gsc
mei                   204800  6 mei_gsc,mei_hdcp,mei_pxp,mei_me
i915                 4657152  16
i2c_algo_bit           20480  2 xe,i915
drm_buddy              20480  2 xe,i915
ttm                   114688  3 drm_ttm_helper,xe,i915
drm_display_helper    274432  2 xe,i915
cec                    98304  3 drm_display_helper,xe,i915
video                  81920  4 asus_wmi,asus_nb_wmi,xe,i915

lspci | grep 0000:03:00.0
0000:03:00.0 VGA compatible controller: Intel Corporation DG2 [Arc A750] (rev 08)

https://www.kernel.org/doc/html/latest/gpu/i915.html
https://www.kernel.org/doc/html/latest/driver-api/mei/index.html?highlight=mei

2 Likes
20

Good work :100: :fedora:

21

I wonder if this is a race condition with i915 attempting to read something from mass storage before LUKS is unlocked.