Re: [Crash-utility] The problems when running SuSE 12 on VirtualBox

Wednesday, 18 November 2015

By the way, perhaps there's an issue caused by running Xen inside VirtualBox?

----- Original Message -----
...

 ----- Original Message -----
 > Hi Dave,
 > 
 > So I try to execute "crash -d8 vmlinux-3.12.49-6-xen.gz" command:
 > 
 >  # crash -d8 vmlinux-3.12.49-6-xen.gz

 Hello Nan,

 Sorry, but I'm running out of ideas here.  You could try uncompressing
 the vmlinux-3.12.49-6-xen.gz file, but I'm guessing that it won't make
 a difference.

 Here is what the debug info shows:

 You are using the correct file, because /proc/version matches the
 linux_banner
 string in the vmlinux file, which it found using "/usr/bin/strings":

 > /proc/version:
 > Linux version 3.12.49-6-xen (geeko@buildhost) (gcc version 4.8.5 (SUSE
 > Linux) ) #1 SMP Mon Oct 26 16:05:37 UTC 2015 (11560c3)
 > /var/tmp/vmlinux-3.12.49-6-xen.gz_L3Bnwm:
 > Linux version 3.12.49-6-xen (geeko@buildhost) (gcc version 4.8.5 (SUSE
 >Linux) ) #1 SMP Mon Oct 26 16:05:37 UTC 2015 (11560c3)

 SUSE splits their vmlinux file into a stripped vmlinux-3.12.49-6-xen
 file and an associated vmlinux-3.12.49-6-xen.debug file.  That is
 supported by the crash utility; vmlinux-3.12.49-6-xen.debug was
 not found in the ./ (current) directory, nor in the ./.debug directory,
 but it was found in the the /usr/lib/debug/boot directory:

 > NOTE: gnu_debuglink file: vmlinux-3.12.49-6-xen.debug
 > crc32: 82102e72
 >  GETBUF(25 -> 1)
 > ./vmlinux-3.12.49-6-xen.debug: not readable/found
 > ./.debug/vmlinux-3.12.49-6-xen.debug: not readable/found
 > /usr/lib/debug/boot/vmlinux-3.12.49-6-xen.debug: CRC matches

 So everything looks fine until it actually starting reading data
 from /dev/mem.

 Here it's trying to read the in-kernel configuration data, but it
 is not started with MAGIC_START "IKCFG_ST" string:

 > <readmem: ffffffff804d8ae0, KVADDR, "kernel_config_data", 32768,
(ROE),
 > 2de9ff0>
 > <read_dev_mem: addr: ffffffff804d8ae0 paddr: 4d8ae0 cnt: 1312>
 > <read_dev_mem: addr: ffffffff804d9000 paddr: 4d9000 cnt: 4096>
 > <read_dev_mem: addr: ffffffff804da000 paddr: 4da000 cnt: 4096>
 > <read_dev_mem: addr: ffffffff804db000 paddr: 4db000 cnt: 4096>
 > <read_dev_mem: addr: ffffffff804dc000 paddr: 4dc000 cnt: 4096>
 > <read_dev_mem: addr: ffffffff804dd000 paddr: 4dd000 cnt: 4096>
 > <read_dev_mem: addr: ffffffff804de000 paddr: 4de000 cnt: 4096>
 > <read_dev_mem: addr: ffffffff804df000 paddr: 4df000 cnt: 4096>
 > <read_dev_mem: addr: ffffffff804e0000 paddr: 4e0000 cnt: 2784>
 > WARNING: could not find MAGIC_START!

 Then it tries to read the cpu_xxxx_mask pointers, but it finds them
 all equal to zero:

 > <readmem: ffffffff804ce490, KVADDR, "cpu_possible_mask", 8, (FOE),
 > 7ffc963725a8>
 > <read_dev_mem: addr: ffffffff804ce490 paddr: 4ce490 cnt: 8>
 > <readmem: ffffffff804ce480, KVADDR, "cpu_present_mask", 8, (FOE),
 > 7ffc963725a8>
 > <read_dev_mem: addr: ffffffff804ce480 paddr: 4ce480 cnt: 8>
 > <readmem: ffffffff804ce488, KVADDR, "cpu_online_mask", 8, (FOE),
 > 7ffc963725a8>
 > <read_dev_mem: addr: ffffffff804ce488 paddr: 4ce488 cnt: 8>
 > <readmem: ffffffff804ce478, KVADDR, "cpu_active_mask", 8, (FOE),
 > 7ffc963725a8>
 > <read_dev_mem: addr: ffffffff804ce478 paddr: 4ce478 cnt: 8>

 I say that because if a virtual address was found in each location, it would
 then read the mask at that location, and then the contents of the cpu_mask
 would be translated.  For example, this is what my laptop's output looks
 like,
 where 8 cpus are possible, but 4 cpus exist:

   <readmem: ffffffff81806d18, KVADDR, "cpu_possible_mask", 8, (FOE),
   7fff70bec038>
   <read_memory_device: addr: ffffffff81806d18 paddr: 1806d18 cnt: 8>
   <readmem: ffffffff81ce0a20, KVADDR, "possible", 16, (ROE), f57620>
   <read_memory_device: addr: ffffffff81ce0a20 paddr: 1ce0a20 cnt: 16>
   cpu_possible_mask: 0 1 2 3 4 5 6 7
   <readmem: ffffffff81806d08, KVADDR, "cpu_present_mask", 8, (FOE),
   7fff70bec038>
   <read_memory_device: addr: ffffffff81806d08 paddr: 1806d08 cnt: 8>
   <readmem: ffffffff81ce0a30, KVADDR, "present", 16, (ROE), f57620>
   <read_memory_device: addr: ffffffff81ce0a30 paddr: 1ce0a30 cnt: 16>
   cpu_present_mask: 0 1 2 3
   <readmem: ffffffff81806d10, KVADDR, "cpu_online_mask", 8, (FOE),
   7fff70bec038>
   <read_memory_device: addr: ffffffff81806d10 paddr: 1806d10 cnt: 8>
   <readmem: ffffffff81ce0a10, KVADDR, "online", 16, (ROE), f57620>
   <read_memory_device: addr: ffffffff81ce0a10 paddr: 1ce0a10 cnt: 16>
   cpu_online_mask: 0 1 2 3
   <readmem: ffffffff81806d00, KVADDR, "cpu_active_mask", 8, (FOE),
   7fff70bec038>
   <read_memory_device: addr: ffffffff81806d00 paddr: 1806d00 cnt: 8>
   <readmem: ffffffff81ce0a40, KVADDR, "active", 16, (ROE), f57620>
   <read_memory_device: addr: ffffffff81ce0a40 paddr: 1ce0a40 cnt: 16>
   cpu_active_mask: 0 1 2 3

 Later on it reads the system utsname structure and displays just
 the kernel version from it, which should be "3.12.49-6-xen", but
 obviously "0.8.0" is garbage:

 > <readmem: ffffffff808647a4, KVADDR, "init_uts_ns", 390, (ROE),
d1a0dc>
 > <read_dev_mem: addr: ffffffff808647a4 paddr: 8647a4 cnt: 390>
 > base kernel version: 0.8.0

 Lastly, it tries to read the "linux_banner" string, but the WARNING
 message actually means that it found no ASCII characters at that
 location:

 > <readmem: ffffffff804c80c0, KVADDR, "accessible check", 8, (ROE|Q),
 > 7ffc9636f928>
 > <read_dev_mem: addr: ffffffff804c80c0 paddr: 4c80c0 cnt: 8>
 > <readmem: ffffffff804c80c0, KVADDR, "read_string characters", 1499,
 > (ROE|Q), 7ffc9636fc80>
 > <read_dev_mem: addr: ffffffff804c80c0 paddr: 4c80c0 cnt: 1499>
 > WARNING: cannot read linux_banner string
 > /proc/version:
 > Linux version 3.12.49-6-xen (geeko@buildhost) (gcc version 4.8.5 (SUSE
 > Linux) ) #1 SMP Mon Oct 26 16:05:37 UTC 2015 (11560c3)
 > linux_banner:
 > 

 At that point it just gives up:

 > crash: /var/tmp/vmlinux-3.12.49-6-xen.gz_L3Bnwm and /dev/mem do not match!

 So it looks like the virtual-to-physical address translation itself is
 not working correctly.  But I cannot speculate why it's failing.

 Since Red Hat no longer supports Xen, support in the crash utility has been
 maintained by patches posted by SUSE engineers and others on this mailing
 list.

 Can anybody on this mailing list confirm that crash runs OK on Xen dom0
 kernels of this vintage?

 Dave

 > crash 7.1.3
 > Copyright (C) 2002-2014  Red Hat, Inc.
 > Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
 > Copyright (C) 1999-2006  Hewlett-Packard Co
 > Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
 > Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
 > Copyright (C) 2005, 2011  NEC Corporation
 > Copyright (C) 1999, 2002, 2007  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.
 > 
 > get_live_memory_source: /dev/mem
 > /proc/version:
 > Linux version 3.12.49-6-xen (geeko@buildhost) (gcc version 4.8.5 (SUSE
 > Linux) ) #1 SMP Mon Oct 26 16:05:37 UTC 2015 (11560c3)
 > /var/tmp/vmlinux-3.12.49-6-xen.gz_L3Bnwm:
 > Linux version 3.12.49-6-xen (geeko@buildhost) (gcc version 4.8.5 (SUSE
 > Linux) ) #1 SMP Mon Oct 26 16:05:37 UTC 2015 (11560c3)
 > readmem: read_dev_mem() -> /dev/mem
 > GETBUF(32 -> 0)
 > NOTE: gnu_debuglink file: vmlinux-3.12.49-6-xen.debug
 > crc32: 82102e72
 >   GETBUF(25 -> 1)
 > ./vmlinux-3.12.49-6-xen.debug: not readable/found
 > ./.debug/vmlinux-3.12.49-6-xen.debug: not readable/found
 > /usr/lib/debug/boot/vmlinux-3.12.49-6-xen.debug: CRC matches
 >   FREEBUF(1)
 > FREEBUF(0)
 > gdb /usr/lib/debug/boot/vmlinux-3.12.49-6-xen.debug
 > GNU gdb (GDB) 7.6
 > Copyright (C) 2013 Free Software Foundation, Inc.
 > License GPLv3+: GNU GPL version 3 or later
 > <http://gnu.org/licenses/gpl.html>
 > This is free software: you are free to change and redistribute it.
 > There is NO WARRANTY, to the extent permitted by law.  Type "show
copying"
 > and "show warranty" for details.
 > This GDB was configured as "x86_64-unknown-linux-gnu"...
 > GETBUF(248 -> 0)
 >   GETBUF(1500 -> 1)
 > 
 >   FREEBUF(1)
 > FREEBUF(0)
 > <readmem: ffffffff804d8ae0, KVADDR, "kernel_config_data", 32768,
(ROE),
 > 2de9ff0>
 > <read_dev_mem: addr: ffffffff804d8ae0 paddr: 4d8ae0 cnt: 1312>
 > <read_dev_mem: addr: ffffffff804d9000 paddr: 4d9000 cnt: 4096>
 > <read_dev_mem: addr: ffffffff804da000 paddr: 4da000 cnt: 4096>
 > <read_dev_mem: addr: ffffffff804db000 paddr: 4db000 cnt: 4096>
 > <read_dev_mem: addr: ffffffff804dc000 paddr: 4dc000 cnt: 4096>
 > <read_dev_mem: addr: ffffffff804dd000 paddr: 4dd000 cnt: 4096>
 > <read_dev_mem: addr: ffffffff804de000 paddr: 4de000 cnt: 4096>
 > <read_dev_mem: addr: ffffffff804df000 paddr: 4df000 cnt: 4096>
 > <read_dev_mem: addr: ffffffff804e0000 paddr: 4e0000 cnt: 2784>
 > WARNING: could not find MAGIC_START!
 > GETBUF(248 -> 0)
 > FREEBUF(0)
 > GETBUF(64 -> 0)
 > <readmem: ffffffff804ce490, KVADDR, "cpu_possible_mask", 8, (FOE),
 > 7ffc963725a8>
 > <read_dev_mem: addr: ffffffff804ce490 paddr: 4ce490 cnt: 8>
 > <readmem: ffffffff804ce480, KVADDR, "cpu_present_mask", 8, (FOE),
 > 7ffc963725a8>
 > <read_dev_mem: addr: ffffffff804ce480 paddr: 4ce480 cnt: 8>
 > <readmem: ffffffff804ce488, KVADDR, "cpu_online_mask", 8, (FOE),
 > 7ffc963725a8>
 > <read_dev_mem: addr: ffffffff804ce488 paddr: 4ce488 cnt: 8>
 > <readmem: ffffffff804ce478, KVADDR, "cpu_active_mask", 8, (FOE),
 > 7ffc963725a8>
 > <read_dev_mem: addr: ffffffff804ce478 paddr: 4ce478 cnt: 8>
 > FREEBUF(0)
 > <readmem: ffffffff809b7548, KVADDR, "phys_to_machine_mapping", 8,
(FOE),
 > d2a2b8>
 > <read_dev_mem: addr: ffffffff809b7548 paddr: 9b7548 cnt: 8>
 > <readmem: ffffffff80a56588, KVADDR, "max_pfn", 8, (FOE), d2a2c0>
 > <read_dev_mem: addr: ffffffff80a56588 paddr: a56588 cnt: 8>
 > GETBUF(248 -> 0)
 > FREEBUF(0)
 > GETBUF(248 -> 0)
 > FREEBUF(0)
 > <readmem: ffffffff80a08e38, KVADDR, "timekeeper xtime_sec", 8, (ROE),
 > 7ffc963725c8>
 > <read_dev_mem: addr: ffffffff80a08e38 paddr: a08e38 cnt: 8>
 > <readmem: ffffffff808647a4, KVADDR, "init_uts_ns", 390, (ROE),
d1a0dc>
 > <read_dev_mem: addr: ffffffff808647a4 paddr: 8647a4 cnt: 390>
 > base kernel version: 0.8.0
 > <readmem: ffffffff804c80c0, KVADDR, "accessible check", 8, (ROE|Q),
 > 7ffc9636f928>
 > <read_dev_mem: addr: ffffffff804c80c0 paddr: 4c80c0 cnt: 8>
 > <readmem: ffffffff804c80c0, KVADDR, "read_string characters", 1499,
 > (ROE|Q), 7ffc9636fc80>
 > <read_dev_mem: addr: ffffffff804c80c0 paddr: 4c80c0 cnt: 1499>
 > WARNING: cannot read linux_banner string
 > /proc/version:
 > Linux version 3.12.49-6-xen (geeko@buildhost) (gcc version 4.8.5 (SUSE
 > Linux) ) #1 SMP Mon Oct 26 16:05:37 UTC 2015 (11560c3)
 > linux_banner:
 > 
 > crash: /var/tmp/vmlinux-3.12.49-6-xen.gz_L3Bnwm and /dev/mem do not match!
 > 
 > Usage:
 > 
 >   crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS]     (dumpfile form)
 >   crash [OPTION]... [NAMELIST]                          (live system form)
 > 
 > Enter "crash -h" for details.
 > 
 > 
 > 
 > 
 > It is the same result. So does it mean my "vmlinux-3.12.49-6-xen.gz"
 > isn't right file?
 > Best Regards
 > Nan Xiao
 > 
 > 
 > On Tue, Nov 17, 2015 at 11:22 PM, Dave Anderson <anderson(a)redhat.com&gt;
 > wrote:
 > >
 > > If you simply enter "crash" on the command line in order to run live,
a
 > > search
 > > is made for a kernel file that contains the /proc/version string, for
 > > example:
 > >
 > >   # cat /proc/version
 > >   Linux version 4.4.0-0.rc0.git9.1.fc23.x86_64
 > >   (root(a)hp-dl980g7-02.rhts.eng.bos.re
 > >   dhat.com) (gcc version 5.1.1 20150618 (Red Hat 5.1.1-4) (GCC) ) #1 SMP
 > >   Mon Nov 1
 > >   6 14:32:21 EST 2015
 > >   #
 > >
 > > And when running on a live system in that manner, the "NAMELIST"
kernel
 > > file needs
 > > to be uncompressed:
 > >
 > >   $ man crash
 > >   CRASH(8)
 > >
 > >   NAME
 > >        crash - Analyze Linux crash dump data or a live system
 > >
 > >   SYNOPSIS
 > >        crash [OPTION]... NAMELIST MEMORY-IMAGE    (dumpfile form)
 > >        crash [OPTION]... [NAMELIST]               (live system form)
 > >
 > >   ... [ cut ] ...
 > >
 > >   OPTIONS
 > >        NAMELIST
 > >               This is a pathname to an uncompressed kernel image (a
 > >               vmlinux
 > >               file), or
 > >               a Xen hypervisor image (a xen-syms file)  which  has  been
 > >               compiled with
 > >               the "-g" option.  If using the dumpfile form, a
