From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: Ian Campbell <ijc@hellion.org.uk>,
linux-kernel@vger.kernel.org, Kel Modderman <kel@otaku42.de>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: kernel BUG at lib/radix-tree.c:473!
Date: Thu, 14 Aug 2008 10:38:32 -0700 [thread overview]
Message-ID: <48A46D98.1010607@goop.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0808141347480.11013@blonde.site>
Hugh Dickins wrote:
> In both cases it's handling a page fault: I'm curious as to what kind
> of vma this fault is occurring on. Could you devise a way of getting
> us /proc/<pid>/maps output, together with the faulting address, when
> it hits one of these BUGs? Or should I try to put together a patch
> for that?
>
Irritatingly, it looks like the i386 register dump doesn't include cr2.
My 64-bit dump has cr2 as 00007fb12cb2a000 which is a good solid
usermode address. I'll run X under strace to see if that gives a clue
to what it corresponds to.
J
next prev parent reply other threads:[~2008-08-14 17:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 7:02 kernel BUG at lib/radix-tree.c:473! Ian Campbell
2008-08-14 10:41 ` Peter Zijlstra
2008-08-14 13:06 ` Hugh Dickins
2008-08-14 14:56 ` Ian Campbell
2008-08-14 17:42 ` Hugh Dickins
2008-08-14 17:38 ` Jeremy Fitzhardinge [this message]
2008-08-14 19:33 ` Jeremy Fitzhardinge
2008-08-14 21:03 ` Hugh Dickins
2008-08-14 22:04 ` Jeremy Fitzhardinge
2008-08-14 22:48 ` Markus Armbruster
2008-08-17 12:09 ` Jaya Kumar
2008-08-17 14:00 ` zhang wenjie
2008-08-14 23:13 ` Johannes Weiner
2008-08-15 0:00 ` Hugh Dickins
2008-08-17 16:19 ` Ian Campbell
2008-08-18 1:32 ` Nick Piggin
2008-08-18 7:54 ` Ian Campbell
2008-08-18 8:04 ` Peter Zijlstra
2008-08-18 8:05 ` Nick Piggin
2008-08-18 8:22 ` Jaya Kumar
-- strict thread matches above, loose matches on Subject: below --
2008-08-17 3:37 zhang wenjie
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=48A46D98.1010607@goop.org \
--to=jeremy@goop.org \
--cc=armbru@redhat.com \
--cc=hugh@veritas.com \
--cc=ijc@hellion.org.uk \
--cc=kel@otaku42.de \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox