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] Xen & Transmeta (from xen-users)

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Xen & Transmeta (from xen-users)
From: "Carl Holtje ;021;vcsg6;" <cwh0803@xxxxxxxxxx>
Date: Wed, 1 Jun 2005 10:08:11 -0400 (EDT)
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 01 Jun 2005 14:08:26 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <6959b40101aa41470b346b8b0bf6a9c0@xxxxxxxxxxxx>
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: <Pine.GSO.4.58.0505241113400.16688@xxxxxxxxxxxxxxxx> <Pine.LNX.4.58.0505240925480.9339@xxxxxxxxxxxxxxx> <Pine.GSO.4.58.0505241128360.16688@xxxxxxxxxxxxxxxx> <Pine.LNX.4.58.0505240931540.9339@xxxxxxxxxxxxxxx> <4293878E.9090903@xxxxxxx> <Pine.GSO.4.58.0505251429370.20392@xxxxxxxxxxxxxxxx> <ecd2cfedbbd92a7bf208569b1e5fbeb1@xxxxxxxxxxxx> <Pine.GSO.4.58.0505261651450.20484@xxxxxxxxxxxxxxxx> <cd23d293fb9a3a92f4811bc17bfcca22@xxxxxxxxxxxx> <Pine.GSO.4.58.0505311542020.26084@xxxxxxxxxxxxxxxx> <6897e54f155e86bc8e55e2f33e69f51d@xxxxxxxxxxxx> <Pine.GSO.4.58.0506010917490.28466@xxxxxxxxxxxxxxxx> <6959b40101aa41470b346b8b0bf6a9c0@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, 1 Jun 2005, Keir Fraser wrote:

>
> On 1 Jun 2005, at 14:24, Carl Holtje ;021;vcsg6; wrote:
>
> > I can get you a register dump, the location the stack trace starts at
> > (ESP), the call trace from that point, and what it's determined to be
> > the
> > faulty linear address -- is this enough?
>
> Yes. The stack trace is the least useful bit, although it's sometime
> useful for working out what arguments were passed to functions in the
> backtrace.

Excellent!

The sysms file is available at
[http://www.cs.rit.edu/~cwh0803/xen/xen-2.0-testing-syms].

A note about the symbols -- there are strings I've added for debug/tracing
purposes, most of which are of the form ' -> XXX'...

The debug dump is as follows (let me know if you need more):

========== BEGIN DEBUG DUMP ==========
Initializing CPU#0
ACPI: RSDP (v000 OID_00                        ) @ 0x000e4010
CPU:            0
EIP:            0808:[<fc5349c0>]
EFLAGS:         00210086
eax:  ffff27c0  ebx:  0e7fb7c0  ecx:  00000000  edx:  00000000
esi:  fc4e4010  edi:  00000024  ebp:  0e7fb7c0  esp:  fc503c20
ds: 0810  es: 0810  fs: 0810  gs: 0810  ss: 0810

Stack Trace from ESP=fc503c20:
{NOT DISPLAYED}

Call Trace from ESP=fc503c20: [<fc525520>] [<fc5237f0>] [<fc50400c>]
Faulting linear address might be ffff27c4

CPU0 FATAL TRAP 14 (page fault), ERROR_CODE 0009, IN INTERRUPT CONTEXT
=========== END DEBUG DUMP ===========

Please let me know if you need anything else or want me to try stuff..

Thanks for your help!

Carl


- --

"There are 10 types of people in the world: Those who understand binary
and those that don't."


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel