Hi Dave I use crash all the time on SLES dumps. I still have problems with the SLAB stuff, even with 5.0. "crash: unable to initialize kmem slab cache subsystem" Is there a fix for this or am I missing something in creating the debug vmlinux kernel crash 5.0.0 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 "x86_64-unknown-linux-gnu"... WARNING: could not find MAGIC_START! please wait... (gathering kmem slab cache data)\ crash: seek error: kernel virtual address: 1082fffea00 type: "kmem_cache buffer" ----> crash: unable to initialize kmem slab cache subsystem SYSTEM MAP: map.0 DEBUG KERNEL: vmlinux (2.6.5-7.244-smp) DUMPFILE: dump.0 CPUS: 4 DATE: Sat Feb 6 12:43:37 2010 UPTIME: 213503982289 days, 20:38:24 LOAD AVERAGE: 260.75, 259.77, 258.95 TASKS: 1167 NODENAME: linuscs73 RELEASE: 2.6.5-7.252-smp VERSION: #2 SMP Mon Jun 22 13:11:57 PDT 2009 MACHINE: x86_64 (2666 Mhz) MEMORY: 32.7 GB PANIC: "manual" PID: 8741 COMMAND: "lkcd_config" TASK: 107ed5d6b40 [THREAD_INFO: 1024f3ac000] CPU: 2 STATE: TASK_RUNNING (PANIC) Thanks Laurence ----- Original Message ----- From: "Chandan12 K" <chandan12.k(a)tcs.com&gt; To: "Discussion list for crash utility usage, maintenance and development" <crash-utility(a)redhat.com&gt; Cc: "Discussion list for crash utility usage, maintenance and development" <crash-utility(a)redhat.com&gt;, crash-utility-bounces(a)redhat.com Sent: Tuesday, February 9, 2010 8:59:01 AM Subject: Re: [Crash-utility] Reasons why kdump isn't activated First you need to figure out the reason of your system failure. If its complete power failure, then kexec wont be able to load a new kernel in current context. Secondly, is kexec properly configured in your system? Chandan Kumar Tata Consultancy Services Mailto: chandan12.k(a)tcs.com Website: http://www.tcs.com ____________________________________________ Experience certainty. IT Services Business Solutions Outsourcing ____________________________________________ From: Gallus <gall.cwpl(a)gmail.com&gt; To: "Discussion list for crash utility usage, maintenance and development" <crash-utility(a)redhat.com&gt; Date: 02/09/2010 07:10 PM Subject: [Crash-utility] Reasons why kdump isn't activated Sent by: crash-utility-bounces(a)redhat.com Hi, what can be any reasons why kdump mechanism isn't triggered? My first though is that it means a hardware failure, not a kernel problem. Regards, Mariusz Gniazdowski -- Crash-utility mailing list Crash-utility(a)redhat.com https://www.redhat.com/mailman/listinfo/crash-utility =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you -- Crash-utility mailing list Crash-utility(a)redhat.com https://www.redhat.com/mailman/listinfo/crash-utility