vmlinux
 > >               file
 > >               may be
 > >               compressed in either gzip or bzip2 formats.
 > >   ...
 > >
 > >
 > > And here it finds the uncompressed vmlinux in one of the search
 > > directories,
 > > in this case, in
 > > /usr/lib/debug/lib/modules/4.4.0-0.rc0.git9.1.fc23.x86_64:
 > >
 > >   # crash
 > >
 > >   crash 7.1.3
 > >   Copyright (C) 2002-2014  Red Hat, Inc.
 > >   Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
 > >   Copyright (C) 1999-2006  Hewlett-Packard Co
 > >   Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
 > >   Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
 > >   Copyright (C) 2005, 2011  NEC Corporation
 > >   Copyright (C) 1999, 2002, 2007  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 (GDB) 7.6
 > >   Copyright (C) 2013 Free Software Foundation, Inc.
 > >   License GPLv3+: GNU GPL version 3 or later
 > >   <http://gnu.org/licenses/gpl.html>
 > >   This is free software: you are free to change and redistribute it.
 > >   There is NO WARRANTY, to the extent permitted by law.  Type "show
 > >   copying"
 > >   and "show warranty" for details.
 > >   This GDB was configured as "x86_64-unknown-linux-gnu"...
 > >
 > >         KERNEL:
 > >         /usr/lib/debug/lib/modules/4.4.0-0.rc0.git9.1.fc23.x86_64/vmlinux
 > >       DUMPFILE: /dev/crash
 > >           CPUS: 160
 > >           DATE: Tue Nov 17 09:45:09 2015
 > >         UPTIME: 17:53:29
 > >   LOAD AVERAGE: 0.08, 0.03, 0.05
 > >          TASKS: 1714
 > >       NODENAME: hp-dl980g7-02.rhts.eng.bos.redhat.com
 > >        RELEASE: 4.4.0-0.rc0.git9.1.fc23.x86_64
 > >        VERSION: #1 SMP Mon Nov 16 14:32:21 EST 2015
 > >        MACHINE: x86_64  (2260 Mhz)
 > >         MEMORY: 1006 GB
 > >            PID: 7595
 > >        COMMAND: "crash"
 > >           TASK: ffff881f6f804700  [THREAD_INFO: ffff881f66888000]
 > >            CPU: 41
 > >          STATE: TASK_RUNNING (ACTIVE)
 > >
 > >   crash>
 > >
 > > But if the vmlinux file is compressed:
 > >
 > >   # cd /usr/lib/debug/lib/modules/4.4.0-0.rc0.git9.1.fc23.x86_64
 > >   # ls
 > >   vmlinux
 > >   # gzip vmlinux
 > >   # ls
 > >   vmlinux.gz
 > >   #
 > >
 > > It won't find it, and crash normally fails like so:
 > >
 > >   # crash
 > >
 > >   crash 7.1.3
 > >   Copyright (C) 2002-2014  Red Hat, Inc.
 > >   Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
 > >   Copyright (C) 1999-2006  Hewlett-Packard Co
 > >   Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
 > >   Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
 > >   Copyright (C) 2005, 2011  NEC Corporation
 > >   Copyright (C) 1999, 2002, 2007  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.
 > >
 > >   crash: cannot find booted kernel -- please enter namelist argument
 > >
 > >
 > >   Usage:
 > >
 > >     crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS]   (dumpfile form)
 > >     crash [OPTION]... [NAMELIST]                        (live system
 > >     form)
 > >
 > >   Enter "crash -h" for details.
 > >   #
 > >
 > > However, I can manually enter the compressed filename:
 > >
 > >   # crash vmlinux.gz
 > >
 > >   crash 7.1.3-1.fc23
 > >   Copyright (C) 2002-2014  Red Hat, Inc.
 > >   Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
 > >   Copyright (C) 1999-2006  Hewlett-Packard Co
 > >   Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
 > >   Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
 > >   Copyright (C) 2005, 2011  NEC Corporation
 > >   Copyright (C) 1999, 2002, 2007  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 (GDB) 7.6
 > >   Copyright (C) 2013 Free Software Foundation, Inc.
 > >   License GPLv3+: GNU GPL version 3 or later
 > >   <http://gnu.org/licenses/gpl.html>
 > >   This is free software: you are free to change and redistribute it.
 > >   There is NO WARRANTY, to the extent permitted by law.  Type "show
 > >   copying"
 > >   and "show warranty" for details.
 > >   This GDB was configured as "x86_64-unknown-linux-gnu"...
 > >
 > >         KERNEL: vmlinux.gz
 > >       DUMPFILE: /dev/crash
 > >           CPUS: 160
 > >           DATE: Tue Nov 17 10:11:42 2015
 > >         UPTIME: 18:20:02
 > >   LOAD AVERAGE: 0.16, 0.05, 0.06
 > >          TASKS: 1714
 > >       NODENAME: hp-dl980g7-02.rhts.eng.bos.redhat.com
 > >        RELEASE: 4.4.0-0.rc0.git9.1.fc23.x86_64
 > >        VERSION: #1 SMP Mon Nov 16 14:32:21 EST 2015
 > >        MACHINE: x86_64  (2260 Mhz)
 > >         MEMORY: 1006 GB
 > >            PID: 7660
 > >        COMMAND: "crash"
 > >           TASK: ffff881f66888c40  [THREAD_INFO: ffff881f6e998000]
 > >            CPU: 59
 > >          STATE: TASK_RUNNING (ACTIVE)
 > >
 > >   crash>
 > >
 > > Dave
 > >
 > >
 > > ----- Original Message -----
 > >> Hi Dave,
 > >>
 > >> # crash -d8
 > >>
 > >> crash 7.1.3
 > >> Copyright (C) 2002-2014  Red Hat, Inc.
 > >> Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
 > >> Copyright (C) 1999-2006  Hewlett-Packard Co
 > >> Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
 > >> Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
 > >> Copyright (C) 2005, 2011  NEC Corporation
 > >> Copyright (C) 1999, 2002, 2007  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.
 > >>
 > >>
 > >> find_booted_kernel: search for [Linux version 3.12.49-6-xen
 > >> (geeko@buildhost) (gcc version 4.8.5 (SUSE Linux) ) #1 SMP Mon Oct 26
 > >> 16:05:37 UTC 2015 (11560c3)]
 > >> mount_points[0]: / (1eeb2a0)
 > >> mount_points[1]: /sys (1eeb2c0)
 > >> mount_points[2]: /proc (1eeb2e0)
 > >> mount_points[3]: /dev (1eeb300)
 > >> mount_points[4]: /sys/kernel/security (1eeb320)
 > >> mount_points[5]: /dev/shm (1eeb350)
 > >> mount_points[6]: /dev/pts (1eeb370)
 > >> mount_points[7]: /run (1eeb390)
 > >> mount_points[8]: /sys/fs/cgroup (1eeb3b0)
 > >> mount_points[9]: /sys/fs/cgroup/systemd (1eeb3e0)
 > >> mount_points[10]: /sys/fs/pstore (1eeb420)
 > >> mount_points[11]: /sys/fs/cgroup/cpuset (1eeb450)
 > >> mount_points[12]: /sys/fs/cgroup/cpu,cpuacct (1eeb490)
 > >> mount_points[13]: /sys/fs/cgroup/memory (1eeb4d0)
 > >> mount_points[14]: /sys/fs/cgroup/devices (1eeb510)
 > >> mount_points[15]: /sys/fs/cgroup/freezer (1eeb550)
 > >> mount_points[16]: /sys/fs/cgroup/blkio (1eeb590)
 > >> mount_points[17]: /sys/fs/cgroup/perf_event (1eeb5c0)
 > >> mount_points[18]: / (1eeb600)
 > >> mount_points[19]: /proc/sys/fs/binfmt_misc (1eeb620)
 > >> mount_points[20]: /sys/kernel/debug (1eeb660)
 > >> mount_points[21]: /dev/mqueue (1eeb690)
 > >> mount_points[22]: /.snapshots (1eeb6b0)
 > >> mount_points[23]: /var/spool (1eeb6d0)
 > >> mount_points[24]: /var/opt (1eeb6f0)
 > >> mount_points[25]: /var/log (1eeb710)
 > >> mount_points[26]: /var/tmp (1eeb730)
 > >> mount_points[27]: /var/lib/libvirt/images (1eeb750)
 > >> mount_points[28]: /var/lib/mailman (1eeb790)
 > >> mount_points[29]: /var/crash (1eeb7c0)
 > >> mount_points[30]: /var/lib/pgsql (1eeb7e0)
 > >> mount_points[31]: /var/lib/named (1eeb810)
 > >> mount_points[32]: /var/lib/mariadb (1eeb840)
 > >> mount_points[33]: /tmp (1eeb870)
 > >> mount_points[34]: /usr/local (1eeb890)
 > >> mount_points[35]: /srv (1eeb8b0)
 > >> mount_points[36]: /boot/grub2/x86_64-efi (1eeb8d0)
 > >> mount_points[37]: /opt (1eeb910)
 > >> mount_points[38]: /boot/grub2/i386-pc (1eeb930)
 > >> mount_points[39]: /home (1eeb960)
 > >> mount_points[40]: /var/lib/xenstored (1eeb980)
 > >> mount_points[41]: /run/user/0/gvfs (1eeb9b0)
 > >> mount_points[42]: /run/media/root/SLE-12-SP1-Server-DVD-x86_643179
 > >> (1eeb9e0)
 > >> searchdirs[13]: /usr/lib/debug/lib/modules/3.12.49-6-xen/
 > >> searchdirs[0]: /usr/src/linux/
 > >> searchdirs[1]: /boot/
 > >> searchdirs[2]: /boot/efi/redhat
 > >> searchdirs[3]: /boot/efi/EFI/redhat
 > >> searchdirs[4]: /
 > >> searchdirs[5]: /usr/src/packages/
 > >> searchdirs[6]: /usr/src/linux-3.12.49-6/
 > >> searchdirs[7]: /usr/src/linux-3.12.49-6-obj/
 > >> searchdirs[8]: /usr/src/linux-obj/
 > >> searchdirs[9]: /usr/src/debug/
 > >> searchdirs[10]: /lib/modules/3.12.49-6-xen/build/
 > >> searchdirs[11]: /usr/src/redhat/BUILD/kernel-3.12.49/linux/
 > >> searchdirs[12]: /usr/src/redhat/BUILD/kernel-3.12.49/linux-3.12.49/
 > >> find_booted_kernel: check: /usr/src/linux/Makefile
 > >> find_booted_kernel: check: /usr/src/linux/Kbuild
 > >> find_booted_kernel: check: /usr/src/linux/Kconfig
 > >> find_booted_kernel: check: /usr/src/linux/MAINTAINERS
 > >> find_booted_kernel: check: /usr/src/linux/README.SUSE
 > >> find_booted_kernel: check: /usr/src/linux/COPYING
 > >> find_booted_kernel: check: /usr/src/linux/CREDITS
 > >> find_booted_kernel: check: /usr/src/linux/README
 > >> find_booted_kernel: check: /usr/src/linux/REPORTING-BUGS
 > >> find_booted_kernel: check: /boot/boot.readme
 > >> crash: /boot/symtypes-3.12.49-6-xen.gz: original filename unknown
 > >>        Use "-f /boot/symtypes-3.12.49-6-xen.gz" on command line
