From: Andrew Morton <akpm@linux-foundation.org>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: jbarnes@virtuousgeek.org, eric@anholt.net,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, stable@kernel.org
Subject: Re: Intel 915GM MCHBAR bug
Date: Fri, 5 Jun 2009 13:00:33 -0700 [thread overview]
Message-ID: <20090605130033.5ff3d0b5.akpm@linux-foundation.org> (raw)
In-Reply-To: <1244188941.23533.16.camel@penberg-laptop>
On Fri, 05 Jun 2009 11:02:21 +0300
Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> Hi Jesse,
>
> (I am cc'ing linux-kernel.)
>
> On Mon, 01 Jun 2009 22:31:13 +0300
> > Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> >
> > > Hi Jesse,
> > >
> > > I am seeing this on my Eee PC 701 which is running a Ubuntu
> > > 2.6.28-11.42-generic stock kernel:
> > >
> > > [ 76.826966] [drm:i915_gem_detect_bit_6_swizzle] *ERROR* Couldn't
> > > read from MCHBAR. Disabling tiling.
> > > [ 76.827215] [drm] Initialized i915 1.6.0 20080730 on minor 0
> > > [ 76.834037] [drm:i915_setparam] *ERROR* unknown parameter 4
> > > [ 76.834104] [drm:i915_getparam] *ERROR* Unknown parameter 6
> > >
> > > Google turned up this patch
> > >
> > > http://lists.freedesktop.org/archives/intel-gfx/2009-January/001186.html
> > >
> > > but I don't seem to find it mainline kernel.
> > >
> > > Was the bug fixed in some other way? It seem that distributions have
> > > not yet picked up your patch and I am unsure if it's in any of the
> > > -stable kernels.
>
> On Thu, 2009-06-04 at 11:27 +0100, Jesse Barnes wrote:
> > I think Eric acked it but may not have pushed it to drm-intel-next
> > yet. Should happen in the next week or two though as we prepare the
> > merge window series.
>
> OK, thanks for the info! FYI, I tested 2.6.30-rc8 with your patch
> applied and everything works smoothly on my EeePC 701. I did not test
> plain 2.6.30-rc8 as I expect it to show same kind of behavior as Ubuntu
> distro kernel. Is this correct or do you want me to test 2.6.30-rc8 too?
>
> I wonder why the patch hasn't received more attention as it's a pretty
> critical bug. The _default_ Ubuntu 9.04 netbook remix installation is
> completely broken for EeePC 701 (and probably others as well) without
> the patch. And it's not as if I'm the only one that suffers from it. A
> quick Google search reveals that a lot of people are hitting it.
>
> So I really do think we need to merge this patch to the upcoming 2.6.31
> ASAP and backport it to -stable after it has gotten some more testing.
>
Wanna show us the patch?
Because the world could certainly do with more i915 bugfixes :(
next prev parent reply other threads:[~2009-06-05 20:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A242C81.6020906@cs.helsinki.fi>
[not found] ` <20090604112738.4c01d35e@jbarnes-x200>
2009-06-05 8:02 ` Intel 915GM MCHBAR bug Pekka Enberg
2009-06-05 20:00 ` Andrew Morton [this message]
2009-06-05 21:09 ` Woody Suwalski
2009-06-06 6:14 ` Pekka Enberg
2009-06-06 6:27 ` Andrew Morton
2009-06-06 6:37 ` Pekka Enberg
2009-06-06 20:27 ` Jesse Barnes
2009-06-09 22:07 ` [Intel-gfx] " Jesse Barnes
2009-06-09 22:28 ` Andrew Morton
2009-06-29 17:33 ` [stable] " Greg KH
2009-06-29 18:27 ` Greg KH
2009-06-29 18:51 ` Ozan Çağlayan
2009-06-29 20:45 ` Greg KH
2009-06-06 22:58 ` Andy Whitcroft
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=20090605130033.5ff3d0b5.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=eric@anholt.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=stable@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