From: Felipe Balbi <balbi@ti.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Felipe Balbi <balbi@ti.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
David Airlie <airlied@linux.ie>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: i915 not working on Dell e6410
Date: Mon, 25 Feb 2013 16:56:22 +0200 [thread overview]
Message-ID: <20130225145622.GI15499@arwen.pp.htv.fi> (raw)
In-Reply-To: <20130225144906.GB19874@cantiga.alporthouse.com>
[-- Attachment #1: Type: text/plain, Size: 1036 bytes --]
Hi,
On Mon, Feb 25, 2013 at 02:49:07PM +0000, Chris Wilson wrote:
> On Mon, Feb 25, 2013 at 04:43:12PM +0200, Felipe Balbi wrote:
> > Hi,
> >
> > On Mon, Feb 25, 2013 at 02:39:18PM +0000, Chris Wilson wrote:
> > > On Mon, Feb 25, 2013 at 04:24:11PM +0200, Felipe Balbi wrote:
> > > > Hi folks,
> > > >
> > > > I have a Dell e6410 whose framebuffer gets corrupted with v3.7.9 and
> > > > v3.8.0 but works fine with v3.6.11.
> > > >
> > > > Below you can find lspci and my .config, maybe I'm missing something ?
>
> That looks like https://bugzilla.freedesktop.org/show_bug.cgi?id=60391
> which is fixed by
>
> commit da88a5f7f7d434e2cde1b3e19d952e6d84533662
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date: Wed Feb 13 09:31:53 2013 +0000
>
> drm/i915: Disable WC PTE updates to w/a buggy IOMMU on ILK
>
> or by passing intel_iommu=off on the commandline.
and so it does, thanks. That's going to be merged on v3.9 right ? Hope
there's a stable tag in it, thanks
cheers
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-02-25 14:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 14:24 Felipe Balbi
2013-02-25 14:39 ` Chris Wilson
[not found] ` <20130225144312.GG15499@arwen.pp.htv.fi>
2013-02-25 14:49 ` Chris Wilson
2013-02-25 14:56 ` Felipe Balbi [this message]
2013-02-25 14:59 ` Chris Wilson
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=20130225145622.GI15499@arwen.pp.htv.fi \
--to=balbi@ti.com \
--cc=airlied@linux.ie \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®