Oh, it turned out be my fault, as I used a wrong vmlinux, causing the
version mismatch.
After recompiling kernel and use correct vmlinux, it works now.
Thanks,
Qu
Qu Wenruo wrote on 2015/08/04 08:59 +0800:
Dave Anderson wrote on 2015/08/03 13:32 -0400:
>
>
> ----- Original Message -----
>>
>>
>> ----- Original Message -----
>>> Hi all,
>>>
>>> I updated my kernel to 4.2-rc4 but suddenly crash failed to analyse the
>>> kernel with the following error message:
>>> ------
>>> crash: invalid kernel virtual address: 170000001d type:
"possible"
>>> WARNING: cannot read cpu_possible_map
>>> crash: invalid kernel virtual address: 3800000046 type: "present"
>>> WARNING: cannot read cpu_present_map
>>> crash: invalid kernel virtual address: 240000002d type: "online"
>>> WARNING: cannot read cpu_online_map
>>> crash: invalid kernel virtual address: 570000006e type: "active"
>>> WARNING: cannot read cpu_active_map
>>> crash: cannot determine base kernel version
>>> crash: /home/adam/linux-btrfs/vmlinux and vmcore do not match!
>>> ------
>>>
>>> Crash 7.1.0 and 7.1.2 fails with the same error.
>>>
>>> Previously I'm testing 4.2-rc1 kernel and 7.1.0 works like a charm.
>>>
>>> So is there something wrong with the new kernel?
>>>
>>> Thanks,
>>> Qu
>>
>> The most recent kernel version I've tested is Fedora's
>> 4.2.0-0.rc4.git1.1.fc23.x86_64,
>> although I'm not sure how that version correlates with upstream
>> 4.2-rc1. It is based
>> upon linux-4.1.tar.xz with a bunch of patches.
>
> FYI, the changelog of the Fedora kernel-4.2.0-0.rc4.git1.1.fc23
> package indicates that
> it is based upon Linux v4.2-rc4.
>
> Dave
>
Hi Dave,
Thanks for the reply.
Although I didn't use stock fedora/RHEL kernel, I compiled one by myself.
Maybe some fedora patches changed the behavior?
I've attached the config file.
Although I'm not sure if config is related to this problem.
>
>
>> Here is a live system session with the Fedora version of crash:
>>
>> # crash
>>
>> crash 7.1.2-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:
>> /usr/lib/debug/lib/modules/4.2.0-0.rc4.git1.1.fc23.x86_64/vmlinux
>> DUMPFILE: /dev/crash
>> CPUS: 160
>> DATE: Mon Aug 3 13:00:49 2015
>> UPTIME: 03:58:44
>> LOAD AVERAGE: 0.59, 0.36, 0.17
>> TASKS: 1714
>> NODENAME:
hp-dl980g7-02.rhts.eng.bos.redhat.com
>> RELEASE: 4.2.0-0.rc4.git1.1.fc23.x86_64
>> VERSION: #1 SMP Tue Jul 28 20:21:39 UTC 2015
>> MACHINE: x86_64 (2261 Mhz)
>> MEMORY: 1006 GB
>> PID: 38013
>> COMMAND: "crash"
>> TASK: ffff881f668e6400 [THREAD_INFO: ffff881f68ad0000]
>> CPU: 61
>> STATE: TASK_RUNNING (ACTIVE)
>>
>> crash>
>>
>> Can you run on the live system? If so, it's most likely an issue with
>> the vmcore.
>>
>> Post the output of "crash -d8 vmlinux vmcore". The debug output may
>> yield some clues.
Output attached too.
Thanks,
Qu
>>
>> Dave
>>
>>
>> --
>> Crash-utility mailing list
>> Crash-utility(a)redhat.com
>>
https://www.redhat.com/mailman/listinfo/crash-utility
>>