lkml.org 
[lkml]   [2008]   [Sep]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [Bug #11382] e1000e: 2.6.27-rc1 corrupts EEPROM/NVM
Jiri Kosina wrote:
>
> Yes, I think that xorg/xorg i915 driver/libdrm/GEM/whatever are the
> biggest suspect currently, according to the data that has been gathered so
> far.
>
> Still, what confuses me a little bit -- the EEPROM of the card is set to
> all 0xff, once the corruption happens. Isn't that a quite a coincidence,
> that bytes representing "nothing" in this context are used?
>

Typical card EEPROMs are serial - either I2C or SPI. I believe the
Intel cards use SPI EEPROMs, but I'm not sure.

[Disclaimer: I don't actually know SPI all that well; I know I2C better.
However, I'm pretty sure the following argument does apply to both.]

Consider a corruption which turns a read command into a write command --
often just a single bit difference. Now, the EEPROM will expect data in
to write, but nothing will be driving the data line, so it will
typically be a 1. As the host tries to read, it will therefore fill the
EEPROM with all ones.

-hpa


\
 
 \ /
  Last update: 2008-09-25 20:51    [W:0.103 / U:0.260 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site