From jgreco@aurora.sol.net  Thu Aug 27 20:44:07 1998
Received: from aurora.sol.net (aurora.sol.net [206.55.65.76])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11014
          for <FreeBSD-gnats-submit@freebsd.org>; Thu, 27 Aug 1998 20:44:04 -0700 (PDT)
          (envelope-from jgreco@aurora.sol.net)
Received: (from jgreco@localhost)
	by aurora.sol.net (8.8.8/8.8.8/SNNS-1.02) id WAA07182;
	Thu, 27 Aug 1998 22:43:11 -0500 (CDT)
Message-Id: <199808280343.WAA07182@aurora.sol.net>
Date: Thu, 27 Aug 1998 22:43:11 -0500 (CDT)
From: Joe Greco <jgreco@solaria.sol.net>
Reply-To: jgreco@solaria.sol.net
To: FreeBSD-gnats-submit@freebsd.org, jgreco@solaria.sol.net
Subject: de driver still buggy - power cycle of death
X-Send-Pr-Version: 3.2

>Number:         7767
>Category:       kern
>Synopsis:       de driver still buggy - power cycle of death
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Aug 27 20:50:00 PDT 1998
>Closed-Date:    Fri Nov 16 13:42:01 PST 2001
>Last-Modified:  Fri Nov 16 13:42:21 PST 2001
>Originator:     Joe Greco
>Release:        All tested releases
>Organization:
sol.net Network Services - Solaria Public Access UNIX
>Environment:

de-based 10/100 PCI Ethernet card
Bay Networks 350F

>Description:

Power cycling the Bay Switch causes the de interface to stop working.  The
interface becomes un-pingable and unresponsive.  The rest of the system
remains functional.  This is highly annoying when you have to log in to
16 machines to fix all the boxes that you had plugged into the switch.

I have noticed varying specifics under different cards.  For example,
a Kingston PCI 21041 10Mbps card may print that it has autoselected
the AUI or BNC ports at the time the switch is cycled - even though 
these ports do not exist on a KNE40T.

The SMC 9332BDT/9334BDT 10/100 cards appear to have the correct status 
lights indicating the current mode of operation, but when I type the
"ifconfig <ifc> down", they will print a message that the 100baseTX
mode has been selected.

See my previous report for a possibly related bug.

Both of these bugs are rather annoying and problematic.  If it wasn't
for the port density offered by some de-based cards, ...

>How-To-Repeat:

Power cycle the Bay Switch.

>Fix:
	
Reset box, or

ifconfig <ifc> down; ifconfig <ifc> up

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: mike 
State-Changed-When: Thu Jul 19 12:29:22 PDT 2001 
State-Changed-Why:  

Does this problem still occur in newer versions of FreeBSD, 
such as 4.3-RELEASE? 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=7767 
State-Changed-From-To: feedback->closed 
State-Changed-By: bmah 
State-Changed-When: Fri Nov 16 13:42:01 PST 2001 
State-Changed-Why:  
Feedback timeout (3+ months). 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=7767 
>Unformatted:
