Opened 2 years ago
Closed 2 years ago
#17865 closed bug (no change required)
Cannot boot using a USB - spinlock() kernel panic
Reported by: | prjg2112 | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | System/Kernel | Version: | R1/beta3 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | x86-64 |
Description (last modified by )
System specs as reported by lspci and lsusb are included but I'll repeat what I wrote on the forums.
Screenshot of crash --> https://imgur.com/HynVfVZ
Ryzen 7 5700G 16 GB RAM Radeon 6700 XT video card Asus Prime X570 motherboard
Downloaded beta and burned it with rufus. Checksums match, so I know it’s not a bad rip. I’ve tried the nightlies and a different USB drive with the same result. It goes through the Haiku splash screen boot process where the icons lights up sequentially then hangs. I’ve tried the failsafe video driver, same story. Reset the BIOS to failsafe defaults, still hangs. I’ve taken a screenshot of where it hangs after setting the debug mode to on-screen. I've tried nightlies with the same result.
OK, a bit more - thinking that rufus may not be 100% compatible with the anyboot iso, I burned a new rip using dd - same result. However, I'm noticing the CPU number listed in the panic is changing between crashes, ranging from 0 to 15 (I have an 8 core, 16 thread CPU). I'm going to try booting it single core and see if that helps, and I'll edit this further.
Attachments (3)
Change History (7)
by , 2 years ago
by , 2 years ago
comment:1 by , 2 years ago
Description: | modified (diff) |
---|
comment:2 by , 2 years ago
by , 2 years ago
Attachment: | 20220811_170745.jpg added |
---|
comment:4 by , 2 years ago
Resolution: | → no change required |
---|---|
Status: | new → closed |
This is actually somewhat expected behavior if you are booting with onscreen debug output, paging enabled, and have multiple CPUs/cores. If you want to boot with onscreen debug output, choose "Disable SMP" also.
As for the hang with all icons lit, please try a nightly build. If the problem still occurs there, open a new ticket; but this one is not really an "issue".
Please attach the screenshot instead of linking to external website.