From mboxrd@z Thu Jan 1 00:00:00 1970 From: dyoung@redhat.com (Dave Young) Date: Tue, 26 Dec 2017 09:35:17 +0800 Subject: arm64 crashkernel fails to boot on acpi-only machines due to ACPI regions being no longer mapped as NOMAP In-Reply-To: <20171226013217.GA2119@dhcp-128-65.nay.redhat.com> References: <20171219060927.GH28046@linaro.org> <20171221103440.GJ28046@linaro.org> <20171222083308.cy3vwlyhig22q5ee@fireball> <20171225032500.GA8877@linaro.org> <20171226013217.GA2119@dhcp-128-65.nay.redhat.com> Message-ID: <20171226013517.GA2186@dhcp-128-65.nay.redhat.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org [snip] > > > Well, we may be able to change pr_warn() to pr_warn_once() here, but > > > I hope that adding "numa=off" to kernel command line should also work. > > > > Hmm, adding "numa=off" to crashkernel bootargs works, and TBH it was > > my initial thought process as well, but I am not sure if this will > > cause any regressions on aarch64 systems which use crashdump feature. > > It should be fine since we use numa=off by default for all other arches > ie. x86, ppc64 and s390. Actually disabling numa in kdump kernel can save > mm component memory usage. > Forgot to say I means in RHEL and Fedora we use numa=off for kdump..