From owner-freebsd-questions  Thu Jul 10 14:59:13 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id OAA01139
          for questions-outgoing; Thu, 10 Jul 1997 14:59:13 -0700 (PDT)
Received: from ice.cold.org (brandon@cold.org [206.81.134.103])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA01134
          for <freebsd-questions@FreeBSD.ORG>; Thu, 10 Jul 1997 14:59:11 -0700 (PDT)
Received: from localhost (brandon@localhost)
	by ice.cold.org (8.8.5/8.8.5) with SMTP id PAA05628;
	Thu, 10 Jul 1997 15:59:09 -0600 (MDT)
Date: Thu, 10 Jul 1997 15:59:08 -0600 (MDT)
From: Brandon Gillespie <brandon@roguetrader.com>
To: Guy Helmer <ghelmer@cs.iastate.edu>
cc: Brandon Gillespie <brandon@roguetrader.com>, freebsd-questions@FreeBSD.ORG
Subject: BUG in -current ed0 driver? (Re: Help! ed0 no longer works after 'make world' upgrade to -CURRENT)
In-Reply-To: <Pine.HPP.3.96.970710105722.15947G-100000@longshot.cs.iastate.edu>
Message-ID: <Pine.BSF.3.96.970710155626.5621A-100000@ice.cold.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Thu, 10 Jul 1997, Guy Helmer wrote:
> On Thu, 10 Jul 1997, Brandon Gillespie wrote:
> 
> > On Thu, 10 Jul 1997, Brandon Gillespie wrote:
> > > I just upgraded from 2.2.2-RELEASE to 3.0-CURRENT with a make world, then
> > > a recompile of my kernel.  However, my ed0 is no longer working!  It has
> > > the exact same port/irq settings as my kernel did with 2.2.2, and it
> > > probes in the boot sequence.  But when it tries to initialize the network
> > > all I get is:
> > > 
> > >    ed0: device timeout
> > 
> > It appears to be working.. all I did:
> > 
> > first boot: didn't work
> > boot -c, set irq/port (even though its to the same thing): didn't work
> > recompile kernel (same config), reboot: didn't work
> > reboot with old 2.2.2 kernel: didn't boot, dunno if it would have worked
> > reboot back to 3.0: works??
> 
> FWIW, I've been running 3.0-current for over a month now on my 386/40, and
> the WD8003E quit working yesterday while the system was in operation (I
> was running a cvsup at the time).  Ever since it quit working, I get "ed0: 
> device timeout" when the system runs the networking configuration at boot
> time, and I've booted numerous times; the card didn't seem to work under
> Win95, either. None of my (10-year old) WD8003EBT cards would even allow
> the system to go through POST (bus speed problems?), so I'm waiting for a
> cheap NE2000 clone to arrive. 

Actually, after a few more tests I can safely say that the following
behaviour occurs EVERY time:

  1) Hard Boot system with 3.0 kernel, ed0: device timeout
  2) Hard Boot system with 2.2.2 kernel, ed0 works (but of course, the
     OS doesn't load because of version incompatabilities)
  3) *soft* boot (just reset) into 3.0 kernel, ed0 WORKS??

Because of this behaviour, I'm assuming the 2.2.2 kernel is doing
something (initializing in some way?) which the 3.0 kernel isn't, and
which is sticking around with the soft boot...