[Bug 263555] Re: [intrepid] 2.6.27 e1000e driver places Intel ICH8and ICH9 gigE chipsets at risk

[Jesse Brandeburg]

Tom Jaeger wrote:
> I just checked my syslog and interestingly, the first time I got the
> "e1000e: probe of 0000:00:19.0 failed with error -5" error was during
> wake-up from standby.  The syslog doesn't indicate an X server crash
> (or restart) between booting the computer and suspending it.  I'm not
> sure how useful this information is, but I thought I'd mention it
> just in case.  Let me know if you want more information.

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)

-- 
[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk
https://bugs.launchpad.net/bugs/263555
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.