-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 13/04/12 17:17, Yinghai Lu wrote: >>> 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?? > > for-pci-res-alloc include > > for-pci-hostbridge-cleanup for-pci-busn-alloc > for-pci-root-bus-hotplug for-pci-for-each-res-addon at plus 7 > patches. > > maybe there is some problem with for-pci-for-each-res-addon. > > just rebase for-pci-res-alloc to for-pci-root-bus-hotplug. Please > check if the problem still there. > > Thanks > > Yinghai BTW, previously, I was based on your for-pci-busn-alloc branch, didn't see any problems there. Recompiling now with a clean merge of updated for-pci-res-alloc on top of my linus tracking branch... -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+IXpEACgkQGcb56gMuC63ubwCgkyr2d4Xp/4OpLo4ehIYrabtO /SgAoKDaYPOxX9qRznUjUIoYAmPF3thA =s+mx -----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
