#19218 closed bug (fixed)
PANIC: VMArea::Unwire(0x82033000, 0x1000, 0): no such range
Reported by: | markh | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | R1/beta6 |
Component: | Drivers/Disk/SCSI | Version: | R1/beta5 |
Keywords: | Cc: | ||
Blocked By: | #14003 | Blocking: | #19222 |
Platform: | All |
Description
Haiku crashes when booting with the message:
PANIC: VMArea::Unwire(0x82033000, 0x1000, 0): no such range
It still worked with revision hrev58201, though I have not narrowed it down further. I can check if that is helpful. This happens on x86_gcc2 It is an Intel Core i7-3632QM @ 2.20 GHz with 16GB of memory
If need be I can upload a photo of the crash or add part of the call stack (it is pretty long).
Attachments (1)
Change History (12)
comment:1 by , 3 weeks ago
comment:2 by , 3 weeks ago
I am not sure if I can find the exact hrev that is crashing, but from the boot menu I can select a state from 2024-10-20 16:13:33 and that one crashes with this error. I will attach a photo with the crash.
comment:3 by , 3 weeks ago
There have been a few fixes after that date, in particular related to memory in 32 bit systems. Can you try latest nightly?
comment:4 by , 3 weeks ago
I see that I was a bit vague about which revisions I tried. Sorry about that. The latest revision I tried is hrev58291 which still has the same issue.
comment:5 by , 3 weeks ago
Can you retest with hrev58279 or the nearest revision before that you can find?
comment:6 by , 3 weeks ago
I couldn't test with that exact revision (see https://discuss.haiku-os.org/t/installing-zstd-library-while-on-older-revision/15842/2), but I did test with hrev58278 which still works and hrev58282 which fails with the same error. Hope that is specific enough.
comment:7 by , 3 weeks ago
Blocked By: | 14003 added |
---|---|
Component: | System/Kernel → Drivers/Disk/SCSI |
Milestone: | Unscheduled → R1/beta6 |
Platform: | x86 → All |
comment:8 by , 3 weeks ago
Choosing the option "Ignore memory beyond 4 GiB" for the safe mode options fixes the issue. That allowed me to check the exact revision that causes the crash and it is indeed hrev58280.
comment:9 by , 3 weeks ago
Blocking: | 19222 added |
---|
What hrev is crashing? And yes, a photo would be helpful.