From owner-freebsd-current Thu Jun 3 7:13:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from southpass.baynetworks.com (ns2.BayNetworks.COM [134.177.3.16]) by hub.freebsd.org (Postfix) with ESMTP id 6E783151C9 for ; Thu, 3 Jun 1999 07:13:37 -0700 (PDT) (envelope-from thomma@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h016b.s86b1.BayNetworks.COM [134.177.1.107]) by southpass.baynetworks.com (8.9.1/8.9.1) with ESMTP id HAA16822; Thu, 3 Jun 1999 07:09:51 -0700 (PDT) Received: from fedex.engwest.baynetworks.com (fedex.engwest.baynetworks.com [134.177.110.46]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with SMTP id HAA05068; Thu, 3 Jun 1999 07:13:36 -0700 (PDT) Received: from carrera.engwest (carrera.engwest.baynetworks.com) by fedex.engwest.baynetworks.com (4.1/SMI-4.1) Received: from localhost by carrera.engwest (SMI-8.6/SMI-SVR4) id HAA23711; Thu, 3 Jun 1999 07:10:00 -0700 To: rb@gid.co.uk Cc: current@FreeBSD.ORG Subject: Re: Panic on reboot In-Reply-To: Your message of "Thu, 3 Jun 1999 11:49:06 +0000" References: X-Mailer: Mew version 1.92 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990603071000E.thomma@baynetworks.com> Date: Thu, 03 Jun 1999 07:10:00 -0700 From: Tamiji Homma X-Dispatcher: imput version 971024 Lines: 20 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bob, > For a few weeks, I've been seeing a double fault panic on rebooting after > building world followed by kernel. The panic hits right after "syncing > disks... done". It doesn't seem to happen if the machine hasn't done a fair > bit of work since last reboot, and it's happening on two separate machines > (one is SMP). Do you happen to have non-existing devices in kernel config file? I have been seeing the double fault panic on SMP system. It seemed to be related to non-existing device when I looked at it with debugger. When I got rid of unnecessary devices from config file, the panic went away. I didn't investigate which device was causing it, though. Tammy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message