From owner-freebsd-current Fri Mar 14 5:11:20 2003 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 60D8D37B401 for ; Fri, 14 Mar 2003 05:11:19 -0800 (PST) Received: from out003.verizon.net (out003pub.verizon.net [206.46.170.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id 58DC143F93 for ; Fri, 14 Mar 2003 05:11:18 -0800 (PST) (envelope-from bleez@verizon.net) Received: from gravy.kishka.net ([151.197.249.111]) by out003.verizon.net (InterMail vM.5.01.05.27 201-253-122-126-127-20021220) with ESMTP id <20030314131117.YPSK3697.out003.verizon.net@gravy.kishka.net> for ; Fri, 14 Mar 2003 07:11:17 -0600 Received: from localhost (localhost [127.0.0.1]) by gravy.kishka.net (8.12.8/8.12.8) with ESMTP id h2EDBHqe001447 for ; Fri, 14 Mar 2003 08:11:17 -0500 (EST) (envelope-from bleez@verizon.net) Date: Fri, 14 Mar 2003 08:11:17 -0500 (EST) From: Bryan Liesner X-X-Sender: root@gravy.kishka.net To: freebsd-current@freebsd.org Subject: panic on boot (devfs_find) Message-ID: <20030314075657.E1432@gravy.kishka.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Authentication-Info: Submitted using SMTP AUTH at out003.verizon.net from [151.197.249.111] at Fri, 14 Mar 2003 07:11:17 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I made posts here recently describing some panics which are somehow related to disappearing/never created device nodes. I am unable to produce a core dump at all, as it panics before / is mounted. The documented kern.dumpdev (unknown oid) doesn't exist and setting dumpdev=ad0s1b in loader.conf doesn't help either. I compiled the faulty kernel with ddb and found that the failure was in devfs_find(). I'm trying to gather more information. Any tips on how to get a proper core dump would be appreciated. As described in my earlier posts, this started happening sometime shortly after commits done after 3/10/2003. Now, really, am I the only one experiencing this? -Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message