Re: [Crash-utility] crash read error: kernel virtual address / vmcore address mismatch ?
Hi ,
Sorry about re posting this as i did not find solution ...
I m facing a issue where on
#crash /data/linux-2.6.30.8/vmlinux /proc/vmcore
Do yourself a favor and copy /proc/vmcore to somewhere on disk. Then
reboot the system into the original kernel, and run crash on the saved
vmcore. I've never seen crash run on a /proc/vmcore file from the
secondary kernel.
Also, after rebooting the the original kernel, please confirm that
crash runs OK on the live system.
crash 6.1.6
Copyright (C) 2002-2013 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.3.1
Copyright (C) 2011 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 "i686-pc-linux-gnu"...
crash: read error: kernel virtual address: c127a9c8 type: "cpu_possible_mask"
Please show the full output of "crash -d8 vmlinux vmcore".
I have attached the output . d8.txt
I did follow few threads around , I have a case similar to
https://www.redhat.com/archives/crash-utility/2010-August/msg00029.html
Both the System Kernel and the Debug Kernel are the same.
I don't know what you mean by "System Kernel" and "Debug Kernel".
With respect to kdump and the crash utility, the only kernel that is
of interest is the vmlinux that was running when the primary system
crashed.
My current config for
CONFIG_PHYSICAL_START=0x1000000
CONFIG_RELOCATABLE=y
CONFIG_PHYSICAL_ALIGN=0x400000
The /proc/kallsyms is diffrent between the System Kernel and Debug Kernel.
On the System Kernel it starts from 0x400000 .On the Debug kernel it
starts from 0x1000000.
Again, the "Debug" kernel is irrelevant -- presuming by "Debug" you
mean
the relocated "secondary" kernel that was kexec'd after the primary kernel
crashed.
You are right , the System Kernel means the Primary kernel and Debug-
Secondary/Relocated kernel.
if i change the CONFIG_PHYSICAL_START=0x400000 . It does NOT core dump.
my crashkernel=128M is the setting on grub.
Let me know if you need more info
What "core dumps", the crash utility?
Here the crash utility does not core dump , its the Kernel which does
not vmcore on the above mentioned address .
Again, trying to run the crash utility
while running on a 128MB secondary kernel is definitely not advisable.
I did increase the crashkernel to 256M but it results the same .
Thanks,
Anand
Dave
Attachments:
- d8.txt (text/plain — 862.8 KB)