to
 > >> prevent this message.
 > >>
 > >> find_booted_kernel: check: /boot/symtypes-3.12.49-6-xen.gz
 > >> crash: /boot/symtypes-3.12.49-6-default.gz: original filename unknown
 > >>        Use "-f /boot/symtypes-3.12.49-6-default.gz" on command
line to
 > >> prevent this message.
 > >>
 > >> find_booted_kernel: check: /boot/symtypes-3.12.49-6-default.gz
 > >> crash: /boot/xen-4.5.1_10-1.gz: original filename unknown
 > >>        Use "-f /boot/xen-4.5.1_10-1.gz" on command line to
prevent this
 > >>        message.
 > >>
 > >> WARNING: machine type mismatch:
 > >>          crash utility: X86_64
 > >>          /var/tmp/xen-4.5.1_10-1.gz_Meuxmq: X86
 > >>
 > >> find_booted_kernel: check: /boot/xen-4.5.1_10-1.gz
 > >> crash: /boot/xen-4.5.gz: original filename unknown
 > >>        Use "-f /boot/xen-4.5.gz" on command line to prevent this
 > >>        message.
 > >>
 > >> WARNING: machine type mismatch:
 > >>          crash utility: X86_64
 > >>          /var/tmp/xen-4.5.gz_rsb8Dt: X86
 > >>
 > >> find_booted_kernel: check: /boot/xen-4.5.gz
 > >> crash: /boot/xen-4.gz: original filename unknown
 > >>        Use "-f /boot/xen-4.gz" on command line to prevent this
message.
 > >>
 > >> WARNING: machine type mismatch:
 > >>          crash utility: X86_64
 > >>          /var/tmp/xen-4.gz_G4wt4w: X86
 > >>
 > >> find_booted_kernel: check: /boot/xen-4.gz
 > >> crash: /boot/xen-dbg-4.5.1_10-1.gz: original filename unknown
 > >>        Use "-f /boot/xen-dbg-4.5.1_10-1.gz" on command line to
prevent
 > >> this message.
 > >>
 > >> WARNING: machine type mismatch:
 > >>          crash utility: X86_64
 > >>          /var/tmp/xen-dbg-4.5.1_10-1.gz_Kh7vDA: X86
 > >>
 > >> find_booted_kernel: check: /boot/xen-dbg-4.5.1_10-1.gz
 > >> crash: /boot/xen-dbg-4.5.gz: original filename unknown
 > >>        Use "-f /boot/xen-dbg-4.5.gz" on command line to prevent
this
 > >>        message.
 > >>
 > >> WARNING: machine type mismatch:
 > >>          crash utility: X86_64
 > >>          /var/tmp/xen-dbg-4.5.gz_Yc9ZkE: X86
 > >>
 > >> find_booted_kernel: check: /boot/xen-dbg-4.5.gz
 > >> crash: /boot/xen-dbg-4.gz: original filename unknown
 > >>        Use "-f /boot/xen-dbg-4.gz" on command line to prevent
this
 > >>        message.
 > >>
 > >> WARNING: machine type mismatch:
 > >>          crash utility: X86_64
 > >>          /var/tmp/xen-dbg-4.gz_0JpLaI: X86
 > >>
 > >> find_booted_kernel: check: /boot/xen-dbg-4.gz
 > >> crash: /boot/xen-dbg.gz: original filename unknown
 > >>        Use "-f /boot/xen-dbg.gz" on command line to prevent this
 > >>        message.
 > >>
 > >> WARNING: machine type mismatch:
 > >>          crash utility: X86_64
 > >>          /var/tmp/xen-dbg.gz_XCKM8L: X86
 > >>
 > >> find_booted_kernel: check: /boot/xen-dbg.gz
 > >> find_booted_kernel: check: /boot/xen-syms
 > >> find_booted_kernel: check: /boot/xen-syms-4.5.1_10-1
 > >> find_booted_kernel: check: /boot/xen-syms-dbg
 > >> find_booted_kernel: check: /boot/xen-syms-dbg-4.5.1_10-1
 > >> crash: /boot/xen.gz: original filename unknown
 > >>        Use "-f /boot/xen.gz" on command line to prevent this
message.
 > >>
 > >> WARNING: machine type mismatch:
 > >>          crash utility: X86_64
 > >>          /var/tmp/xen.gz_3rstYS: X86
 > >>
 > >> find_booted_kernel: check: /boot/xen.gz
 > >> find_booted_kernel: check: /boot/System.map-3.12.49-6-xen
 > >> find_booted_kernel: check: /boot/config-3.12.49-6-xen
 > >> crash: /boot/symvers-3.12.49-6-xen.gz: original filename unknown
 > >>        Use "-f /boot/symvers-3.12.49-6-xen.gz" on command line
