Re: possible race on HEAD?

[Peter Avalos <pavalos@xxxxxxxxxxxx>]

On Fri, May 11, 2007 at 10:46:11AM -0700, Matthew Dillon wrote:
> 
>     "clock" is a namecache lock.  It's possible that you found a deadlock
>     but it is also possible that a low level block device or NFS mount got
>     stuck or something of that ilk.
> 

FYI, I don't have NFS mounts.

>     Drop into the debugger, panic the system, and see if you can get a
>     kernel core dump.  If you can, upload the core and the kernel to leaf.
> 

Tried to panic, here's what I got:

CPU0 stopping CPUs: 0x00000002
 stopped
Stopped at      siointr1+0xf7:  movl    $0,brk_state2.10163
db> panic
panic: from debugger
mp_lock = 00000000; cpuid = 0; lapic.id = 00000000
Trace beginning at frame 0xff807af0
panic(c02ffa3f,0,c02fbb2e,ff807b24,ff807b24) at panic+0x182
panic(c02fbb2e,ff807be8,c013d32a,c02e69c2,0) at panic+0x182
db_gdb(c02e69c2,0,ffffffff,ff807b5c,2) at db_gdb
db_command_loop(c02e69c2,c03ab820,10,ff807c10,0) at db_command_loop+0x45d
db_trap(3,0,2,1,ff807c64) at db_trap+0xad
kdb_trap(3,0,ff807c70,ff807c54,2c) at kdb_trap+0x17b
trap(ff807c70) at trap+0x626
calltrap() at calltrap+0xd
--- trap 0, eip = 0, esp = 0xff807cb4, ebp = 0xd358dd48 ---
(null)(181,b,0,0,12c) at 0
boot() called on cpu#0

syncing disks... panic: assertion: mycpu->gd_intr_nesting_level == 0 in _lwkt_gettokref
mp_lock = 00000000; cpuid = 0; lapic.id = 00000000
boot() called on cpu#0
Uptime: 1d19h17m16s

And then it hard locked on me...had to power cycle.

--Peter

Attachment: pgp00001.pgp
Description: PGP signature