From owner-freebsd-current Thu Aug 24 14:52:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (Postfix) with ESMTP id 1FC1237B43C; Thu, 24 Aug 2000 14:52:30 -0700 (PDT) Received: (from smap@localhost) by whistle.com (8.10.0/8.10.0) id e7OLqKW01284; Thu, 24 Aug 2000 14:52:20 -0700 (PDT) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma001281; Thu, 24 Aug 2000 14:52:15 -0700 Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.3) id OAA02179; Thu, 24 Aug 2000 14:52:15 -0700 (PDT) (envelope-from archie) From: Archie Cobbs Message-Id: <200008242152.OAA02179@bubba.whistle.com> Subject: Re: panic: reducing sbsize: lost count, uid = 1001 In-Reply-To: "from Brian Fundakowski Feldman at Aug 24, 2000 09:10:09 am" To: Brian Fundakowski Feldman Date: Thu, 24 Aug 2000 14:52:15 -0700 (PDT) Cc: Alfred Perlstein , John Polstra , current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know if this is related to the problems you guys are looking at, but I have a box that every so often (every couple of months) panics with a "panic: recieve 1" panic. This panic happens when the socket character count is bogus during a recv(2), etc. system call. So several months ago I came up with a patch to try and track this down, and with the patch it panics immediately.. but I couldn't figure out why at the time and haven't pursued it since then. Anyway, for what it's worth, the patch I was using is here: ftp://ftp.whistle.com/pub/archie/misc/sbcheck.patch Some variant of it may be useful for tracking down this problem too. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message