FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Crash Utility

 
 
LinkBack Thread Tools
 
Old 04-20-2010, 08:01 AM
Pavan Naregundi
 
Default crash seek error, failed to read vmcore file

Hi Everyone,

We are facing a problem while analysing the vmcore on PPC64 systems
running SLES11 SP1.

===============
please wait... (gathering kmem slab cache data)
crash: seek error: kernel virtual address: c0000000af715480 type:
"kmem_cache buffer"

crash: unable to initialize kmem slab cache subsystem

please wait... (gathering module symbol data)
WARNING: cannot access vmalloc'd module memory

please wait... (gathering task table data)
crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid
=====================

Version: crash-5.0.3

Command used:
#crash vmlinux-2.6.32.10-0.4.99.25.62005-ppc64.debug
vmlinux-2.6.32.10-0.4.99.25.62005-ppc64 vmcore

Attaching the output of the above command..


Using crash -d8 for above command,
========================
<snip>
<readmem: c00000000134ffa0, KVADDR, "memory section", 32, (FOE),
122f94b0>
addr: c00000000134ffa0 paddr: 134ffa0 cnt: 32
<readmem: c00000000134ffc0, KVADDR, "memory section", 32, (FOE),
122f94b0>
addr: c00000000134ffc0 paddr: 134ffc0 cnt: 32
<readmem: c00000000134ffe0, KVADDR, "memory section", 32, (FOE),
122f94b0>
addr: c00000000134ffe0 paddr: 134ffe0 cnt: 32
NOTE: page_hash_table does not exist in this kernel

please wait... (gathering kmem slab cache data)<readmem:
c0000000012fc718, KVADDR, "cache_chain", 8, (FOE), fffeff7f108>
addr: c0000000012fc718 paddr: 12fc718 cnt: 8
GETBUF(248 -> 1)
FREEBUF(1)
GETBUF(10344 -> 1)
<readmem: c000000000d8af90, KVADDR, "kmem_cache buffer", 10344, (FOE),
1082f5d8>
addr: c000000000d8af90 paddr: d8af90 cnt: 10344
GETBUF(248 -> 2)
FREEBUF(2)
FREEBUF(1)
GETBUF(10344 -> 1)
<readmem: c0000000af715480, KVADDR, "kmem_cache buffer", 10344, (ROE),
1082f5d8>
addr: c0000000af715480 paddr: af715480 cnt: 10344

crash: seek error: kernel virtual address: c0000000af715480 type:
"kmem_cache buffer"
FREEBUF(1)

crash: unable to initialize kmem slab cache subsystem
=================================

NOTE: Crash was able to read a vmcore on the same system that was
manually generated using: echo c > /proc/sysrq-trigger.

Thanks..
Pavan
ovenlp2:/var/crash/2010-04-10-16:34 # ../crash vmlinux-2.6.32.10-0.4.99.25.62005-ppc64.debug vmlinux-2.6.32.10-0.4.99.25.62005-ppc64 vmcore

crash 5.0.3
Copyright (C) 2002-2010 Red Hat, Inc.
Copyright (C) 2004, 2005, 2006 IBM Corporation
Copyright (C) 1999-2006 Hewlett-Packard Co
Copyright (C) 2005, 2006 Fujitsu Limited
Copyright (C) 2006, 2007 VA Linux Systems Japan K.K.
Copyright (C) 2005 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.0
Copyright (C) 2009 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 "powerpc64-unknown-linux-gnu"...

please wait... (gathering kmem slab cache data)
crash: seek error: kernel virtual address: c0000000af715480 type: "kmem_cache buffer"

crash: unable to initialize kmem slab cache subsystem

please wait... (gathering module symbol data)
WARNING: cannot access vmalloc'd module memory

please wait... (gathering task table data)
crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: cannot read pid_hash upid

crash: seek error: kernel virtual address: c000000081a84000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000128dd0000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000001b80ca920 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000891c3720 type: "fill_task_struct"

crash: seek error: kernel virtual address: c00000012130c000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c00000013cde3aa0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000aafd07e0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000089ca0000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000c97237a0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000128dd4000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000088520ae0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000b5358f00 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000099805240 type: "fill_task_struct"

crash: seek error: kernel virtual address: c00000012849de60 type: "fill_task_struct"

