Date: Tue, 27 Mar 2007 14:18:46 +0200 From: Andre Oppermann <andre@freebsd.org> To: Andrey Chernov <ache@freebsd.org> Cc: Garrett Cooper <youshi10@u.washington.edu>, freebsd-current@freebsd.org Subject: Re: Latest -current complete lockup (tcp changes?) Message-ID: <46090BA6.5060206@freebsd.org> In-Reply-To: <20070327054501.GA1026@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> <46099675.3040609@u.washington.edu> <20070327052810.GA772@nagual.pp.ru> <20070327054501.GA1026@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Andrey Chernov wrote: > On Tue, Mar 27, 2007 at 09:28:10AM +0400, Andrey Chernov wrote: > >>On Tue, Mar 27, 2007 at 10:11:01PM +0000, Garrett Cooper wrote: >> >>>>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. >> >>Additional non-default details from my machine which may (or may not) >>affect the thing: > > > Yet one detail about lockup: external pings to the machine works in the > lockup situation, but no any TCP services is available. > Attempting to press power button to initiate soft reboot says that "acpi > ... not ready yet". This bug is really strange and there is no direct and obvious explanation. A leaked TCP_INFO lock can't really be the cause of the problem as Robert explained. 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? -- Andre
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46090BA6.5060206>