![]() | |||||||||||||
Messages in this thread |
On Mon, 29 Sep 2008 19:21:02 -0700 (PDT) Linus Torvalds <torvalds@linux-foundation.org> wrote: > > > On Tue, 30 Sep 2008, Dave Airlie wrote: > > > > If it is X related then its both a kernel + X server issue, the > > e1000e driver opens the barn door, the X server drives the horses > > through it. > > Are you sure? There was a mandriva report abou NVM corruption on an > e100 too (that one apparently just caused PXE failure, the networking > worked fine). > > So I wonder if it's _purely_ X-server-related, adn the reason people > blame 2.6.27-rc1 is just timing of some X update and then people just > look at the kernel beceuse the 'network card failed' looks so > kernel-related. > > The reason I mention that is right now it looks like the distros are > just running around disabling the e1000e module, or perhaps > downgrading it. Which may not even work! btw, we're also working on making some parts of the kernel more robust against certain types of bugs; for example the ioremap checks and sysfs resource checks. There's a set of checks and API changes we can do to make it less likely that drivers end up doing bad stuff; but that's obviously more for 2.6.28 than for .27 -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org | ||||||||||||
| Last update: 2008-09-30 05:23 [from the cache] ©2003-2008 | |||||||||||||