From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mtaout01-winn.ispmail.ntl.com ([81.103.221.47]:13635 "EHLO mtaout01-winn.ispmail.ntl.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932074Ab2DMNwb (ORCPT ); Fri, 13 Apr 2012 09:52:31 -0400 From: Steven Newbury Reply-To: Steven Newbury To: Steven Newbury Cc: Yinghai Lu , "Barnes, Jesse" , Dave Airlie , Bjorn Helgaas , linux-pci@vger.kernel.org, DRI mailing list Subject: drm-next i915 regression? ( was: Re: PCI resources above 4GB) References: <1333968563.5678.19.camel@infinity> <4F8467AA.90305@snewbury.org.uk> <4F848357.3060007@snewbury.org.uk> <4F848E10.1090703@snewbury.org.uk> <1334089568.4083.2.camel@Nokia-N900> <4F84A3EC.6030903@snewbury.org.uk> <1334229754.30606.7.camel@Nokia-N900> <1334248841.2910.6.camel@Nokia-N900> <1334317529.2910.21.camel@Nokia-N900> <4F8814F7.20808@snewbury.org.uk> <4F8820F0.5010607@snewbury.org.uk> <4F88297B.3020200@snewbury.org.uk> In-Reply-To: <4F88297B.3020200@snewbury.org.uk> Content-Type: text/plain; charset=utf-8 Date: Fri, 13 Apr 2012 14:52:08 +0100 Message-Id: <1334325128.2910.24.camel@Nokia-N900> Mime-Version: 1.0 Sender: linux-pci-owner@vger.kernel.org List-ID: On Fri, 13 Apr 2012, 14:26:19 BST, Steven Newbury wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 13/04/12 13:49, Steven Newbury wrote: > > On 13/04/12 12:58, Steven Newbury wrote: > > > > > > It's not stable, crashes soon after GMA comes up. (Could be > > > > unrelated breakage in linus/master? Probably not but I will > > > > verify.)  I noticed the high allocations are occuring from the > > > > top of 64-bit address-space, whilst /proc/cpuinfo shows only > > > > 48 bits of virtual addressing.  Could that be why..? > > > To reply to myself again, I should have said crashes shortly > > > after Xorg initialises using the intel driver, in both cases! > > > I'm building a kernel now without the patch set to see if it's > > > unrelated.  If it still dies I'll try applying your patch set to > > > a branch without the changes from linus/master... (should have > > > done that anyway...) > > > > Okay, I instead created a branch from an older 3.4-rc1+ kernel > > tree, running it now, and it seems to be stable.  Something perhaps > > in the newer tree not playing nicely.  I'll see if I can bisect it, > > or at least base of rc2 if that works... (I'm a little wary of > > crashing the system too much and losing my btrfs filesystem...) > rc2 is fine as well.  Not sure what happened there, I need to be more > careful about keeping a clean tree to work from. I'm pretty sure the crash was a from a drm-next regression. I'll try bisecting it....