Re: Latest -current complete lockup (tcp changes?)

From: David Wolfskill <david_at_catwhisker.org>
Date: Sat, 24 Mar 2007 10:45:34 -0700
On Sat, Mar 24, 2007 at 06:12:59PM +0100, Pawel Worach wrote:
> Andrey Chernov wrote:
> >Very recent -current cause complete lockup in case and after small amount 
> >of network activity happens. No panic, no ddb console - nothing just 
> >lockup. Previously working kernel is from Mar 22. I suspect 
> >recent round of TCP changes.
> >
> 
> Here is what I see which is tcp related.
> ...

> # ident /usr/src/sys/netinet/tcp_input.c
> /usr/src/sys/netinet/tcp_input.c:
>      $FreeBSD: src/sys/netinet/tcp_input.c,v 1.328 2007/03/23 20:16:50 
> andre Exp $

As I mentioned ealrier, I'm not seeing a problm with today's CURRENT,
and check my CURRENT sources:

g1-18(6.2-S)[2] ident usr/src/sys/netinet/tcp_input.c
usr/src/sys/netinet/tcp_input.c:
     $FreeBSD: src/sys/netinet/tcp_input.c,v 1.328 2007/03/23 20:16:50 andre Exp $
g1-18(6.2-S)[3] 

so I'd guess that the problem Andrey is reporting either doesn't lie
there or is related to a configuration difference between our systems
or usages.

Peace,
david
-- 
David H. Wolfskill				david_at_catwhisker.org
Believe SORBS at your own risk: 63.193.123.122 has been static since Aug 1999.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.

Received on Sat Mar 24 2007 - 16:45:35 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:07 UTC