crash: seek error: kernel virtual address: c00000008914c7c0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000001212d4000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000121157060 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000121764000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000001217cc000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000121300000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c00000008ef5c3c0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000194f8a620 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000089f48000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000c9cf4000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000128870000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000089bb0000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000081461d80 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000aafde0e0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000893e8000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000c972da60 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000128075840 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000924d0000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000898f4000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000098f7c000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000121d78f80 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000092f4e2e0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c00000008a8d0000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c00000008942aa20 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000128ff4000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000194f854c0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000c9760000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000001a0b44000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000089c04000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000c9393ca0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000128553820 type: "fill_task_struct"

crash: seek error: kernel virtual address: c00000008ef505e0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000088525c40 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000128556e60 type: "fill_task_struct"

crash: seek error: kernel virtual address: c00000009980bec0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000001284956c0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000e9400000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000092baa720 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000121151f00 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000a688c000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000089090000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000089758000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000924d8000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000891506e0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000a64a0a60 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000089510000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000128ddc000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000b53558c0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000aafd5940 type: "fill_task_struct"

crash: seek error: kernel virtual address: c00000013cde55c0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000c8e18000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000c9728900 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000128a20000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000c9910000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000c97252c0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000a6d71e00 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000081a88000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000994a9200 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000a4d6d9e0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000a3cb0860 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000b535c540 type: "fill_task_struct"

crash: seek error: kernel virtual address: c00000008852c8c0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000894273e0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000128b0e360 type: "fill_task_struct"

crash: seek error: kernel virtual address: c00000012849a820 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000092ba55c0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000a6aac000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000121af0000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000c91c0000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c00000012159db60 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000121968000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c00000008ef55740 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000e8ba1f00 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000c939c440 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000b53573e0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000a6cb8000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000081468a00 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000089b68c80 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000128551d00 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000001284b0000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000aafd3e20 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000121d7c5c0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000b5352280 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000e9404000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000c9cfc000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c00000008942e060 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000001b80c72e0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000891c6d60 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000a6364000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000121304000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000194f88b00 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000893b0000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000a6cb4000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c00000018b3f4000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000a6560ae0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000aafdaaa0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000c9ccc000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000001213f4000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000a6d98000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c00000009980d9e0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c00000012855a4a0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000099808880 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000089420760 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000128954000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c00000012849c340 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000001217c0000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000089147660 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000128072200 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000121155540 type: "fill_task_struct"

crash: seek error: kernel virtual address: c00000012176c000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000898fc000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c00000008ef52100 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000089b84000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000c91c4000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000c9dec000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000a3cb2380 type: "fill_task_struct"

crash: seek error: kernel virtual address: c00000013cdedd60 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000c9cf0000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000898f0000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000092f45b40 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000099806d60 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000c8b28c80 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000994a5bc0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000089098000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000089428f00 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000194f839a0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000001210e8000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000a6378000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000994a40a0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c00000008915dfe0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000001a0b48000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000e8ba3a20 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000128878000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000b5353da0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c00000012855dae0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000814638a0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000128555340 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000c9de8000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000891c8880 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000aafd7460 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000128490560 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000128208000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000128078e80 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000001211503e0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000089754000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000a6f28000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000001b80c3ca0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000b5350760 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000994a76e0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000aafdc5c0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000c9726de0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000994ae360 type: "fill_task_struct"

crash: seek error: kernel virtual address: c00000019492c000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000c972bf40 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000089f60000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000121d73e20 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000088527760 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000c1cd3da0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c00000008852e3e0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000128492080 type: "fill_task_struct"

crash: seek error: kernel virtual address: c00000008914e2e0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000c9400000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c00000012807c4c0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000121158b80 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000c9cc4000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000001285b3ba0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c00000008ef53c20 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000e8ba03e0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000121afc000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000893e4000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000893b4000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000891c5240 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000089422280 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000089094000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000001285501e0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000c8e20000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000a6d90000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000a4d68880 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000092f4c7c0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000dcd4c000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c00000008942c540 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000001b80c0660 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000001212bc0c0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000121308000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000089423da0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000194f86fe0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000089d65cc0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000089c08000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000aafd2300 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000121706fe0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000894258c0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c00000012855bfc0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000088524120 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000128558980 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000897b4000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000128493ba0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000089750000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c00000013f0e4000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000001280706e0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000121153a20 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000121768000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000089b8c000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c00000008ef57260 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000089158e80 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000a64a76e0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000c9702280 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000c9cc0000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c00000008146db60 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000b535e060 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000121710000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c00000008146c040 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000994aad20 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000c995c000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000c16f4000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000a6654000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000194f81e80 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000121af4000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000c8b25640 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000121598a00 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000c1cd73e0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000e8ba8b80 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000c9390660 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000b535aa20 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000a64a40a0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000a64a9200 type: "fill_task_struct"

