From: Will Deacon <will.deacon@arm.com>
To: Robert Richter <robert.richter@cavium.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Hanjun Guo <hanjun.guo@linaro.org>,
Yisheng Xie <xieyisheng1@huawei.com>,
James Morse <james.morse@arm.com>
Subject: Re: [PATCH 2/2] arm64: mm: enable CONFIG_HOLES_IN_ZONE for NUMA
Date: Fri, 6 Jan 2017 12:03:40 +0000 [thread overview]
Message-ID: <20170106120339.GA20726@arm.com> (raw)
In-Reply-To: <20170105194944.GY4930@rric.localdomain>
On Thu, Jan 05, 2017 at 08:49:44PM +0100, Robert Richter wrote:
> On 05.01.17 13:22:00, Robert Richter wrote:
> > On 05.01.17 12:08:20, Will Deacon wrote:
> > > I really can't see how the fix causes a crash, and I couldn't reproduce
> > > it on any of my boards, nor could any of the Linaro folk afaik. Are you
> > > definitely running mainline with just these two patches from Ard?
> >
> > Yes, just both patches applied. Various other solutions were working.
>
> I have retested the same kernel (v4.9 based) as before and now it
> boots fine including rtc-efi device registration (it was crashing
> there):
>
> rtc-efi rtc-efi: rtc core: registered rtc-efi as rtc0
>
> There could be a difference in firmware and mem setup, though I also
> downgraded the firmware to test it, but can't reproduce it anymore. I
> could reliable trigger the crash the first time.
>
> FTR the oops.
Hmm, I just can't help but think you were accidentally running with
additional patches when you saw this oops previously. For example,
your log looks very similar to this one:
http://lists.infradead.org/pipermail/linux-arm-kernel/2016-December/473666.html
but then again, these crashes probably often look alike.
Will
next prev parent reply other threads:[~2017-01-06 12:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 9:11 [PATCH 0/2] arm64: numa: fix spurious BUG() on NOMAP regions Ard Biesheuvel
2016-12-14 9:11 ` [PATCH 1/2] mm: don't dereference struct page fields of invalid pages Ard Biesheuvel
2017-01-04 12:16 ` Will Deacon
2016-12-14 9:11 ` [PATCH 2/2] arm64: mm: enable CONFIG_HOLES_IN_ZONE for NUMA Ard Biesheuvel
2016-12-15 15:39 ` Robert Richter
2016-12-15 16:07 ` Ard Biesheuvel
2016-12-16 17:10 ` Robert Richter
2016-12-16 1:57 ` Hanjun Guo
2016-12-16 17:14 ` Robert Richter
2017-01-04 13:28 ` Will Deacon
2017-01-04 13:50 ` Ard Biesheuvel
2017-01-04 14:02 ` Will Deacon
2017-01-05 11:24 ` Robert Richter
2017-01-05 12:08 ` Will Deacon
2017-01-05 12:22 ` Robert Richter
2017-01-05 19:49 ` Robert Richter
2017-01-06 12:03 ` Will Deacon [this message]
2017-01-06 12:22 ` Ard Biesheuvel
2017-02-06 13:36 ` Robert Richter
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=20170106120339.GA20726@arm.com \
--to=will.deacon@arm.com \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=hanjun.guo@linaro.org \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=robert.richter@cavium.com \
--cc=xieyisheng1@huawei.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).