From nobody@FreeBSD.org  Mon Jun 23 12:50:37 2008
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 8DF5A1065676
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 23 Jun 2008 12:50:37 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21])
	by mx1.freebsd.org (Postfix) with ESMTP id 7C04A8FC18
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 23 Jun 2008 12:50:37 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.14.2/8.14.2) with ESMTP id m5NCobiu003545
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 23 Jun 2008 12:50:37 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.14.2/8.14.1/Submit) id m5NCobcp003544;
	Mon, 23 Jun 2008 12:50:37 GMT
	(envelope-from nobody)
Message-Id: <200806231250.m5NCobcp003544@www.freebsd.org>
Date: Mon, 23 Jun 2008 12:50:37 GMT
From: Kris Shaw <shawkris@hotmail.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: EEPROM corruption with Compaq NC3163 NIC
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         124904
>Category:       kern
>Synopsis:       [fxp] EEPROM corruption with Compaq NC3163 NIC
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    yongari
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Jun 23 13:00:08 UTC 2008
>Closed-Date:    
>Last-Modified:  Wed Jul 08 04:50:33 UTC 2009
>Originator:     Kris Shaw
>Release:        6.2-RELEASE-p11
>Organization:
>Environment:
FreeBSD freenas.local 6.2-RELEASE-p11 FreeBSD 6.2-RELEASE-p11 #0: Wed Mar 12 18:17:49 CET 2008 root@pcbsd62:/usr/obj/freenas/usr/src/sys/FREENAS-i386   i386
>Description:

Server: Compaq ML350 G2
Nic: Embedded Compaq NC3163

After booting FreeBSD 6.2 (FreeNAS 0.686.3) the embedded network
controller starts to report PXE-E05 errors (EEPROM corrupted) on each
bootup. Disabling PXE boot in server BIOS removes boot up error, but
EEPROM corruption still causes problems because other operating systems
detect EEPROM problems (e.g. Linux e100 driver).

Vendor ID: 0x0E11
Device ID: 0xB134

NC3163 is controlled by fxp driver as it is based on Intel 82559 chipset.
Looking through fxp source code I can see that code exists to re-program
EEPROM. Perhaps the EEPROM update isn't appropriate for NC3163?

>How-To-Repeat:
Boot FreeBSD 6.3
>Fix:


>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->freebsd-net 
Responsible-Changed-By: linimon 
Responsible-Changed-When: Tue Jun 24 08:14:04 UTC 2008 
Responsible-Changed-Why:  
Reclassify. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=124904 
State-Changed-From-To: open->feedback 
State-Changed-By: yongari 
State-Changed-When: Tue Jun 23 08:39:57 UTC 2009 
State-Changed-Why:  
Would you show me the output of "pciconf -lcv"? Also please give me 
more information for what other operating systems do when it detects 
EEPROM corruption. Do they write updated checksum to EEPROM? 
FreeBSD never write new data to EEPROM unless it have to disable 
dynamic standby mode. Did you see the message something like the 
following while fxp(4) probe is in progress? 
fxp0: Disabling dynamic standby mode in EEPROM 


Responsible-Changed-From-To: freebsd-net->yongari 
Responsible-Changed-By: yongari 
Responsible-Changed-When: Tue Jun 23 08:39:57 UTC 2009 
Responsible-Changed-Why:  
Grab. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=124904 

From: Kristian Shaw <shawkris@hotmail.com>
To: <bug-followup@freebsd.org>
Cc:  
Subject: Re: kern/124904: [fxp] EEPROM corruption with Compaq NC3163 NIC
Date: Mon, 29 Jun 2009 18:03:27 +0000

 --_f3b8b519-c87a-4887-9470-453ae3c23886_
 Content-Type: text/plain; charset="iso-8859-1"
 Content-Transfer-Encoding: quoted-printable
 
 
 Sorry=2C the server isn't used with FreeBSD anymore so I can't really troub=
 leshoot this any futher. The EEPROM corruption was also detected in Linux. =
 I actually replaced the system add-in board in the server (daughterboard wi=
 th SCSI=2C VGA and LAN) and that was corrupted too after booting FreeBSD.
 
 _________________________________________________________________
 Get the best of MSN on your mobile
 http://clk.atdmt.com/UKM/go/147991039/direct/01/=
 
 --_f3b8b519-c87a-4887-9470-453ae3c23886_
 Content-Type: text/html; charset="iso-8859-1"
 Content-Transfer-Encoding: quoted-printable
 
 <html>
 <head>
 <style>
 .hmmessage P
 {
 margin:0px=3B
 padding:0px
 }
 body.hmmessage
 {
 font-size: 10pt=3B
 font-family:Verdana
 }
 </style>
 </head>
 <body class=3D'hmmessage'>
 Sorry=2C the server isn't used with FreeBSD anymore so I can't really troub=
 leshoot this any futher. The EEPROM corruption was also detected in Linux. =
 I actually replaced the system add-in board in the server (daughterboard wi=
 th SCSI=2C VGA and LAN) and that was corrupted too after booting FreeBSD.<S=
 PAN lang=3DEN-GB><BR></SPAN><SPAN lang=3DEN-GB></SPAN><br /><hr />
 Upgrade to Internet Explorer 8 Optimised for MSN. <a href=3D'http://extras.=
 uk.msn.com/internet-explorer-8/?ocid=3DT010MSN07A0716U' target=3D'_new'>Dow=
 nload Now</a></body>
 </html>=
 
 --_f3b8b519-c87a-4887-9470-453ae3c23886_--

From: Pyun YongHyeon <pyunyh@gmail.com>
To: Kristian Shaw <shawkris@hotmail.com>
Cc: yongari@freebsd.org, bug-followup@freebsd.org
Subject: Re: kern/124904: [fxp] EEPROM corruption with Compaq NC3163 NIC
Date: Tue, 30 Jun 2009 17:19:40 +0900

 On Mon, Jun 29, 2009 at 06:20:04PM +0000, Kristian Shaw wrote:
 > The following reply was made to PR kern/124904; it has been noted by GNATS.
 > 
 > From: Kristian Shaw <shawkris@hotmail.com>
 > To: <bug-followup@freebsd.org>
 > Cc:  
 > Subject: Re: kern/124904: [fxp] EEPROM corruption with Compaq NC3163 NIC
 > Date: Mon, 29 Jun 2009 18:03:27 +0000
 > 
 
 [...]
 
 >  Sorry=2C the server isn't used with FreeBSD anymore so I can't really troub=
 >  leshoot this any futher. The EEPROM corruption was also detected in Linux. =
 >  I actually replaced the system add-in board in the server (daughterboard wi=
 >  th SCSI=2C VGA and LAN) and that was corrupted too after booting FreeBSD.
 
 Sorry I still don't understand this issue. Do you mean you want to
 detect "EEPROM corruption" in driver and show a warning message for
 it? Linux just prints a warning message and abort attaching driver
 for the hardware if it see checksum mismatch. Linux give users way
 to ignore EEPROM corruption but still have no way to fix EEPROM
 corruption except spewing a warning message. So the end result is
 the same for both FreeBSD and Linux.
 I still wonder how detecting EEPROM corruption in driver can fix
 EEPROM corruption of controller.
State-Changed-From-To: feedback->open 
State-Changed-By: yongari 
State-Changed-When: Wed Jul 8 04:48:55 UTC 2009 
State-Changed-Why:  
Feedback received but submitter has difficulty in accessing the 
hardware as the server isn't used with FreeBSD anymore. 
I still have no idea whether it's a bug of fxp(4) becase PXE/BIOS 
has nothing to do with driver. 

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