crash: seek error: kernel virtual address: c00000008914aca0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c0000000aafd8f80 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000121d72300 type: "fill_task_struct"

crash: seek error: kernel virtual address: c000000128c20000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000c9703da0 type: "fill_task_struct"

crash: seek error: kernel virtual address: c00000012820c000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c000000098f78000 type: "fill_thread_info"

crash: seek error: kernel virtual address: c0000000a64ac840 type: "fill_task_struct"
please wait... (determining panic task)
crash: seek error: kernel virtual address: c000000089090000 type: "64-bit KVADDR"
ovenlp2:/var/crash/2010-04-10-16:34 #

--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
 
Old 04-20-2010, 01:14 PM
Dave Anderson
 
Default crash seek error, failed to read vmcore file

----- "Pavan Naregundi" <pavan@linux.vnet.ibm.com> wrote:

> Hi Everyone,
>
> We are facing a problem while analysing the vmcore on PPC64 systems
> running SLES11 SP1.
>
> ===============
> please wait... (gathering kmem slab cache data)
>
> crash: seek error: kernel virtual address: c0000000af715480 type: "kmem_cache buffer"
>
> crash: unable to initialize kmem slab cache subsystem
>
> please wait... (gathering module symbol data)
> WARNING: cannot access vmalloc'd module memory
>
> please wait... (gathering task table data)
> crash: cannot read pid_hash upid
>
> crash: cannot read pid_hash upid
>
> crash: cannot read pid_hash upid
> =====================
>
> Version: crash-5.0.3
>
> Command used:
> #crash vmlinux-2.6.32.10-0.4.99.25.62005-ppc64.debug
> vmlinux-2.6.32.10-0.4.99.25.62005-ppc64 vmcore
>
> Attaching the output of the above command..
>
>
> Using crash -d8 for above command,
> ========================
> <snip>
> <readmem: c00000000134ffa0, KVADDR, "memory section", 32, (FOE), 122f94b0>
> addr: c00000000134ffa0 paddr: 134ffa0 cnt: 32
> <readmem: c00000000134ffc0, KVADDR, "memory section", 32, (FOE), 122f94b0>
> addr: c00000000134ffc0 paddr: 134ffc0 cnt: 32
> <readmem: c00000000134ffe0, KVADDR, "memory section", 32, (FOE), 122f94b0>
> addr: c00000000134ffe0 paddr: 134ffe0 cnt: 32
> NOTE: page_hash_table does not exist in this kernel
>
> please wait... (gathering kmem slab cache data)
> <readmem: c0000000012fc718, KVADDR, "cache_chain", 8, (FOE), fffeff7f108>
> addr: c0000000012fc718 paddr: 12fc718 cnt: 8
> GETBUF(248 -> 1)
> FREEBUF(1)
> GETBUF(10344 -> 1)
> <readmem: c000000000d8af90, KVADDR, "kmem_cache buffer", 10344, (FOE), 1082f5d8>
> addr: c000000000d8af90 paddr: d8af90 cnt: 10344
> GETBUF(248 -> 2)
> FREEBUF(2)
> FREEBUF(1)
> GETBUF(10344 -> 1)
> <readmem: c0000000af715480, KVADDR, "kmem_cache buffer", 10344, (ROE), 1082f5d8>
> addr: c0000000af715480 paddr: af715480 cnt: 10344
>
> crash: seek error: kernel virtual address: c0000000af715480 type: "kmem_cache buffer"
> FREEBUF(1)
>
> crash: unable to initialize kmem slab cache subsystem
> =================================
>
> NOTE: Crash was able to read a vmcore on the same system that was
> manually generated using: echo c > /proc/sysrq-trigger.

The cause for seek errors depends upon the type
of dumpfile.

