From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG] Page allocation failures with newest kernels
Date: Tue, 31 May 2016 14:15:20 +0100 [thread overview]
Message-ID: <20160531131520.GI24936@arm.com> (raw)
In-Reply-To: <60e8df74202e40b28a4d53dbc7fd0b22@IL-EXCH02.marvell.com>
On Tue, May 31, 2016 at 01:10:44PM +0000, Yehuda Yitschak wrote:
> During some of the stress tests we also came across a different warning
> from the arm64 page management code
> It looks like a race is detected between HW and SW marking a bit in the PTE
A72 (which I believe is the CPU in that SoC) is a v8.0 CPU and therefore
doesn't have hardware DBM.
> Not sure it's really related but I thought it might give a clue on the issue
> http://pastebin.com/ASv19vZP
There have been a few patches from Catalin to fix up the hardware DBM
patches, so it might be worth trying to reproduce this failure with a
more recent kernel. I doubt this is related to the allocation failures,
however.
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Yehuda Yitschak <yehuday@marvell.com>
Cc: "Marcin Wojtas" <mw@semihalf.com>,
"Robin Murphy" <robin.murphy@arm.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Lior Amsalem" <alior@marvell.com>,
"Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Grzegorz Jaszczyk" <jaz@semihalf.com>,
"Nadav Haklai" <nadavh@marvell.com>,
"Tomasz Nowicki" <tn@semihalf.com>,
"Gregory Clément" <gregory.clement@free-electrons.com>
Subject: Re: [BUG] Page allocation failures with newest kernels
Date: Tue, 31 May 2016 14:15:20 +0100 [thread overview]
Message-ID: <20160531131520.GI24936@arm.com> (raw)
In-Reply-To: <60e8df74202e40b28a4d53dbc7fd0b22@IL-EXCH02.marvell.com>
On Tue, May 31, 2016 at 01:10:44PM +0000, Yehuda Yitschak wrote:
> During some of the stress tests we also came across a different warning
> from the arm64 page management code
> It looks like a race is detected between HW and SW marking a bit in the PTE
A72 (which I believe is the CPU in that SoC) is a v8.0 CPU and therefore
doesn't have hardware DBM.
> Not sure it's really related but I thought it might give a clue on the issue
> http://pastebin.com/ASv19vZP
There have been a few patches from Catalin to fix up the hardware DBM
patches, so it might be worth trying to reproduce this failure with a
more recent kernel. I doubt this is related to the allocation failures,
however.
Will
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Yehuda Yitschak <yehuday@marvell.com>
Cc: "Marcin Wojtas" <mw@semihalf.com>,
"Robin Murphy" <robin.murphy@arm.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Lior Amsalem" <alior@marvell.com>,
"Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Grzegorz Jaszczyk" <jaz@semihalf.com>,
"Nadav Haklai" <nadavh@marvell.com>,
"Tomasz Nowicki" <tn@semihalf.com>,
"Gregory Clément" <gregory.clement@free-electrons.com>
Subject: Re: [BUG] Page allocation failures with newest kernels
Date: Tue, 31 May 2016 14:15:20 +0100 [thread overview]
Message-ID: <20160531131520.GI24936@arm.com> (raw)
In-Reply-To: <60e8df74202e40b28a4d53dbc7fd0b22@IL-EXCH02.marvell.com>
On Tue, May 31, 2016 at 01:10:44PM +0000, Yehuda Yitschak wrote:
> During some of the stress tests we also came across a different warning
> from the arm64 page management code
> It looks like a race is detected between HW and SW marking a bit in the PTE
A72 (which I believe is the CPU in that SoC) is a v8.0 CPU and therefore
doesn't have hardware DBM.
> Not sure it's really related but I thought it might give a clue on the issue
> http://pastebin.com/ASv19vZP
There have been a few patches from Catalin to fix up the hardware DBM
patches, so it might be worth trying to reproduce this failure with a
more recent kernel. I doubt this is related to the allocation failures,
however.
Will
next prev parent reply other threads:[~2016-05-31 13:15 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 3:02 [BUG] Page allocation failures with newest kernels Marcin Wojtas
2016-05-31 3:02 ` Marcin Wojtas
2016-05-31 3:02 ` Marcin Wojtas
2016-05-31 10:17 ` Robin Murphy
2016-05-31 10:17 ` Robin Murphy
2016-05-31 10:17 ` Robin Murphy
2016-05-31 10:29 ` Marcin Wojtas
2016-05-31 10:29 ` Marcin Wojtas
2016-05-31 10:29 ` Marcin Wojtas
2016-05-31 13:10 ` Yehuda Yitschak
2016-05-31 13:10 ` Yehuda Yitschak
2016-05-31 13:10 ` Yehuda Yitschak
2016-05-31 13:15 ` Will Deacon [this message]
2016-05-31 13:15 ` Will Deacon
2016-05-31 13:15 ` Will Deacon
2016-06-02 5:48 ` Marcin Wojtas
2016-06-02 5:48 ` Marcin Wojtas
2016-06-02 5:48 ` Marcin Wojtas
2016-06-02 13:52 ` Mel Gorman
2016-06-02 13:52 ` Mel Gorman
2016-06-02 13:52 ` Mel Gorman
2016-06-02 19:01 ` Marcin Wojtas
2016-06-02 19:01 ` Marcin Wojtas
2016-06-02 19:01 ` Marcin Wojtas
2016-06-03 9:53 ` Mel Gorman
2016-06-03 9:53 ` Mel Gorman
2016-06-03 9:53 ` Mel Gorman
2016-06-03 11:57 ` Marcin Wojtas
2016-06-03 11:57 ` Marcin Wojtas
2016-06-03 11:57 ` Marcin Wojtas
2016-06-03 12:36 ` Mel Gorman
2016-06-03 12:36 ` Mel Gorman
2016-06-03 12:36 ` Mel Gorman
2016-06-07 17:36 ` Marcin Wojtas
2016-06-07 17:36 ` Marcin Wojtas
2016-06-07 17:36 ` Marcin Wojtas
2016-06-08 10:09 ` Mel Gorman
2016-06-08 10:09 ` Mel Gorman
2016-06-08 10:09 ` Mel Gorman
2016-06-09 18:13 ` Marcin Wojtas
2016-06-09 18:13 ` Marcin Wojtas
2016-06-09 18:13 ` Marcin Wojtas
2016-06-10 16:08 ` Marcin Wojtas
2016-06-10 16:08 ` Marcin Wojtas
2016-06-10 16:08 ` Marcin Wojtas
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=20160531131520.GI24936@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.