[haiku-bugs] Re: [Haiku] #5550: Boot Panic with ipwifi3945(abg) : out of MTRRs! [r35779]
- From: "composr" <trac@xxxxxxxxxxxx>
- Date: Mon, 08 Mar 2010 21:55:00 -0000
#5550: Boot Panic with ipwifi3945(abg) : out of MTRRs! [r35779]
---------------------------+------------------------------------------------
Reporter: composr | Owner: bonefish
Type: bug | Status: assigned
Priority: critical | Milestone: Unscheduled
Component: System/Kernel | Version: R1/Development
Keywords: | Blockedby:
Platform: x86 | Blocking:
---------------------------+------------------------------------------------
Comment(by composr):
Replying to [comment:5 bonefish]:
> As in "can't enter the kernel debugger via Alt-SysReq-D"? Or does it
just fail continuing to boot? An unfortunate side effect of a panic in the
boot process is that, if you stay too long in KDL, I/O can time out, which
might stop the boot process.
>
Both; I have tried any forms of input whatever, as well as re-entering the
debugger, with no success.
> The Linux stuff is not so interesting. A complete syslog up to the point
where the panic() occurs would be helpful. Unfortunately the interesting
part is missing in the attached one. If you could capture the serial
output, that would be perfect. Alternatively in the kernel debugger a
"syslog | tail 50" may or may not contain the missing output (more might
be needed). You could also try a to replace the panic() in [http://dev
.haiku-
os.org/browser/haiku/trunk/src/system/kernel/arch/x86/arch_vm.cpp#L125] by
a dprintf(). Maybe it will fully boot. If it doesn't and you can enter the
kernel debugger, you could run "on_exit sync" and "co" in the hope that it
writes back all syslog additions to disk. And reboot thereafter.
I will, of course, try to have a syslog that captures that; it is not
practical for me to catch the on-screen output before and up to the panic,
since I don't have the ability to do that. I will certainly try to
capture the log and re-post it up here for you. The linux stuff was only
due to a request, as per the previous comment. I apologise if it's
superfluous.
> As a general hint: Most Linux distributions have a "befs" file system
module which does at least allow you to read-access BFS volumes. I.e. you
don't need to boot Haiku to grab the syslog.
This may provide with a better chance of getting the panic text. Will
reply with the aforementioned information. I, too, want to see what the
log looks like leading to the panic :)
--
Ticket URL: <http://dev.haiku-os.org/ticket/5550#comment:6>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
