From owner-freebsd-current@FreeBSD.ORG Thu Dec 11 22:19:26 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 46F5D106564A; Thu, 11 Dec 2008 22:19:26 +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 F1C948FC19; Thu, 11 Dec 2008 22:19:25 +0000 (UTC) (envelope-from rdivacky@lev.vlakno.cz) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 623309CB19A; Thu, 11 Dec 2008 23:14:39 +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 hbUGkvF3TLfS; Thu, 11 Dec 2008 23:14:27 +0100 (CET) Received: from lev.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id A42D89CB238; Thu, 11 Dec 2008 23:14:27 +0100 (CET) Received: (from rdivacky@localhost) by lev.vlakno.cz (8.14.2/8.14.2/Submit) id mBBMERs7012442; Thu, 11 Dec 2008 23:14:27 +0100 (CET) (envelope-from rdivacky) Date: Thu, 11 Dec 2008 23:14:27 +0100 From: Roman Divacky To: Robert Watson Message-ID: <20081211221427.GA12310@freebsd.org> References: <20081210164345.GA32188@freebsd.org> <20081210214248.GA69246@freebsd.org> <20081211174023.GA57297@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 22:19:26 -0000 On Thu, Dec 11, 2008 at 07:08:55PM +0000, Robert Watson wrote: > > On Thu, 11 Dec 2008, Roman Divacky wrote: > > >>>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? > > I have several boxes, real and virtual, using DHCP and very recent (tm) > kernels and no sign of this panic. That's why I think there's something > going on here that's a bit more subtle. For example, we'd really like to > know what in the rw_wlock() call got tripped over as a NULL pointer... > > >>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 > > OK. Once you get the panic, I think the most interesting questions have to > do with the contents of *inp, *inp->inp_lock.lock_object, etc. It might > also be interesting to know whether any UDP use triggers the panic, or just > DHCP. You can test this by booting to single-user, configuring lo0 > manually, and then doing "dig @127.0.0.1 ." or some other activity that > triggers a UDP packet to be sent. I just booted r185942 and it seems to work fine, so I guess it could have been some stale obj file or something. sorry for the noise