From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: joserz@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org
Cc: paulus@samba.org, mpe@ellerman.id.au, oohall@gmail.com
Subject: Re: KVM guests freeze under upstream kernel
Date: Thu, 20 Jul 2017 09:42:50 +1000 [thread overview]
Message-ID: <1500507770.3350.41.camel@kernel.crashing.org> (raw)
In-Reply-To: <20170719194634.GA1222@pacoca>
On Wed, 2017-07-19 at 16:46 -0300, joserz@linux.vnet.ibm.com wrote:
> Hello!
>
> We're not able to boot any KVM guest using upstream kernel (cb8c65ccff7f77d0285f1b126c72d37b2572c865 - 4.13.0-rc1+).
> After reaching the SLOF initial counting, the guest simply freezes:
Can you send our .config ?
> SLOF
> **********************************************************************
> QEMU Starting
> Build Date = Mar 3 2017 13:29:19
> FW Version = git-66d250ef0fd06bb8
> Press "s" to enter Open Firmware.
>
> C0360
>
> After bisecting I found the commit:
>
> https://github.com/torvalds/linux/commit/ebd3119
>
> powerpc/mm: Add devmap support for ppc64
>
> Add support for the devmap bit on PTEs and PMDs for PPC64 Book3S. This
> is used to differentiate device backed memory from transparent huge
> pages since they are handled in more or less the same manner by the core
> mm code.
>
> Reverting the commit and rebuilding 4.13.0-rc1+ was enough to make a workaround.
> But I'll need some help from you guys in order to solve it.
>
> Thanks!
>
> Jose Ziviani
next prev parent reply other threads:[~2017-07-19 23:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 19:46 KVM guests freeze under upstream kernel joserz
2017-07-19 22:31 ` Michael Ellerman
2017-07-19 23:42 ` Benjamin Herrenschmidt [this message]
2017-07-20 3:02 ` joserz
2017-07-20 5:21 ` Paul Mackerras
2017-07-21 1:18 ` joserz
2017-07-26 13:18 ` joserz
2017-07-27 3:14 ` Michael Ellerman
2017-07-27 6:56 ` Suraj Jitindar Singh
2017-07-27 11:10 ` Michael Ellerman
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=1500507770.3350.41.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=joserz@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=oohall@gmail.com \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).