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: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64
From: "Puthiyaparambil, Aravindh" <aravindh.puthiyaparambil@xxxxxxxxxx>
Date: Tue, 9 Aug 2005 22:35:36 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Davis, Jason" <jason.davis@xxxxxxxxxx>, "Magolan, John F" <John.Magolan@xxxxxxxxxx>, "Subrahmanian, Raj" <raj.subrahmanian@xxxxxxxxxx>, "Vessey, Bruce A" <Bruce.Vessey@xxxxxxxxxx>
Delivery-date: Wed, 10 Aug 2005 02:42:50 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcWdAZeo7cFZVA22QViz6u3TsjtZZwAR8SiA
Thread-topic: [Xen-devel] Unknown interrupt on x86_64 Xen on ES7000 x86_64
> > It looks like the page fault/interrupt is happening in map_alloc().
> > see that alloc_heap_pages() and map_alloc() are called before
> > 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 found out that the "Unknown Interrupt" issue happens only when debug
is turned on in Xen (verbose & debug=y in Rules.mk). When debug is
turned off the systems dies in the middle of "Scrubbing Free RAM". I
have attached a serial output of the boot messages
(es7000_x86_64_nodebug_6065.txt). This could be Bugzilla #147.
Should I be still trying to find the faulting address in the debug case?

> > 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.

Please see the attached dell_x86_64_timer.txt file.


Attachment: dell_x86_64_timer.txt
Description: dell_x86_64_timer.txt

Attachment: es7000_x86_64_nodebug_6065.txt
Description: es7000_x86_64_nodebug_6065.txt

Xen-devel mailing list