From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM64: kernel panics in DABT in sys_msync path
Date: Tue, 26 Sep 2017 18:31:13 +0100 [thread overview]
Message-ID: <20170926173112.GA16650@arm.com> (raw)
In-Reply-To: <547ed590-3ab4-cc11-cbea-f587541d2b08@codeaurora.org>
Yury, Richard,
On Tue, Sep 26, 2017 at 08:23:35AM -0600, Ruigrok, Richard wrote:
> On 9/26/2017 4:23 AM, Will Deacon wrote:
> > On Mon, Sep 25, 2017 at 01:54:57PM -0600, Ruigrok, Richard wrote:
> >> I also found this issue with kernels from 4.11 through 4.13. In my tests, I
> >> found that it reproduces only with 4K page and Transparent Huge Pages. With 64K
> >> page I was not able to reproduce. RH also reported it here: https://
> >> bugzilla.redhat.com/show_bug.cgi?id=1491504 Linaro reported on the RPK kernel
> >> (4.12) on Centriq2400 and ThunderX
> >>
> >>
> >> https://bugs.linaro.org/show_bug.cgi?id=3191
> >>
> >> https://bugs.linaro.org/show_bug.cgi?id=3068.
> > These two aren't the same bug (that's a forward progress issue that we're
> > currently working on). I don't have permission to look at the redhat one,
> > but is it just an RCU stall or actually the Oops reported by Yury?
> >
> >> I was able to bisect down to a specific commit.
> > I think we're chasing two different things here, so not sure I trust the
> > bisect!
> >
> The RCU stall is side effect.? The issue I'm seeing has the same stack
> trace and same stimulus (rwtest).? Following are the details.
FWIW, I think I've worked out what's going on here and I should have a patch
tomorrow.
Will
next prev parent reply other threads:[~2017-09-26 17:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-24 21:36 ARM64: kernel panics in DABT in sys_msync path Yury Norov
2017-09-25 10:53 ` Will Deacon
2017-09-25 14:02 ` Yury Norov
2017-09-25 19:04 ` Yury Norov
2017-09-25 20:52 ` Ruigrok, Richard
[not found] ` <a3b714ae-97a5-8458-9bf7-140eeeebc4b9@codeaurora.org>
2017-09-26 10:23 ` Will Deacon
2017-09-26 11:54 ` Yury Norov
2017-09-26 14:23 ` Ruigrok, Richard
2017-09-26 17:31 ` Will Deacon [this message]
2017-09-27 15:50 ` Will Deacon
2017-09-27 18:00 ` Richard Ruigrok
2017-09-28 3:31 ` Richard Ruigrok
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=20170926173112.GA16650@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).