Opened 17 years ago
Closed 17 years ago
#1035 closed bug (invalid)
KDL on boot - bfs block allocator
| Reported by: | darkwyrm | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | System/Kernel | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
When I attempt to boot Haiku on real hardware, the I get a KDL even before I get to a blue screen. It has a page fault while interrupts are disabled with a NULL address and EIP. debugger backtrace reveals that the fault occurred in the bfs block allocator thread.
Attachments (1)
Change History (5)
comment:1 by , 17 years ago
by , 17 years ago
| Attachment: | SerialDebug.txt added |
|---|
Entire serial debug output from start of boot to KDL
comment:2 by , 17 years ago
Sorry about that. I thought from your kernel wizardry skillz you might be able to figure it out from there. :) I just attached the entire serial output. It's been ages since I last tried to boot on real hardware, so I don't know how recently it stopped working.
comment:3 by , 17 years ago
If it would happen over here as well, maybe; but remote debugging requires as much information as possibly. Thanks for the update, could you please enter "bt" and "thread" in the KDL and provide that as well?
comment:4 by , 17 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
As it turns out, the real problem has to do with the prebuilt images @ haikuhost.com that I was using. The revision listed on the archive is _way_ ahead of the actual revision built into the image (a little after 20000 IIRC). Building the tree on my machine takes quite a while, so I was using the prebuilts. Installing a revision from the last couple of days shows that the bug has been already fixed.
How about some more info like a real stack trace? And since when does this happen?