From asami@silvia.HIP.Berkeley.EDU  Sat May  6 02:37:54 1995
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA29813
          for <FreeBSD-gnats-submit@freebsd.org>; Sat, 6 May 1995 02:37:51 -0700
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id CAA04901; Sat, 6 May 1995 02:37:34 -0700
Message-Id: <199505060937.CAA04901@silvia.HIP.Berkeley.EDU>
Date: Sat, 6 May 1995 02:37:34 -0700
From: asami@berkeley.edu
To: FreeBSD-gnats-submit@freebsd.org
Cc: babkin@hq.icb.chel.su
Subject: ep0 problems on Dell
X-Send-Pr-Version: 3.2

>Number:         384
>Category:       kern
>Synopsis:       ep0 conflicts with some other drivers
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    asami
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat May  6 02:40:02 1995
>Closed-Date:    Fri Feb 9 02:47:53 PST 1996
>Last-Modified:  Fri Feb  9 02:50:17 PST 1996
>Originator:     Satoshi Asami
>Release:        FreeBSD 2.0-950412-SNAP i386
>Organization:
University of California
>Environment:

	Dell XPS Pentium 90, 3com 3c509 Ethernet, IDE HD

>Description:

	After installing FreeBSD from floppy and it reboots from the
	hard disk, it gets stuck after probing the devices in PCI bus.
	Disabling wt0 and ie0 from the -c prompt fixes it.  I thought
	it is very strange because ep0 and wt0 is on port 0x300 but
	ie0 is on 0x360.

>How-To-Repeat:

	As above.

>Fix:
	
	No idea, I'm just a newbie. :)

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: pst 
State-Changed-When: Thu Feb 8 11:29:29 PST 1996 
State-Changed-Why:  
Is this stale? 


Responsible-Changed-From-To: freebsd-bugs->asami 
Responsible-Changed-By: pst 
Responsible-Changed-When: Thu Feb 8 11:29:29 PST 1996 
Responsible-Changed-Why:  
Returned to reporter. 
State-Changed-From-To: feedback->closed 
State-Changed-By: asami 
State-Changed-When: Fri Feb 9 02:47:53 PST 1996 
State-Changed-Why:  
I guess this is a known problem (probes stepping on each other's 
toes).  The GENERIC kernel now even has a note about intrusive 
probes at the top of the network devices section. 

Since I don't have the hardware to test this on, I'm going to close it. 
>Unformatted:


