From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Andre Przywara <andre.przywara@arm.com>,
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: Wed, 16 Dec 2015 16:43:52 +0100 [thread overview]
Message-ID: <1885710.UNGYhDGGcI@wuerfel> (raw)
In-Reply-To: <56717B6F.2040008@arm.com>
On Wednesday 16 December 2015 14:55:43 Andre Przywara wrote:
> Using the plain multi_v7_defconfig (which doesn't have LPAE and makes me
> loose half of the RAM on that box) didn't show the bug so far.
> One of the effects of turning on LPAE is that dma_addr_t and phys_addr_t
> turn to 64-bit, with long, int and void* still being 32-bit. Can you
> think of any issues that could be related to that?
>
Another difference between the platforms is highmem. On Midway,
almost all of RAM is highmem, which needs a lot of special handling
that we don't need on platform with less RAM.
To rule out both of highmem and LPAE, it might be interesting to
test again on Midway with CONFIG_HIGHMEM and CONFIG_LPAE disabled.
This will limit the RAM to 768MB, but if the bug still shows up,
you know it's something else.
Arnd
next prev parent reply other threads:[~2015-12-16 15:44 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 [this message]
2015-12-17 3:55 ` Ming Lei
2015-12-17 9:28 ` Andre Przywara
2015-12-17 9:46 ` Arnd Bergmann
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=1885710.UNGYhDGGcI@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).