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] Re: crash with Xen dom0 image from kdump

Hi, Kazuo

Great!
I'll try to use your tool and Horms patch.

Best Regards,

Akio Takebe

>Hi,
>
>I tried to use crash (http://people.redhat.com/~anderson/) with 
>x86_32 xen domain0 image, which is extracted from whole-machine dump
>image made by kexec/kdump.
>
>'kmem -i' cause some error, but other almost all commands I tried seem
>to work well.
>This may be some helps for xen development and troubleshooting.
>
>regards,
>
>---------------------------------------------------------------------------
>(... get vmcore with kexec/kdump ...)
>$ ./dom0cut_x86_32.py -txen -f -dvmcore -odom0core -xxen-syms -vvmlinux-2.6
>.16
>$ crash vmlinux dom0core
>
>crash 4.0-2.24
>Copyright (C) 2002, 2003, 2004, 2005, 2006  Red Hat, Inc.
>Copyright (C) 2004, 2005, 2006  IBM Corporation
>Copyright (C) 1999-2006  Hewlett-Packard Co
>Copyright (C) 2005  Fujitsu Limited
>Copyright (C) 2005  NEC Corporation
>Copyright (C) 1999, 2002  Silicon Graphics, Inc.
>Copyright (C) 1999, 2000, 2001, 2002  Mission Critical Linux, Inc.
>This program is free software, covered by the GNU General Public License,
>and you are welcome to change it and/or distribute copies of it under
>certain conditions.  Enter "help copying" to see the conditions.
>This program has absolutely no warranty.  Enter "help warranty" for details.
> 
>GNU gdb 6.1
>Copyright 2004 Free Software Foundation, Inc.
>GDB is free software, covered by the GNU General Public License, and you are
>welcome to change it and/or distribute copies of it under certain conditions.
>Type "show copying" to see the conditions.
>There is absolutely no warranty for GDB.  Type "show warranty" for details.
>This GDB was configured as "i686-pc-linux-gnu"...
>
>
>      KERNEL: vmlinux                           
>    DUMPFILE: dom0core
>        CPUS: 2
>        DATE: Wed May 24 18:52:04 2006
>      UPTIME: 00:04:32
>LOAD AVERAGE: 0.46, 0.10, 0.03
>       TASKS: 26
>    NODENAME: (none)
>     RELEASE: 2.6.16.13-xen
>     VERSION: #3 SMP Wed May 24 10:08:29 JST 2006
>     MACHINE: i686  (866 Mhz)
>      MEMORY: 887.4 MB
>       PANIC: "SysRq : Trigger a crashdump"
>         PID: 163
>     COMMAND: "echo"
>        TASK: c024e050  [THREAD_INFO: f3f0e000]
>         CPU: 0
>       STATE: TASK_RUNNING (SYSRQ)
>
>crash> bt
>PID: 163    TASK: c024e050  CPU: 0   COMMAND: "echo"
> #0 [f3f0ffbc] ret_from_fork at c01050a8
> #1 [f3f0ffb8] system_call at c01051d2
>    EAX: 00000004  EBX: 00000001  ECX: b7e8c000  EDX: 00000002 
>    DS:  007b      ESI: 00000002  ES:  007b      EDI: 00000000 
>    SS:  007b      ESP: bf8ad750  EBP: bf8ad774 
>    CS:  0073      EIP: b7f35a88  ERR: 00000004  EFLAGS: 00000246 
>crash> kmem -i
>              PAGES        TOTAL      PERCENTAGE
> TOTAL MEM   225145     879.5 MB         ----
>      FREE   216192     844.5 MB   96% of TOTAL MEM
>      USED     8953        35 MB    3% of TOTAL MEM
>    SHARED   216640     846.2 MB   96% of TOTAL MEM
>kmem: invalid kernel virtual address: 0  type: "inode buffer"
>---------------------------------------------------------------------------
>-- 
>Kazuo Moriwaka <moriwaka@xxxxxxxxxxxxx>

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

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