From owner-freebsd-hackers@FreeBSD.ORG Fri Oct 3 22:44:47 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 DA1CA16A4B3 for ; Fri, 3 Oct 2003 22:44:46 -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 h945cEUW014196 for ; Sat, 4 Oct 2003 01:38:14 -0400 (EDT) (envelope-from green@green.bikeshed.org) Received: from localhost (green@localhost)h945cDxp014188 for ; Sat, 4 Oct 2003 01:38:13 -0400 (EDT) Message-Id: <200310040538.h945cDxp014188@green.bikeshed.org> To: hackers@FreeBSD.org From: Brian Fundakowski Feldman Date: Sat, 04 Oct 2003 01:38:13 -0400 Sender: green@green.bikeshed.org Subject: 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 05:44:47 -0000 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.