This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64

To: "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>
Subject: Re: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Mon, 8 Aug 2005 19:33:10 +0100
Cc: "Davis, Jason" <jason.davis@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, "Magolan, John F" <John.Magolan@xxxxxxxxxx>, "Vessey, Bruce A" <Bruce.Vessey@xxxxxxxxxx>, "Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>
Delivery-date: Mon, 08 Aug 2005 18:37:22 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <EF8D308BE33AF54D8934DF26520252D30261F750@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <EF8D308BE33AF54D8934DF26520252D30261F750@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 8 Aug 2005, at 19:10, Puthiyaparambil, Aravindh wrote:

I am getting an "Unknown Interrupt" message with changeset 6050 on the
ES7000 x86_64 box running x86_64 SLES9 SP2 RC3. The system dies after
that. Any idea why this could be happening?
I am not sure if this is related to

Definitely a different bug, but this one shouldn;t be hard to track down. Probably you are talking a page fault very early during boot. I'd suggest working out where this occurs by adding printk statements (probably paging_init() in arch/x86/x86_64/mm.c would be a good place to start).

When I tried the same changeset on my Dell PowerEdge 470 box I am seeing
something totally different and very scary :-)
Is anybody else seeing this?

I think the HPET on your system is not working for some reason! Please try removing the call to init_hpet() from init_platform_timer() in arch/x86/time.c -- just fall back to init_pit(). You should then see 'Platform timer is xxxMHz PIT' rather than 'Platform timer is xxxMHz HPET' in Xen's boot log.

If that fixes your problem (very likely) then we can try and work out why the HPET is failing to work. Perhaps see whether native Linux successfully uses it, for example.

 -- Keir

Xen-devel mailing list