[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LNX.1.10.0809231229460.4671@pegasus.suse.cz>
Date: Tue, 23 Sep 2008 16:29:16 +0200 (CEST)
From: Jiri Kosina <jkosina@...e.cz>
To: David Miller <davem@...emloft.net>, david.vrabel@....com
cc: airlied@...il.com, rjw@...k.pl, linux-kernel@...r.kernel.org,
kernel-testers@...r.kernel.org, chrisl@...are.com
Subject: Re: [Bug #11382] e1000e: 2.6.27-rc1 corrupts EEPROM/NVM
On Mon, 22 Sep 2008, David Miller wrote:
> So I went through the changes from 2.6.27-rc5 until the SHA1
> ID ec0c15afb41fd9ad45b53468b60db50170e22346 and there were
> definitely no E1000 or E1000E changes during that time.
Some recent comments on [1] seem to indicate that this is somehow coupled
into prior problems/panics with Intel graphics.
David, was this also your case, or did the EEPROM got garbled out of a
sudden?
[1] https://bugzilla.novell.com/show_bug.cgi?id=425480
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists