Date: Mon, 2 Dec 1996 20:10:55 -0800 (PST) From: erich@microsoft.com To: freebsd-gnats-submit@freebsd.org Subject: kern/2140: FreeBSD leaves EtherExpress 16 net card in bad state Message-ID: <199612030410.UAA05899@freefall.freebsd.org> Resent-Message-ID: <199612030420.UAA06265@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>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: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Dec 2 20:20:02 PST 1996 >Last-Modified: >Originator: Eric Hanchrow >Organization: Microsoft Corporation >Release: 2.1.6 >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: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199612030410.UAA05899>