From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM64: kernel oops in 4.4-rc4+
Date: Tue, 8 Dec 2015 10:51:52 +0000 [thread overview]
Message-ID: <20151208105152.GB19612@arm.com> (raw)
In-Reply-To: <20151208103013.GA19612@arm.com>
On Tue, Dec 08, 2015 at 10:30:13AM +0000, Will Deacon wrote:
> On Tue, Dec 08, 2015 at 02:30:33PM +0800, Ming Lei wrote:
> > The attached kernel oops can be triggered immediately after
> > running the following command on APM Mustang:
> >
> > $stress-ng --all 8 -t 10m
> >
> > [1] kernel oops log
> > stress-ng: info: [5220] 5 failures reached, aborting stress process
> > [ 265.782659] kernel BUG at ./arch/arm64/include/asm/pgtable.h:282!
>
> Yikes, this means we're replacing a writable pte with a clean pte, so
> there's a potential race w/ hardware DBM.
>
> Could you dump pte and *ptep please?
I tried running this on my Juno and pretty quickly saw the OOM killer
coming in. Perhaps, in your case, pte is a swap entry and its confusing
the checks (so pte_dirty/pte_young are looking at random bits of the
file offset)?
Anyway, I'll wait for you to dump those values.
Will
next prev parent reply other threads:[~2015-12-08 10:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 6:30 ARM64: kernel oops in 4.4-rc4+ Ming Lei
2015-12-08 10:30 ` Will Deacon
2015-12-08 10:51 ` Will Deacon [this message]
2015-12-08 12:06 ` Catalin Marinas
2015-12-08 13:08 ` Ming Lei
2015-12-08 13:49 ` Will Deacon
2015-12-08 16:08 ` Catalin Marinas
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=20151208105152.GB19612@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 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.