Date: Wed, 28 Mar 2007 12:51:04 +0400 From: Andrey Chernov <ache@freebsd.org> To: Andre Oppermann <andre@freebsd.org> Cc: Garrett Cooper <youshi10@u.washington.edu>, freebsd-current@freebsd.org Subject: Re: Latest -current complete lockup (tcp changes?) Message-ID: <20070328085104.GA20674@nagual.pp.ru> In-Reply-To: <460A2B97.9040404@freebsd.org> References: <200703251620.20879.nb_root@videotron.ca> <20070325202749.GA1503@kobe.laptop> <460705AE.5040107@freebsd.org> <20070327045252.GA3256@nagual.pp.ru> <46099675.3040609@u.washington.edu> <20070327052810.GA772@nagual.pp.ru> <20070327054501.GA1026@nagual.pp.ru> <46090BA6.5060206@freebsd.org> <20070328074611.GA19740@nagual.pp.ru> <460A2B97.9040404@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 28, 2007 at 10:47:19AM +0200, Andre Oppermann wrote: > Andrey Chernov wrote: > >On Tue, Mar 27, 2007 at 02:18:46PM +0200, Andre Oppermann wrote: > > > >>Could you revert sys/netinet/tcp_input.c back to rev. 1.327 while leaving > >>all others at HEAD and look if the bug can be reproduced? > > > > > >Yes! Reverting to 1.327 really helps, lockup is gone! Thanx! > > You tried with a fully updated system before the backout as well? > There was a time window where TCP was indeed broken. It panic'ed > though. Yes. My case is not related to SACK options KASSERT - my kernel even not go so far to get that panic and I get lockup even when disable SACK by sysctl. -- http://ache.pp.ru/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070328085104.GA20674>