From: Thomas Gleixner <tglx@linutronix.de>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
Ingo Molnar <mingo@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
kernel-build-reports@lists.linaro.org,
Matt Hart <matthew.hart@linaro.org>,
stable@vger.kernel.org
Subject: Re: stable/linux-4.14.y boot: 108 boots: 0 failed, 107 passed with 1 conflict (v4.14.11)
Date: Wed, 3 Jan 2018 10:48:23 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1801031046270.1957@nanos> (raw)
In-Reply-To: <de09d482-9cf1-e695-ee57-f91e2277c8de@collabora.com>
On Wed, 3 Jan 2018, Guillaume Tucker wrote:
> On 03/01/18 03:11, kernelci.org bot wrote:
> > stable/linux-4.14.y boot: 108 boots: 0 failed, 107 passed with 1 conflict
> > (v4.14.11)
> >
> > Full Boot Summary:
> > https://kernelci.org/boot/all/job/stable/branch/linux-4.14.y/kernel/v4.14.11/
> > Full Build Summary:
> > https://kernelci.org/build/stable/branch/linux-4.14.y/kernel/v4.14.11/
> >
> > Tree: stable
> > Branch: linux-4.14.y
> > Git Describe: v4.14.11
> > Git Commit: 0d59679df5b53755c00ea0292df696f97bfc950d
> > Git URL:
> > http://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
> > Tested: 59 unique boards, 23 SoC families, 16 builds out of 185
> >
> > Boot Regressions Detected:
> >
> > x86:
> >
> > x86_64_defconfig:
> > qemu:
> > lab-mhart: new failure (last pass: v4.14.10)
> >
> > Conflicting Boot Failure Detected: (These likely are not failures as other
> > labs are reporting PASS. Needs review.)
> >
> > x86:
> >
> > x86_64_defconfig:
> > qemu:
> > lab-mhart: FAIL
> > lab-collabora: PASS
>
> Well, it turns out this is not exactly a conflict as there's a
> subtle difference between the qemu devices in lab-mhart and in
> lab-collabora. The ones in lab-collabora are configured to use
> KVM, and it looks like the ones in lab-mhart aren't.
>
> So this job with KVM enabled passes in lab-collabora:
>
> https://lava.collabora.co.uk/scheduler/job/1032358
>
> but it fails if I tell LAVA (qemu) to disable KVM:
>
> https://lava.collabora.co.uk/scheduler/job/1032359
>
> with the same panic as in lab-mhart. It seems like it's failing
> to return from an interrupt:
>
> http://lava.streamtester.net/scheduler/job/87308
>
> [ 2.678828] ? native_iret+0x7/0x7
> [ 2.679208] WARNING: can't dereference iret registers at 00000000ffc66068
> for ip page_fault+0x11/0x60
>
> This triggered an automated bisection on kernelci.org, please see
> the results below.
>
> I may run another bisection with this config enabled earlier in
> the history to track down the actual change in the code that
> introduced the issue, let me know if it's worth doing.
No, because before that commit not all pieces are in place.
Can you please try the failing kernel with pti=off on the command line?
I'll start a test instance here as well.
Thanks,
tglx
next prev parent reply other threads:[~2018-01-03 9:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5a4c49c8.50b91c0a.2b051.322e@mx.google.com>
2018-01-03 9:44 ` stable/linux-4.14.y boot: 108 boots: 0 failed, 107 passed with 1 conflict (v4.14.11) Guillaume Tucker
2018-01-03 9:48 ` Thomas Gleixner [this message]
2018-01-03 9:55 ` Guillaume Tucker
2018-01-03 10:36 ` Thomas Gleixner
2018-01-03 11:14 ` Paolo Bonzini
2018-01-03 19:55 ` Thomas Gleixner
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=alpine.DEB.2.20.1801031046270.1957@nanos \
--to=tglx@linutronix.de \
--cc=dave.hansen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=guillaume.tucker@collabora.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=matthew.hart@linaro.org \
--cc=mingo@kernel.org \
--cc=stable@vger.kernel.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