From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S965982AbbLPPoo (ORCPT <rfc822;w@1wt.eu>);
	Wed, 16 Dec 2015 10:44:44 -0500
Received: from mout.kundenserver.de ([212.227.126.130]:58286 "EHLO
	mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1752442AbbLPPoX (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Wed, 16 Dec 2015 10:44:23 -0500
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
Message-ID: <1885710.UNGYhDGGcI@wuerfel>
User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; )
In-Reply-To: <56717B6F.2040008@arm.com>
References: <566FF3ED.1000503@arm.com> <CACVXFVN3w0Y_8k3TiKoGytbayXiB+mRhgDn-OueV2+e93i=4AQ@mail.gmail.com> <56717B6F.2040008@arm.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-Provags-ID: V03:K0:3BClooogyyBGc7m5B7iEWtKF5GFSD6K8FWRIOx6HJZfX+cAgh8T
 wt5D7Rlft7VF3Odl3fQOfahV+Dvh82NezP1HVeNUMd5n/ezOTZYnBDRONBoybsVEfvFgdkZ
 h4v9lmvmQjy6EDwVRoNN6Or0vp7gq5FPhrAhZTeKXCnTnJR44k56NB98qUVZ+tLUp4Npe5/
 dPNRS/QtJVXUATsPHuVLQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:xkAtTFHUz9w=:zPdpjlDLEEbTVuM3M5Ep5J
 69ls14vchRnjNMorn/c6LlFP6/Pg4y4e+shwEu8Krk/TsrFGZs9cJ9yODWKspRs3nE12nmAg9
 4ACaPj8v1IW7sGYzKnGqFAlBrZpIEsWQuABP7Hg+ET8mmbL335RGO6xHlmw3FhfaVB1UOo2JD
 xvqT7+ggJsbwT5Y73hd0Sxlo4erQIM3dKLLnxiCqDobohrNNnhJa920Fp3wujpsykWs23QbR4
 f310HejpTD5pQKS4shz2le3Pi+BpRZQdolGUQGq2gMGPrAkohvtxM6cIytGX4XSHj7WxtIHBO
 uiPP3WoCfOQyxBbvqXv7Xzow1Vuwj902j9UHpidTI2Usf4PkShgHI5U6A+2aSLjAVd1vDEbFJ
 PxG21N77UeKHNCegxvdekuJNlwoRTRm2ceiPIwfmjtFdBKlprVg21Eak59EPOeu+Io87i4JWQ
 rJ3qolNIeSKegZcR1J4RsPC2Ek9/BrSTlhWpU1y2QDd/WPYPIlXyPIQG4h1wAbXn3rzIno6vQ
 nH2fxZGK3ImR6jmWR4LMKrupXPsGFay6wJG9gLmv/DLNMJhV72kHdTZYbNXcHq7MjI3637lCK
 uSku1B2NRsyZiJ65ZCSDM14FkKFPeHG6UxnHtsR/dtYFeE3E3/ATf/us3XJpVead5WzMkrRle
 iNWihjMkt0JAFSL/i/rDFEMbLsBsrPnbdMSCFRRcdKfV5o15Pc+NLEnjXR5WgNgmj/55dUGe/
 beUBMYfTUGLPNwVz
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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