Public bug reported: [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/[email protected]/ [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. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1934511 somerville ** Tags added: oem-priority originate-from-1934511 somerville -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936998 Title: e1000e blocks the boot process when it tried to write checksum to its NVM To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1936998/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
