tech-net archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: apparently missing locking in if_bnx.c

I compiled with kgdb enabled.  I ran it in the debugger, did a stack trace and 

#0 0xc0276d64 in breakpoint()
#1 0xc0575512 in kgdb_connect (verbose=0)
#2 0xc057557f in kgdb_panic()
#3 0x00000000 in ?? ()

Useful, huh?

I can try using ddb instead.


On Mar 6, 2012, at 10:59 AM, Manuel Bouyer wrote:

> On Tue, Mar 06, 2012 at 10:45:11AM -0500, Beverly Schwartz wrote:
>> I can get a kernel to boot with the recommended KASSERTs, but as soon as I 
>> try to ssh into the machine, I get a panic on:
>> KASSERT(curcpu()->ci_biglock_count > 0);
> OK, so this means the kernel lock is not held. What's interesting
> now is how we did get there. Can you set ddb.onpanic=1 in /etc/sysctl.conf
> and get a stack trace from here ?
> -- 
> Manuel Bouyer <>
>     NetBSD: 26 ans d'experience feront toujours la difference
> --

Home | Main Index | Thread Index | Old Index