[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] SLES10 Big smp HPET domain_crash() c/s 13161

  • To: "Woller, Thomas" <thomas.woller@xxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Fri, 29 Dec 2006 10:08:09 +0000
  • Delivery-date: Fri, 29 Dec 2006 02:07:56 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Accq0SL2Dj7aZnwpTKGdoklUY7dbnAAYBqi3
  • Thread-topic: [Xen-devel] SLES10 Big smp HPET domain_crash() c/s 13161

On 28/12/06 10:40 pm, "Woller, Thomas" <thomas.woller@xxxxxxx> wrote:

> I am seeing a domain_crash in the HVM HPET code when booting a SLES10
> Big SMP kernel on a 64bit hypervisor.
> pae=1, apic=1, acpi=1, memory=512, vcpus=1, cpus="0"
> There are 4 cores in the system, and Dom0 is SMP with vcpus on all cores
> (any core, not pinned).
> This same SLES10 Big SMP kernel boots fine on a 64bit hv with a 3.0.3
> base of code, i.e. prior to hvm hpet additions.  I tried booting this
> guest kernel with hpet=disable but did not make a difference, and still
> crashed at hpet.c:374. Testing is on 13161 changeset from xen-unstable.

This should be easily reproducible. I'll take a look -- I expect the hpet
code just needs some 'loosening' in what it accepts.

 -- Keir

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.