From: Mike Galbraith <efault@gmx.de>
To: Takashi Iwai <tiwai@suse.de>, Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 4.13-rc7: WARNING at arch/x86/kvm/mmu.c:717 (and a crash thereafter)
Date: Mon, 28 Aug 2017 16:41:15 +0200 [thread overview]
Message-ID: <1503931275.5701.7.camel@gmx.de> (raw)
In-Reply-To: <1503928376.5709.11.camel@gmx.de>
On Mon, 2017-08-28 at 15:52 +0200, Mike Galbraith wrote:
> On Mon, 2017-08-28 at 14:26 +0200, Takashi Iwai wrote:
> > Hi,
> >
> > I seem to get a kernel warning when running KVM on Dell desktop with
> > IvyBridge like below. As you can see, a bad page BUG is triggered
> > after that, too. The problem is not triggered always, but it happens
> > occasionally.
> >
> > I haven't seen this on 4.13-rc4 at all, and IIRC, it started happening
> > since rc5. So this might be a regression at rc5. But, as it doesn't
> > happen always, I can't be 100% sure about it, and it's quite difficult
> > to bisect (the test case isn't reliable), unfortunately.
> >
> > Any hint for further debugging this?
>
> Maybe a way to make failure more likely. This is an RT kernel, but
> trying to build a fat kernel over NFS from a KVM clone of my
> workstation (full topology, half of ram) didn't survive one build.
Bah, plain master in guest/host survived.
-Mike
prev parent reply other threads:[~2017-08-28 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 12:26 4.13-rc7: WARNING at arch/x86/kvm/mmu.c:717 (and a crash thereafter) Takashi Iwai
2017-08-28 13:06 ` Adam Borowski
2017-08-28 13:15 ` Takashi Iwai
2017-08-28 13:29 ` Richard Weinberger
2017-08-28 13:52 ` Mike Galbraith
2017-08-28 14:41 ` Mike Galbraith [this message]
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=1503931275.5701.7.camel@gmx.de \
--to=efault@gmx.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=tiwai@suse.de \
--cc=x86@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