On Wed, Oct 04, 2006 at 01:06:37PM -0400, Vivek Khera wrote: > > On Oct 4, 2006, at 12:39 PM, Kris Kennaway wrote: > > >>> > >>>The only thing I think was running at the time would be a large file > >>>copy from a remote system to this one using rsync. > >> > >>As I understand, you got the panic. Then, you shall post the panic > >>message. > >>If you have core file, then running kgdb on the core may show > >>required > >>information. > >>(it shall be on the console exactly before en > >>and backtrace (using the bt command of ddb) of the paniced thread. > > > >YOu can also do 'show msgbuf' from DDB. > > > > i ran kgdb on the vmcore file. since the dump was generated by > calling doadump from DDB, the backtrace was showing the call stack of > that. > > from what i read in the output from kgdb, it seems that something > locked the kernel and we broke to debugger from the watchdog timeout > (I enable software watchdog).
Hmm, be careful with that - if you set the timeout too low (and note that for some workloads O(minutes) may even be too low) then you'll get a lot of false positives. Kris
pgpZ34qBnPXV7.pgp
Description: PGP signature
