#18949 closed bug (duplicate)
kernel not loading with more than 4GB of RAM
| Reported by: | zeldakatze | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | System/Kernel | Version: | R1/beta4 |
| Keywords: | Cc: | ||
| Blocked By: | #14659 | Blocking: | |
| Platform: | All |
Description
Hello, I noticed that on my desktop computer (a Ryzen 5 2600 with an Asus B450+ Mainboard, 16GB of RAM, booting with CSM) Haiku (hrev56578+96) won't boot unless I select the ignore memory above 4GB option. It seems like the kernel won't even run, as there is neither onscreen debug output nor a syslog that is being generated. I've tried updating to the newest nightly aswell (at the time (4th July) beta4_hrev57804), but with that, it won't boot at all, regardless of which boot options I select. I will try to update to the newest nightly aswell. The old state is booting, so I don't think it is a problem with the bootloader. I could also try booting it with UEFI, but currently, I've set it up with legacy CSM to be able to boot without having to redo some partition layout from my preexisting partitions. I'll attach the syslog of the successful boot with hrev56578+96.
kind regards, zeldakatze
Attachments (2)
Change History (7)
by , 4 months ago
comment:1 by , 4 months ago
| Keywords: | kernel 4gb ram hangs startup removed |
|---|---|
| Platform: | x86-64 → All |
I'm a bit confused. Is there a version that boots without "4GB memory limit" option enabled? Or does every hrev only boot with that option set?
I think Ryzen systems have always needed this option when booting with BIOS/CSM, see #13370 (which was fixed, but it just uncovered another issue which is also linked in that ticket.)
comment:2 by , 3 weeks ago
| Blocked By: | 14659 added |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
comment:3 by , 3 weeks ago
The kernel starts now, though there are multiple Assertions being triggered, mainly about caching. The system starts however, you have to wait for some time until the mouse is actually usable. The system crashed after ~10 minutes whilst checkfs was running with a general protection fault.
I'll attach the syslog, though it seems to me, that the debugger was not logged. I can try to append it's messages aswell
by , 3 weeks ago
| Attachment: | previous_syslog added |
|---|
syslog with hrev58228, system was reset shortly after the assertions as to not cut off the debugger stacktraces
syslog (hrev56578+96, limited to 4gb ram)