From owner-freebsd-current@FreeBSD.ORG Thu Dec 11 17:45:14 2008 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 408731065670; Thu, 11 Dec 2008 17:45:14 +0000 (UTC) (envelope-from rdivacky@lev.vlakno.cz) Received: from vlakno.cz (77-93-215-190.static.masterinter.net [77.93.215.190]) by mx1.freebsd.org (Postfix) with ESMTP id ED5A88FC25; Thu, 11 Dec 2008 17:45:12 +0000 (UTC) (envelope-from rdivacky@lev.vlakno.cz) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id B2F829CB1BE; Thu, 11 Dec 2008 18:40:26 +0100 (CET) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (lev.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rPXprjPJdvfY; Thu, 11 Dec 2008 18:40:24 +0100 (CET) Received: from lev.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 398509CB2B8; Thu, 11 Dec 2008 18:40:24 +0100 (CET) Received: (from rdivacky@localhost) by lev.vlakno.cz (8.14.2/8.14.2/Submit) id mBBHeNdm057568; Thu, 11 Dec 2008 18:40:23 +0100 (CET) (envelope-from rdivacky) Date: Thu, 11 Dec 2008 18:40:23 +0100 From: Roman Divacky To: Robert Watson Message-ID: <20081211174023.GA57297@freebsd.org> References: <20081210164345.GA32188@freebsd.org> <20081210214248.GA69246@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: current@FreeBSD.org Subject: Re: [PANIC]: rw_lock panic in in_pcballoc() in r185864 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 11 Dec 2008 17:45:14 -0000 On Wed, Dec 10, 2008 at 10:58:14PM +0000, Robert Watson wrote: > > On Wed, 10 Dec 2008, Roman Divacky wrote: > > >hm... I wondered how it could work before that.... anyway, I got this crash > > Well, nothing says it still works that way, that's just the theory :-). > > >>So, given that this code has worked for quite a long time for many > >>people, this really raises two questions: (1) how reproduceable is this > >>and at what point does it kick in during the boot/runtime, and (2) when > >>did this start happening in terms of updating your source? > > > >ad (1): I get this on every boot when dhcp kicks in (it uses udp I > >believe) ie. 100% reproducible > > > >ad (2): Mon Dec 8 23:02:27 CET 2008 kernel (svn up-dated at most 10 > >minutes before that) works 100% ok > > > >I have the crash dump and the kernel at hand so I can do basically > >anything you ask me to do :) anything I can provide? > > Well, to be honest, the easiest thing to do may be to play the binary > search game to narrow down the point where the problem starts a bit more. > There are a few kinds of things that might lead to this problem -- perhaps > we (I?) mucked up initialization of the inpcb with recent changes, or a > virtualization-related change tripped something up, or a locking/scheduler > change or such. it's something between 185772 and 185864, dont you have any dhcp-enabled machine? if so.. can you reproduce that? > The other thing that would be helpful is a dump of *inp so that we can see > what state inp_lock is in. I foolishly deleted the kernel matching the vmcore, I'll try to do that tomorrow