From owner-freebsd-stable Wed Mar 6 14:51:31 2002 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7B80A37B402 for ; Wed, 6 Mar 2002 14:51:26 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g26MpM258927; Wed, 6 Mar 2002 14:51:22 -0800 (PST) (envelope-from dillon) Date: Wed, 6 Mar 2002 14:51:22 -0800 (PST) From: Matthew Dillon Message-Id: <200203062251.g26MpM258927@apollo.backplane.com> To: Ian Dowse Cc: "Jan L. Peterson" , freebsd-stable@FreeBSD.ORG Subject: Re: crashes on 4.5-RELEASE References: <200203062130.aa57106@salmon.maths.tcd.ie> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :.. :>- if (space < resid + clen && uio && :>+ if (space < resid + clen && : :>even with INVARIANTS turned off. Nor have I seen an xl0 watchdog :>timeout. : :I actually doubt that this patch could help with the panics you :were seeing. The only problem this is known to fix is one where you :have an NFS filesystem mounted, and you load an IPFW rule that :blocks outgoing NFS packets. In that situation it causes the system :.. I didn't think the patch would help much either but two people have reported to me that it seems to solve their crashing problems. I wonder if a TCP nfs mount would cause the problem to occur more often. Then you wouldn't need an IPFW rule.... a simple TCP stall in a heavily loaded environment would be enough to cause the output buffer to grow to a considerable size. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message