KDL on boot with Lenovo V14 G4 AMN

[grexe]

With the latest nightly as of today, Haiku boots from an USB 3.1 pen drive until the boot icon lights up but then goes into KDL debugging land with the info attached as screenshot.

I cannot even reboot but have to hard power off the machine. Also I cannot enter the boot menu, tried shift and space keys to no avail.

The machine is a Lenovo V14 G4 AMN AMD Ryzen 3 7320U with Radeon graphics NVME SSD SKHynix 8Gb RAM

Google detected text here for convenience:

PANIC: did not find any boot partitions!

Welcome to Kernel Debugging Land

Thread 21 "main2" running on CPU 4

Stack trace for thread 21 "main2"

kernel stack: 0xffffffff82994000 to 0xffffffff829a9000

frame

coller

@ffffffff82998940 (+32) ffffffff80150300

ffffffff82908990 (+88) ffffffff80067528

2 ffffffff829089f0 (+96) ffffffff880b8bd4 3 ffffffff82908048 (+ 80) ffffffff800b8f6e

4 ffffffff829a8b30 (+240) ffffffff80069307 5 ffffffff829.8F60 (+1872) ffffffff80112556 <kernel_x86-64> panic() + 0xb7 kernel x86_64 vfs_mount boot file system() + 6x166

6 ffffffff829a8fb0 (+ 80 ffffffff80068609 7 ffffffff82998fd0 (+32) ffffffff8008f547 <kernel_x86_64 ZL5main2Py() + 0x99 <kernel_x86_64 219common thread_entryPv() + 0x37

initial commands: syslog ta 15

<image>Function + offset

<kernel x86 64% arch debug.coll_with fault_handler() + Bla kennel x86_64 debug.call_with_fault handler() + 0x78

<kernel x86 6 ZL20kernel_debugger_loopPKc80P13_va_list tagi () + BxF4 <kernel x86 642L24kernel_debugger_internal PKc30_P13, va list tagi()+86

165cmain2 21_kstack@0xffffffff82904000 + 0x4fe0

content size: 2097151488

block size:

512

physical block

size: 512

child count:

index: status:

3

0

flags: volume:

2

-1

disk system:

file_systems/ntfs/11

name:

Basic data partition

content name:

WINRE ORV

type:

Microsoft Recovery

content type:

NT File System

params:

<NULL

content params:

<NULL

kdebug syslog | tail 25

disk system:

name:

Basic cata partition

content name:

NULL

type:

Windows data

content type:

<NULL

params:

content params: partition 4: /dev/disk/mwme/8/3

<NULL

offset:

size:

block size: content size:

physical block size: 512

259963010048

2097152008 (2008 MB)

2099151488

512

child count:

index:3

status: flags:2

volume:-1

disk system:

File systems/ritfs/vi Basic data partition

name:

content name: WINRE DRV

type: Microsoft Recovery

content type: NT File Syston <NULL

params:

content params: <NULL> kdebug

[waddlesplash]

When did this stop working?

[grexe]

It never worked on this machine. I was just trying out Haiku on a new laptop.

[grexe]

Ok some update: I was able to invoke the boot menu by pressing space bar *right* when powering up the machine, it's that fast:) However, no sensible combination of safe mode / boot options helped. It seems that Haiku does not find the USB boot partition (from which it just booted) and then tries to search the disk for bootable partitions, then fails on the NTFS repair partition.

I tried safe mode, safe mode + no NTFS disk + no NTFS FS. Also without NVMe driver. When ruling out the NTFS issue, I see that USB XHCI driver cannot find the boot partition:

[korli]

Did you try with on-screen syslog output enabled, without paging?

[grexe]

Text from the KDL debugger when only USB drive is available:

PANIC: did not find any boot partitions!

Welcome to Kernel Debugging Land...

Thread 21 "main2" running on CPU 4

stack trace for thread 21 "main2"

kernel stack: 0xffffffff8291c000 to 0xffffffff82921000

Frame

<image>:function + offset

0 ffffffff82920940 (+32) ffffffff80150780 1 ffffffff82920990 (+ 80) ffffffff80067618

<kernel_x86_64 arch_debug_call_with_fault_handler() + 0x1a <kernel_x86_64 debug_call_with_fault_handler() + 0x78

2 ffffffff829209f0 3 ffffffff82920a40 (+ 80) ffffffff800b909e

(+96) ffffffff800b8d04 <kernel_x86_64 _ZL20kernel_debugger_loopPKcS0_P13_va_list_tagi() + 0xf4

<kernel_x86_64 _ZL24kernel_debugger_internalPKcS0_P13_va_list_tagi () + 0x6e

4 ffffffff82920630 (+240) ffffffff80069437 5 ffffffff82920f60 (+1072) ffffffff80112866 <kernel_x86_64 vfs_mount_boot_file_system() + 0x166

<kernel_x86_64 panic() + 0xb7

6 ffffffff82920fb0 (+ 80) ffffffff80068df9 <kernel_x86_64_ZL5main2Pv () + 0x99

7ffffffff82920fd0 (+32) ffffffff8008f637

<kernel_x86_64 _ZL19common_thread_entryPv () + 0x37 160:main2_21_kstack@0xffffffff8291c000 + 0x4fe0

8 0000000000000000 (+ 0) ffffffff82920fe0

initial commands: syslog | tail 15

usb error xhci 2: failed to enable slot: Operation timed out usb error xhci 2: failed to enable slot: Operation timed out

usb hub 22: get_boot_partitions(): boot volume message:

port 3: new device connected

KMessage: buffer: 0xffffffff82785400 (size/capacity: 255/255), flags: Oxa

field: "partition offset" (LLNG): 6291456 (0x600000)

field: "packaged"

(BOOL): true (LONG): 0 (0x0)

field: "boot method"

field: "disk identifier" (RAWT): data at 0xffffffff82785460, 79 bytes

intel: pm_std_ops (0x1)

get_boot_partitions(): boot method type: 0

intel: pm_std_ops (0x2)

intel: ep_std_ops (0x1)

intel: ep_std_ops (0x2)

DiskDeviceManager:: Initial DeviceScan() returned error: No such file or directory

debug

caller