From owner-freebsd-hackers@FreeBSD.ORG Sat Oct 4 18:37:04 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5330A16A4B3; Sat, 4 Oct 2003 18:37:04 -0700 (PDT) Received: from smtp.omnis.com (smtp.omnis.com [216.239.128.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA73843FE0; Sat, 4 Oct 2003 18:37:03 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from softweyr.homeunix.net (66-91-236-204.san.rr.com [66.91.236.204]) by smtp-relay.omnis.com (Postfix) with ESMTP id B447172DCF; Sat, 4 Oct 2003 18:35:44 -0700 (PDT) From: Wes Peters Organization: Softweyr To: Sam Leffler , Brian Fundakowski Feldman , hackers@freebsd.org Date: Sat, 4 Oct 2003 18:37:01 -0700 User-Agent: KMail/1.5.4 References: <200310040538.h945cDxp014188@green.bikeshed.org> <200310041139.52357.sam@errno.com> In-Reply-To: <200310041139.52357.sam@errno.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200310041837.01922.wes@softweyr.com> Subject: Re: Is socket buffer locking as questionable as it seems? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Oct 2003 01:37:04 -0000 On Saturday 04 October 2003 11:39 am, Sam Leffler wrote: > On Friday 03 October 2003 10:38 pm, Brian Fundakowski Feldman wrote: > > I keep getting these panics on my SMP box (no backtrace or DDB or > > crash dump of course, because panic() == hang to FreeBSD these days): > > panic: receive: m == 0 so->so_rcv.sb_cc == 52 > > From what I can tell, all sorts of socket-related calls are "MP-safe" > > and yet never even come close to locking the socket buffer. From > > what I can tell, the easiest way for this occur would be sbrelease() > > being called from somewhere that it's supposed to, but doesn't, have > > sblock(). Has anyone seen these, or a place to start looking? Maybe > > a way to get panics to stop hanging the machine? TIA if anyone has > > some enlightenment. > > Haven't seen anything on my SMP test box. As Robert has already said > sockets are still implicitly locked by Giant. You need to provide more > information like what version you are running and what your system is > doing when the panic occurs. > > FWIW panic does not hang for me so you might first try to figure out > why that's occuring. Is this one of the areas you are planning to get to, Sam? -- Where am I, and what am I doing in this handbasket? Wes Peters wes@softweyr.com