From owner-freebsd-stable  Sun Oct 13 14:35:17 2002
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8682037B401
	for <stable@freebsd.org>; Sun, 13 Oct 2002 14:35:16 -0700 (PDT)
Received: from mail-2.zoominternet.net (mail-2.zoominternet.net [63.67.120.22])
	by mx1.FreeBSD.org (Postfix) with SMTP id B459943EA9
	for <stable@freebsd.org>; Sun, 13 Oct 2002 14:35:15 -0700 (PDT)
	(envelope-from dmmiller@cvzoom.net)
Received: (qmail 11072 invoked from network); 13 Oct 2002 21:35:14 -0000
Received: from unknown (HELO acs-24-154-37-142.zoominternet.net) ([24.154.37.142]) (envelope-sender <dmmiller@cvzoom.net>)
          by mail-2.zoominternet.net (qmail-ldap-1.03) with SMTP
          for <chrisy@flix.net>; 13 Oct 2002 21:35:14 -0000
Date: Sun, 13 Oct 2002 17:35:15 -0400 (EDT)
From: Donn Miller <dmmiller@cvzoom.net>
X-X-Sender: dmmiller@daemonstar.zoominternet.net
To: Chrisy Luke <chrisy@flix.net>
Cc: Ian Dowse <iedowse@maths.tcd.ie>, <stable@freebsd.org>
Subject: Re: 4,7 Kernel panic
In-Reply-To: <20021013200414.GA76736@flix.net>
Message-ID: <20021013173001.O53436-100000@daemonstar.zoominternet.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-stable.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-stable>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-stable>
X-Loop: FreeBSD.ORG



On Sun, 13 Oct 2002, Chrisy Luke wrote:

> Donn Miller wrote (on Oct 13):
> > So the error is in the probe/attach routines.  Correct in that the fatal
> > trap only occurs on certain machines.  On my laptop, the kernel bombs
> > immediately after the EISA bus is probed.  For example:
> >
> > eisa0:  <EISA bus> *BOMB*
>
> I commented out the EISA code in nexus_attach(), and my 4.7-S boots
> fine:
>
> #if 0
>         if (!devclass_get_device(devclass_find("eisa"), 0)) {
>                 child = device_add_child(dev, "eisa", 0);
>                 if (child == NULL)
>                         panic("nexus_attach eisa");
>                 device_probe_and_attach(child);
>         }
> #endif

I saw a related post on Google, dating back to 2000.  It was the same
deal, except it was bombing out on the ISA bus probe.  The guy's solution
was to substitute nexus_add_child for device_add_child, although that
sounds like an ugly hack, and it's probably wrong.

FWIR, I never saw the "on motherboard" message printed; I only saw the
"eisa0:  <EISA bus>" before the fatal trap occured.  I know it's possible to
step through the entire probe/attach routines after doing "boot -d", but it got
a little tedious.  Too many low-level asm statements to step through.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message