This is limited to ICH8, ICH9 and ICH10 systems running the 2.6.27-rc
kernels.  Reports are that things work fine until there is a panic in
another driver which looks to have written all over the LOMs
non-volatile memory causing the problem.

Cheers,
John
-----------------------------------------------------------
"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.", Benjamin
Franklin 1755 
 

>-----Original Message-----
>From: Breno Leitao [mailto:[EMAIL PROTECTED] 
>Sent: Tuesday, September 23, 2008 8:56 AM
>To: Thomas Jacob
>Cc: [email protected]
>Subject: Re: [E1000-devel] e1000e EEPROM corruption,which 
>versions are affected?
>
>Thomas Jacob wrote:
>> I'd be very interested in a statement about exactly
>> which versions of the kernel and also the standalone package 
>> contain this faulty driver.
>
>I am wondering which NIC version is affected by this problem.
>All e1000e supported NIC, or just some specific cards ?
>
>---------------------------------------------------------------
>----------
>This SF.Net email is sponsored by the Moblin Your Move 
>Developer's challenge
>Build the coolest Linux based applications with Moblin SDK & 
>win great prizes
>Grand prize is a trip for two to an Open Source event anywhere 
>in the world
>http://moblin-contest.org/redirect.php?banner_id=100&url=/
>_______________________________________________
>E1000-devel mailing list
>[email protected]
>https://lists.sourceforge.net/lists/listinfo/e1000-devel
>

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
E1000-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/e1000-devel

Reply via email to