On 09-Jun-01 Richard Todd wrote:
> Backtraces posted here in hopes they might enlighten someone. 
> This is with kernel source from June 6 (specifically,
> "Sticky Date: 2001." according to cvs status).  The machine
> is a dual PII/400; dmesg follows the backtraces from the two panics. If you
> want more information from these two core files, please let me know.
> Note that the first panic is somewhat muddled by the fact that, while 
> syncing disks from the vm_object.c panic, it apparently paniced again with
> "Giant locked" at i386/trap.c:1153.  That probably confuses the issue 
> greatly.

Yes, I need the first traceback, not the second.  One question: are you using
ktrace?  ddb is your friend here, as it can do a traceback when you have the
first panic.

> P.S. Stupid -current question: How does one tell what process was running
> that triggered a panic?  This used to be findable with "p *curproc" in
> gdb, but that doesn't seem to work anymore.

You have to look at the list of per-cpu data (look at the gd_allcpu list).  In
ddb you can use 'show pcpu' to look at per-cpu data.  At some point, gdb needs
to be taught the notion of a 'current CPU' and be taught a way to access
per-cpu data of the current CPU.

> 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 
> ---
>#0  dumpsys () at ../../kern/kern_shutdown.c:478
> 478           if (dumping++) {
> (kgdb) bt
>#0  dumpsys () at ../../kern/kern_shutdown.c:478
>#1  0xc026b35f in boot (howto=256) at ../../kern/kern_shutdown.c:321
>#2  0xc026b7d1 in panic (fmt=0xc0484808 "mutex %s not owned at %s:%d")
>     at ../../kern/kern_shutdown.c:600
>#3  0xc0263c25 in _mtx_assert (m=0xc0576ca0, what=1, 
>     file=0xc04ab834 "../../vm/vm_object.c", line=261)
>     at ../../kern/kern_mutex.c:567
>#4  0xc03f0fee in vm_object_reference (object=0xc8bbc1e0)
>     at ../../vm/vm_object.c:261
>#5  0xc03d6872 in ffs_write (ap=0xc8ce0e80)
>     at ../../ufs/ufs/ufs_readwrite.c:421
>#6  0xc025e175 in ktrwrite (vp=0xc8b67680, kth=0xc112df00, uio=0x0)
>     at vnode_if.h:303
>#7  0xc025dadb in ktrpsig (vp=0xc8b67680, sig=6, action=0, mask=0xc8b24090, 
>     code=0) at ../../kern/kern_ktrace.c:202
>#8  0xc0270204 in postsig (sig=6) at ../../kern/kern_sig.c:1542
>#9  0xc042983e in userret (p=0xc8b23ee0, frame=0xc8ce0fa8, oticks=2655)
>     at ../../i386/i386/trap.c:175
>#10 0xc042c603 in ast (framep=0xc8ce0fa8) at ../../i386/i386/trap.c:1320
>#11 0xc0417b00 in doreti_ast ()

Ok, this one is the ktrace bogon that was recently brought to my attention.


John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!"  -  http://www.FreeBSD.org/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to