WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Failure to get memory for GATT table, again

To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Failure to get memory for GATT table, again
From: Jacob Gorm Hansen <jacobg@xxxxxxx>
Date: Tue, 01 Feb 2005 00:23:29 -0800
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 01 Feb 2005 08:26:51 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D123623@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D123623@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0 (X11/20050116)
Ian Pratt wrote:
I seem to have narroved the problem down to the function direct_remap_area_pages() which fails on an MMU update.

Xen tells me about this, in:

(XEN) (file=/mnt/hda3/home/jacobg/xeno-unstable.bk/xen/include/asm/mm.h, line=157) Error pfn 0003ff40: ed=fc599260, sd=fc5996a0, caf=80000002, taf=f0000001


You're trying to do this in dom0, right? Do you have any other domains
running?

Yes, only dom0 is running.

If so, use the 'q' debug key to find out the domain pointers. It might
be helpful to add a show_registers after the DPRINTK so that we can see
the call trace.

I added the following:

struct xen_regs *regs = (struct xen_regs *)get_execution_context();
show_registers(regs);

and the output is now:

(XEN) (file=/mnt/hda3/home/jacobg/xeno-unstable.bk/xen/include/asm/mm.h, line=157) Error pfn 0003ff40: ed=fc599260, sd=fc5996a0, caf=80000002, taf=f0000001
(XEN) CPU:    0
(XEN) EIP:    0061:[<c011418a>]
(XEN) EFLAGS: 00001206
(XEN) eax: 00000001   ebx: f2265a0c   ecx: 00000021   edx: 00000000
(XEN) esi: 00000021   edi: 00020000   ebp: f8880000   esp: f22659e8
(XEN) ds: 007b   es: 007b   fs: 0000   gs: 0000   ss: 0069
(XEN) Stack trace from ESP=fc503fe4:
(XEN) f22659e8 00000069 0000007b 0000007b 00000000 00000000 fc5963e0
(XEN) Call Trace from ESP=fc503fe4:


Hope this helps.

Jacob


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel