Bug 836978

Summary: Intel 82574L, e1000e - "The NVM Checksum Is Not Valid"
Product: Red Hat Enterprise Linux 6 Reporter: Konrad Mosoń <mosonkonrad>
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
kernel sub component: NIC Drivers QA Contact: Red Hat Kernel QE team <kernel-qe>
Status: CLOSED DUPLICATE Docs Contact:
Severity: high    
Priority: unspecified CC: mosonkonrad, MurzNN, network-qe
Version: 6.2Flags: mosonkonrad: needinfo-
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-06 12:50:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Konrad Mosoń 2012-07-02 11:41:10 UTC
Description of problem:

After reboot, network device gone broken.

OS:      CentOS 6.2
Kernel:  2.6.32-220.23.1.el6.x86_64
Driver:  e1000e
HW:      > lspci | grep Ethernet
01:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection

Error looks identical as in bug:  https://bugzilla.redhat.com/show_bug.cgi?id=459202

"The NVM Checksum Is Not Valid"



Version-Release number of selected component (if applicable):
kernel-2.6.32-220.23.1.el6.x86_64


How reproducible:
1. Depends on your luck.


Steps to Reproduce:
It occured after reboot. But i have 3 the same machines with 3 the same ethernet controllers, and another 2 works (still).
I copied eeprom from other machines, but i have no idea now to restore it to broken cards, because eth0 and eth1 are missing, so ethtool -E doesn't works

  
Actual results:
No eth0 and eth1 interfaces. Only lo in "ifconfig -a" output.


Expected results:
Have eth0 and eth1 and network connectivity.

Comment 2 Prarit Bhargava 2012-07-06 12:50:50 UTC

*** This bug has been marked as a duplicate of bug 836977 ***

Comment 3 Murz 2013-12-03 19:14:15 UTC
Got the same problem, but access to bug 836977 is denied. Can you post solution here?