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: Tue, 9 Aug 2005 08:35:15 +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: Tue, 09 Aug 2005 07:39:20 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <EF8D308BE33AF54D8934DF26520252D30261FB63@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: <EF8D308BE33AF54D8934DF26520252D30261FB63@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 8 Aug 2005, at 23:54, Puthiyaparambil, Aravindh wrote:

I put a few printks in paging_init and friends. This is the call tree
that I mapped out.

paging_init()->alloc_domheap_pages()->alloc_heap_pages()-> map_alloc()

It looks like the page fault/interrupt is happening in map_alloc(). I
see that alloc_heap_pages() and map_alloc() are called before without
any issues. Not sure why it is tripping up now. Any ideas?

Not really. Perhaps some part of the bitmap is not properly mapped? I think you'll have to add a bunch more tracing -- find out what address is actually faulting and work backwards to see why it's not mapped. If it looks like it should be valid then maybe look at the code that is intended to 1:1 map all RAM, in arch/x86/setup.c:__start_xen() (the code is wrapped in CONFIG_x86_64).

I tried that patch. The serial output now shows "Platform timer is
1.193MHz PIT" but that does not fix the problem. I am still getting
those fatal errors.

Enable the #if 0'ed code in arch/x86/time.c:local_time_calibration(). That should get us more diagnostics out.

 -- Keir

Xen-devel mailing list