Date: Mon, 17 Feb 2003 14:38:43 -0500 (EST) From: Andrew Gallatin <gallatin@cs.duke.edu> To: Dag-Erling Smorgrav <des@ofug.org> Cc: alpha@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: top-of-tree alpha kernel panics during boot Message-ID: <15953.14915.548457.683546@grasshopper.cs.duke.edu> In-Reply-To: <xzplm0e4sui.fsf@flood.ping.uio.no> References: <xzpn0l0v119.fsf@flood.ping.uio.no> <xzpk7fz58r0.fsf@flood.ping.uio.no> <xzpfzqn57pi.fsf@flood.ping.uio.no> <15952.60850.445423.454870@grasshopper.cs.duke.edu> <xzp7kbz571q.fsf@flood.ping.uio.no> <15952.61478.809737.101419@grasshopper.cs.duke.edu> <xzplm0e4sui.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Smorgrav writes: > Andrew Gallatin <gallatin@cs.duke.edu> writes: > > You might be able to get some idea of what's happening by enabling KTR > > and tracing everything, then dumping the trace buffer at your > > breakpoint. > > Of course, the KTR-enabled kernel fails to crash. > > *sigh* > > but I bet it'll segfault like nobody's business if I let it boot to > multiuser, so I'm stuck with my Jan 9 kernel. Ugh. About the only thing I can suggest is to pepper the startup code with Debugger() calls, and do something of a binary search. Having just done that to track some vm faults before vm is setup, I know that's about as much fun as eating dirt. But I can't think of a better idea. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15953.14915.548457.683546>