Re: What is best method to debug freezes/hangs?

2007-12-05 Thread Derek Ragona

At 08:49 PM 12/4/2007, yar wrote:


My question is how best to go about debugging sporadic freezes and hangs.
Just looking for general methods.On a couple of our IDS systems there
are sporadic hangs or freezes that occur every couple weeks or so, that are
recoverable by either system reboots or taking out and reinserting the Gig
fiber ethernet sniffing cables, but I  never can find anything in
/var/logs/messages to tell what is going on. I'm assuming that may have to
compile in kernel debugger support, but from what I read briefly, doesn't
that require an actual crash with the resultant reboot and a debugger
readable file  left in /var/crash?  That doesn't happen, there is no
automatic reboot just a freeze/hang (box falls off network and at the
console unable to type until one of the two above mentioned measures are
take. The systems are:

Dell 1850's
Free BSD 6.2
2 Gb ram
running various open source IDS software  BRO

Thanks


I would be sure your systems are running the generic kernel, or as close to 
generic that is possible to rule out anything you could have introduced by 
running a custom kernel.


I would also run complete diagnostics on the hardware to rule out any 
hardware issues.


You can also gather some information by having a script run top 
periodically and logging this to a file to see what the system is 
doing.  You can check the last log entry of this file after a freeze/hang 
to see what was going on.


-Derek

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


What is best method to debug freezes/hangs?

2007-12-04 Thread yar

My question is how best to go about debugging sporadic freezes and hangs.
Just looking for general methods.On a couple of our IDS systems there
are sporadic hangs or freezes that occur every couple weeks or so, that are
recoverable by either system reboots or taking out and reinserting the Gig
fiber ethernet sniffing cables, but I  never can find anything in
/var/logs/messages to tell what is going on. I'm assuming that may have to
compile in kernel debugger support, but from what I read briefly, doesn't
that require an actual crash with the resultant reboot and a debugger
readable file  left in /var/crash?  That doesn't happen, there is no
automatic reboot just a freeze/hang (box falls off network and at the
console unable to type until one of the two above mentioned measures are
take. The systems are:

Dell 1850's
Free BSD 6.2
2 Gb ram 
running various open source IDS software  BRO

Thanks
-- 
View this message in context: 
http://www.nabble.com/What-is-best-method-to-debug-freezes-hangs--tf4947151.html#a14164268
Sent from the freebsd-questions mailing list archive at Nabble.com.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: What is best method to debug freezes/hangs?

2007-12-04 Thread Per olof Ljungmark

yar wrote:

My question is how best to go about debugging sporadic freezes and hangs.
Just looking for general methods.On a couple of our IDS systems there
are sporadic hangs or freezes that occur every couple weeks or so, that are
recoverable by either system reboots or taking out and reinserting the Gig
fiber ethernet sniffing cables, but I  never can find anything in
/var/logs/messages to tell what is going on. I'm assuming that may have to
compile in kernel debugger support, but from what I read briefly, doesn't
that require an actual crash with the resultant reboot and a debugger
readable file  left in /var/crash?  That doesn't happen, there is no
automatic reboot just a freeze/hang (box falls off network and at the
console unable to type until one of the two above mentioned measures are
take. 


In my case with the above behaviour a debug kernel and ctrl+alt+esc 
would work and that is probably true most of the times.


http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html

HTH,
--per
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]