On 17-Oct-2002 Lars Eggert wrote:
> Hi,
>
> I'm tracking down a lock order reversal for hsu@, and just came across
> this other locking panic twice in the last few hours. I run with WITNESS
> and WITNESS_SKIPSPIN, and have never seen this happen unless I set
> debug.witness_ddb=1. The name of the mutex looks definitly fishy.
>
> Let me knowif I can provide more information (tried to get a core dump,
> but machine hung hard after typing "panic".)
>
> panic: mtx_lock() of spin mutex $,J@4(J@^@^GN@^D @
> /usr/src/sys/kern/kern_descrip.c:488
> cpuid = 1; lapic.id = 02000000
> Debugger("panic")
> Stopped at Debugger+0x5a: xchgl %ebx,in_Debugger.0
> db> trace
> Debugger(c043d4b2,2000000,c043c6ef,eb519c70,1) at Debugger+0x5a
> panic(c043c6ef,c04a2a74,c043a64f,1e8,eb519cb4) at panic+0x12f
> _mtx_lock_flags(c04a2c34,0,c043a64f,1e8,c7238c00) at _mtx_lock_flags+0xa7
> do_dup(c69fb9c0,1,ffffffff,4,c69fba54) at do_dup+0xe6
> dup2(c69fb9c0,eb519d10,c046443d,42d,c69fa3e8) at dup2+0x33
> syscall(2f,2f,2f,4,815aa00) at syscall+0x406
> Xint0x80_syscall() at Xint0x80_syscall+0x1d
> --- syscall (90, FreeBSD ELF32, dup2), eip = 0x80986cf, esp =
> 0xbfbe74bc, ebp = 0xbfbe7988 ---
> db> panic
> panic: from debugger
> cpuid = 1; lapic.id = 02000000
> boot() called on cpu#1
What is line 488 of src/sys/kern/kern_descrip.c?
--
John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/
"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
