From: Mike Galbraith <efault@gmx.de>
To: kvm <kvm@vger.kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: 5.0-rc1 KVM inspired "BUG: Bad page state in process" spew
Date: Wed, 09 Jan 2019 06:38:58 +0100 [thread overview]
Message-ID: <1547012338.4926.11.camel@gmx.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 3355 bytes --]
Greetings,
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.
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
[ 1532.687704] BUG: Bad page state in process systemd-journal pfn:1027ba
[ 1532.689039] BUG: Bad page state in process systemd-journal pfn:1027de
[ 1532.694762] BUG: Bad page state in process systemd-journal pfn:102602
[ 1532.696337] BUG: Bad page state in process systemd-journal pfn:102726
[ 1533.086254] BUG: Bad page state in process CPU 0/KVM pfn:100a48
[ 1533.086869] BUG: Bad page state in process CPU 0/KVM pfn:100a49
[ 1533.087413] BUG: Bad page state in process CPU 0/KVM pfn:100a4a
[ 1533.087947] BUG: Bad page state in process CPU 0/KVM pfn:100a4b
[ 1533.088477] BUG: Bad page state in process CPU 0/KVM pfn:100a4c
[ 1533.089044] BUG: Bad page state in process CPU 0/KVM pfn:100a4d
[ 1533.089586] BUG: Bad page state in process CPU 0/KVM pfn:100a4e
[ 1533.090121] BUG: Bad page state in process CPU 0/KVM pfn:100a61
[ 1533.090657] BUG: Bad page state in process CPU 0/KVM pfn:100a62
[ 1533.091191] BUG: Bad page state in process CPU 0/KVM pfn:100a63
[ 1533.091739] BUG: Bad page state in process CPU 0/KVM pfn:100a64
[ 1533.092276] BUG: Bad page state in process CPU 0/KVM pfn:100a65
[ 1533.092814] BUG: Bad page state in process CPU 0/KVM pfn:100a66
[ 1533.093348] BUG: Bad page state in process CPU 0/KVM pfn:100a67
[ 1533.093940] BUG: Bad page state in process CPU 0/KVM pfn:1017e8
[ 1533.094512] BUG: Bad page state in process CPU 0/KVM pfn:1017e9
[ 1533.095049] BUG: Bad page state in process CPU 0/KVM pfn:1017ea
[ 1533.095585] BUG: Bad page state in process CPU 0/KVM pfn:1017eb
[ 1533.096120] BUG: Bad page state in process CPU 0/KVM pfn:1017ee
[ 1533.096679] BUG: Bad page state in process CPU 0/KVM pfn:101a20
[ 1533.097221] BUG: Bad page state in process CPU 0/KVM pfn:101a22
[ 1533.097757] BUG: Bad page state in process systemd-journal pfn:101ce4
[ 1533.098162] BUG: Bad page state in process systemd-journal pfn:101ce5
[ 1533.098535] BUG: Bad page state in process CPU 0/KVM pfn:101ce6
[ 1533.099075] BUG: Bad page state in process CPU 0/KVM pfn:101ce7
[ 1533.099667] BUG: Bad page state in process CPU 0/KVM pfn:1024cc
[ 1533.101840] BUG: Bad page state in process CPU 0/KVM pfn:1024e9
[ 1533.102379] BUG: Bad page state in process CPU 0/KVM pfn:1024ea
[ 1533.102935] BUG: Bad page state in process CPU 0/KVM pfn:1024eb
[ 1533.103516] BUG: Bad page state in process CPU 0/KVM pfn:102bc8
[ 1533.105771] BUG: Bad page state in process CPU 0/KVM pfn:102be0
[ 1533.106308] BUG: Bad page state in process CPU 0/KVM pfn:102be1
[ 1533.106875] BUG: Bad page state in process CPU 0/KVM pfn:102be2
[ 1533.107412] BUG: Bad page state in process CPU 0/KVM pfn:102be3
[ 1533.111166] BUG: Bad page state in process CPU 0/KVM pfn:102bee
[-- Attachment #2: config.xz --]
[-- Type: application/x-xz, Size: 39140 bytes --]
next reply other threads:[~2019-01-09 5:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 5:38 Mike Galbraith [this message]
2019-01-09 14:42 ` 5.0-rc1 KVM inspired "BUG: Bad page state in process" spew Adam Borowski
2019-01-09 15:03 ` Mike Galbraith
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=1547012338.4926.11.camel@gmx.de \
--to=efault@gmx.de \
--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