From: Russell King <rmk@arm.linux.org.uk>
To: Qin Dehua <qindehua@gmail.com>
Cc: linux-kernel@vger.kernel.org, santosh.shilimkar@ti.com,
dan.j.williams@intel.com, neilb@suse.de
Subject: Re: PROBLEM: ARM-dma-mapping-fix-for-speculative-prefetching cause OOPS
Date: Thu, 30 Jun 2011 08:43:01 +0100 [thread overview]
Message-ID: <20110630074301.GC27959@flint.arm.linux.org.uk> (raw)
In-Reply-To: <BANLkTimfF3_R5VS4xOriGp+-3j-r7V0W0w@mail.gmail.com>
On Thu, Jun 30, 2011 at 12:09:15PM +0800, Qin Dehua wrote:
> The 2.6.38.8 Kernel make our IOP 341 XScale processor based RAID6 crashes.
>
> After doing a bisection, We found commit
> 2ffe2da3e71652d4f4cae19539b5c78c2a239136 cause the problem.
>
> That commit is only for ARMv6 and ARMv7 CPUs, so we revert it on
> 2.6.38.8 Kernel, and then our raid box runs OK.
>
> Following are some kernel messages when the system crashes:
>
> * The kernel config has CONFIG_ASYNC_PQ=y CONFIG_RAID6_PQ=y
These traces are from 2.6.32... And I assume have CONFIG_BUG unset
because you have no verbose bug reporting (it's not reporting the
file/line which is necessary to identify which BUG has been hit in
the raid code.)
Could you reproduce with CONFIG_BUG=y please?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2011-06-30 7:43 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 [this message]
2011-06-30 11:16 ` Qin Dehua
2011-06-30 11:28 ` Russell King
2011-06-30 18:02 ` Dan Williams
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=20110630074301.GC27959@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=qindehua@gmail.com \
--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).