Bug#1053281: linux-image-6.5.0-1-amd64: Debian does not boot at cold start on kernel 6.5.0-1-amd64 on Intel NUC 12
Hi On kernel 6.6 (linux-image-6.6.9-amd64) the issue is solved - display works on cold boot using output handled by both GPU's: CPU-integrated Intel Iris Xe (Thunderbolt) and Intel ARC 770M (HDMI). -- Thanks Kazimierz
Processed: Re: Bug#1053281: linux-image-6.5.0-1-amd64: Debian does not boot at cold start on kernel 6.5.0-1-amd64 on Intel NUC 12
Processing control commands: > retitle -1 No display output on Intel NUC 12 on DP/HDMI on cold boot; works > with CPU-integrated Intel Iris Xe (TB4) Bug #1053281 [src:linux] Cold boot failure on Intel NUC 12 with Intel ARC GPU output (DP or HDMI), but not with CPU-integrated Intel Iris Xe (TB4) Changed Bug title to 'No display output on Intel NUC 12 on DP/HDMI on cold boot; works with CPU-integrated Intel Iris Xe (TB4)' from 'Cold boot failure on Intel NUC 12 with Intel ARC GPU output (DP or HDMI), but not with CPU-integrated Intel Iris Xe (TB4)'. -- 1053281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053281 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1053281: linux-image-6.5.0-1-amd64: Debian does not boot at cold start on kernel 6.5.0-1-amd64 on Intel NUC 12
Control: retitle -1 No display output on Intel NUC 12 on DP/HDMI on cold boot; works with CPU-integrated Intel Iris Xe (TB4) On Saturday, 4 November 2023 10:19:49 CET kurom...@stodwa.org wrote: > On 2023-11-03 14:20, Diederik de Haas wrote: > > On Friday, 3 November 2023 13:49:01 CET Diederik de Haas wrote: > >> My findings are: > >> > 1. If I use Thunderbolt 4 output (usb-c at the back) everything works > >> > fine. > >> > 2. If I use one of DP or HDMI ports the issue occurs. > >> > > >> > Manual for this Intel NUC12 states that both DP and HDMI outputs are > >> > handled by Intel ARC A770M GPU, while Thunderbolt4 output is handled by > >> > CPU-integrated Intel Iris Xe. > > > > And does it really not boot or are you 'only' getting no display > > output? If the latter, can you ssh into your NUC and share `dmesg` output? > > Hopefully that'll give a clue as to why the DP/HDMI outputs aren't working > > properly. > > 2. That's a valid question :) It does boot after all, only display is stuck. Adjusted bug title accordingly. > I was able to get dmesg -> attached. > I don't remember if I mentioned that, but 'nomodeset' kernel param does > not help.. There are a few things that stood out to me from `dmesg`: [0.00] x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks ... [2.977094] EDAC MC0: Giving out device to module igen6_edac controller Intel_client_SoC MC#0: DEV :00:00.0 (INTERRUPT) [2.979900] EDAC MC1: Giving out device to module igen6_edac controller Intel_client_SoC MC#1: DEV :00:00.0 (INTERRUPT) [2.979922] EDAC igen6 MC1: HANDLING IBECC MEMORY ERROR [2.979923] EDAC igen6 MC1: ADDR 0x7fffe0 [2.979925] EDAC igen6 MC0: HANDLING IBECC MEMORY ERROR [2.979926] EDAC igen6 MC0: ADDR 0x7fffe0 [2.980809] EDAC igen6: v2.5.1 Likely not relevant for this bug, but you may want to look into it anyway. [5.183228] NET: Registered PF_ALG protocol family [5.322597] i915 :03:00.0: [drm] *ERROR* Device is non-operational; MMIO access returns 0x! [5.325270] i915 :03:00.0: Device initialization failed (-5) [5.326526] i915: probe of :03:00.0 failed with error -5 Pretty sure that *is* the relevant part. I _think_ it's best to get the upstream maintainers involved, but I don't know who they are. Hopefully one of the (actual) kernel-team members does know that. [ 66.579068] snd_hda_intel :04:00.0: couldn't bind with audio component [ 66.579127] snd_hda_intel :04:00.0: HSW/BDW HD-audio HDMI/DP requires binding with gfx driver My guess is that's a consequence of the earlier error. You can verify that by checking a 'normal' boot and it then likely won't have those lines. signature.asc Description: This is a digitally signed message part.
Bug#1053281: linux-image-6.5.0-1-amd64: Debian does not boot at cold start on kernel 6.5.0-1-amd64 on Intel NUC 12
On 2023-11-03 14:20, Diederik de Haas wrote: On Friday, 3 November 2023 13:49:01 CET Diederik de Haas wrote: My findings are: > 1. If I use Thunderbolt 4 output (usb-c at the back) everything works > fine. > 2. If I use one of DP or HDMI ports the issue occurs. > > Manual for this Intel NUC12 states that both DP and HDMI outputs are > handled by Intel ARC A770M GPU, while Thunderbolt4 output is handled by > CPU-integrated Intel Iris Xe. As this issue only happens on cold boot, have you checked whether there's an updated BIOS for your system? And does it really not boot or are you 'only' getting no display output? If the latter, can you ssh into your NUC and share `dmesg` output? Hopefully that'll give a clue as to why the DP/HDMI outputs aren't working properly. 1. I have most recent BIOS (Aug '23). 2. That's a valid question :) It does boot after all, only display is stuck. I was able to get dmesg -> attached. I don't remember if I mentioned that, but 'nomodeset' kernel param does not help.. -- Kazimierz [0.00] Linux version 6.5.0-3-amd64 (debian-kernel@lists.debian.org) (gcc-13 (Debian 13.2.0-5) 13.2.0, GNU ld (GNU Binutils for Debian) 2.41) #1 SMP PREEMPT_DYNAMIC Debian 6.5.8-1 (2023-10-22) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-3-amd64 root=UUID=bf0e1c3b-f21b-443d-a929-d450ea6a2f30 ro quiet [0.00] x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009dfff] usable [0.00] BIOS-e820: [mem 0x0009e000-0x0009efff] reserved [0.00] BIOS-e820: [mem 0x0009f000-0x0009] usable [0.00] BIOS-e820: [mem 0x000a-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0x347e9fff] usable [0.00] BIOS-e820: [mem 0x347ea000-0x3d71] reserved [0.00] BIOS-e820: [mem 0x3d72-0x3d805fff] ACPI data [0.00] BIOS-e820: [mem 0x3d806000-0x3d9bdfff] ACPI NVS [0.00] BIOS-e820: [mem 0x3d9be000-0x417fefff] reserved [0.00] BIOS-e820: [mem 0x417ff000-0x417f] usable [0.00] BIOS-e820: [mem 0x4180-0x47ff] reserved [0.00] BIOS-e820: [mem 0x48c0-0x4f7f] reserved [0.00] BIOS-e820: [mem 0xc000-0xcfff] reserved [0.00] BIOS-e820: [mem 0xfe00-0xfe010fff] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved [0.00] BIOS-e820: [mem 0xfed0-0xfed00fff] reserved [0.00] BIOS-e820: [mem 0xfed2-0xfed7] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xff00-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x0008b07f] usable [0.00] NX (Execute Disable) protection: active [0.00] e820: update [mem 0x2aeb4018-0x2af76a57] usable ==> usable [0.00] e820: update [mem 0x2aeb4018-0x2af76a57] usable ==> usable [0.00] extended physical RAM map: [0.00] reserve setup_data: [mem 0x-0x0009dfff] usable [0.00] reserve setup_data: [mem 0x0009e000-0x0009efff] reserved [0.00] reserve setup_data: [mem 0x0009f000-0x0009] usable [0.00] reserve setup_data: [mem 0x000a-0x000f] reserved [0.00] reserve setup_data: [mem 0x0010-0x2aeb4017] usable [0.00] reserve setup_data: [mem 0x2aeb4018-0x2af76a57] usable [0.00] reserve setup_data: [mem 0x2af76a58-0x347e9fff] usable [0.00] reserve setup_data: [mem 0x347ea000-0x3d71] reserved [0.00] reserve setup_data: [mem 0x3d72-0x3d805fff] ACPI data [0.00] reserve setup_data: [mem 0x3d806000-0x3d9bdfff] ACPI NVS [0.00] reserve setup_data: [mem 0x3d9be000-0x417fefff] reserved [0.00] reserve setup_data: [mem 0x417ff000-0x417f] usable [0.00] reserve setup_data: [mem 0x4180-0x47ff] reserved [0.00] reserve setup_data: [mem 0x48c0-0x4f7f] reserved [0.00] reserve setup_data: [mem 0xc000-0xcfff] reserved [0.00] reserve setup_data: [mem 0xfe00-0xfe010fff] reserved [0.00] reserve setup_data: [mem 0xfec0-0xfec00fff] reserved [0.00] reserve setup_data: [mem 0xfed0-0xfed00fff] reserved [0.00] reserve setup_data: [mem
Bug#1053281: linux-image-6.5.0-1-amd64: Debian does not boot at cold start on kernel 6.5.0-1-amd64 on Intel NUC 12
On Friday, 3 November 2023 13:49:01 CET Diederik de Haas wrote: > My findings are: > > 1. If I use Thunderbolt 4 output (usb-c at the back) everything works > > fine. > > 2. If I use one of DP or HDMI ports the issue occurs. > > > > Manual for this Intel NUC12 states that both DP and HDMI outputs are > > handled by Intel ARC A770M GPU, while Thunderbolt4 output is handled by > > CPU-integrated Intel Iris Xe. As this issue only happens on cold boot, have you checked whether there's an updated BIOS for your system? And does it really not boot or are you 'only' getting no display output? If the latter, can you ssh into your NUC and share `dmesg` output? Hopefully that'll give a clue as to why the DP/HDMI outputs aren't working properly. signature.asc Description: This is a digitally signed message part.
Bug#1053281: linux-image-6.5.0-1-amd64: Debian does not boot at cold start on kernel 6.5.0-1-amd64 on Intel NUC 12
Control: reopen -1 Control: notfixed -1 6.5.8-1 Control: retitle -1 Cold boot failure on Intel NUC 12 with Intel ARC GPU output (DP or HDMI), but not with CPU-integrated Intel Iris Xe (TB4) On Friday, 3 November 2023 10:04:03 CET kurom...@stodwa.org wrote: > I found out, issue is not fixed - it's only I switched video output at > same time when kernel was updated. > My findings are: > 1. If I use Thunderbolt 4 output (usb-c at the back) everything works > fine. > 2. If I use one of DP or HDMI ports the issue occurs. > > Manual for this Intel NUC12 states that both DP and HDMI outputs are > handled by Intel ARC A770M GPU, while Thunderbolt4 output is handled by > CPU-integrated Intel Iris Xe. Bummer, reopened and retitled accordingly signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#1053281: linux-image-6.5.0-1-amd64: Debian does not boot at cold start on kernel 6.5.0-1-amd64 on Intel NUC 12
Processing control commands:
> reopen -1
Bug #1053281 {Done: Diederik de Haas } [src:linux]
linux-image-6.5.0-1-amd64: Debian does not boot at cold start on kernel
6.5.0-1-amd64 on Intel NUC 12
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 6.5.8-1.
> notfixed -1 6.5.8-1
Bug #1053281 [src:linux] linux-image-6.5.0-1-amd64: Debian does not boot at
cold start on kernel 6.5.0-1-amd64 on Intel NUC 12
Ignoring request to alter fixed versions of bug #1053281 to the same values
previously set
> retitle -1 Cold boot failure on Intel NUC 12 with Intel ARC GPU output (DP or
> HDMI), but not with CPU-integrated Intel Iris Xe (TB4)
Bug #1053281 [src:linux] linux-image-6.5.0-1-amd64: Debian does not boot at
cold start on kernel 6.5.0-1-amd64 on Intel NUC 12
Changed Bug title to 'Cold boot failure on Intel NUC 12 with Intel ARC GPU
output (DP or HDMI), but not with CPU-integrated Intel Iris Xe (TB4)' from
'linux-image-6.5.0-1-amd64: Debian does not boot at cold start on kernel
6.5.0-1-amd64 on Intel NUC 12'.
--
1053281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053281
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1053281: linux-image-6.5.0-1-amd64: Debian does not boot at cold start on kernel 6.5.0-1-amd64 on Intel NUC 12
Package: src:linux Version: 6.5.3-1 Severity: important X-Debbugs-Cc: kurom...@stodwa.org Dear Maintainer, * What is the issue? When I cold boot my Intel NUC12SNKi72, boot process of my Debian sid hangs at Loading initial ramdisk EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Measured initrd data into PCR 9 Suspected problem source is firmware loading and/or i915 driver because it has dual Intel GPU (CPU-included and A770M) configuration, which is not very popular. * What exactly did you do (or not do) that was effective (or ineffective)? Added "nomodeset" kernel param -> it made issue even worse. It hangs same way, but ctrl+alt+del does not reboot OS. Installed bookworm-backports kernel linux-image-6.4.0-0.deb12.2-amd64 (6.4.4-3~bpo12+1) - it works properly on this version. * What was the outcome of this action? OS does not boot. I found two workarounds for kernel 6.5: 1. Boot Windows first, reboot and boot Debian. 2. Let Debian hang as described above, press ctrl+alt+del to reboot. After that Debian will boot properly. It won't boot though if I reboot while in Grub - it must attempt to load initrd to let Debian boot after reboot. The issue was reported on Ubuntu kernel 6.5 as well: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/2037176 -- Package-specific info: ** Version: Linux version 6.5.0-1-amd64 (debian-kernel@lists.debian.org) (gcc-13 (Debian 13.2.0-4) 13.2.0, GNU ld (GNU Binutils for Debian) 2.41) #1 SMP PREEMPT_DYNAMIC Debian 6.5.3-1 (2023-09-13) ** Command line: BOOT_IMAGE=/boot/vmlinuz-6.5.0-1-amd64 root=UUID=bf0e1c3b-f21b-443d-a929-d450ea6a2f30 ro quiet ** Tainted: U (64) * taint requested by userspace application ** Kernel log: [5.014518] usb 1-1.5: new high-speed USB device number 11 using xhci_hcd [5.144618] usb 1-1.5: New USB device found, idVendor=0bda, idProduct=5418, bcdDevice= 1.01 [5.144622] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [5.144622] usb 1-1.5: Product: BillBoard Device [5.144623] usb 1-1.5: Manufacturer: Realtek [5.214504] usb 1-1.1.5: new high-speed USB device number 12 using xhci_hcd [5.332226] usb 1-1.1.5: New USB device found, idVendor=0bda, idProduct=1100, bcdDevice= 1.01 [5.332230] usb 1-1.1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [5.332232] usb 1-1.1.5: Product: HID Device [5.332233] usb 1-1.1.5: Manufacturer: Realtek [5.402517] usb 1-1.1.2.3: new full-speed USB device number 13 using xhci_hcd [5.424418] Bluetooth: hci0: Waiting for firmware download to complete [5.425079] Bluetooth: hci0: Firmware loaded in 1538277 usecs [5.425167] Bluetooth: hci0: Waiting for device to boot [5.441106] Bluetooth: hci0: Device booted in 15611 usecs [5.441472] bluetooth hci0: firmware: direct-loading firmware intel/ibt-0040-0041.ddc [5.441500] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0040-0041.ddc [5.444292] Bluetooth: hci0: Applying Intel DDC parameters completed [5.447239] Bluetooth: hci0: Firmware timestamp 2023.13 buildtype 1 build 62562 [5.509488] usb 1-1.1.2.3: New USB device found, idVendor=413c, idProduct=2514, bcdDevice= 2.22 [5.509510] usb 1-1.1.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [5.509512] usb 1-1.1.2.3: Product: Dell Universal Receiver [5.509513] usb 1-1.1.2.3: Manufacturer: Dell Computer Corp [5.516437] Bluetooth: MGMT ver 1.22 [5.521038] NET: Registered PF_ALG protocol family [5.582555] usb 1-1.6: new high-speed USB device number 14 using xhci_hcd [5.677319] pipewire[1235]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set [5.700275] usb 1-1.6: New USB device found, idVendor=0bda, idProduct=1101, bcdDevice= 1.01 [5.700279] usb 1-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [5.700280] usb 1-1.6: Product: HID Device [5.700280] usb 1-1.6: Manufacturer: Realtek [5.709487] mc: Linux media interface: v0.10 [5.710256] hid: raw HID events driver (C) Jiri Kosina [5.722243] videodev: Linux video capture interface: v2.00 [5.731497] usbcore: registered new interface driver usbhid [5.731499] usbhid: USB HID core driver [5.734394] input: Dell C2422HE Consumer Control as /devices/pci:00/:00:14.0/usb1/1-1/1-1.3/1-1.3:1.3/0003:413C:C00B.0001/input/input17 [5.734823] usb 1-1.4: Found UVC 1.50 device Integrated_Webcam_5M_IR (413c:c00a) [5.752288] usb 1-1.3: Warning! Unlikely big volume range (=18944), cval->res is probably wrong. [5.752308] usb 1-1.3: [2] FU [Headset Playback Volume] ch = 2, val = -18944/0/1 [5.757326] usb 1-1.3: Warning! Unlikely big volume range (=18944), cval->res is probably wrong. [5.757334] usb 1-1.3: [6] FU [Headset Capture Volume] ch = 2, val = -18944/0/1 [5.774563] usb 1-1.1.2.4: new high-speed USB device number 15 using xhci_hcd [5.794553] input: Dell C2422HE as