to
 > >> prevent this message.
 > >>
 > >> find_booted_kernel: check: /boot/symvers-3.12.49-6-xen.gz
 > >> find_booted_kernel: check: /boot/sysctl.conf-3.12.49-6-xen
 > >> find_booted_kernel: check: /boot/vmlinux-3.12.49-6-xen.gz
 > >> find_booted_kernel: found: /boot/vmlinux-3.12.49-6-xen.gz
 > >> get_live_memory_source: /dev/mem
 > >> /proc/version:
 > >> Linux version 3.12.49-6-xen (geeko@buildhost) (gcc version 4.8.5 (SUSE
 > >> Linux) ) #1 SMP Mon Oct 26 16:05:37 UTC 2015 (11560c3)
 > >> /var/tmp/vmlinux-3.12.49-6-xen.gz_ecPt06:
 > >> Linux version 3.12.49-6-xen (geeko@buildhost) (gcc version 4.8.5 (SUSE
 > >> Linux) ) #1 SMP Mon Oct 26 16:05:37 UTC 2015 (11560c3)
 > >> readmem: read_dev_mem() -> /dev/mem
 > >> GETBUF(32 -> 0)
 > >> NOTE: gnu_debuglink file: vmlinux-3.12.49-6-xen.debug
 > >> crc32: 82102e72
 > >>   GETBUF(31 -> 1)
 > >> /boot//vmlinux-3.12.49-6-xen.debug: not readable/found
 > >> /boot//.debug/vmlinux-3.12.49-6-xen.debug: not readable/found
 > >> /usr/lib/debug/boot/vmlinux-3.12.49-6-xen.debug: CRC matches
 > >>   FREEBUF(1)
 > >> FREEBUF(0)
 > >> gdb /usr/lib/debug/boot/vmlinux-3.12.49-6-xen.debug
 > >> GNU gdb (GDB) 7.6
 > >> Copyright (C) 2013 Free Software Foundation, Inc.
 > >> License GPLv3+: GNU GPL version 3 or later
 > >> <http://gnu.org/licenses/gpl.html>
 > >> This is free software: you are free to change and redistribute it.
 > >> There is NO WARRANTY, to the extent permitted by law.  Type "show
 > >> copying"
 > >> and "show warranty" for details.
 > >> This GDB was configured as "x86_64-unknown-linux-gnu"...
 > >> GETBUF(248 -> 0)
 > >>   GETBUF(1500 -> 1)
 > >>
 > >>   FREEBUF(1)
 > >> FREEBUF(0)
 > >> <readmem: ffffffff804d8ae0, KVADDR, "kernel_config_data",
32768, (ROE),
 > >> 2f22000>
 > >> <read_dev_mem: addr: ffffffff804d8ae0 paddr: 4d8ae0 cnt: 1312>
 > >> <read_dev_mem: addr: ffffffff804d9000 paddr: 4d9000 cnt: 4096>
 > >> <read_dev_mem: addr: ffffffff804da000 paddr: 4da000 cnt: 4096>
 > >> <read_dev_mem: addr: ffffffff804db000 paddr: 4db000 cnt: 4096>
 > >> <read_dev_mem: addr: ffffffff804dc000 paddr: 4dc000 cnt: 4096>
 > >> <read_dev_mem: addr: ffffffff804dd000 paddr: 4dd000 cnt: 4096>
 > >> <read_dev_mem: addr: ffffffff804de000 paddr: 4de000 cnt: 4096>
 > >> <read_dev_mem: addr: ffffffff804df000 paddr: 4df000 cnt: 4096>
 > >> <read_dev_mem: addr: ffffffff804e0000 paddr: 4e0000 cnt: 2784>
 > >> WARNING: could not find MAGIC_START!
 > >> GETBUF(248 -> 0)
 > >> FREEBUF(0)
 > >> GETBUF(64 -> 0)
 > >> <readmem: ffffffff804ce490, KVADDR, "cpu_possible_mask", 8,
(FOE),
 > >> 7fffb4ff6918>
 > >> <read_dev_mem: addr: ffffffff804ce490 paddr: 4ce490 cnt: 8>
 > >> <readmem: ffffffff804ce480, KVADDR, "cpu_present_mask", 8,
(FOE),
 > >> 7fffb4ff6918>
 > >> <read_dev_mem: addr: ffffffff804ce480 paddr: 4ce480 cnt: 8>
 > >> <readmem: ffffffff804ce488, KVADDR, "cpu_online_mask", 8,
(FOE),
 > >> 7fffb4ff6918>
 > >> <read_dev_mem: addr: ffffffff804ce488 paddr: 4ce488 cnt: 8>
 > >> <readmem: ffffffff804ce478, KVADDR, "cpu_active_mask", 8,
(FOE),
 > >> 7fffb4ff6918>
 > >> <read_dev_mem: addr: ffffffff804ce478 paddr: 4ce478 cnt: 8>
 > >> FREEBUF(0)
 > >> <readmem: ffffffff809b7548, KVADDR, "phys_to_machine_mapping",
8, (FOE),
 > >> d2a2b8>
 > >> <read_dev_mem: addr: ffffffff809b7548 paddr: 9b7548 cnt: 8>
 > >> <readmem: ffffffff80a56588, KVADDR, "max_pfn", 8, (FOE),
d2a2c0>
 > >> <read_dev_mem: addr: ffffffff80a56588 paddr: a56588 cnt: 8>
 > >> GETBUF(248 -> 0)
 > >> FREEBUF(0)
 > >> GETBUF(248 -> 0)
 > >> FREEBUF(0)
 > >> <readmem: ffffffff80a08e38, KVADDR, "timekeeper xtime_sec", 8,
(ROE),
 > >> 7fffb4ff6938>
 > >> <read_dev_mem: addr: ffffffff80a08e38 paddr: a08e38 cnt: 8>
 > >> <readmem: ffffffff808647a4, KVADDR, "init_uts_ns", 390, (ROE),
d1a0dc>
 > >> <read_dev_mem: addr: ffffffff808647a4 paddr: 8647a4 cnt: 390>
 > >> base kernel version: 0.0.0
 > >> <readmem: ffffffff804c80c0, KVADDR, "accessible check", 8,
(ROE|Q),
 > >> 7fffb4ff3c98>
 > >> <read_dev_mem: addr: ffffffff804c80c0 paddr: 4c80c0 cnt: 8>
 > >> <readmem: ffffffff804c80c0, KVADDR, "read_string characters",
1499,
 > >> (ROE|Q), 7fffb4ff3ff0>
 > >> <read_dev_mem: addr: ffffffff804c80c0 paddr: 4c80c0 cnt: 1499>
 > >> WARNING: cannot read linux_banner string
 > >> /proc/version:
 > >> Linux version 3.12.49-6-xen (geeko@buildhost) (gcc version 4.8.5 (SUSE
 > >> Linux) ) #1 SMP Mon Oct 26 16:05:37 UTC 2015 (11560c3)
 > >> linux_banner:
 > >>
 > >> crash: /var/tmp/vmlinux-3.12.49-6-xen.gz_ecPt06 and /dev/mem do not
 > >> match!
 > >>
 > >> Usage:
 > >>
 > >>   crash [OPTION]... NAMELIST MEMORY-IMAGE[@ADDRESS]     (dumpfile form)
 > >>   crash [OPTION]... [NAMELIST]                          (live system
 > >>   form)
 > >>
 > >> Enter "crash -h" for details.
 > >>
 > >> Thanks!
 > >> Best Regards
 > >> Nan Xiao
 > >>
 > >>
 > >> On Tue, Nov 17, 2015 at 12:56 PM, Dave Anderson
<anderson(a)prospeed.net&gt;
 > >> wrote:
 > >> > Can you show the full output of "crash -d8"?
 > >> >
 > >> >
 > >> >
 > >> > Sent from my Verizon Wireless 4G LTE smartphone
 > >> >
 > >> >
 > >> > -------- Original message --------
 > >> > From: Nan Xiao <xiaonan830818(a)gmail.com&gt;
 > >> > Date: 11/16/2015 8:55 PM (GMT-05:00)
 > >> > To: "Discussion list for crash utility usage, maintenance and
 > >> > development"
 > >> > <crash-utility(a)redhat.com&gt;
 > >> > Subject: Re: [Crash-utility] The problems when running SuSE 12 on
 > >> > VirtualBox
 > >> >
 > >> > Hi Dietmar & Dave,
 > >> >
 > >> > Thanks very much for your time and answer! But for question 3, there
 > >> > is still no answer.
 > >> >
 > >> > I just execute "crash" with no parameters in the command
line, and
 > >> > want
 > >> > to
 > >> > debug
 > >> > Dom0:
 > >> >
 > >> > # crash
 > >> > ......
 > >> > WARNING: could not find MAGIC_START!
 > >> > WARNING: cannot read linux_banner string
 > >> > crash: /var/tmp/vmlinux-3.12.49-6-xen.gz_JWv5bU and /dev/mem do not
 > >> > match!
 > >> > ......
 > >> >
 > >> > So why does this operation fail?
 > >> > Best Regards
 > >> > Nan Xiao
 > >> >
 > >> >
 > >> > On Mon, Nov 16, 2015 at 10:48 PM, Dave Anderson
