From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Newbury Subject: Re: drm-next i915 regression? ( was: Re: PCI resources above 4GB) Date: Fri, 13 Apr 2012 19:12:47 +0100 Message-ID: <4F886C9F.70808@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> <4F88647B.9070209@snewbury.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4F88647B.9070209@snewbury.org.uk> 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 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-----