From owner-freebsd-hackers@FreeBSD.ORG Sat Oct 4 16:27:55 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from green.bikeshed.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 477DA16A4B3; Sat, 4 Oct 2003 16:27:53 -0700 (PDT) Received: from green.bikeshed.org (localhost [127.0.0.1]) by green.bikeshed.org (8.12.10/8.12.9) with ESMTP id h94NRlpb005282; Sat, 4 Oct 2003 19:27:47 -0400 (EDT) (envelope-from green@green.bikeshed.org) Received: from localhost (green@localhost)h94NRh0s005278; Sat, 4 Oct 2003 19:27:45 -0400 (EDT) Message-Id: <200310042327.h94NRh0s005278@green.bikeshed.org> X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: Sam Leffler In-Reply-To: Message from Sam Leffler of "Sat, 04 Oct 2003 11:39:52 PDT." <200310041139.52357.sam@errno.com> From: "Brian F. Feldman" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 04 Oct 2003 19:27:43 -0400 Sender: green@green.bikeshed.org cc: hackers@freebsd.org 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: Sat, 04 Oct 2003 23:27:55 -0000 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. I turned off sync on panic so maybe I'll be okay now. That never, ever, worked for me starting a couple years ago and I forgot I had it disabled locally. I see it immediately on boot and I couldn't tell you why; this is a NAT box, and a million other things. I'm running the most current current I can possibly run, of course. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\