You didn't mention which type of dumpfile the vmcore
is, so I'll presume that it's either an ELF-format
kdump or a compressed kdump created by makedumpfile.

If it's an ELF-format kdump, seek errors are returned
by the read_netdump() function in netdump.c. If the
ELF header indicates that the physical address is contained
within one of the PT_LOAD segments, it calculates the
vmcore file offset from that, and simply does this:

if (lseek(nd->ndfd, offset, SEEK_SET) == -1)
return SEEK_ERROR;

But that's highly unlikely to fail, even if the lseek
offset is beyond the end of the file. And if it went
beyond the end of the vmcore file, the subsequent read()
would fail, and return a READ_ERROR instead. Also, if
none of the ELF header PT_LOAD segments contain the requested
physical address, it also would have returned a READ_ERROR.

So presuming that it's a compressed kdump, the seek error
most likely comes from here in read_diskdump() in diskdump.c:

if ((pfn >= dd->header->max_mapnr) || !page_is_ram(pfn))
return SEEK_ERROR;

where the requested physical address pfn values are larger
than the max_mapnr value advertised in the header.

When you do any "crash -d# ...", the dumpfile header will
be dumped first. What does that show?

Dave


--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
 
Old 04-21-2010, 06:09 AM
Pavan Naregundi
 
Default crash seek error, failed to read vmcore file

On Tue, 2010-04-20 at 09:14 -0400, Dave Anderson wrote:
> ----- "Pavan Naregundi" <pavan@linux.vnet.ibm.com> wrote:
>
> The cause for seek errors depends upon the type
> of dumpfile.
>
> You didn't mention which type of dumpfile the vmcore
> is, so I'll presume that it's either an ELF-format
> kdump or a compressed kdump created by makedumpfile.
>
> So presuming that it's a compressed kdump, the seek error
> most likely comes from here in read_diskdump() in diskdump.c:
>
> if ((pfn >= dd->header->max_mapnr) || !page_is_ram(pfn))
> return SEEK_ERROR;
>
> where the requested physical address pfn values are larger
> than the max_mapnr value advertised in the header.
>
> When you do any "crash -d# ...", the dumpfile header will
> be dumped first. What does that show?
>
> Dave


Dave,

Dumpfile is compressed kdump created by makedumpfile.

header shows the following values:
max_mapnr: 32768
block_shift: 16

Yes. Adding some debug printf's shows me that (pfn >=
dd->header->max_mapnr) fails.

For example: in the first seek error,
crash: seek error: kernel virtual address: c0000000af715480 type:
"kmem_cache buffer"

paddr: af715480 => pfn=44913

crash -d8 log: http://pastebin.com/qrCvyPfR

Thanks..Pavan



--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
 
Old 04-21-2010, 01:58 PM
Dave Anderson
 
Default crash seek error, failed to read vmcore file

----- "Pavan Naregundi" <pavan@linux.vnet.ibm.com> wrote:

> On Tue, 2010-04-20 at 09:14 -0400, Dave Anderson wrote:
> > ----- "Pavan Naregundi" <pavan@linux.vnet.ibm.com> wrote:
> >
> > The cause for seek errors depends upon the type
> > of dumpfile.
> >
> > You didn't mention which type of dumpfile the vmcore
> > is, so I'll presume that it's either an ELF-format
> > kdump or a compressed kdump created by makedumpfile.
> >
> > So presuming that it's a compressed kdump, the seek error
> > most likely comes from here in read_diskdump() in diskdump.c:
> >
> > if ((pfn >= dd->header->max_mapnr) || !page_is_ram(pfn))
> > return SEEK_ERROR;
> >
> > where the requested physical address pfn values are larger
> > than the max_mapnr value advertised in the header.
> >
> > When you do any "crash -d# ...", the dumpfile header will
> > be dumped first. What does that show?
> >
> > Dave
>
>
> Dave,
>
> Dumpfile is compressed kdump created by makedumpfile.
>
> header shows the following values:
> max_mapnr: 32768
> block_shift: 16
>
> Yes. Adding some debug printf's shows me that (pfn >=
> dd->header->max_mapnr) fails.
>
> For example: in the first seek error,
> crash: seek error: kernel virtual address: c0000000af715480 type:
> "kmem_cache buffer"
>
> paddr: af715480 => pfn=44913
>
> crash -d8 log: http://pastebin.com/qrCvyPfR
>
> Thanks..Pavan

