From owner-freebsd-current  Fri Oct 29  4:16:47 1999
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP id 5C45B14D7F
	for <current@FreeBSD.ORG>; Fri, 29 Oct 1999 04:16:44 -0700 (PDT)
	(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id NAA16598;
	Fri, 29 Oct 1999 13:16:39 +0200 (CEST)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <199910291116.NAA16598@freebsd.dk>
Subject: Re: Current kernel locks up during boot
In-Reply-To: <3.0.6.32.19991029115708.0079b380@192.168.255.1> from Bob Bishop at "Oct 29, 1999 11:57:08 am"
To: rb@gid.co.uk (Bob Bishop)
Date: Fri, 29 Oct 1999 13:16:38 +0200 (CEST)
Cc: current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It seems Bob Bishop wrote:
> Hi,
> 
> -current kernels from the past 48hrs or so lock up during boot on my SMP
> box, as in:
> 
> ...and there it freezes. Total lockup, reset button or power cycle only.
> Apparently it's barfing either on one of the PCI netcard probes, or trying
> to initialise ed0 which on an older kernel probes as:
> 
> ed0 at port 0x300-0x31f iomem 0xd8000 irq 10 on isa0
> ed0: address 00:20:18:72:97:67, type NE2000 (16 bit) 
> 
> Any ideas?

Well it happens on single CPU machines as well, I think the ed driver is
borked in current.
There is also a new problem with some newbus realloc failure that made 
me loose my box just a few hours ago, I'll look into it when I get to 
the console...

-Soren


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