-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 13/04/12 18:38, Steven Newbury wrote: > 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. > > Still Oopses. I'm going to try linus/master. Perhaps it's a > filesystem corruption triggering it? I do find it a little > suspicious that it occurs in "btrfs:find_workspace" though, code > which deals with memory allocations... Damn. It still oopses with my linus tracking branch! I'm going to restore from backup and see if it still happens. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+IbJ8ACgkQGcb56gMuC60bVQCfbIQEd+kpJBrXdeiz/sfJOCC2 f9oAnA4DYSOD1ApvbMl937dxG2i6SYDv =uZ3A -----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
