From owner-freebsd-current@FreeBSD.ORG Thu Apr 8 09:23:04 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E6F316A4CE; Thu, 8 Apr 2004 09:23:04 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB1A743D5C; Thu, 8 Apr 2004 09:23:03 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.10/8.12.10) with ESMTP id i38GMgPq048640; Thu, 8 Apr 2004 12:22:42 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i38GMgTD048637; Thu, 8 Apr 2004 12:22:42 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Thu, 8 Apr 2004 12:22:42 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Brian F. Feldman" In-Reply-To: <200404081610.i38GA05d072719@green.homeunix.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@FreeBSD.org Subject: Re: panic on one cpu leaves others running... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Apr 2004 16:23:04 -0000 On Thu, 8 Apr 2004, Brian F. Feldman wrote: > Robert Watson wrote: > > > > panic: m 0 so->so_rcv.sb_cc 17 > > at line 860 in file ../../../kern/uipc_socket.c > > What made you receive that panic? I remember having that exact panic > (sb_cc size being a little different, obviously) months ago... and > having it disappear. Did you have networking out from Giant where it > shouldn't have yet been? ;) This is running without Giant over most of the network stack. However, I'm still working on tracking down the source of the problem -- I'm beginning to wonder if it's not an existing race opened up by releasing locks in areas where only memory allocations required sleeping would have opened the race previously. I got this panic during local UNIX domain socket IPC between the sshd bits. I suspect what's going on, but need to look in more detail, is that something is messed up relating to control mbufs -- I.e., ancillary data transfer. If you're interested in taking a look at the current work-in-progress, take a look at the rwatson_netperf branch in perforce, or at: http://www.watson.org/~robert/freebsd/netperf/ I can also add you to the CC list for new patch versions if you like. Pretty shortly, I'll be sending them to arch@ instead, but I need to resolve a few problems in socket locking (including this one). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Senior Research Scientist, McAfee Research > > -- > Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ > <> green@FreeBSD.org \ The Power to Serve! \ > Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ > > >