Comment 265 for bug 263555
Revision history for this message
|
|
#265 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Sorry to interfere, our ESX expert told me that under ESX 3.5 it wasn't necessary to have processes _writing_ to the EEPROM for this problem to occur. Rather, it happened if two processes were just _reading_ the EEPROM at the same time, due to a broken locking bit in the HW of some NICS (82546, that's what I was told).