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 kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
