From: Dan Williams <dan.j.williams@intel.com>
To: Qin Dehua <qindehua@gmail.com>
Cc: Russell King <rmk@arm.linux.org.uk>,
linux-kernel@vger.kernel.org, santosh.shilimkar@ti.com,
neilb@suse.de
Subject: Re: PROBLEM: ARM-dma-mapping-fix-for-speculative-prefetching cause OOPS
Date: Thu, 30 Jun 2011 11:02:54 -0700 [thread overview]
Message-ID: <BANLkTimo18w5yuE4jtATPvbgENCL04LMpA@mail.gmail.com> (raw)
In-Reply-To: <20110630112804.GA21481@flint.arm.linux.org.uk>
On Thu, Jun 30, 2011 at 4:28 AM, Russell King <rmk@arm.linux.org.uk> wrote:
> On Thu, Jun 30, 2011 at 07:16:24PM +0800, Qin Dehua wrote:
>> Commit 2ffe2da3e follows v2.6.32, the message is from kernel build on
>> commit 2ffe2da3e.
>>
>> The config has CONFIG_BUG=y and CONFIG_DEBUG_BUGVERBOSE=y, but the
>> message is Oops, not BUG() macro, so they don't have line number.
>
> In that case, the raid5 code contains an explicit NULL pointer
> dereference which isn't a BUG() - the code line disassembles to:
>
> 0: ebfff1bc bl 0xffffc6f8
> 4: e28dd044 add sp, sp, #68 ; 0x44
> 8: e8bd8ff0 pop {r4, r5, r6, r7, r8, r9, sl, fp, pc}
> c: e3a03000 mov r3, #0 ; 0x0
> 10: e5833000 str r3, [r3] <=== faulting instruction
>
> So, if you're saying that's not a BUG(), then I don't know what it is
> and I'm afraid I can't help because the oops doesn't make any sense
> to me.
>
QinDehua,
Can you rebuild with CONFIG_DEBUG_INFO=y, reproduce the crash and then
send the output of:
$ gdb drivers/md/raid5.o
(gdb) li *(raid5d+0x580)
(gdb) li *(__release_stripe+0x1e4)
etc...
...those offsets might change so just grab whatever "PC is at "
reports in the oops.
--
Dan
next prev parent reply other threads:[~2011-06-30 18:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-30 4:09 PROBLEM: ARM-dma-mapping-fix-for-speculative-prefetching cause OOPS Qin Dehua
2011-06-30 7:43 ` Russell King
2011-06-30 11:16 ` Qin Dehua
2011-06-30 11:28 ` Russell King
2011-06-30 18:02 ` Dan Williams [this message]
2011-07-01 4:54 ` Qin Dehua
2011-07-07 9:39 ` Russell King
2011-07-08 4:38 ` Qin Dehua
2011-07-08 8:07 ` Russell King
2011-07-08 17:32 ` Russell King
2011-07-08 20:13 ` Dan Williams
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=BANLkTimo18w5yuE4jtATPvbgENCL04LMpA@mail.gmail.com \
--to=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=qindehua@gmail.com \
--cc=rmk@arm.linux.org.uk \
--cc=santosh.shilimkar@ti.com \
/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;
as well as URLs for NNTP newsgroup(s).