From: Steven Newbury <steve@snewbury.org.uk>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Daniel Vetter <daniel@ffwll.ch>,
linux-pci@vger.kernel.org,
DRI mailing list <dri-devel@lists.freedesktop.org>,
"Barnes, Jesse" <jesse.barnes@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>
Subject: btrfs oops [was Re: drm-next i915 regression? ( was: Re: PCI resources above 4GB)]
Date: Fri, 13 Apr 2012 18:12:49 +0100 [thread overview]
Message-ID: <4F885E91.4090900@snewbury.org.uk> (raw)
In-Reply-To: <CAE9FiQVWSW9cQYuM8RWBVb4dP5vJJ_e=Ld7PSgchzhp6muYToA@mail.gmail.com>
-----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-----
next prev parent reply other threads:[~2012-04-13 17:13 UTC|newest]
Thread overview: 94+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-09 10:49 PCI resources above 4GB Steven Newbury
2012-04-10 0:51 ` Bjorn Helgaas
2012-04-10 10:53 ` Steven Newbury
2012-04-10 15:16 ` Yinghai Lu
[not found] ` <4F8467AA.90305@snewbury.org.uk>
2012-04-10 17:29 ` Steven Newbury
2012-04-10 18:40 ` Yinghai Lu
2012-04-10 18:44 ` Steven Newbury
2012-04-10 19:00 ` Steven Newbury
2012-04-10 19:04 ` Steven Newbury
2012-04-10 19:16 ` Yinghai Lu
2012-04-10 19:46 ` Steven Newbury
2012-04-10 20:07 ` Yinghai Lu
2012-04-10 20:26 ` Steven Newbury
2012-04-10 20:45 ` Yinghai Lu
2012-04-10 21:19 ` Steven Newbury
2012-04-11 3:37 ` Bjorn Helgaas
2012-04-11 5:33 ` Steven Newbury
2012-04-11 9:03 ` Steven Newbury
2012-04-11 14:33 ` Steven Newbury
2012-04-11 23:59 ` Bjorn Helgaas
2012-04-12 11:39 ` Steven Newbury
2012-04-12 0:57 ` Yinghai Lu
2012-04-12 11:22 ` Steven Newbury
2012-04-12 16:07 ` Yinghai Lu
2012-04-12 16:40 ` Steven Newbury
2012-04-13 8:26 ` Yinghai Lu
2012-04-13 8:34 ` Steven Newbury
2012-04-13 11:45 ` Steven Newbury
2012-04-13 11:58 ` Steven Newbury
2012-04-13 11:58 ` Steven Newbury
2012-04-13 12:49 ` Steven Newbury
2012-04-13 12:49 ` Steven Newbury
2012-04-13 13:26 ` Steven Newbury
2012-04-13 13:26 ` Steven Newbury
2012-04-13 13:52 ` drm-next i915 regression? ( was: Re: PCI resources above 4GB) Steven Newbury
2012-04-13 14:08 ` Steven Newbury
2012-04-13 14:08 ` Steven Newbury
2012-04-13 14:13 ` Daniel Vetter
2012-04-13 14:19 ` Steven Newbury
2012-04-13 15:23 ` Steven Newbury
2012-04-13 15:23 ` Steven Newbury
2012-04-13 15:49 ` Steven Newbury
2012-04-13 16:17 ` Yinghai Lu
2012-04-13 17:12 ` Steven Newbury [this message]
2012-04-13 17:38 ` Steven Newbury
2012-04-13 18:12 ` Steven Newbury
2012-04-13 21:51 ` Btrfs corruption Oops " Steven Newbury
2012-04-14 17:37 ` PCI resources above 4GB Steven Newbury
2012-04-14 17:37 ` Steven Newbury
2012-04-14 18:05 ` Steven Newbury
2012-04-14 18:05 ` Steven Newbury
2012-04-14 18:42 ` Steven Newbury
2012-04-14 18:42 ` Steven Newbury
2012-04-14 19:08 ` Steven Newbury
2012-04-14 19:08 ` Steven Newbury
2012-04-14 19:21 ` Steven Newbury
2012-04-14 19:21 ` Steven Newbury
2012-04-14 20:48 ` Yinghai Lu
2012-04-15 10:19 ` Steven Newbury
2012-04-15 10:19 ` Steven Newbury
2012-04-15 10:20 ` Steven Newbury
2012-04-15 10:20 ` Steven Newbury
2012-04-15 11:37 ` Steven Newbury
2012-04-15 11:37 ` Steven Newbury
2012-04-15 17:25 ` Steven Newbury
2012-04-15 17:25 ` Steven Newbury
2012-04-15 17:31 ` Steven Newbury
2012-04-15 17:31 ` Steven Newbury
2012-04-15 20:05 ` Yinghai Lu
2012-04-15 20:06 ` Yinghai Lu
2012-04-16 6:54 ` Yinghai Lu
2012-04-16 7:01 ` Steven Newbury
2012-04-16 7:01 ` Steven Newbury
2012-04-16 17:29 ` Yinghai Lu
2012-04-18 7:21 ` Steven Newbury
2012-04-18 7:21 ` Steven Newbury
2012-04-24 9:49 ` Steven Newbury
2012-04-24 9:49 ` Steven Newbury
[not found] ` <4FB227D3.7090002@snewbury.org.uk>
[not found] ` <CAE9FiQX48eCS85eWMFxm6fCWgu2zwxvSywtQhsf-35WEvBfJVQ@mail.gmail.com>
2012-05-17 12:27 ` Steven Newbury
2012-05-17 12:34 ` Steven Newbury
2012-05-17 16:36 ` Yinghai Lu
2012-05-18 7:45 ` Yinghai Lu
2012-05-18 9:08 ` Yinghai Lu
2012-05-21 17:27 ` Steven Newbury
2012-05-21 17:27 ` Steven Newbury
2012-05-29 23:19 ` Bjorn Helgaas
2012-06-01 23:06 ` Bjorn Helgaas
2012-04-15 3:21 ` Yinghai Lu
2012-04-15 10:18 ` Steven Newbury
2012-04-15 10:18 ` Steven Newbury
2012-04-15 11:31 ` Steven Newbury
2012-04-15 11:31 ` Steven Newbury
2012-04-12 16:29 ` Steven Newbury
2012-04-11 11:43 ` Steven Newbury
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F885E91.4090900@snewbury.org.uk \
--to=steve@snewbury.org.uk \
--cc=bhelgaas@google.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jesse.barnes@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.