Date: Mon, 23 Jun 2008 12:50:37 GMT From: Kris Shaw <shawkris@hotmail.com> To: freebsd-gnats-submit@FreeBSD.org Subject: gnu/124904: EEPROM corruption with Compaq NC3163 NIC Message-ID: <200806231250.m5NCobcp003544@www.freebsd.org> Resent-Message-ID: <200806231300.m5ND08Ap084470@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 124904 >Category: gnu >Synopsis: EEPROM corruption with Compaq NC3163 NIC >Confidential: no >Severity: serious >Priority: low >Responsible: freebsd-bugs >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: >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: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200806231250.m5NCobcp003544>