Date: Tue, 27 Mar 2007 08:52:52 +0400 From: Andrey Chernov <ache@freebsd.org> To: Andre Oppermann <andre@freebsd.org> Cc: freebsd-current@freebsd.org, Giorgos Keramidas <keramida@freebsd.org>, Nicolas Blais <nb_root@videotron.ca> Subject: Re: Latest -current complete lockup (tcp changes?) Message-ID: <20070327045252.GA3256@nagual.pp.ru> In-Reply-To: <460705AE.5040107@freebsd.org> References: <20070324124732.GA767@nagual.pp.ru> <200703251348.58972.nb_root@videotron.ca> <20070325194946.GC79938@kobe.laptop> <200703251620.20879.nb_root@videotron.ca> <20070325202749.GA1503@kobe.laptop> <460705AE.5040107@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Mar 26, 2007 at 01:28:46AM +0200, Andre Oppermann wrote: > Giorgos Keramidas wrote: > >Hi Andre, > > > >The attached thread below is a reply from Nicolas Blais which shows some > >problems with the recent SACK changes. Any idea how we can proceed from > >this point? > > Please update to rev. 1.36 of sys/netinet/tcp_sack.c. The KASSERT() was > too tight but actually caught a bug that would have caused a crash anyway. The problem is deeper than that ((( I still got the same lockup, just with more net activity. I even try to completely disable sack, with the same result, so probem is somewhere else. Last working kernel still from Mar 22. -- http://ache.pp.ru/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070327045252.GA3256>