public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: Juergen Gross <jgross@suse.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION][x86] Commit f5b2831d65 cause boot failure in VMware ESXi 5.1 guest
Date: Mon, 29 Dec 2014 09:18:39 +0800	[thread overview]
Message-ID: <54A0ABEF.1000106@cn.fujitsu.com> (raw)
In-Reply-To: <549EB95F.9090209@suse.com>


-------- Original Message --------
Subject: Re: [REGRESSION][x86] Commit f5b2831d65 cause boot failure in 
VMware ESXi 5.1 guest
From: Juergen Gross <jgross@suse.com>
To: Qu Wenruo <quwenruo@cn.fujitsu.com>
Date: 2014年12月27日 21:51
> On 12/26/2014 02:57 AM, Qu Wenruo wrote:
>> Hi all,
>>
>> When testing v3.19-rc1 kernel(in fact, try to test), the kernel itself
>> fail to boot on VMware ESXi 5.1 guest.
>> The boot failure is quite easy to describe, only one line is output:
>> "Probing EDD (edd=off to disable)...ok"
>>
>> No other output(including warning/bug_on/backtrace or whatever) and the
>> guest just hangs.
>> It's OK on v3.18, so it's a regression.
>>
>> Bisect points to the following commit:
>> commit f5b2831d654167d77da8afbef4d2584897b12d0c
>> Author: Juergen Gross <jgross@suse.com>
>> Date:   Mon Nov 3 14:02:02 2014 +0100
>>
>>      x86: Respect PAT bit when copying pte values between large and
>> normal pages
>>
>>      The PAT bit in the ptes is not moved to the correct position when
>>      copying page protection attributes between entries of different 
>> sized
>>      pages. Translate the ptes according to their page size.
>>
>>
>> I have also created the kernel BZ report:
>> https://bugzilla.kernel.org/show_bug.cgi?id=90321
>>
>> Hopes this can be resolved in next rc.
>
> As the same issue has been reported with VMWare workstation which was
> related to an error in the PAT MSR emulation of VMWare, I guess this
> will be the same problem. I've already sent a patch.
>
> You should be able to boot with the "nopat" kernel option.
>
>
> Juergen
Thanks for the explanation. Again the closed source blob to blame.

Anyway, the nopat option works.

Great thanks
Qu

      reply	other threads:[~2014-12-29  1:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-26  1:57 [REGRESSION][x86] Commit f5b2831d65 cause boot failure in VMware ESXi 5.1 guest Qu Wenruo
2014-12-26  3:21 ` Peter Hurley
2014-12-27 13:51 ` Juergen Gross
2014-12-29  1:18   ` Qu Wenruo [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=54A0ABEF.1000106@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.com \
    --cc=jgross@suse.com \
    --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