From nobody@FreeBSD.org  Mon Oct 23 08:31:46 2006
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 843CE16A40F
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 23 Oct 2006 08:31:46 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8EBF543D67
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 23 Oct 2006 08:31:44 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id k9N8VSwx082392
	for <freebsd-gnats-submit@FreeBSD.org>; Mon, 23 Oct 2006 08:31:28 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id k9N8VS6Y082390;
	Mon, 23 Oct 2006 08:31:28 GMT
	(envelope-from nobody)
Message-Id: <200610230831.k9N8VS6Y082390@www.freebsd.org>
Date: Mon, 23 Oct 2006 08:31:28 GMT
From: Victor Melnichenko<melnichenko@uatele.com>
To: freebsd-gnats-submit@FreeBSD.org
Subject: em1: The EEPROM Checksum Is Not Valid
X-Send-Pr-Version: www-3.0

>Number:         104705
>Category:       i386
>Synopsis:       [em] em1: The EEPROM Checksum Is Not Valid
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    remko
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Mon Oct 23 08:40:13 GMT 2006
>Closed-Date:    Sun Mar 25 11:20:53 GMT 2007
>Last-Modified:  Sun Mar 25 11:20:53 GMT 2007
>Originator:     Victor Melnichenko
>Release:        6.1
>Organization:
Inter-Telecom
>Environment:
> uname -a
FreeBSD test.uatele.com 6.1-RELEASE-p10 FreeBSD 6.1-RELEASE-p10 #0: Thu Oct 12 11:19:58 EEST 2006     root@test.uatele.com:/usr/src/sys/i386/compile/TEST-SMP  i386
>Description:
I'am got a two Intel 82572EI PCI-X Gigabit Ethernet card's.

pciconf -lv

em0@pci3:0:0:   class=0x020000 card=0x10828086 chip=0x107d8086 rev=0x06 hdr=0x00
    vendor   = 'Intel Corporation'
    device   = 'PRO/1000 PT'
    class    = network
    subclass = ethernet
em1@pci4:0:0:   class=0x020000 card=0x10828086 chip=0x107d8086 rev=0x06 hdr=0x00
    vendor   = 'Intel Corporation'
    device   = 'PRO/1000 PT'
    class    = network
    subclass = ethernet

dmesg

em0: <Intel(R) PRO/1000 Network Connection Version - 3.2.18> port 0x8000-0x801f 
mem 0xf8020000-0xf803ffff,0xf8000000-0xf801ffff irq 17 at device 0.0 on pci3
em0: [GIANT-LOCKED]
em0: Ethernet address: 00:15:17:0d:94:bd
em1: <Intel(R) PRO/1000 Network Connection Version - 3.2.18> port 0x9000-0x901f 
mem 0xfa020000-0xfa03ffff,0xfa000000-0xfa01ffff irq 18 at device 0.0 on pci4
em1: [GIANT-LOCKED]
em1: Ethernet address: 00:15:17:0d:94:d1

Sometimes em0 or em1 was "freeze" with next messages in /var/log/messages(after "ifconfig <em_int> down && ifconfig <em_int> up" commands):
Oct 20 16:17:12 test kernel: em1: The EEPROM Checksum Is Not Valid
Oct 20 16:17:12 test kernel: em1: Unable to initialize the hardware

With lastest driver(6.1.4) from intel.com problem not solved.

>How-To-Repeat:
I dont know :(

>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: remko 
State-Changed-When: Wed Dec 13 14:59:15 UTC 2006 
State-Changed-Why:  
OK a lot had changed in the EM card recently, can you please 
test whether that solved your problem? I got a mentioning 
that it might also be hardware specific, which means that the 
used hardware may be flakey. Let's see how far we can come with 
this. 


Responsible-Changed-From-To: freebsd-i386->remko 
Responsible-Changed-By: remko 
Responsible-Changed-When: Wed Dec 13 14:59:15 UTC 2006 
Responsible-Changed-Why:  
Grab the PR so that i can track feedback. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=104705 
State-Changed-From-To: feedback->closed 
State-Changed-By: remko 
State-Changed-When: Sun Mar 25 11:20:51 UTC 2007 
State-Changed-Why:  
Jack send me a report a long time ago that this appears to be flakey 
hardware. We cannot do much about that so close the ticket. Thanks for 
using FreeBSD though! 

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