From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: Internal error: Oops - BUG() / kvm boot race - arm64 kpti patchset related
Date: Wed, 28 Feb 2018 16:18:33 +0000 [thread overview]
Message-ID: <20180228161833.GB22612@arm.com> (raw)
In-Reply-To: <20180228161256.GA31013@akinoame>
On Wed, Feb 28, 2018 at 05:12:56PM +0100, Paolo Pisati wrote:
> On Wed, Feb 28, 2018 at 04:07:35PM +0000, Will Deacon wrote:
> > On Wed, Feb 28, 2018 at 04:45:23PM +0100, Paolo Pisati wrote:
> > > Reproducible on 4.16-rc3 and 4.4.20 using defconfig - the failure it's
> > > intermittent, but i could reproduce it 100% if i boot loop the kvm instance
> > > (it usually shows up in less than 10 iterations but i tested 32 boots before
> > > marking it good).
> >
> > [...]
> >
> > > Anything else i can do to help debug this?
> >
> > If you could share the crash log, that would be helpful.
>
> Oops log here:
> https://launchpadlibrarian.net/358687166/submission_2018-02-26T14.58.17.996524.html#9-1-log
The patch that Ard linked to should resolve that particular crash.
I see this is a 4.13-based kernel. Is the source tree available anywhere?
Will
next prev parent reply other threads:[~2018-02-28 16:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 15:45 Internal error: Oops - BUG() / kvm boot race - arm64 kpti patchset related Paolo Pisati
2018-02-28 15:51 ` Ard Biesheuvel
2018-02-28 16:13 ` Paolo Pisati
2018-02-28 15:51 ` Marc Zyngier
2018-02-28 16:15 ` Paolo Pisati
2018-02-28 16:07 ` Will Deacon
2018-02-28 16:12 ` Paolo Pisati
2018-02-28 16:18 ` Will Deacon [this message]
2018-02-28 16:25 ` Paolo Pisati
2018-02-28 16:18 ` Mark Rutland
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=20180228161833.GB22612@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.