All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: Jan Beulich <jbeulich@suse.com>, xen-devel@lists.xen.org
Subject: Re: Xen-unstable: Bisected Host boot failure on AMD Phenom
Date: Thu, 2 Mar 2017 17:38:46 +0000	[thread overview]
Message-ID: <23971dc3-7ce3-077b-e1d6-e61dea0d47ef@citrix.com> (raw)
In-Reply-To: <dbf70ff4-33d7-31a4-33d7-97fc9469a7d3@eikelenboom.it>

On 02/03/17 17:29, Sander Eikelenboom wrote:
> On 02/03/17 15:55, Andrew Cooper wrote:
>> On 02/03/17 14:42, Sander Eikelenboom wrote:
>>> Hi Andrew / Jan,
>>>
>>> While testing current xen-unstable staging i ran into my host rebooting in early kernel boot. 
>>> Bisection has turned up:
>>>     5cecf60f439e828f4bc0d2a368ced9a73b130cb7 is the first bad commit
>>>     Author: Andrew Cooper <andrew.cooper3@citrix.com>
>>>     Date:   Fri Feb 17 17:10:50 2017 +0000
>>>
>>>     x86/cpuid: Handle leaf 0x1 in guest_cpuid()
>>>
>>> Hardware is a AMD phenom x6.
>>> Below is the output of serial console of a failed boot.
>> Hmm.  Sorry for breaking this (although my AMD servers are booting fine).
> No problem, it is the staging branch of the unstable tree anyway ;-)
>
>> It is unfortunately not entirely obvious what Linux is objecting to, and
>> must be related to something visible in the emulated view.
>>
>> Does this delta make any difference?
> Yes it does, boots fine with this patch applied, thanks !

That is bad though. :s

It means that something in dom0 has an aversion to my attempt to lie
less about the topology.

Do you mind checking whether

res->b = cpuid_ebx(0x1) & 0xff00ffffu;

causes is to break again?

That will confirm whether the breakage is to do with Logical Processors
Per Package (which I suspect is the case), or the APIC ID field (which
has always been unstable in the past).

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-03-02 17:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-02 14:42 Xen-unstable: Bisected Host boot failure on AMD Phenom Sander Eikelenboom
2017-03-02 14:55 ` Andrew Cooper
2017-03-02 17:29   ` Sander Eikelenboom
2017-03-02 17:38     ` Andrew Cooper [this message]
2017-03-02 18:25       ` Sander Eikelenboom
2017-03-02 18:29         ` Andrew Cooper
2017-03-02 18:51           ` Sander Eikelenboom
2017-03-02 18:56             ` Andrew Cooper
2017-03-02 19:15               ` Boris Ostrovsky
2017-03-02 19:17                 ` Andrew Cooper
2017-03-02 19:28                   ` Sander Eikelenboom
2017-03-02 19:36                     ` Andrew Cooper
2017-03-02 19:33                   ` Boris Ostrovsky
2017-03-02 20:02                     ` Andrew Cooper

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=23971dc3-7ce3-077b-e1d6-e61dea0d47ef@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=linux@eikelenboom.it \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.