OK, so the compressed dumpfile has exactly 32768 pages of physical
memory, or exactly 2GB. That being the case, the crash utility
will fail all readmem attempts above that value, and obviously
there is critical data above the artificial 2GB threshold.

The question at hand is why kdump is creating a truncated dumpfile
with a max_mapnr of 32768:

(1) makedumpfile determines the "max_mapnr" value based upon the
highest physical address found in any of the PT_LOAD segments
of the /proc/vmcore file on the secondary kernel.
(2) the /proc/vmcore PT_LOAD segments were pre-calculated during
the primary kernel's kdump initialization phase, based upon
the values found in the set of "/proc/device-tree/memory@xxx/reg"
files existing in the primary kernel, where the "xxx" is the
starting physical address of the memory region, and the "reg"
file in that directory contains the size of the memory region.

For whatever reason, those files showed a maximum of 2GB of
physical memory. (If you do not use makedumpfile, and then do
a "readelf -a" of the resultant vmcore file, you will see
the PT_LOAD segment values.)

Does the SLES11 vmlinux-2.6.32.10-0.4.99.25.62005-ppc64 kernel
contain this patch?:

http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=8be8cf5b47f72096e42bf88cc3a fff7a942a346c

author Brian King <brking@linux.vnet.ibm.com>
Mon, 19 Oct 2009 05:51:34 +0000 (05:51 +0000)
committer Benjamin Herrenschmidt <benh@kernel.crashing.org>
Fri, 30 Oct 2009 06:20:56 +0000 (17:20 +1100)
commit 8be8cf5b47f72096e42bf88cc3afff7a942a346c
tree 9adff0fa02123f48fbfa40abb55a5c01be8c2fa4
parent 6cff46f4bc6cc4a8a4154b0b6a2e669db08e8fd2
powerpc: Add kdump support to Collaborative Memory Manager

When running Active Memory Sharing, the Collaborative Memory Manager (CMM)
may mark some pages as "loaned" with the hypervisor. Periodically, the
CMM will query the hypervisor for a loan request, which is a single signed
value. When kexec'ing into a kdump kernel, the CMM driver in the kdump
kernel is not aware of the pages the previous kernel had marked as "loaned",
so the hypervisor and the CMM driver are out of sync. Fix the CMM driver
to handle this scenario by ignoring requests to decrease the number of loaned
pages if we don't think we have any pages loaned. Pages that are marked as
"loaned" which are not in the balloon will automatically get switched to "active"
the next time we touch the page. This also fixes the case where totalram_pages
is smaller than min_mem_mb, which can occur during kdump.

Signed-off-by: Brian King <brking@linux.vnet.ibm.com>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>

I ask because we also have an outstanding bugzilla that exhibits similar
behavior, where an abnormally small ppc64 vmcore file gets created
because there was only a single /proc/device-tree/memory@0 directory
file that showed just a small subset of the total physical memory.
Typically there are many of those "memory@xxx" directories, but in
the failing scenario, there was only one /proc/device-tree/memory@0
directory.

Anyway, there's (unproven) speculation that the kernel patch above
is related to the problem.

In any case, unfortunately, there's nothing can be done from the crash
utility's perspective.

Dave


--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
 
Old 04-22-2010, 10:07 AM
Pavan Naregundi
 
Default crash seek error, failed to read vmcore file

