From: Mike Galbraith <efault@gmx.de>
To: Adam Borowski <kilobyte@angband.pl>
Cc: kvm <kvm@vger.kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: 5.0-rc1 KVM inspired "BUG: Bad page state in process" spew
Date: Wed, 09 Jan 2019 16:03:16 +0100 [thread overview]
Message-ID: <1547046196.31155.1.camel@gmx.de> (raw)
In-Reply-To: <20190109144257.erwh52326ucgc5tw@angband.pl>
On Wed, 2019-01-09 at 15:42 +0100, Adam Borowski wrote:
> On Wed, Jan 09, 2019 at 06:38:58AM +0100, Mike Galbraith wrote:
> > KVM seems to be busted in master ATM. All I have to do to have host
> > start screaming and maybe exploding (if the guest doesn't do so first)
> > is to try to install a (obese in this case) kernel over nfs mount of
> > the host in a guest.
> >
> > Kernel producing the spew below is 3bd6e94, config attached.
>
> I get same, except that the BUGs were preceded by a bunch of warnings,
Yeah, I was in too much of a rush...
> > homer: # grep BUG: /netconsole.log
> > [ 1531.909703] BUG: Bad page state in process X pfn:100491
> > [ 1531.958141] BUG: Bad page state in process systemd-journal pfn:100412
> > [ 1532.662359] BUG: Bad page state in process X pfn:10043f
> > [ 1532.664033] BUG: Bad page state in process X pfn:10044d
> > [ 1532.686433] BUG: Bad page state in process systemd-journal pfn:1027b0
>
> the first one being:
>
> Jan 9 00:41:22 umbar kernel: [74122.790461] WARNING: CPU: 2 PID: 26769 at arch/x86/kvm/mmu.c:830 mmu_spte_clear_track_bits+0x7e/0x100
...I also get oodles of those.
-Mike
next prev parent reply other threads:[~2019-01-09 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 5:38 5.0-rc1 KVM inspired "BUG: Bad page state in process" spew Mike Galbraith
2019-01-09 14:42 ` Adam Borowski
2019-01-09 15:03 ` Mike Galbraith [this message]
2019-01-09 19:26 ` Sean Christopherson
2019-01-12 6:43 ` Mike Galbraith
2019-01-14 15:46 ` Sean Christopherson
2019-01-14 17:42 ` Mike Galbraith
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=1547046196.31155.1.camel@gmx.de \
--to=efault@gmx.de \
--cc=kilobyte@angband.pl \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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