<anderson(a)redhat.com&gt;
 > >> > wrote:
 > >> >>
 > >> >>
 > >> >> ----- Original Message -----
 > >> >>> Am Montag 16 November 2015, 14:01:35 schrieb Nan Xiao:
 > >> >>> > Hi Dave,
 > >> >>> >
 > >> >>> > >> (2) "machine type mismatch"
 > >> >>> > >> WARNING: machine type mismatch:
 > >> >>> > >> crash utility: X86_64
 > >> >>> > >> /var/tmp/xen-4.5.1_10-1.gz_E5lLat: X86
 > >> >>> > >>
 > >> >>> > >> But according to "uname -a":
 > >> >>> > >>
 > >> >>> > >>  # uname -a
 > >> >>> > >> Linux linux-6ev3 3.12.49-6-xen #1 SMP Mon Oct 26
16:05:37 UTC
 > >> >>> > >> 2015
 > >> >>> > >> (11560c3) x86_64 x86_64 x86_64 GNU/Linux
 > >> >>> > >>
 > >> >>> > >> The running SuSE is also a 64-bit OS, so whether
can remove
 > >> >>> > >> these
 > >> >>> > >> warnings?
 > >> >>> >
 > >> >>> > > The mismatch message says that
 > >> >>> > > "/var/tmp/xen-4.5.1_10-1.gz_E5lLat"
 > >> >>> > > is
 > >> >>> > > an X86
 > >> >>> > > 32-bit binary.  You cannot use a 32-bit xen binary
with a 64-bit
 > >> >>> > > crash utility
 > >> >>> > > binary.
 > >> >>> >
 > >> >>> > > Run "gunzip xen-4.5.1_10-1.gz", and then
run "file" on the
 > >> >>> > > uncompressed file.
 > >> >>> > > If it's a 32-bit binary, and the dumpfile came
from that kernel,
 > >> >>> > > then
 > >> >>> > > you need
 > >> >>> > > to use a 32-bit crash utility binary.  If the
dumpfile came from
 > >> >>> > > a
 > >> >>> > > 64-bit kernel,
 > >> >>> > > then you're using the wrong xen binary.
 > >> >>> >
 > >> >>> > According to this
 > >> >>> >
 > >> >>> >