On Wed, 2010-04-21 at 09:58 -0400, Dave Anderson wrote:
> ----- "Pavan Naregundi" <pavan@linux.vnet.ibm.com> wrote:
>
> > On Tue, 2010-04-20 at 09:14 -0400, Dave Anderson wrote:
> > > ----- "Pavan Naregundi" <pavan@linux.vnet.ibm.com> wrote:
> > >
> > > The cause for seek errors depends upon the type
> > > of dumpfile.
> > >
> > > You didn't mention which type of dumpfile the vmcore
> > > is, so I'll presume that it's either an ELF-format
> > > kdump or a compressed kdump created by makedumpfile.
> > >
> > > So presuming that it's a compressed kdump, the seek error
> > > most likely comes from here in read_diskdump() in diskdump.c:
> > >
> > > if ((pfn >= dd->header->max_mapnr) || !page_is_ram(pfn))
> > > return SEEK_ERROR;
> > >
> > > where the requested physical address pfn values are larger
> > > than the max_mapnr value advertised in the header.
> > >
> > > When you do any "crash -d# ...", the dumpfile header will
> > > be dumped first. What does that show?
> > >
> > > Dave
> >
> >
> > Dave,
> >
> > Dumpfile is compressed kdump created by makedumpfile.
> >
> > header shows the following values:
> > max_mapnr: 32768
> > block_shift: 16
> >
> > Yes. Adding some debug printf's shows me that (pfn >=
> > dd->header->max_mapnr) fails.
> >
> > For example: in the first seek error,
> > crash: seek error: kernel virtual address: c0000000af715480 type:
> > "kmem_cache buffer"
> >
> > paddr: af715480 => pfn=44913
> >
> > crash -d8 log: http://pastebin.com/qrCvyPfR
> >
> > Thanks..Pavan
>
> OK, so the compressed dumpfile has exactly 32768 pages of physical
> memory, or exactly 2GB. That being the case, the crash utility
> will fail all readmem attempts above that value, and obviously
> there is critical data above the artificial 2GB threshold.
>
> The question at hand is why kdump is creating a truncated dumpfile
> with a max_mapnr of 32768:
>
> (1) makedumpfile determines the "max_mapnr" value based upon the
> highest physical address found in any of the PT_LOAD segments
> of the /proc/vmcore file on the secondary kernel.
> (2) the /proc/vmcore PT_LOAD segments were pre-calculated during
> the primary kernel's kdump initialization phase, based upon
> the values found in the set of "/proc/device-tree/memory@xxx/reg"
> files existing in the primary kernel, where the "xxx" is the
> starting physical address of the memory region, and the "reg"
> file in that directory contains the size of the memory region.
>
> For whatever reason, those files showed a maximum of 2GB of
> physical memory. (If you do not use makedumpfile, and then do
> a "readelf -a" of the resultant vmcore file, you will see
> the PT_LOAD segment values.)
>
> Does the SLES11 vmlinux-2.6.32.10-0.4.99.25.62005-ppc64 kernel
> contain this patch?:
>
> http://git.kernel.org/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=8be8cf5b47f72096e42bf88cc3a fff7a942a346c
>
> I ask because we also have an outstanding bugzilla that exhibits similar
> behavior, where an abnormally small ppc64 vmcore file gets created
> because there was only a single /proc/device-tree/memory@0 directory
> file that showed just a small subset of the total physical memory.
> Typically there are many of those "memory@xxx" directories, but in
> the failing scenario, there was only one /proc/device-tree/memory@0
> directory.
>
> Anyway, there's (unproven) speculation that the kernel patch above
> is related to the problem.
>
> In any case, unfortunately, there's nothing can be done from the crash
> utility's perspective.
>
> Dave

Thank you Dave.

Our SLES11 does not have the above patch you mentioned, but at the same
time system is not AMS enabled and CONFIG_CMM is also not set in the
config file..

This system also has /proc/device-tree/memory@0 dir only..

Regards..Pavan


--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
 
Old 04-22-2010, 01:31 PM
Dave Anderson
 
Default crash seek error, failed to read vmcore file

----- "Pavan Naregundi" <pavan@linux.vnet.ibm.com> wrote:

> >
> > In any case, unfortunately, there's nothing can be done from the crash
> > utility's perspective.
> >
> > Dave
>
> Thank you Dave.
>
> Our SLES11 does not have the above patch you mentioned, but at the same
> time system is not AMS enabled and CONFIG_CMM is also not set in the config file..
>
> This system also has /proc/device-tree/memory@0 dir only..

I don't have access to the original "problem" ppc64 machine,
but here I'm logged into another ppc64, where the memory
advertised in /proc/device-tree is as expected. It has
these file memory@xxx/reg files, showing a set of contiguous
memory chunks. The first one is 128MB, followed by a series
of 16MB chunks:

