-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 13/04/12 16:23, Steven Newbury wrote: > On 13/04/12 15:19, Steven Newbury wrote: >> On 13/04/12 15:13, Daniel Vetter wrote: >>> On Fri, Apr 13, 2012 at 03:08:36PM +0100, Steven Newbury >>> wrote: >>>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >>>> >>>> On 13/04/12 14:52, Steven Newbury wrote: >>>>> On Fri, 13 Apr 2012, 14:26:19 BST, Steven Newbury >>>>> <steve@xxxxxxxxxxxxxxx> 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.... >>>> Sorry, posted too soon! Almost as I clicked on send it froze >>>> again (using rc2 + for-pci-res-alloc ). I had problems with >>>> the earlier patches re. X/i915 stability. Strange. I'll >>>> see if I can track it down. > >>> Please upgrade to the latest version of Linus' upstream git. A >>> few fixes for regressions in drm/i915 just landed there for >>> -rc3. -Daniel > >> Okay. I'll try clean latest linus + for-pci-res-alloc. Will >> report back. > > Looks like either a btrfs regression or bad interaction with > for-pci-res-alloc. Oops attached. Just hit the same oops on the rc1+for-pci-res-alloc kernel I tried earlier so it's not definitely something new in the btrfs code. Seems like it's a 64/32bit pointer issue?? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+ISyEACgkQGcb56gMuC63uRwCcCLm8yx1YVnTBSvT/9jx/IqEb WcYAoJh5iceqZvDDGdJHV88YwEyEnM32 =jfup -----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
