All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ky Srinivasan" <ksrinivasan@novell.com>
To: xen-devel@lists.xensource.com
Subject: hardware support
Date: Mon, 08 May 2006 09:23:36 -0600	[thread overview]
Message-ID: <445F2A37.E57C.0030.0@novell.com> (raw)

We have had some problems bringing up SLES10/Xen on DL360 box (dual
processor). The Compaq boxes have this notion of "auto" mode for
MPS/APIC to deal with buggy OSes and under this setting (which is the
default setting), vanilla Linux (2.6.16) comes up on this box in UP mode
since it finds the local APIC disabled in bios. However, the xen based
kernel tries to come up MP and fails in a non-intuitive way by  hitting
a BUG in the hypervisor code. Following is the stack trace of the xen
based kernel:

[<ff10f8d6>] alloc_vcpu+0x36/0x120
  [<ff1518c0>] smp_prepare_cpus+0x460/0xd30
  [<ff132fcd>] intel_p6_mcheck_init+0xbd/0xe0
  [<ff1555b4>] get_mtrr_state+0xf4/0x110
  [<ff1508f1>] __start_xen+0x5d1/0x9e0
  [<ff123270>] new_tlbflush_clock_period+0x0/0x90
  [<ff10015a>] start_paging+0x52/0x54
  CPU0 FATAL TRAP 6 (invalid opcode), ERROR_CODE 0000, IN INTERRUPT
CONTEXT.
  System shutting down--need manual reset.

As opposed to the vanilla linux kernel (that fails to see the local
apic), xen sees the local apic (incorrectly) and fails to bring up the
secondary CPUs and finally takes the FATAL TRAP as described in the
trace above.

If however, the bios setting is changed to Full APIC mode, both the
vanilla linux kernel and the xen based kernel boot correctly. I wanted
to know if others have seen similar problems. Also, is somebody looking
at addressing  these kinds of issues?

Regards,

K. Y

             reply	other threads:[~2006-05-08 15:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-08 15:23 Ky Srinivasan [this message]
2006-05-08 15:53 ` hardware support Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2012-09-14  0:35 Littlefield, Tyler
2006-11-01  8:07 李增强
2005-03-26 23:05 sten
2005-03-26 23:22 ` Mark Williamson
2001-02-23 10:23 Hardware support Ray
2001-02-23 18:35 ` Keith M Wesolowski

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=445F2A37.E57C.0030.0@novell.com \
    --to=ksrinivasan@novell.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.