Date: Tue, 27 Mar 2007 22:11:01 +0000 From: Garrett Cooper <youshi10@u.washington.edu> To: freebsd-current@freebsd.org Subject: Re: Latest -current complete lockup (tcp changes?) Message-ID: <46099675.3040609@u.washington.edu> In-Reply-To: <20070327045252.GA3256@nagual.pp.ru> 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> <20070327045252.GA3256@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrey Chernov wrote: > 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. I'll give a CVSup / upgrade a try and see what happens. -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46099675.3040609>