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

[Xen-devel] crash can't analyze memory dumpfile of Xen

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] crash can't analyze memory dumpfile of Xen
From: Yuji Shimada <shimada-yxb@xxxxxxxxxxxxxxx>
Date: Wed, 03 Sep 2008 15:42:05 +0900
Delivery-date: Tue, 02 Sep 2008 23:43:22 -0700
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/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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I used the following tools to debug Xen.

  xen-3.3-unstable(changeset 17917)
  kexec-tools 2.0.0
  makedumpfile-1.2.8
  crash 4.0-6.3

Extraction of the memory dumpfile was completed normally. 
And I executed the following command to analyze memory dumpfile of Xen.

    # crash /boot/xen-syms-3.3-unstable dumpfile.core

The following errors occurred.

-------------------------------------------
    crash: invalid kernel virtual address:0
    type:"note_buf_t or crash_note_t"
    WARNING: cannot fill note core.

    crash: cannot read elf note core.
-------------------------------------------

I would like to ask some comments why these errors occurred.

I did the following steps:

 1.Boot Xen with the following Dom0 option. 
     "crashkernel=128M@64M"
   And 2nd kernel is loaded by kexec.

 2.On Dom0 Linux, carry out crash dump.
     # echo c > /sys/sysrq-trigger
 
 3.On 2nd kernel, extract memory dumpfile.
     # makedumpfile -E -X /proc/vmcore dumpfile.core

 4.Reboot Xen and execute the following command.
   And the above errors occurred.
     # crash /boot/xen-syms-3.3-unstable dumpfile.core

I can read the same memory dumpfile by crash command with no error to
debug vmlinux.

Thanks,

--
Yuji Shimada

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

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