From: Arnd Bergmann <arnd@arndb.de>
To: Andre Przywara <andre.przywara@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
Ming Lei <ming.lei@canonical.com>, Jens Axboe <axboe@kernel.dk>,
Rob Herring <rob.herring@linaro.org>,
Eric Auger <eric.auger@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-block@vger.kernel.org
Subject: Re: block layer bug with 4.4-rc3+
Date: Thu, 17 Dec 2015 10:46:49 +0100 [thread overview]
Message-ID: <4730511.HtLlToyPh4@wuerfel> (raw)
In-Reply-To: <56728044.7090906@arm.com>
On Thursday 17 December 2015 09:28:36 Andre Przywara wrote:
>
> So it was running for almost a day without LPAE now, but with highmem,
> and the bug didn't show up. So for the time being I'd avoid another test
> run without highmem, as LPAE alone is sufficient to trigger it.
There is clearly no need to try with both LPAE and HIGHMEM disabled, that
would almost certainly not bring the bug back.
A more useful test might be to try Cubieboard with LPAE enabled, possibly
with LPAE and no highmem, to rule out the possibility that the bug just
gets less likely when you have less highmem.
> Also it seems that CONFIG_HIGHMEM is selected by MULTI_V7, so I can't
> configure it out for this box, but would have to restrict memory to
> 768M, I guess.
>
> Next I will try some tracing as Ming suggested.
It should not be selected by MULTI_V7, the only 'select HIGHMEM' statement
I see is for ARCH_OMAP2PLUS_TYPICAL, and that is not a mandatory option
for anything, it just turns on a few things that are generally useful.
Arnd
next prev parent reply other threads:[~2015-12-17 9:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 11:05 block layer bug with 4.4-rc3+ Andre Przywara
2015-12-15 11:54 ` Ming Lei
2015-12-15 12:23 ` Andre Przywara
2015-12-15 13:39 ` Ming Lei
2015-12-16 14:55 ` Andre Przywara
2015-12-16 15:43 ` Arnd Bergmann
2015-12-17 3:55 ` Ming Lei
2015-12-17 9:28 ` Andre Przywara
2015-12-17 9:46 ` Arnd Bergmann [this message]
2015-12-17 3:52 ` Ming Lei
2015-12-17 12:32 ` Andre Przywara
2015-12-17 12:33 ` Andre Przywara
2015-12-18 8:36 ` Ming Lei
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=4730511.HtLlToyPh4@wuerfel \
--to=arnd@arndb.de \
--cc=andre.przywara@arm.com \
--cc=axboe@kernel.dk \
--cc=eric.auger@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=rob.herring@linaro.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).