linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Taku Izumi <izumi.taku@jp.fujitsu.com>,
	Tony Luck <tony.luck@intel.com>, Mel Gorman <mel@csn.ul.ie>,
	Xishi Qiu <qiuxishi@huawei.com>,
	Dave Hansen <dave.hansen@intel.com>,
	Matt Fleming <matt@codeblueprint.co.uk>,
	Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: kernel-build-reports@lists.linaro.org,
	linux-next@vger.kernel.org, Kevin.Hilman@linaro.org,
	Tyler.Baker@linaro.org, linux-arm-kernel@lists.infradead.org,
	Russell King <linux@arm.linux.org.uk>
Subject: Widespread boot failures on ARM due to "mm/page_alloc.c: calculate zone_start_pfn at zone_spanned_pages_in_node()"
Date: Mon, 4 Jan 2016 22:42:33 +0000	[thread overview]
Message-ID: <20160104224233.GU16023@sirena.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]

Since 20151231 -next has been failing to boot on a wide range of ARM
platforms in the kernelci.org boot tests[1].  Doing bisections with
Arndale and BeagleBone Black identifies 904769ac82ebf (mm/page_alloc.c:
calculate zone_start_pfn at zone_spanned_pages_in_node()) from the akpm
tree as the first broken commit[2,3].  An example bootlog from the
failure is:

   http://storage.kernelci.org/next/next-20151231/arm-multi_v7_defconfig/lab-cambridge/boot-exynos5250-arndale.html

which shows no output on the console once we start the kernel, a brief
sampling of failing boards suggests this is the normal failure mode.
x86 and arm64 targets seem fine (juno shows up as failing but the boot
log seems fine so it's probably a false positive, Mustang was failing
already) and there are a small number of ARM platforms that boot.  I've
not yet had any time to investigate further than that (including trying
a revert of that commit), sorry.

[1] http://kernelci.org/boot/all/job/next/kernel/next-20151231/
[2] https://ci.linaro.org/view/people/job/tbaker-boot-bisect-bot/135/console
[3] https://ci.linaro.org/view/people/job/tbaker-boot-bisect-bot/136/console

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

             reply	other threads:[~2016-01-04 22:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-04 22:42 Mark Brown [this message]
2016-01-04 23:09 ` Widespread boot failures on ARM due to "mm/page_alloc.c: calculate zone_start_pfn at zone_spanned_pages_in_node()" Andrew Morton
2016-01-04 23:55   ` Mark Brown
2016-01-05  0:35     ` Andrew Morton
2016-01-05  0:49       ` Stephen Rothwell
2016-01-05  5:47         ` Stephen Rothwell
2016-01-05  5:49           ` Andrew Morton
2016-01-05 11:45       ` Mark Brown
2016-01-05 12:21         ` Sudeep Holla
2016-01-05 19:24           ` Mark Brown
2016-01-05 19:59           ` Steve Capper
2016-01-06 10:32             ` Sudeep Holla
2016-01-06 15:56             ` Steve Capper
2016-01-06  0:22 ` Guenter Roeck

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=20160104224233.GU16023@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=Kevin.Hilman@linaro.org \
    --cc=Tyler.Baker@linaro.org \
    --cc=akpm@linux-foundation.org \
    --cc=dave.hansen@intel.com \
    --cc=izumi.taku@jp.fujitsu.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=matt@codeblueprint.co.uk \
    --cc=mel@csn.ul.ie \
    --cc=qiuxishi@huawei.com \
    --cc=tony.luck@intel.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).