From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mtaout02-winn.ispmail.ntl.com ([81.103.221.48]:13118 "EHLO mtaout02-winn.ispmail.ntl.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753447Ab2DMN0m (ORCPT ); Fri, 13 Apr 2012 09:26:42 -0400 Message-ID: <4F88297B.3020200@snewbury.org.uk> Date: Fri, 13 Apr 2012 14:26:19 +0100 From: Steven Newbury MIME-Version: 1.0 To: Steven Newbury CC: Yinghai Lu , "Barnes, Jesse" , Dave Airlie , Bjorn Helgaas , linux-pci@vger.kernel.org, DRI mailing list Subject: 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> In-Reply-To: <4F8820F0.5010607@snewbury.org.uk> Content-Type: text/plain; charset=UTF-8 Sender: linux-pci-owner@vger.kernel.org List-ID: -----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. Any idea about how to force the GMA >4G when the BIOS hasn't put it into the middle of SystemRAM? (as it does when docked) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+IKXsACgkQGcb56gMuC62+gACeLDg30iJiukq1pSfu2M1GJzZj xGQAn0DekMqnLcrKXXn7rMwGFgRzJrsC =k+WB -----END PGP SIGNATURE----- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Newbury Subject: Re: PCI resources above 4GB Date: Fri, 13 Apr 2012 14:26:19 +0100 Message-ID: <4F88297B.3020200@snewbury.org.uk> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4F8820F0.5010607@snewbury.org.uk> Sender: linux-pci-owner@vger.kernel.org To: Steven Newbury Cc: Yinghai Lu , "Barnes, Jesse" , Dave Airlie , Bjorn Helgaas , linux-pci@vger.kernel.org, DRI mailing list List-Id: dri-devel@lists.freedesktop.org -----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. Any idea about how to force the GMA >4G when the BIOS hasn't put it into the middle of SystemRAM? (as it does when docked) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+IKXsACgkQGcb56gMuC62+gACeLDg30iJiukq1pSfu2M1GJzZj xGQAn0DekMqnLcrKXXn7rMwGFgRzJrsC =k+WB -----END PGP SIGNATURE-----