[haiku-bugs] Re: [Haiku] #5550: Boot Panic with ipwifi3945(abg) : out of MTRRs! [r35779]
- From: "bonefish" <trac@xxxxxxxxxxxx>
- Date: Mon, 08 Mar 2010 21:11:50 -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 bonefish):
Replying to [comment:4 composr]:
> I understand it is an MTRR setup issue, however, it is irresolvable
without disabling the wireless controller. I have attempted, at muiltiple
builds and boots, to continue from the kernel debugger. After about two
or three panics, it simply freezes the system.
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.
> I have left it alone for up to fifteen minutes after that, with no
response from the system, and had to force a shutdown. I am attaching the
dmesg, kern.log and debug dumps from linux. Let me know what else I can
do to help :) Thanks!
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.
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.
--
Ticket URL: <http://dev.haiku-os.org/ticket/5550#comment:5>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
