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

2023-11-04 Thread kuromski

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: closed by Diederik de Haas (Re: Bug#1053281: issue fixed)

2023-11-03 Thread kuromski

Hi again,
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.

--
Thanks
Kazimierz


On 2023-10-25 22:09, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the src:linux package:

#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

It has been closed by Diederik de Haas .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Diederik de Haas
 by
replying to this email.