From: Jeremy Fitzhardinge <jeremy@goop.org>
To: AP Xen <apxeng@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Ubuntu 10.04 stuck in detect_extended_topology()
Date: Wed, 09 Jun 2010 15:41:26 -0700 [thread overview]
Message-ID: <4C101896.8090608@goop.org> (raw)
In-Reply-To: <006c01cb081e$74908320$5db18960$@com>
On 06/09/2010 02:55 PM, AP Xen wrote:
>
> I am running Xen packaged with CentOS 5.4 and trying to install Ubuntu
> 10.04 as an HVM guest.
>
>
>
> xen_major : 3
>
> xen_minor : 1
>
> xen_extra : .2-164.11.1.el5
>
>
>
> After sprinkling the kernel with printks, I am seeing that it is stuck
> in the function detect_extended_topology() in the following loop:
>
> <snip>
>
> sub_index = 1;
>
> do {
>
> cpuid_count(0xb, sub_index, &eax, &ebx, &ecx, &edx);
>
> printk("%s: after cpuid_count %d\n", __FUNCTION__,
> sub_index);
>
>
>
> /*
>
> * Check for the Core type in the implemented sub leaves.
>
> */
>
> if (LEAFB_SUBTYPE(ecx) == CORE_TYPE) {
>
> core_level_siblings = LEVEL_MAX_SIBLINGS(ebx);
>
> core_plus_mask_width = BITS_SHIFT_NEXT_LEVEL(eax);
>
> break;
>
> }
>
>
>
> sub_index++;
>
> } while (LEAFB_SUBTYPE(ecx) != INVALID_TYPE);
>
> <snip>
>
>
>
> The ECX leaf subtype never returns CORE_TYPE or INVALID_TYPE. So think
> I might be running in to a bug / quirk in the CPUID handling code in
> Xen packaged with CentOS 5.4. Is there a work around for it? Maybe
> specifying something in the cpuid option in the config file.
>
What's the host cpu type? You should be able to completely disable the
extended topology leaf (0xb) with the cpuid= directive in the config file.
J
next prev parent reply other threads:[~2010-06-09 22:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 21:55 Ubuntu 10.04 stuck in detect_extended_topology() AP Xen
2010-06-09 22:41 ` Jeremy Fitzhardinge [this message]
2010-06-10 0:29 ` AP Xen
2010-06-10 0:54 ` Jeremy Fitzhardinge
2010-06-10 6:01 ` Pasi Kärkkäinen
2010-06-10 16:53 ` AP Xen
2010-07-02 13:48 ` Andrew Jones
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=4C101896.8090608@goop.org \
--to=jeremy@goop.org \
--cc=apxeng@gmail.com \
--cc=xen-devel@lists.xensource.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 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.