From: Guenter Roeck <linux@roeck-us.net>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: Andi Kleen <ak@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
David Woodhouse <dwmw@amazon.co.uk>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
kernel-build-reports@lists.linaro.org, stable@vger.kernel.org,
Matt Hart <matthew.hart@linaro.org>
Subject: Re: stable/linux-4.4.y boot: 124 boots: 3 failed, 117 passed with 2 offline, 1 untried/unknown, 1 conflict (v4.4.151)
Date: Fri, 24 Aug 2018 09:30:22 -0700 [thread overview]
Message-ID: <20180824163022.GA5551@roeck-us.net> (raw)
In-Reply-To: <d119ece0-7cb8-cfbe-1806-4f49cecdd516@collabora.com>
Hi Guillaume,
On Fri, Aug 24, 2018 at 08:32:07AM +0100, Guillaume Tucker wrote:
> On 22/08/18 14:51, kernelci.org bot wrote:
> >stable/linux-4.4.y boot: 124 boots: 3 failed, 117 passed with 2 offline, 1 untried/unknown, 1 conflict (v4.4.151)
> >
> >Full Boot Summary: https://kernelci.org/boot/all/job/stable/branch/linux-4.4.y/kernel/v4.4.151/
> >Full Build Summary: https://kernelci.org/build/stable/branch/linux-4.4.y/kernel/v4.4.151/
> >
> >Tree: stable
> >Branch: linux-4.4.y
> >Git Describe: v4.4.151
> >Git Commit: 78f654f6cce3442937b8c7eb4b640357871363c1
> >Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> >Tested: 43 unique boards, 20 SoC families, 22 builds out of 191
> >
> >Boot Regressions Detected:
> [...]
> >x86:
> >
> > defconfig+kvm_guest:
> > x86-x5-z8350:
> > lab-mhart: failing since 6 days (last pass: v4.4.147 - first fail: v4.4.148)
> >
> > x86_64_defconfig:
> > x86-x5-z8350:
> > lab-mhart: failing since 6 days (last pass: v4.4.147 - first fail: v4.4.148)
>
> We've had a couple of automated boot bisections pointing at the
> same commit on an x86 Atom x5-Z8350 platform (AAEON UP-CHT01),
> please see details below. The issue seems to have started with
> v4.4.148.
>
Can you test if a backport of upstream commit d367cef0a7f0 ("x86/mm/pat:
Fix boot crash when 1GB pages are not supported by the CPU") fixes
the problem ? It doesn't apply cleanly, but the conflict is easy to
resolve.
Thanks,
Guenter
next prev parent reply other threads:[~2018-08-24 20:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5b7d6a46.1c69fb81.4c530.6a24@mx.google.com>
2018-08-24 7:32 ` stable/linux-4.4.y boot: 124 boots: 3 failed, 117 passed with 2 offline, 1 untried/unknown, 1 conflict (v4.4.151) Guillaume Tucker
2018-08-24 16:30 ` Guenter Roeck [this message]
2018-08-24 17:41 ` Guenter Roeck
2018-08-24 20:17 ` Guillaume Tucker
2018-08-24 20:35 ` Guenter Roeck
2018-08-24 20:50 ` Andi Kleen
2018-08-24 21:18 ` Guenter Roeck
2018-08-24 20:43 ` Andi Kleen
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=20180824163022.GA5551@roeck-us.net \
--to=linux@roeck-us.net \
--cc=ak@linux.intel.com \
--cc=dwmw@amazon.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=guillaume.tucker@collabora.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=matthew.hart@linaro.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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