[Bug 1936998] Re: e1000e blocks the boot process when it tried to write checksum to its NVM

** Tags removed: verification-needed-focal
** Tags added: verification-done-focal

--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/1936998

Title:
e1000e blocks the boot process when it tried to write checksum to its
NVM

Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux-oem-5.10 source package in Focal:
Fix Committed
Status in linux-oem-5.13 source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
In Progress
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux source package in Impish:
In Progress
Status in linux-oem-5.10 source package in Impish:
Invalid
Status in linux-oem-5.13 source package in Impish:
Invalid

Bug description:
[Impact]
While probing e1000e, it checks its NVM checksum, and write correct checksum back if the checksum is not correct. But for recent GBE update for security, its NVM could be written once for MAC address during production, so write checksum during driver probing is not allowed and would block the boot process.

[Fix]
Intel provides a fix for it.
https://patchwork.ozlabs.org/project/intel-wired-lan/patch/20210718041031.3619696-1-sasha.neftin@intel.com/

[Test]
Verified on a Dell machine which has wrong NVM checksum.

[Where problems could occur]
From what Intel told us, the checksum isn't correct is not a big deal, we could ignore it and it won't lead to any issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1936998/+subscriptions