From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joerg Roedel Subject: Re: Linux 2.6.39-rc3 Date: Fri, 15 Apr 2011 16:33:50 +0200 Message-ID: <20110415143350.GM18463@8bytes.org> References: <20110413193459.GL19819@8bytes.org> <4DA60C30.4060606@kernel.org> <4DA6145D.9070703@kernel.org> <4DA655E7.3000904@zytor.com> <20110415131152.GJ18463@8bytes.org> <20110415131650.GB18660@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20110415131650.GB18660@elte.hu> Sender: linux-kernel-owner@vger.kernel.org To: Ingo Molnar Cc: Linus Torvalds , "H. Peter Anvin" , Yinghai Lu , Alex Deucher , Linux Kernel Mailing List , "dri-devel@lists.freedesktop.org" , Thomas Gleixner , Tejun Heo , alexandre.f.demers@gmail.com List-Id: dri-devel@lists.freedesktop.org On Fri, Apr 15, 2011 at 03:16:50PM +0200, Ingo Molnar wrote: > Ok, but how did the allocation changes start triggering this error in > v2.6.39-rc1? There must still be some layout specific thing here, right? > Do we understand the details of that as well? No, I must admit that I lack enough knowledge about the GPU hardware to make an guess how this tanslation-request happened. All I can tell is the address that was reported in the MCE, it is 0xa0001000 (==the second page of the GART aperture). Maybe Alex can help here. Alex, may it be possible that the GPU generates DMA requests in the GTT area before the GTT is activated (or the activation is completed)? Or can you imagine any other reason? Joerg