post(http://lists.xen.org/archives/html/xen-users/2015-10/msg00141.html),
 > >> >>> > although the xen file is 32-bit, it is the correct file
for
 > >> >>> > running
 > >> >>> > on
 > >> >>> > 64-bit OS. So I am not sure it should be considered as a
bug.
 > >> >>>
 > >> >>> No it's not a bug.
 > >> >>> The file you mentioned is only used for booting the
hypervisor. For
 > >> >>> debugging
 > >> >>> the hypervisor a statically linked hypervisor file has to be
used.
 > >> >>>
 > >> >>> On SLES11 SP4  I have for booting the xen hypervisor:
 > >> >>> # file xen-4.4.2_12-23.1
 > >> >>> xen-4.4.2_12-23.1_x2: ELF 32-bit LSB executable, Intel 80386,
 > >> >>> version
 > >> >>> 1
 > >> >>> (SYSV), statically linked, stripped
 > >> >>>
 > >> >>> For working with crash and the vmcore:
 > >> >>> # file xen-syms-4.4.2_12-23.1
 > >> >>> xen-syms-4.4.2_12-23.1_x2: ELF 64-bit LSB executable, x86-64,
 > >> >>> version
 > >> >>> 1
 > >> >>> (SYSV), statically linked, not stripped
 > >> >>
 > >> >>
 > >> >> Hi Dietmar,
 > >> >>
 > >> >> Thanks for clarifying that.  I should have noticed he was trying
to
 > >> >> use
 > >> >> the
 > >> >> actual xen binary instead of the xen-syms file --  which is
specified
 > >> >> in
 > >> >> the
 > >> >> crash(8) man page.
 > >> >>
 > >> >> And I wasn't even aware that the actual xen binary is a 32-bit
image
 > >> >> --
 > >> >> good
 > >> >> to know...
 > >> >>
 > >> >> Thanks,
 > >> >>   Dave
 > >> >>
 > >> >>
 > >> >>
 > >> >>
 > >> >>
 > >> >>
 > >> >>>
 > >> >>> >
 > >> >>> > >> (3)
 > >> >>> > >>
 > >> >>> > >> WARNING: could not find MAGIC_START!
 > >> >>> > >> WARNING: cannot read linux_banner string
 > >> >>> > >> crash: /var/tmp/vmlinux-3.12.49-6-xen.gz_FjRFMJ
and /dev/mem do
 > >> >>> > >> not
 > >> >>> > >> match!
 > >> >>> > >>
 > >> >>> > >> How can I fix this issue and run crash on SuSE?
 > >> >>> >
 > >> >>> > > For starters, make sure the kernel, the dumpfile,
and the crash
 > >> >>> > > binary
 > >> >>> > > are all
 > >> >>> > > 32-bit or all 64-bit, whichever is appropriate.
 > >> >>> >
 > >> >>> >  # which crash
 > >> >>> > /usr/bin/crash
 > >> >>> >
 > >> >>> > # file /usr/bin/crash
 > >> >>> > /usr/bin/crash: ELF 64-bit LSB executable, x86-64,
version 1
 > >> >>> > (SYSV),
 > >> >>> > dynamically linked (uses shared libs), for GNU/Linux
3.0.0,
 > >> >>> > BuildID[sha1]=e6f9921f98c5b4daedd8dac798c139b77676b588,
stripped
 > >> >>> >
 > >> >>> > Using "crash /boot/vmlinux-3.12.49-6-xen.gz
/proc/kcore" works OK:
 > >> >>>
 > >> >>> This is expected as this is similar to the xen behaviour.
 > >> >>> For booting:
 > >> >>> # file vmlinuz-3.0.101-63-xen
 > >> >>> vmlinuz-3.0.101-63-xen: Linux/x86 Kernel, Setup Version
0x20b,
 > >> >>> bzImage,
 > >> >>> Version 3.0.101, Version 3.0.101-63, RO-rootFS, swap_dev 0x3,
Normal
 > >> >>> VGA
 > >> >>>
 > >> >>> And for debugging:
 > >> >>> # file vmlinux-3.0.101-63-xen
 > >> >>> vmlinux-3.0.101-63-xen: ELF 64-bit LSB executable, x86-64,
version 1
 > >> >>> (SYSV),
 > >> >>> statically linked, not stripped
 > >> >>>
 > >> >>> Dietmar.
 > >> >>>
 > >> >>> >
 > >> >>> > # file /proc/kcore
 > >> >>> > /proc/kcore: ELF 64-bit LSB core file x86-64, version 1
(SYSV),
 > >> >>> > SVR4-style, from
'root=UUID=ed63d5d7-1d2f-45ea-a77b-5b3ae05c1c2e
 > >> >>> > resume=/dev/sda1 splash=silent q'
 > >> >>> >
 > >> >>> >  # crash /boot/vmlinux-3.12.49-6-xen.gz /proc/kcore
 > >> >>> >
 > >> >>> > crash 7.1.3
 > >> >>> > Copyright (C) 2002-2014  Red Hat, Inc.
 > >> >>> > Copyright (C) 2004, 2005, 2006, 2010  IBM Corporation
 > >> >>> > Copyright (C) 1999-2006  Hewlett-Packard Co
 > >> >>> > Copyright (C) 2005, 2006, 2011, 2012  Fujitsu Limited
 > >> >>> > Copyright (C) 2006, 2007  VA Linux Systems Japan K.K.
 > >> >>> > Copyright (C) 2005, 2011  NEC Corporation
 > >> >>> > Copyright (C) 1999, 2002, 2007  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 (GDB) 7.6
 > >> >>> > Copyright (C) 2013 Free Software Foundation, Inc.
 > >> >>> > License GPLv3+: GNU GPL version 3 or later
 > >> >>> > <http://gnu.org/licenses/gpl.html>
 > >> >>> > This is free software: you are free to change and
redistribute it.
 > >> >>> > There is NO WARRANTY, to the extent permitted by law. 
Type "show
 > >> >>> > copying"
 > >> >>> > and "show warranty" for details.
 > >> >>> > This GDB was configured as
"x86_64-unknown-linux-gnu"...
 > >> >>> >
 > >> >>> >       KERNEL: /boot/vmlinux-3.12.49-6-xen.gz
 > >> >>> >    DEBUGINFO:
/usr/lib/debug/boot/vmlinux-3.12.49-6-xen.debug
 > >> >>> >     DUMPFILE: /proc/kcore
 > >> >>> >         CPUS: 1
 > >> >>> >         DATE: Mon Nov 16 00:59:02 2015
 > >> >>> >       UPTIME: 04:55:39
 > >> >>> > LOAD AVERAGE: 0.08, 0.03, 0.05
 > >> >>> >        TASKS: 241
 > >> >>> >     NODENAME: linux-6ev3
 > >> >>> >      RELEASE: 3.12.49-6-xen
 > >> >>> >      VERSION: #1 SMP Mon Oct 26 16:05:37 UTC 2015
(11560c3)
 > >> >>> >      MACHINE: x86_64  (2596 Mhz)
 > >> >>> >       MEMORY: 855.2 MB
 > >> >>> >          PID: 7472
 > >> >>> >      COMMAND: "crash"
 > >> >>> >         TASK: ffff880019ab6540  [THREAD_INFO:
ffff880002dcc000]
 > >> >>> >          CPU: 0
 > >> >>> >        STATE: TASK_RUNNING (ACTIVE)
 > >> >>> >
 > >> >>> > So I think all the files are 64-bits.
 > >> >>> >
 > >> >>> > Thanks!
 > >> >>> > Best Regards
 > >> >>> > Nan Xiao
 > >> >>> >
 > >> >>> >
 > >> >>> > On Fri, Nov 13, 2015 at 10:54 PM, Dave Anderson
 > >> >>> > <anderson(a)redhat.com&gt;
 > >> >>> > wrote:
 > >> >>> > >
 > >> >>> > >
 > >> >>> > > ----- Original Message -----
 > >> >>> > >> Hi all,
 > >> >>> > >>
 > >> >>> > >> Firstly, I am not sure whether posting this
issue on this
 > >> >>> > >> mailing
 > >> >>> > >> list
 > >> >>> > >> is appropriate, if not,
 > >> >>> > >> please forgive me, thanks!
 > >> >>> > >>
 > >> >>> > >> I install SuSE Enterprise Linux 12 (Xen version)
on VirtualBox,
 > >> >>> > >> and
 > >> >>> > >> want
 > >> >>> > >> to use crash.
 > >> >>> > >> Executing "crash" command, and the
output likes this:
 > >> >>> > >>
 > >> >>> > >> # crash
 > >> >>> > >>
 > >> >>> > >> crash 7.1.3
 > >> >>> > >> Copyright (C) 2002-2014  Red Hat, Inc.
 > >> >>> > >> Copyright (C) 2004, 2005, 2006, 2010  IBM
Corporation
 > >> >>> > >> Copyright (C) 1999-2006  Hewlett-Packard Co
 > >> >>> > >> Copyright (C) 2005, 2006, 2011, 2012  Fujitsu
Limited
 > >> >>> > >> Copyright (C) 2006, 2007  VA Linux Systems Japan
K.K.
 > >> >>> > >> Copyright (C) 2005, 2011  NEC Corporation
 > >> >>> > >> Copyright (C) 1999, 2002, 2007  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.
 > >> >>> > >>
 > >> >>> > >> crash: /boot/symtypes-3.12.49-6-xen.gz: original
filename
 > >> >>> > >> unknown
 > >> >>> > >>   Use "-f
/boot/symtypes-3.12.49-6-xen.gz" on command line to
 > >> >>> > >> prevent
 > >> >>> > >> this message.
 > >> >>> > >>
 > >> >>> > >> crash: /boot/symtypes-3.12.49-6-default.gz:
original filename
 > >> >>> > >> unknown
 > >> >>> > >>   Use "-f
/boot/symtypes-3.12.49-6-default.gz" on command line
 > >> >>> > >>   to
 > >> >>> > >> prevent this message.
 > >> >>> > >>
 > >> >>> > >> crash: /boot/xen-4.5.1_10-1.gz: original
filename unknown
 > >> >>> > >>   Use "-f /boot/xen-4.5.1_10-1.gz" on
command line to prevent
 > >> >>> > >>   this
 > >> >>> > >>   message.
 > >> >>> > >>
 > >> >>> > >> WARNING: machine type mismatch:
 > >> >>> > >> crash utility: X86_64
 > >> >>> > >> /var/tmp/xen-4.5.1_10-1.gz_E5lLat: X86
 > >> >>> > >>
 > >> >>> > >> crash: /boot/xen-4.5.gz: original filename
unknown
 > >> >>> > >>   Use "-f /boot/xen-4.5.gz" on command
line to prevent this
 > >> >>> > >>   message.
 > >> >>> > >>
 > >> >>> > >> WARNING: machine type mismatch:
 > >> >>> > >> crash utility: X86_64
 > >> >>> > >> /var/tmp/xen-4.5.gz_0BL7f2: X86
 > >> >>> > >>
 > >> >>> > >> crash: /boot/xen-4.gz: original filename
unknown
 > >> >>> > >>   Use "-f /boot/xen-4.gz" on command
line to prevent this
 > >> >>> > >>   message.
 > >> >>> > >>
 > >> >>> > >> WARNING: machine type mismatch:
 > >> >>> > >> crash utility: X86_64
 > >> >>> > >> /var/tmp/xen-4.gz_PW97tB: X86
 > >> >>> > >>
 > >> >>> > >> crash: /boot/xen-dbg-4.5.1_10-1.gz: original
filename unknown
 > >> >>> > >>   Use "-f /boot/xen-dbg-4.5.1_10-1.gz"
on command line to
 > >> >>> > >>   prevent
 > >> >>> > >> this
 > >> >>> > >>   message.
 > >> >>> > >>
 > >> >>> > >> WARNING: machine type mismatch:
 > >> >>> > >> crash utility: X86_64
 > >> >>> > >> /var/tmp/xen-dbg-4.5.1_10-1.gz_zcILOa: X86
 > >> >>> > >>
 > >> >>> > >> crash: /boot/xen-dbg-4.5.gz: original filename
unknown
 > >> >>> > >>   Use "-f /boot/xen-dbg-4.5.gz" on
command line to prevent this
 > >> >>> > >> message.
 > >> >>> > >>
 > >> >>> > >> WARNING: machine type mismatch:
 > >> >>> > >> crash utility: X86_64
 > >> >>> > >> /var/tmp/xen-dbg-4.5.gz_AEpJfK: X86
 > >> >>> > >>
 > >> >>> > >> crash: /boot/xen-dbg-4.gz: original filename
unknown
 > >> >>> > >>   Use "-f /boot/xen-dbg-4.gz" on
command line to prevent this
 > >> >>> > >> message.
 > >> >>> > >>
 > >> >>> > >> WARNING: machine type mismatch:
 > >> >>> > >> crash utility: X86_64
 > >> >>> > >> /var/tmp/xen-dbg-4.gz_np36Nj: X86
 > >> >>> > >>
 > >> >>> > >> crash: /boot/xen-dbg.gz: original filename
unknown
 > >> >>> > >>   Use "-f /boot/xen-dbg.gz" on command
line to prevent this
 > >> >>> > >>   message.
 > >> >>> > >>
 > >> >>> > >> WARNING: machine type mismatch:
 > >> >>> > >> crash utility: X86_64
 > >> >>> > >> /var/tmp/xen-dbg.gz_1tAiuT: X86
 > >> >>> > >>
 > >> >>> > >> crash: /boot/xen.gz: original filename unknown
 > >> >>> > >>   Use "-f /boot/xen.gz" on command
line to prevent this
 > >> >>> > >>   message.
 > >> >>> > >>
 > >> >>> > >> WARNING: machine type mismatch:
 > >> >>> > >> crash utility: X86_64
 > >> >>> > >> /var/tmp/xen.gz_htZLuv: X86
 > >> >>> > >>
 > >> >>> > >> crash: /boot/symvers-3.12.49-6-xen.gz: original
filename
 > >> >>> > >> unknown
 > >> >>> > >>   Use "-f
/boot/symvers-3.12.49-6-xen.gz" on command line to
 > >> >>> > >>   prevent
 > >> >>> > >> this message.
 > >> >>> > >>
 > >> >>> > >> GNU gdb (GDB) 7.6
 > >> >>> > >> Copyright (C) 2013 Free Software Foundation,
Inc.
 > >> >>> > >> License GPLv3+: GNU GPL version 3 or later
 > >> >>> > >> <http://gnu.org/licenses/gpl.html>
 > >> >>> > >> This is free software: you are free to change
and redistribute
 > >> >>> > >> it.
 > >> >>> > >> There is NO WARRANTY, to the extent permitted by
law.  Type
 > >> >>> > >> "show
 > >> >>> > >> copying"
 > >> >>> > >> and "show warranty" for details.
 > >> >>> > >> This GDB was configured as
"x86_64-unknown-linux-gnu"...
 > >> >>> > >>
 > >> >>> > >> WARNING: could not find MAGIC_START!
 > >> >>> > >> WARNING: cannot read linux_banner string
 > >> >>> > >> crash: /var/tmp/vmlinux-3.12.49-6-xen.gz_FjRFMJ
and /dev/mem do
 > >> >>> > >> not
 > >> >>> > >> match!
 > >> >>> > >>
 > >> >>> > >> Usage:
 > >> >>> > >>
 > >> >>> > >>  crash [OPTION]... NAMELIST
MEMORY-IMAGE[@ADDRESS]
 > >> >>> > >>  (dumpfile
 > >> >>> > >> form)
 > >> >>> > >>  crash [OPTION]... [NAMELIST]                   
      (live
 > >> >>> > >>  system
 > >> >>> > >>  form)
 > >> >>> > >>
 > >> >>> > >> Enter "crash -h" for details.
 > >> >>> > >>
 > >> >>> > >> My question are as follows:
 > >> >>> > >>
 > >> >>> > >> (1) There are so may warnings like this:
 > >> >>> > >>
 > >> >>> > >> crash: xxxxxx: original filename unknown
 > >> >>> > >>   Use "-f xxxxxx" on command line to
prevent this message.
 > >> >>> > >>
 > >> >>> > >> Do I need to add somay "-f xxxxxx"
options on command line? Is
 > >> >>> > >> there
 > >> >>> > >> any better method?
 > >> >>> > >
 > >> >>> > > The message above simply mean that the original
filename of the
 > >> >>> > > compressed
 > >> >>> > > file was not stored in the file's header.  That
means that
 > >> >>> > > whoever
 > >> >>> > > created
 > >> >>> > > the compressed file used "gzip -n" or
"--no-name":
 > >> >>> > >
 > >> >>> > >   $ man gzip
 > >> >>> > >   ... [ cut ] ...
 > >> >>> > >
 > >> >>> > >      -n --no-name
 > >> >>> > >           When  compressing,  do not save the
original file name
 > >> >>> > >           and
 > >> >>> > > time
 > >> >>> > >           stamp by default. (The original name is
always saved
 > >> >>> > >           if
 > >> >>> > >           the
 > >> >>> > >           name
 > >> >>> > >           had to be truncated.) When decompressing,
do not
 > >> >>> > >           restore
 > >> >>> > > the
 > >> >>> > >           original file name if present (remove only
the gzip
 > >> >>> > >           suffix
 > >> >>> > > from
 > >> >>> > >           the compressed file name) and do not
restore the
 > >> >>> > >           original
 > >> >>> > > time
 > >> >>> > >           stamp
 > >> >>> > >           if present (copy it from the compressed
file). This
 > >> >>> > >           option
 > >> >>> > > is
 > >> >>> > >           the
 > >> >>> > >           default when decompressing.
 > >> >>> > >   ...
 > >> >>> > >
 > >> >>> > >> (2) "machine type mismatch"
 > >> >>> > >> WARNING: machine type mismatch:
 > >> >>> > >> crash utility: X86_64
 > >> >>> > >> /var/tmp/xen-4.5.1_10-1.gz_E5lLat: X86
 > >> >>> > >>
 > >> >>> > >> But according to "uname -a":
 > >> >>> > >>
 > >> >>> > >>  # uname -a
 > >> >>> > >> Linux linux-6ev3 3.12.49-6-xen #1 SMP Mon Oct 26
16:05:37 UTC
 > >> >>> > >> 2015
 > >> >>> > >> (11560c3) x86_64 x86_64 x86_64 GNU/Linux
 > >> >>> > >>
 > >> >>> > >> The running SuSE is also a 64-bit OS, so whether
can remove
 > >> >>> > >> these
 > >> >>> > >> warnings?
 > >> >>> > >
 > >> >>> > > The mismatch message says that
 > >> >>> > > "/var/tmp/xen-4.5.1_10-1.gz_E5lLat"
 > >> >>> > > is
 > >> >>> > > an
 > >> >>> > > X86
 > >> >>> > > 32-bit binary.  You cannot use a 32-bit xen binary
with a 64-bit
 > >> >>> > > crash
 > >> >>> > > utility
 > >> >>> > > binary.
 > >> >>> > >
 > >> >>> > > Run "gunzip xen-4.5.1_10-1.gz", and then
run "file" on the
 > >> >>> > > uncompressed
 > >> >>> > > file.
 > >> >>> > > If it's a 32-bit binary, and the dumpfile came
from that kernel,
 > >> >>> > > then
 > >> >>> > > you
 > >> >>> > > need
 > >> >>> > > to use a 32-bit crash utility binary.  If the
dumpfile came from
 > >> >>> > > a
 > >> >>> > > 64-bit
 > >> >>> > > kernel,
 > >> >>> > > then you're using the wrong xen binary.
 > >> >>> > >
 > >> >>> > >> (3)
 > >> >>> > >>
 > >> >>> > >> WARNING: could not find MAGIC_START!
 > >> >>> > >> WARNING: cannot read linux_banner string
 > >> >>> > >> crash: /var/tmp/vmlinux-3.12.49-6-xen.gz_FjRFMJ
and /dev/mem do
 > >> >>> > >> not
 > >> >>> > >> match!
 > >> >>> > >>
 > >> >>> > >> How can I fix this issue and run crash on SuSE?
 > >> >>> > >
 > >> >>> > > For starters, make sure the kernel, the dumpfile,
and the crash
 > >> >>> > > binary are all
 > >> >>> > > 32-bit or all 64-bit, whichever is appropriate.
 > >> >>> > >
 > >> >>> > > Dave
 > >> >>> > >
 > >> >>> > >>
 > >> >>> > >> Thanks very much in advance!
 > >> >>> > >> Best Regards
 > >> >>> > >> Nan Xiao
 > >> >>> > >>
 > >> >>> > >> --
 > >> >>> > >> Crash-utility mailing list
 > >> >>> > >> Crash-utility(a)redhat.com
 > >> >>> > >>
https://www.redhat.com/mailman/listinfo/crash-utility
 > >> >>> > >>
 > >> >>> > >
 > >> >>> > > --
 > >> >>> > > Crash-utility mailing list
 > >> >>> > > Crash-utility(a)redhat.com
 > >> >>> > >
https://www.redhat.com/mailman/listinfo/crash-utility
 > >> >>> >
 > >> >>> > --
 > >> >>> > Crash-utility mailing list
 > >> >>> > Crash-utility(a)redhat.com
 > >> >>> > https://www.redhat.com/mailman/listinfo/crash-utility
 > >> >>> >
 > >> >>>
 > >> >>> --
 > >> >>> Company details: http://ts.fujitsu.com/imprint.html
 > >> >>>
 > >> >>> --
 > >> >>> Crash-utility mailing list
 > >> >>> Crash-utility(a)redhat.com
 > >> >>> https://www.redhat.com/mailman/listinfo/crash-utility
 > >> >>>
 > >> >>
 > >> >> --
 > >> >> Crash-utility mailing list
 > >> >> Crash-utility(a)redhat.com
 > >> >> https://www.redhat.com/mailman/listinfo/crash-utility
 > >> >
 > >> > --
 > >> > Crash-utility mailing list
 > >> > Crash-utility(a)redhat.com
 > >> > https://www.redhat.com/mailman/listinfo/crash-utility
 > >> >
 > >> >
 > >> > --
 > >> > Crash-utility mailing list
 > >> > Crash-utility(a)redhat.com
 > >> > https://www.redhat.com/mailman/listinfo/crash-utility
 > >>
 > >> --
 > >> Crash-utility mailing list
 > >> Crash-utility(a)redhat.com
 > >> https://www.redhat.com/mailman/listinfo/crash-utility
 > >>
 > >
 > > --
 > > Crash-utility mailing list
 > > Crash-utility(a)redhat.com
 > > https://www.redhat.com/mailman/listinfo/crash-utility
 > 
 > --
 > Crash-utility mailing list
 > Crash-utility(a)redhat.com
 > https://www.redhat.com/mailman/listinfo/crash-utility
 > 

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Re: [Crash-utility] The problems when running SuSE 12 on VirtualBox