On Sat, 15 Jul 2006, User Freebsd wrote:
On Wed, 5 Jul 2006, Robert Watson wrote:
If you can get into DDB when the hang has occurred, output via serial
console for the following commands would be very helpful:
show pcpu
show allpcpu
ps
trace
traceall
show locks
show alllocks
show uma
show malloc
show lockedvnods
'k, after 16 days uptime, the server that I got all the debugging turned on
for finally hung up solid ... I was able to break into DDB over the serial
link, and have run all of the above on it ... and the output is attached ...
One thing to note is that the ps listing is not complete ... there are >6k
processes running at the time, and I don't know how to get rid of the
'--more--' prompt :( After 1k processes, I just hit 'q' and went onto the
other commands ...
Also, traceall gave me a 'No such command' error ... now that I think about
it, my luck, it was supposed to be 'trace all'?
If this doesn't provide enough information, please let me know what else I
should do the next time through, besides the above commands ...
Oh, and how do you get DDB to 'dump core' in 6.x? Back in 4.x days, I'd just
do 'panic' (maybe twice) at the DDB prompt, but that didn't work with 6.x ...
it just gave me a stacktrace and then the DDB> prompt both times ...
Quick appendum ... the kernel on this server is from June 28th of this
year ...
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED]
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
