From nobody  Mon Dec  2 20:10:55 1996
Received: (from nobody@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id UAA05899;
          Mon, 2 Dec 1996 20:10:55 -0800 (PST)
Message-Id: <199612030410.UAA05899@freefall.freebsd.org>
Date: Mon, 2 Dec 1996 20:10:55 -0800 (PST)
From: erich@microsoft.com
To: freebsd-gnats-submit@freebsd.org
Subject: FreeBSD leaves EtherExpress 16 net card in bad state
X-Send-Pr-Version: www-1.0

>Number:         2140
>Category:       kern
>Synopsis:       FreeBSD leaves EtherExpress 16 net card in bad state
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Dec  2 20:20:02 PST 1996
>Closed-Date:    Mon May 25 01:03:32 PDT 1998
>Last-Modified:  Mon May 25 01:03:43 PDT 1998
>Originator:     Eric Hanchrow
>Release:        2.1.6
>Organization:
Microsoft Corporation
>Environment:
FreeBSD erich1.dbsd-tst.microsoft.com 2.1.6-RELEASE FreeBSD 2.1.6-RELEASE #0: Sun Nov 24 23:31:18  1996
jkh@whisker.cdrom.com:/usr/src/sys/compile/GENERIC i386
>Description:
After using FreeBSD -- which works fine, by the way -- I typically do "shutdown -r now", and then reboot the computer into Windows NT 4.  When I do this, NT complains that the net card driver couldn't start.  But if I press the computer's 'reset' button and reboot NT, it works fine.  I figure this means that FreeBSD left the net card in some sort of bad state.

Of course the problem is just as likely to be in NT as in FreeBSD, but I thought I'd mention it.
>How-To-Repeat:
Boot FreeBSD 2.1.6 with an Intel EtherExpress 16 card.  Shut down with "shutdown -r now".  Boot Windows NT 4, and log in.  You'll see a message from NT saying that the net card's driver couldn't start.
>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: phk 
State-Changed-When: Mon May 25 01:03:32 PDT 1998 
State-Changed-Why:  

As part of our PR auditing campaign, this PR has been closed due to it's 
age and lack of activity on the PR. 

There is a good chance that the problem reported have been solved 
as part of other activities. 

If this is not the case, please reopen this PR with fresh information 
on the manifestation of the bug. 

Sorry about the late reaction to this PR. 

>Unformatted:
