From owner-freebsd-current@FreeBSD.ORG  Wed Nov 24 01:22:25 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id C667616A4CE; Wed, 24 Nov 2004 01:22:25 +0000 (GMT)
Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id EDEBD43D1D; Wed, 24 Nov 2004 01:22:23 +0000 (GMT)
	(envelope-from ganbold@micom.mng.net)
Received: from [202.179.0.164] (helo=ganbold.micom.mng.net)
	by publicd.ub.mng.net with esmtpa (Exim 4.43 (FreeBSD))
	id 1CWlrm-0001ZV-Nh; Wed, 24 Nov 2004 09:22:43 +0800
Message-Id: <6.2.0.14.2.20041124091640.03064eb0@202.179.0.80>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14
Date: Wed, 24 Nov 2004 09:22:12 +0800
To: Robert Watson <rwatson@freebsd.org>
From: Ganbold <ganbold@micom.mng.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
cc: tomaz.borstnar@over.net
cc: cguttesen@yahoo.dk
cc: scottl@freebsd.org
cc: mhunter@ack.Berkeley.EDU
cc: freebsd-current@freebsd.org
Subject: Re: Page fault in FreeBSD 5.3 on IBM e325, Dual AMD64 2.2GHz, 
 4GB RAM, ServeRAID 6M - problem goes away without TCP sack
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Nov 2004 01:22:25 -0000

At 06:43 PM 11/22/2004, you wrote:

> >
> > It seems to me the problem is related to network stack and threading.
> > Am I right? How to solve this problem?
>
>I've seen reports of this problem with and without debug.mpsafenet=1,
>which suggests it is a network stack bug but not specific to locking. I've
>also seen reports that disabling TCP SACK will make the problem go away,
>which would be good to confirm.  I spent the weekend building up some more
>expertise in TCP and reading a lot of TCP code, and hope to look at this
>problem in more detail today.  You may want to try turning off TCP sack
>using net.inet.tcp.sack.enable=0 in sysctl.conf (or loader.conf).

I  turned off TCP sack using net.inet.tcp.sack.enable=0 in sysctl.conf and 
it seems like the problem goes away.
It is working for more than 20 hours without any crash.
Robert, did you find anything in network stack code? I'm just curious.

thanks a lot,

Ganbold


>Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
>robert@fledge.watson.org      Principal Research Scientist, McAfee Research
>
>
>_______________________________________________
>freebsd-current@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-current
>To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"