From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Vetter Subject: Re: [git pull] drm main pull for 3.4-rc1 Date: Tue, 27 Mar 2012 21:31:24 +0200 Message-ID: <20120327193124.GA1971@phenom.ffwll.local> References: <4F70764F.7030409@linx.net> <20120326143250.GN4014@phenom.ffwll.local> <4F7080D1.4050400@linx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4F7080D1.4050400@linx.net> Sender: linux-kernel-owner@vger.kernel.org To: Tony Vroon Cc: Dave Airlie , DRI mailing list , linux-kernel@vger.kernel.org, Matt Turner List-Id: dri-devel@lists.freedesktop.org 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. -Daniel -- Daniel Vetter Mail: daniel@ffwll.ch Mobile: +41 (0)79 365 57 48