Karsten has been testing kernel with these three patches from the series
applied:
e1000e: reset swflag after resetting hardware
e1000e: fix lockdep issues
e1000e: debug contention on NVM SWFLAG
This was done on a hardware which previously triggered the bug in just a
few test iterations in quite a reliable way. Now, with these patches
applied, the EEPROM corruption didn't happen after several tens of
iterations.
Please note, that the patch that disables the writes to EEPROM on hardware
level was *not* involved in this testing.
Therefore it currently seems that these three patches really address the
race condition issue that was present in the e1000e driver.
It is still not clear why the bug started triggering all of a sudden for
so many people though.
--
Jiri Kosina
SUSE Labs
--