On Thu, 25 Sep 2008, Frans Pop wrote: > Extra datapoint. As far as I've seen this problem has not yet been > reported by any people running Debian. This could point to X.Org as > Debian currently has 7.3 while I think the reports so far have been with > 7.4. Yes, I think that xorg/xorg i915 driver/libdrm/GEM/whatever are the biggest suspect currently, according to the data that has been gathered so far. Still, what confuses me a little bit -- the EEPROM of the card is set to all 0xff, once the corruption happens. Isn't that a quite a coincidence, that bytes representing "nothing" in this context are used? If being set to 0 (it's so easy to call memset(0) on a bogus pointer, there are usually lots of them in the code) or to random garbage, it would seem to be much more understandable, than 0xff. -- 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
