e1000 EEPROM Checksum validity check should be disabled
Bug #60388 reported by
James Troup
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Hardy |
Fix Released
|
High
|
Tim Gardner | ||
linux-source-2.6.17 (Ubuntu) |
Fix Released
|
Undecided
|
Ben Collins | ||
Hardy |
Invalid
|
Undecided
|
Unassigned | ||
linux-source-2.6.20 (Ubuntu) |
Fix Released
|
High
|
Kyle McMartin | ||
Hardy |
Invalid
|
Undecided
|
Unassigned | ||
linux-source-2.6.22 (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned | ||
Hardy |
Invalid
|
Undecided
|
Unassigned |
Bug Description
We have a box here which the e1000 driver refuses to work on, you just get this from the kernel:
e1000: 0000:05:00.0: e1000_probe: The EEPROM Checksum Is Not Valid
e1000: probe of 0000:05:00.0 failed with error -5
I've no idea if the checksum is valid or not, but I do know that forcibly disabling the check in the kernel makes the NIC work without any apparent problems.
There's been a fair bit of discussion about this on LKML about this, see e.g.
http://
Now given this is an Intel NIC in an Intel machine, shipped to us by Intel. If the EEPROM Checksum can be invalid in cases like that, I think we'd better off to changing the error message to be a warning.
Changed in linux-source-2.6.17: | |
assignee: | nobody → ben-collins |
status: | Unconfirmed → Fix Committed |
Changed in linux-source-2.6.20: | |
assignee: | nobody → kyle |
importance: | Undecided → High |
status: | Unconfirmed → In Progress |
Changed in linux-source-2.6.17: | |
status: | Fix Committed → Fix Released |
Changed in linux-source-2.6.22: | |
assignee: | nobody → ubuntu-kernel-team |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in linux: | |
importance: | Undecided → High |
Changed in linux: | |
milestone: | ubuntu-8.04 → ubuntu-8.04.1 |
Changed in linux: | |
assignee: | ben-collins → timg-tpi |
Changed in linux: | |
assignee: | nobody → timg-tpi |
importance: | Undecided → High |
milestone: | none → ubuntu-8.04.1 |
status: | New → Fix Committed |
milestone: | ubuntu-8.04.1 → none |
Changed in linux: | |
assignee: | timg-tpi → nobody |
importance: | High → Undecided |
status: | Fix Committed → Invalid |
To post a comment you must log in.
It seems that this patch has been applied to the 2.6.17 kernel of edgy, but 2.6.19 and 2.6.20 (feisty) again refuse to work with the e1000 driver.
It works flawlessly when applying the patch to 2.6.19/20, i.e. uncommenting the checksum check and recompiling the driver (as done with the machine I am working on).
Regards,
Johannes