I have a Dell Precision 7560, with this issue. I just installed the proposed 5.10.0-1041 oem kernel package for testing.
While it did fix the boot issue, the e1000e driver is failing and I cannot use the wired network interface. Here is the dmesg output of `modprobe e1000e`: [ 293.106059] e1000e: Intel(R) PRO/1000 Network Driver [ 293.106059] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 293.106442] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 293.194836] e1000e 0000:00:1f.6: The NVM Checksum Is Not Valid [ 293.240151] e1000e: probe of 0000:00:1f.6 failed with error -5 Previously I was working around the e1000e NVM issues by building the e1000e module from the 3.8.7 source package from sourceforge. Applying the patches from https://bugzilla.kernel.org/show_bug.cgi?id=213667 to the 5.10.1038-oem kernel source and re-building the e1000e module also solved the issue. ** Bug watch added: Linux Kernel Bug Tracker #213667 https://bugzilla.kernel.org/show_bug.cgi?id=213667 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. 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.nef...@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 -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
