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] Help Debugging Xen Crash

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Help Debugging Xen Crash
From: George Dunlap <dunlapg@xxxxxxxxx>
Date: Tue, 15 Jun 2010 14:38:05 +0100
Cc: Kathy Hadley <Kathy.Hadley@xxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 15 Jun 2010 06:38:53 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received :in-reply-to:references:date:x-google-sender-auth:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=Yrmeos+SN6IJd8rUJiA8PWQIvpGkiFsAIeAxdXfX+OQ=; b=WqMA1Jo4ab2ofRejuqj/BUqNIqlurr6Sasvkbf0HOCX8X4R1MCn3xV9C8PLZ3Cx1n4 dvyPHlQD97WKBCbAjH54sP3NRM/VoRaDUo/rgBv+nfXrKTDnOz6xXFtwnCv22A9de8Wc Zk1mQE9LRK7RWpNnBw9++tdJtDOijn0nwIlN8=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=VtOFPs0gePya2SnZEXIEpCTTKZuqMh9/Qx6b3XkfunVSRMf6BPs5zvSI2w6XKY6VJv YsgCN2RG8aG+ZrYf+UxMIKmxO6aaTpMCcJijtN9N8ZsUuEI9dN1NcgBl46h4gsYPxYx0 usyLLrlUOmtiFfmAAJcKZg4sqeq0SFmWpw7A8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C83D3DEE.178BB%keir.fraser@xxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <D3E384327F5C6D48AADCEA84160B7D7301470CC8@xxxxxxxxxxxxxxx> <C83D3DEE.178BB%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
The following thread has a discussion of setting up a serial console
for debugging, if you need it:

http://www.mailinglistarchive.com/html/xen-devel@xxxxxxxxxxxxxxxxxxx/2009-05/msg00004.html

 -George

On Tue, Jun 15, 2010 at 2:25 PM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:
> Connect a serial line and collect the hypervisor's debug console output.
> You'll probably get a crash dump when the machine reboots itself.
>
>  -- Keir
>
> On 15/06/2010 14:13, "Kathy Hadley" <Kathy.Hadley@xxxxxxxxxxxxxxx> wrote:
>
>> Greetings,
>>   I am trying to debug a Xen crash and need some help.  When I am attempting
>> to use the (relatively) new adjust_global scheduler callback function, the
>> machine reboots (this may be due to other changes I have made in the
>> hypervisor to modify DornerWorks¹ ARINC 653 scheduler to work with CPU 
>> pools).
>> I have enabled xend/xenstored tracing, but the log files do not contain
>> anything useful.  I have used gdb to trace to the point where the hypercall 
>> is
>> made from Dom0 to the hypervisor, but do not know how to proceed from here. 
>>  I
>> have read about using kdb to debug the hypervisor, but I am a bit confused.
>> It looks as though kdb (in http://xenbits.xensource.com/ext/debuggers.hg) is
>> integrated into a particular branch of Xen, which is not kept synchronized
>> with the current version of xen-unstable.  Can I use kdb with any version of
>> Xen?  If so, how?  What files do I need to download and what should I do to
>> build them?  Or does someone have other suggestions?
>>
>>   Thank you,
>> Kathy Hadley
>> DornerWorks, Ltd.
>>
>>
>>
>>
>>
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

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

<Prev in Thread] Current Thread [Next in Thread>