Comment 84 for bug 263555

Jesse Brandeburg wrote:
> Tom your machine may need a bios update to fix your suspend issue. I'm
> not sure yet if this is related to the issue we're seeing with other
> users who appear to just be rebooting. It is a very interesting data
> point however, so thanks for posting. If you can post if you're running
> i686 or x86_64, and let us know if you have an ethtool -e dump from
> after the failure (may need modified e1000e that doesn't goto or set err
> = after printing failed NVM checksum)
>
There actually wasn't any issue with suspend, it's just that the
corruption happened between boot and suspend (which caused the driver to
be reloaded, I guess) -- without any X crash or reboot. I have seen a
lot of random X crashes lately though, and also a few instances of the
system hanging and NumLock blinking (are these kernel panics?). I'm
attaching the relevant part of /var/log/messages. I did do a bios
update a few days ago, though. I'm running i686 (on a thinkpad x61t).
The dump isn't very interesting, it's all 0xff. I'll also attach a
modified kernel module for the latest intrepid kernel, in case somebody
else is in a similar situation. Would it make sense to write some
random junk in the EEPROM to see if the issue appears again? I don't
need a network adapter at the moment.