memory@0: 0000000000000000 0000000008000000
memory@8000000: 0000000008000000 0000000001000000
memory@9000000: 0000000009000000 0000000001000000
memory@a000000: 000000000a000000 0000000001000000
memory@b000000: 000000000b000000 0000000001000000
memory@c000000: 000000000c000000 0000000001000000
memory@d000000: 000000000d000000 0000000001000000
memory@e000000: 000000000e000000 0000000001000000
memory@f000000: 000000000f000000 0000000001000000
memory@10000000: 0000000010000000 0000000001000000
memory@11000000: 0000000011000000 0000000001000000
memory@12000000: 0000000012000000 0000000001000000
memory@13000000: 0000000013000000 0000000001000000
memory@14000000: 0000000014000000 0000000001000000
memory@15000000: 0000000015000000 0000000001000000
memory@16000000: 0000000016000000 0000000001000000
memory@17000000: 0000000017000000 0000000001000000
memory@18000000: 0000000018000000 0000000001000000
memory@19000000: 0000000019000000 0000000001000000
memory@1a000000: 000000001a000000 0000000001000000
memory@1b000000: 000000001b000000 0000000001000000
memory@1c000000: 000000001c000000 0000000001000000
memory@1d000000: 000000001d000000 0000000001000000
memory@1e000000: 000000001e000000 0000000001000000
memory@1f000000: 000000001f000000 0000000001000000
memory@20000000: 0000000020000000 0000000001000000
memory@21000000: 0000000021000000 0000000001000000
memory@22000000: 0000000022000000 0000000001000000
memory@23000000: 0000000023000000 0000000001000000
memory@24000000: 0000000024000000 0000000001000000
memory@25000000: 0000000025000000 0000000001000000
memory@26000000: 0000000026000000 0000000001000000
memory@27000000: 0000000027000000 0000000001000000
memory@28000000: 0000000028000000 0000000001000000
memory@29000000: 0000000029000000 0000000001000000
memory@2a000000: 000000002a000000 0000000001000000
memory@2b000000: 000000002b000000 0000000001000000
memory@2c000000: 000000002c000000 0000000001000000
memory@2d000000: 000000002d000000 0000000001000000
memory@2e000000: 000000002e000000 0000000001000000
memory@2f000000: 000000002f000000 0000000001000000
memory@30000000: 0000000030000000 0000000001000000
memory@31000000: 0000000031000000 0000000001000000
memory@32000000: 0000000032000000 0000000001000000
memory@33000000: 0000000033000000 0000000001000000
memory@34000000: 0000000034000000 0000000001000000
memory@35000000: 0000000035000000 0000000001000000
memory@36000000: 0000000036000000 0000000001000000
memory@37000000: 0000000037000000 0000000001000000
memory@38000000: 0000000038000000 0000000001000000
memory@39000000: 0000000039000000 0000000001000000
memory@3a000000: 000000003a000000 0000000001000000
memory@3b000000: 000000003b000000 0000000001000000
memory@3c000000: 000000003c000000 0000000001000000
memory@3d000000: 000000003d000000 0000000001000000
memory@3e000000: 000000003e000000 0000000001000000
memory@3f000000: 000000003f000000 0000000001000000
memory@40000000: 0000000040000000 0000000001000000
memory@41000000: 0000000041000000 0000000001000000
memory@42000000: 0000000042000000 0000000001000000
memory@43000000: 0000000043000000 0000000001000000
memory@44000000: 0000000044000000 0000000001000000
memory@45000000: 0000000045000000 0000000001000000
memory@46000000: 0000000046000000 0000000001000000
memory@47000000: 0000000047000000 0000000001000000
memory@48000000: 0000000048000000 0000000001000000
memory@49000000: 0000000049000000 0000000001000000
memory@4a000000: 000000004a000000 0000000001000000
memory@4b000000: 000000004b000000 0000000001000000
memory@4c000000: 000000004c000000 0000000001000000
memory@4d000000: 000000004d000000 0000000001000000
memory@4e000000: 000000004e000000 0000000001000000
memory@4f000000: 000000004f000000 0000000001000000
memory@50000000: 0000000050000000 0000000001000000
memory@51000000: 0000000051000000 0000000001000000
memory@52000000: 0000000052000000 0000000001000000
memory@53000000: 0000000053000000 0000000001000000
memory@54000000: 0000000054000000 0000000001000000
memory@55000000: 0000000055000000 0000000001000000
memory@56000000: 0000000056000000 0000000001000000
memory@57000000: 0000000057000000 0000000001000000
memory@58000000: 0000000058000000 0000000001000000
memory@59000000: 0000000059000000 0000000001000000
memory@5a000000: 000000005a000000 0000000001000000
memory@5b000000: 000000005b000000 0000000001000000
memory@5c000000: 000000005c000000 0000000001000000
memory@5d000000: 000000005d000000 0000000001000000
memory@5e000000: 000000005e000000 0000000001000000
memory@5f000000: 000000005f000000 0000000001000000
memory@60000000: 0000000060000000 0000000001000000
memory@61000000: 0000000061000000 0000000001000000
memory@62000000: 0000000062000000 0000000001000000
memory@63000000: 0000000063000000 0000000001000000
memory@64000000: 0000000064000000 0000000001000000
memory@65000000: 0000000065000000 0000000001000000
memory@66000000: 0000000066000000 0000000001000000
memory@67000000: 0000000067000000 0000000001000000
memory@68000000: 0000000068000000 0000000001000000
memory@69000000: 0000000069000000 0000000001000000
memory@6a000000: 000000006a000000 0000000001000000
memory@6b000000: 000000006b000000 0000000001000000
memory@6c000000: 000000006c000000 0000000001000000
memory@6d000000: 000000006d000000 0000000001000000
memory@6e000000: 000000006e000000 0000000001000000
memory@6f000000: 000000006f000000 0000000001000000
memory@70000000: 0000000070000000 0000000001000000
memory@71000000: 0000000071000000 0000000001000000
memory@72000000: 0000000072000000 0000000001000000
memory@73000000: 0000000073000000 0000000001000000
memory@74000000: 0000000074000000 0000000001000000
memory@75000000: 0000000075000000 0000000001000000
memory@76000000: 0000000076000000 0000000001000000
memory@77000000: 0000000077000000 0000000001000000
memory@78000000: 0000000078000000 0000000001000000
memory@79000000: 0000000079000000 0000000001000000
memory@7a000000: 000000007a000000 0000000001000000
memory@7b000000: 000000007b000000 0000000001000000

