-----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----- -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
