Similar to ixgbe, this is useful for diagnosing problems. In particular, the errata sheets identify the EEPROM version for many fixes.
Details
Details
- Reviewers
gallatin grehan - Group Reviewers
Intel Networking - Commits
- rGc60b5d477cb4: e1000: print EEPROM/NVM/OROM versions
rG38d7f1c5b391: e1000: Lock nvm print sysctl
rG73922769f0c2: e1000: print EEPROM/NVM/OROM versions
rG884b89510faa: e1000: Lock nvm print sysctl
rG293663f4da9e: e1000: print EEPROM/NVM/OROM versions
rG9b3e252e59c6: e1000: Lock nvm print sysctl
82579LM:
em0: EEPROM V0.13-4
i219 (2) SPT:
em0: EEPROM V0.8-3
i210:
igb0: EEPROM V3.25-0 eTrack 0x800005cc
i350:
igb0: EEPROM V1.63-0 eTrack 0x800009fb
Diff Detail
Diff Detail
- Lint
Lint Skipped - Unit
Tests Skipped
Event Timeline
sys/dev/e1000/if_em.c | ||
---|---|---|
4510 | If it was me, I'd probably print something like "NVM version unknown" |
sys/dev/e1000/if_em.c | ||
---|---|---|
4647 | This will be committed as a separate bug fix, it prevents a KASSERT deep in the shared code |
Comment Actions
@gallatin can you have another look? The locking model on the e1000 is tricky due to the HW so I stashed the info on attach. There's a separate KASSERT fix for em_print_nvm_info for review as well.