So the end of physical memory is at 7b000000 + 1000000, which
I can verify by running crash on the live system:

crash> eval 7b000000 + 0x1000000
hexadecimal: 7c000000 (1984MB)
decimal: 2080374784
octal: 17400000000
binary: 00000000000000000000000000000000011111000000000000 00000000000000
crash> eval 7c000000 / 64k
hexadecimal: 7c00 (31KB)
decimal: 31744
octal: 76000
binary: 00000000000000000000000000000000000000000000000001 11110000000000
crash> p num_physpages
num_physpages = $9 = 31744
crash>

and which matches what's in the kernel memory zone data:

crash> kmem -n
NODE SIZE PGLIST_DATA BOOTMEM_DATA NODE_ZONES
0 31744 c00000007bfdf280 c000000000a53c50 c00000007bfdf280
c00000007bfe1900
c00000007bfe3f80
MEM_MAP START_PADDR START_MAPNR
f000000000000000 0 0

ZONE NAME SIZE MEM_MAP START_PADDR START_MAPNR
0 DMA 31744 f000000000000000 0 0
1 Normal 0 0 0 0
2 Movable 0 0 0 0

...

So everything looks fine.

But if your system has just a single /proc/device-tree/memory@0
directory whose size doesn't match up with what the live kernel is
using, then that's the kernel bug.

> In any case, unfortunately, there's nothing can be done from the crash
> utility's perspective.

BTW, you can get minimal data from your truncated vmcore using
the --minimal switch that IBM contributed a while back:

# crash --minimal vmcore vmlinux

It at least offers the log, dis, rd, sym and eval commands, which may
or may not help. It's actually come in quite handy a few times.

Anyway, if you guys come up with a kernel fix, can you post it here
as well?

Thanks,
Dave





--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
 
Old 04-23-2010, 06:43 AM
Pavan Naregundi
 
Default crash seek error, failed to read vmcore file

On Thu, 2010-04-22 at 09:31 -0400, Dave Anderson wrote:
>
> Anyway, if you guys come up with a kernel fix, can you post it here
> as well?
>
> Thanks,
> Dave

Sure. I will do that..

Thanks..Pavan

--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
 

Thread Tools




All times are GMT. The time now is 06:48 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org