From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Newbury Subject: btrfs oops [was Re: drm-next i915 regression? ( was: Re: PCI resources above 4GB)] Date: Fri, 13 Apr 2012 18:12:49 +0100 Message-ID: <4F885E91.4090900@snewbury.org.uk> References: <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> <4F88297B.3020200@snewbury.org.uk> <1334325128.2910.24.camel@Nokia-N900> <4F883364.3080601@snewbury.org.uk> <20120413141305.GI4525@phenom.ffwll.local> <4F88360E.704@snewbury.org.uk> <4F8844E1.5080806@snewbury.org.uk> <4F884B21.604@snewbury.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-pci-owner@vger.kernel.org To: Yinghai Lu Cc: Daniel Vetter , linux-pci@vger.kernel.org, DRI mailing list , "Barnes, Jesse" , Bjorn Helgaas List-Id: dri-devel@lists.freedesktop.org -----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-----