Date: Wed, 29 Mar 2000 08:04:12 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: Dave Boers <djb@wit389306.student.utwente.nl> Cc: Tommy Hallgren <thallgren@yahoo.com>, Jeremiah Gowdy <jgowdy@home.com>, freebsd-smp@FreeBSD.ORG Subject: Re: SMP and vn Message-ID: <200003291604.IAA63016@apollo.backplane.com> References: <20000327183911.18682.qmail@web124.yahoomail.com> <20000329132919.A10781@relativity.student.utwente.nl>
index | next in thread | previous in thread | raw e-mail
:That may be, but though I've got most of my lockups when X was running, in
:most cases X was doing the screen saver (blank screen) and I was logged in
:remote (or the system hang occurred during the night).
:
:Anyway, the system hangs don't seem to be related to heavy memory usage.
:(Even people with Asus dual pentium boards get smp related system hangs.)
:Also, my Abit BP6 board was just fine (uptimes of 20+ days or so ;- between
:-current updates) up and until last christmas or so.
:
:So, I'm not inclined to thinking it's a hardware problem at all.
:
: Regards,
:
: Dave.
I suspect you are getting a panic, but due to X running you can't
see it. The goal should be to get to a DDB prompt on the console
to be able to see the panic and 'trace' and 'ps', and then to
(if possible) get a kernel core by typing 'panic' from the DDB prompt.
What you want to do is compile the DDB kernel config option into the
kernel, then switch out of the X session (typically with ctl-alt-F1 or
F2) before you leave for the day. If it crunches while you are
accessing it remotely, when you come in the next day you should see a
DDB prompt and a panic message and be able to 'trace', 'ps', and then
'panic' the system.
-Matt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003291604.IAA63016>