Re: diagnostic assertion "solocked2(so, so2)" failed

[Jachym Holecek <freza%NetBSD.org@localhost>]

# Manuel Bouyer 2009-08-11:
> I got this panic on a netbsd-5 kernel:
> panic: kernel diagnostic assertion "solocked2(so, so2)" failed: file 
> "/home/bouyer/src-5/src/sys/kern/uipc_usrreq.c", line 559                     
>              
> fatal breakpoint trap in supervisor mode
> trap type 1 code 0 eip c03d035c cs 8 eflags 246 cr2 8077132 ilevel 4
> Stopped in pid 23735.1 (sendmail) at    netbsd:breakpoint+0x4:  popl    %ebp
> db{1}> bt
> breakpoint(c06341a3,d2c43b38,c2cca800,c0312a97,bf157f98,c32fdf3d,c,c0329cb3, 
> 50435051,c2cca800) at netbsd:breakpoint+0x4
> panic(c0673c38,c05f9771,c062a2f9,c062a8f0,22f,d2c43c5c,d2c43b7c,c0364825,c05f9771,c062a8f0)
>  at netbsd:panic+0x1b0
> __kernassert(c05f9771,c062a8f0,22f,c062a2f9,d2d89d60,d3ba2d40,c32fdf49,d22bc440,0,0)
>  at netbsd:__kernassert+0x39
> uipc_usrreq(c2ee2a0c,9,c32fdf00,0,0,d1e4bd20,3,c43be0,c2ee2a64,0) at 
> netbsd:uipc_usrreq+0x965
> sosend(c2ee2a0c,0,d2c43c94,c32fdf00,0,0,d1e4bd20,9,0,2) at netbsd:sosend+0x403
> soo_write(d1b7b7c0,d1b7b7c0,d2c43c94,d1b69840,1,3,d1b7b7c0,d2c43c54,0,10) at 
> netbsd:soo_write+0x3e
> do_filewritev(5,bf157f30,2,d1b7b7c0,1,d2c43d28,d2c43d3c,c03d8908,d1e4bd20,d2c43d00)
>  at netbsd:do_filewritev+0x190
> sys_writev(d1e4bd20,d2c43d00,d2c43d28,8077000,d2d89d60,d2d89d60,1,5,bf157f30,2)
>  at netbsd:sys_writev+0x37
> syscall(d2c43d48,b3,ab,bf15001f,affd001f,1,bf157f98,bf157f58,afd2a0b0,0) at 
> netbsd:syscall+0xc8
> db{1}>
> 
> Does it ring a bell to someone ?

Looks like something that has been regularly happening to me after about
an hour of bittorrent traffic (MP amd64, internet via iwn(4)). Upgrade to
-current helped, or at least I'm seeing a different panic now on the same
machine (mbuf of length one makes something in ieee80211_crypto_tkip.c
explode). Wifi setup changed from static WEP to WPA along with OS upgrade.

        -- Jachym