Any way to debug a hard lockup?
Joe Marcus Clarke
marcus at marcuscom.com
Wed Jul 7 12:18:36 PDT 2004
On Wed, 2004-07-07 at 15:03, Conrad J. Sabatier wrote:
> For the last few days, my amd64 box (Athlon 64 3200+, 5.2-CURRENT,
> updating just about daily lately) has been locking up hard fairly
> often, and I have no clue as to why.
> Checking the logs after rebooting reveals nothing at all out of the
> ordinary. The box just "seizes up" and that's that. Only thing to do
> is a power-down and restart.
> Changing from SCHED_ULE to SCHED_4BSD appears to make no difference at
> My other box, an older (32-bit) Athlon, has been rock stable. I've
> been keeping both machines updated simultaneously to exactly the same
> revisions, using as near-identical system settings as possible also,
> the main difference being I'm running X.org/GNOME on the amd64 box and
> no X on the i386 box.
> Any suggestions? Instinct tells me it may be a problem with some of
> the ports I'm running (X.org/GNOME, hence the Cc:s), but how to verify?
> Sure, I could run without X a while and see how it goes, but that still
> won't help to isolate the problem, if it is, in fact, port-related.
You'll need to use a serial console and DDB to debug these problems.
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html on setting that up. Once the machine breaks into the debugger, you'll be able to get a stack trace.
PGP Key : http://www.marcuscom.com/pgp.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-amd64/attachments/20040707/201c1c03/attachment.bin
More information about the freebsd-amd64