Bug 463503
Summary: | EEPROM/NVM of the e1000e becomes corrupted | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Andy Gospodarek <agospoda> |
Component: | kernel | Assignee: | Andy Gospodarek <agospoda> |
Status: | CLOSED ERRATA | QA Contact: | Martin Jenner <mjenner> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.3 | CC: | bruce.w.allan, ddomingo, djuran, dkovalsk, gbeshers, jane.lv, jcm, jesse.brandeburg, john.ronciak, jvillalo, keve.a.gabbert, ltroan, martinez, peterm, rpacheco, tao, youquan.song |
Target Milestone: | beta | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://bugzilla.kernel.org/show_bug.cgi?id=11382 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
The e1000e driver for Intel(R) PRO/1000 ethernet devices has been updated to the upstream version 0.3.3.3-k2. With this update, the EEPROM and NVM of supported devices are now write-protected.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2009-01-20 20:06:21 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 459202 | ||
Bug Blocks: | 432382, 436045, 454962 |
Description
Andy Gospodarek
2008-09-23 18:46:48 UTC
John, Can you update this BZ with your latest updates? We have been submitting patches to the e1000e to protect the NVM. We will be submitting another patch later today that has a way to make the NVM read only. If you want to write to the NVM for any reason, you will need to reload the driver with a load time parameter to be able to write the NVM. We will be pushing the patch as _the_ mechanism to protect the NVM for the e1000e driver. So with this fix added to the e1000e driver we see no reason to hold up the driver update for this driver. All of these patches will not fix the cause of the problem but will protect the NVM from being corrupted. So the next reboot of the system the LOM will still be seen on the PCI bus. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release. in kernel-2.6.18-118.el5 You can download this test kernel from http://people.redhat.com/dzickus/el5 since this was root caused to be due to CONFIG_DYNAMIC_FTRACE and I don't think el5 has ftrace enabled (correct me if I'm wrong) then I don't think there is anything to worry about for EL5. You are correct, Jesse. We will ship with the protection anyway since it's already in there and will ease the concerns of some of our customers. Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: The e1000e driver for Intel(R) PRO/1000 ethernet devices has been updated to the upstream version 0.3.3.3-k2. With this update, the EEPROM and NVM of supported devices are now write-protected. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2009-0225.html |