From nobody@FreeBSD.org  Sun Aug 15 23:07:38 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 164E216A4CE
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 15 Aug 2004 23:07:38 +0000 (GMT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0E57243D1F
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 15 Aug 2004 23:07:38 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i7FN7b8M064537
	for <freebsd-gnats-submit@FreeBSD.org>; Sun, 15 Aug 2004 23:07:37 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.11/8.12.11/Submit) id i7FN7bCQ064536;
	Sun, 15 Aug 2004 23:07:37 GMT
	(envelope-from nobody)
Message-Id: <200408152307.i7FN7bCQ064536@www.freebsd.org>
Date: Sun, 15 Aug 2004 23:07:37 GMT
From: Pete French <pete@twisted.org.uk>
To: freebsd-gnats-submit@FreeBSD.org
Subject: bge driver for 3Com 3C996B on amd64 prevents clean reboot into WIndows
X-Send-Pr-Version: www-2.3

>Number:         70500
>Category:       amd64
>Synopsis:       [bge] bge driver for 3Com 3C996B on amd64 prevents clean reboot into WIndows
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-amd64
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Aug 15 23:10:16 GMT 2004
>Closed-Date:    Thu Dec 08 20:32:38 GMT 2005
>Last-Modified:  Thu Dec 08 20:32:38 GMT 2005
>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:
State-Changed-From-To: open->closed 
State-Changed-By: glebius 
State-Changed-When: Thu Dec 8 20:31:53 GMT 2005 
State-Changed-Why:  
This doesn't look like FreeBSD problem. 

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