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

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Tue, Aug 11, 2009 at 11:50:17AM +0200, Jachym Holecek wrote:
> 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.

note that this panic is in the unix socket code, not tcp. does your
bittorent client use unix sockets ? 

-- 
Manuel Bouyer, LIP6, Universite Paris VI.           
Manuel.Bouyer%lip6.fr@localhost
     NetBSD: 26 ans d'experience feront toujours la difference
--