mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Tony Vroon <tony@linx.net>
Cc: Dave Airlie <airlied@linux.ie>,
	DRI mailing list <dri-devel@lists.freedesktop.org>,
	linux-kernel@vger.kernel.org, Matt Turner <mattst88@gmail.com>
Subject: Re: [git pull] drm main pull for 3.4-rc1
Date: Tue, 27 Mar 2012 22:39:13 +0200	[thread overview]
Message-ID: <20120327203913.GA2436@phenom.ffwll.local> (raw)
In-Reply-To: <20120327193124.GA1971@phenom.ffwll.local>

On Tue, Mar 27, 2012 at 09:31:24PM +0200, Daniel Vetter wrote:
> On Mon, Mar 26, 2012 at 03:44:33PM +0100, Tony Vroon wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> > 
> > On 26/03/12 15:32, Daniel Vetter wrote:
> > > Also, can you check whether disabling vt-d does work around the
> > > issue?
> > 
> > Yes, that does appear to stay operational for longer on:
> > Linux adrastea 3.3.0-06972-ge22057c #1 SMP PREEMPT Mon Mar 26 11:29:21
> > BST 2012 x86_64 Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz GenuineIntel
> > GNU/Linux
> > 
> > Obviously I would like to have x2apic and my IOMMU back...
> 
> Can you try out the for-chainsaw branch from
> 
> git://people.freedesktop.org/~danvet/drm
> 
> Afaics it seems to help here on my snb with VT-d enabled. But that means
> it'll still crash eventually with tons of DMAR fault message (like yours).
> But compared to previous kernels it now doesn't insta-die for me. So no
> high hopes, please, but it would be interesting to know how this fares for
> you.
> 
> Meanwhile I'll be trying a few other funky tricks.

Yet another thing to try: Can you append intel_iommu=igfx_off to your
kernel cmdline? If you can, try this both on mainline kernels and with my
additional patches.
-Daniel
-- 
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48

  reply	other threads:[~2012-03-27 20:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-21 10:47 Dave Airlie
2012-03-21 17:31 ` InKi Dae
2012-03-21 17:47   ` Dave Airlie
2012-03-22 20:23 ` Linus Torvalds
2012-03-24 19:15 ` Linus Torvalds
2012-03-24 19:21   ` Daniel Vetter
2012-03-26 13:59 ` Tony Vroon
2012-03-26 14:32   ` Daniel Vetter
2012-03-26 14:36     ` Tony Vroon
2012-03-27 10:01       ` Daniel Vetter
2012-03-27 10:11         ` Tony Vroon
2012-03-27 10:24           ` Tony Vroon
2012-03-26 14:44     ` Tony Vroon
2012-03-27 19:31       ` Daniel Vetter
2012-03-27 20:39         ` Daniel Vetter [this message]
2012-03-28  8:55           ` Tony Vroon
2012-03-29 12:39             ` Daniel Vetter
2012-03-29 12:43               ` Tony Vroon

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=20120327203913.GA2436@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mattst88@gmail.com \
    --cc=tony@linx.net \
    /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

Powered by JetHome