From: Arjan van de Ven <arjan@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@gmail.com>, Jiri Kosina <jkosina@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
jesse.brandeburg@intel.com
Subject: Re: Linux 2.6.27-rc8
Date: Mon, 29 Sep 2008 20:19:45 -0700 [thread overview]
Message-ID: <20080929201945.26327311@infradead.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0809291909360.3389@nehalem.linux-foundation.org>
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
next prev parent reply other threads:[~2008-09-30 3:21 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 22:39 Linux 2.6.27-rc8 Linus Torvalds
2008-09-29 23:09 ` david
2008-09-29 23:33 ` Jiri Kosina
2008-09-30 1:56 ` Linus Torvalds
2008-09-30 1:59 ` Dave Airlie
2008-09-30 2:06 ` Arjan van de Ven
2008-09-30 2:23 ` Linus Torvalds
2008-09-30 2:24 ` Linus Torvalds
2008-09-30 12:06 ` Alan Cox
2008-09-30 3:42 ` Brandeburg, Jesse
2008-09-30 12:05 ` Alan Cox
2008-09-30 2:21 ` Linus Torvalds
2008-09-30 2:39 ` Dave Airlie
2008-09-30 3:19 ` Arjan van de Ven [this message]
2008-09-30 7:11 ` Jiri Kosina
2008-09-30 7:58 ` Eric Piel
2008-09-30 16:28 ` Luiz Fernando N. Capitulino
2008-09-30 18:27 ` Herton Ronaldo Krzesinski
2008-09-30 2:30 ` Brandeburg, Jesse
2008-09-30 22:07 ` Thomas Gleixner
2008-09-30 7:06 ` Jiri Kosina
2008-09-30 14:09 ` Krzysztof Halasa
2008-09-30 14:11 ` Jiri Kosina
2008-09-30 15:48 ` Allan, Bruce W
2008-10-01 15:37 ` Jiri Kosina
2008-09-30 7:43 ` Typo bug [Re: Linux 2.6.27-rc8] J.A. Magallón
2008-09-30 7:55 ` Ingo Molnar
2008-09-30 8:02 ` J.A. Magallón
2008-09-30 8:05 ` Ingo Molnar
2008-10-01 21:33 ` Domenico Andreoli
2008-10-02 5:27 ` Willy Tarreau
2008-10-02 9:26 ` Ingo Molnar
2008-10-02 9:45 ` Domenico Andreoli
2008-09-30 18:47 ` H. Peter Anvin
2008-09-30 19:30 ` Yinghai Lu
2008-09-30 19:59 ` H. Peter Anvin
2008-09-30 21:35 ` Yinghai Lu
2008-09-30 21:37 ` H. Peter Anvin
2008-09-30 21:42 ` Yinghai Lu
2008-09-30 22:02 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080929201945.26327311@infradead.org \
--to=arjan@infradead.org \
--cc=airlied@gmail.com \
--cc=jesse.brandeburg@intel.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox