From: Chris Friesen <chris.friesen@windriver.com>
To: Huaitong Han <oenhan@gmail.com>, lkml <linux-kernel@vger.kernel.org>
Cc: <linux-mm@kvack.org>
Subject: Re: "swap_free: Bad swap file entry" and "BUG: Bad page map in process" but no swap configured
Date: Tue, 21 Nov 2017 09:45:27 -0600 [thread overview]
Message-ID: <5A144A17.8010909@windriver.com> (raw)
In-Reply-To: <CAAuJbeJPw9AeuDrO=q8Y+VkUoq1XQLWcbEYVQXywiP5nR=qaVg@mail.gmail.com>
I think we tracked it down to the "eptad" kernel option on Broadwell processors.
Setting "kvm-intel.eptad=0" turned it off.
Chris
On 11/20/2017 03:07 AM, Huaitong Han wrote:
> Hi, Chris
>
> I have met the same issue too, did you have found out the root cause ?
>
> Thanks a lot.
>
> Huaitong Han
>
>
> 2016-10-12 0:02 GMT+08:00 Chris Friesen <chris.friesen@windriver.com>:
>> On 10/08/2016 02:05 AM, Hillf Danton wrote:
>>>
>>> On Friday, October 07, 2016 5:01 AM Chris Friesen
>>>>
>>>>
>>>> I have Linux host running as a kvm hypervisor. It's running CentOS. (So
>>>> the
>>>> kernel is based on 3.10 but with loads of stuff backported by RedHat.) I
>>>> realize this is not a mainline kernel, but I was wondering if anyone is
>>>> aware of
>>>> similar issues that had been fixed in mainline.
>>>>
>>> Hey, dunno if you're looking for commit
>>> 6dec97dc929 ("mm: move_ptes -- Set soft dirty bit depending on pte
>>> type")
>>> Hillf
>>
>>
>> CONFIG_MEM_SOFT_DIRTY doesn't exist in our kernel so I don't think this is
>> the issue. Thanks for the suggestion though.
>>
>> Chris
prev parent reply other threads:[~2017-11-21 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 21:01 Chris Friesen
2016-10-08 8:05 ` Hillf Danton
2016-10-11 16:02 ` Chris Friesen
2017-11-20 9:07 ` Huaitong Han
2017-11-21 15:45 ` Chris Friesen [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=5A144A17.8010909@windriver.com \
--to=chris.friesen@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oenhan@gmail.com \
/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
Powered by JetHome