Date: Fri, 31 Mar 2000 09:52:06 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Systems Administrator <geniusj@ods.org>, Greg Lehey <grog@lemis.com>, current@FreeBSD.ORG Subject: Re: NFS/Vinum problems Message-ID: <200003311752.JAA29716@apollo.backplane.com> References: <Pine.BSF.4.10.10003311007140.28524-100000@ods.org> <200003311747.JAA29684@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
::Jason DiCioccio
Another possibility -- could you post your 'dmesg' output? One thing
that NFS does do is severely exercise both the network and the SCSI
device in a concurrent fashion.
If you happen to be using an NCR SCSI chipset, that could be the cause
of the problem (though I have never in my life seen the panic message
you posted in relation to the NCR cards).
If you can get the panic regularly then it may be worthwhile trying to
get some more information out of it. If you compile up a kernel with
the DDB option and your console is not running X, then the kernel will
drop into DDB on the console when it panics and allow you to do a
stack 'trace'. You may also be able to then dump the machine by typing
'panic' manually at the ddb prompt after copying down the trace
information.
-Matt
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?200003311752.JAA29716>