From nobody@FreeBSD.ORG  Sat May 13 22:25:06 2000
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id E778B37BCBB; Sat, 13 May 2000 22:25:06 -0700 (PDT)
Message-Id: <20000514052506.E778B37BCBB@hub.freebsd.org>
Date: Sat, 13 May 2000 22:25:06 -0700 (PDT)
From: transistor@ct2600.org
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@FreeBSD.org
Subject: After I configured my network settings and brought up the ep0 interface my computer locks up
X-Send-Pr-Version: www-1.0

>Number:         18541
>Category:       i386
>Synopsis:       After I configured my network settings and brought up the ep0 interface my computer locks up
>Confidential:   no
>Severity:       non-critical
>Priority:       high
>Responsible:    mdodd
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat May 13 22:30:01 PDT 2000
>Closed-Date:    Mon Apr 14 11:26:33 PDT 2003
>Last-Modified:  Mon Apr 14 11:26:33 PDT 2003
>Originator:     transistor
>Release:        4.0 Release
>Organization:
none
>Environment:
ep0: eeprom failed to come ready
>Description:
I have a 3com 3c509 isa ethernet card in my system. After configuring my network settings in the installer program I attempted to bring the interface up and the computer locked up.
>How-To-Repeat:
Boot off the freebsd 4.0 cdrom. Go through with the install process. When you reach the network setup part enter all your settings. After your done entering in the settings it will ask you if you want to bring the interface up. Say yes and the computer will lock up.
>Fix:
?

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->mdodd 
Responsible-Changed-By: mdodd 
Responsible-Changed-When: Mon Jul 17 23:55:45 PDT 2000 
Responsible-Changed-Why:  
'ep' seems to be my problem. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=18541 
State-Changed-From-To: open->closed 
State-Changed-By: mdodd 
State-Changed-When: Mon Apr 14 11:25:42 PDT 2003 
State-Changed-Why:  
I've seen this one and know the cause. 

Disable other confliting drivers to prevent your card from 
being stomped on and wedging the driver in a non-terminal loop. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=18541 
>Unformatted:
