Date: Wed, 29 Mar 2000 08:54:45 -0800 From: Arun Sharma <adsharma@sharmas.dhs.org> To: dillon@apollo.backplane.com Cc: freebsd-smp@freebsd.org Subject: Re: SMP and vn Message-ID: <200003291654.IAA22036@sharmas.dhs.org> In-Reply-To: <200003291604.IAA63016@apollo.backplane.com> References: <20000327183911.18682.qmail@web124.yahoomail.com> <20000329132919.A10781@relativity.student.utwente.nl> <200003291604.IAA63016@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> :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. I've had freezes when not running X and it didn't drop into DDB on the console. Will adding more asserts in suspected places help ? -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003291654.IAA22036>