Date: Sun, 15 Aug 2004 23:07:37 GMT From: Pete French <pete@twisted.org.uk> To: freebsd-gnats-submit@FreeBSD.org Subject: amd64/70500: bge driver for 3Com 3C996B on amd64 prevents clean reboot into WIndows Message-ID: <200408152307.i7FN7bCQ064536@www.freebsd.org> Resent-Message-ID: <200408152310.i7FNAGQh003851@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 70500 >Category: amd64 >Synopsis: bge driver for 3Com 3C996B on amd64 prevents clean reboot into WIndows >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Aug 15 23:10:16 GMT 2004 >Closed-Date: >Last-Modified: >Originator: Pete French >Release: 5.2-CURRENT (cvsup 14th August 2004) >Organization: Drayhouse >Environment: >Description: After running FreeBSD with a 3Com 3C996B gigabit ether card, using the bge driver, when rebooting into Windows XP the card refuses to start. The card has to be disabled and then re-enabled in windows before it will work. This applies both t a worm reboot and also a cold restart. It is repeatable and always happens after running FreeBSD/amd64. I have not tried it on the i386 version. >How-To-Repeat: Boot FreeBSD then boot Windows XP. >Fix: Workaround is to disable/enable the card from the device manager in Winddows to get it to start properly. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200408152307.i7FN7bCQ064536>