From owner-freebsd-current  Wed May 17 08:22:31 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id IAA06452
          for current-outgoing; Wed, 17 May 1995 08:22:31 -0700
Received: from ns1.win.net (NS1.WIN.NET [204.215.209.3])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id IAA06446
          for <current@freebsd.org>; Wed, 17 May 1995 08:22:29 -0700
Received: (from bugs@localhost) by ns1.win.net (8.6.11/8.6.9) id LAA20369 for current@freebsd.org; Wed, 17 May 1995 11:24:29 -0400
From: Mark Hittinger <bugs@ns1.win.net>
Message-Id: <199505171524.LAA20369@ns1.win.net>
Subject: -cur boot hangs since may 1
To: current@FreeBSD.org
Date: Wed, 17 May 1995 11:24:26 -0400 (EDT)
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 740       
Sender: current-owner@FreeBSD.org
Precedence: bulk


Hi

My plate was emptier than usual today and I had a chance to do a little DDB'n.
Here is the scoop:  If you have a 3com etherlink-III card (ep0) and you try to
boot a generic style kernel it hangs in various places during the boot.  This,
of course, sends one on various wild goose chases.  I've seen this problem
since May 1 but really haven't had time to roll up my sleeves and chase it
till now.

If you disable ie0 during a '-c' boot dialog (or build a kernel without ie0) 
then things work great.

All my boxes have ep0 cards so I have been an unhappy boy for many days.

I am looking at the probe technique in the ie0 driver to see what has
been changed.  It may be confusing the 3c509 card.

Regards,

Mark Hittinger
bugs@win.net