Synopsis: [panic] panic after spinlock held too long with FreeBSD 7.2-RELEASE-p2 on CPU: Intel(R) Atom(TM) CPU 330 @ 1.60GHz (1618.46-MHz K8-class CPU)
State-Changed-From-To: open->feedback
State-Changed-By: gavin
State-Changed-When: Mon Jul 27 13:32:23 UTC 2009
State-Changed-Why:
To submitter: Firstly, could you please provide the output of:
ps -aux -M /var/crash/vmcore.0
Also, is this something that has only ever happened once, or can you reproduce
it easily? Are you in a position where you can get information out of the
system from the kernel debugger if it happens again? If so, the output
of "show alllocks; alltrace; ps; show allpcpu" would be very useful.
If you don't have interactive access to the debugger, have no way of logging
the output, or need the achine up as quickly as possible, you should be able
to make use of the textdump(4) facility, enabled from the command prompt as
follows:
ddb script kdb.enter.panic="textdump set; capture on; show allpcpu; bt; ps; alltrace; show alllock; call doadump; reset"
sysctl debug.ddb.textdump.pending=1
then please provide the ddb.txt from /var/crash
Responsible-Changed-From-To: freebsd-bugs->gavin
Responsible-Changed-By: gavin
Responsible-Changed-When: Mon Jul 27 13:32:23 UTC 2009
Responsible-Changed-Why:
Track
http://www.freebsd.org/cgi/query-pr.cgi?pr=137117
_______________________________________________
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscribe@freebsd.org"