[lkml]   [2008]   [Sep]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Linux 2.6.27-rc8
On Mon, 29 Sep 2008, Linus Torvalds wrote:

> > Intel is working with us on tracking down and resolving the issue, but
> > this is not going as well as one would like to see (one attempt, one
> > card with completely hosed EEPROM contents ... and restoring the
> > contents is not *that* trivial).
> What's the magic to trigger it? I've got a laptop with that e1000e chip
> in it, and am obviously running a recent kernel on it. Do people have a
> handle on it? Is it actually verified to be kernel-related, and not
> related to the X server etc?

So far it seems to be that you need 1) something close to xorg 7.4 and
2) 2.6.27-rcX kernel to trigger it. Not every system having e1000e is

Apparently it is some kind of race, as it usually takes multiple cycles to
trigger (on one of our testing machines this took three attempts to
trigger for the first time, and then after unbricking the machine and
restarting testing, the reproduction tests have been running for several

It always seems to happen when X is probing/initializing the graphics
card. So it really seems to be some badness in Xorg intel driver
initialization code, and kernel/hardware allows bad things to happen.

Last time I heard, our X developers are suspecting vbeinit initialization
code in Intel driver and are looking into it.

Also, we are going to release next opensuse/SLES beta with patches that
should mitigate the problem (Jesse has posted a new version of them), so
hopefully we will then receive some stacktraces from the users who are
able to trigger the problem more easily.

Jiri Kosina

 \ /
  Last update: 2008-09-30 09:09    [W:0.098 / U:2.252 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site