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 02-13-2012, 06:29 AM
Adil Mujeeb
 
Default crash tool not working

Thanks Dave for looking into the problem i am facing.

as suggested, i tried the things. Please see the output below:

--------------------------------------
hltncra110731:/home/adil # nm -Bn linux-2.6.32.12-0.7/vmlinux | grep _stext
ffffffff82000198 T _stext
hltncra110731:/home/adil # cat /proc/kallsyms | grep _stext
ffffffff82000198 T _stext
hltncra110731:/home/adil # cat /proc/kallsyms | grep -e
kernel_config_data -e cpu_possible_mask
ffffffff8281a660 R cpu_possible_mask
ffffffff82827aa0 r kernel_config_data
ffffffff82a16ec0 r __ksymtab_cpu_possible_mask
ffffffff82a28730 r __kcrctab_cpu_possible_mask
ffffffff82a322b6 r __kstrtab_cpu_possible_mask
hltncra110731:/home/adil #
--------------------------------------

--------------------------------------
hltncra110731:/home/adil # crash linux-2.6.32.12-0.7/vmlinux

crash 5.0.1
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"...
--------------------------------------
After the above output the machine got freezed. After waiting for
sometime, i have to hard reboot the machine. There is no crash log
generated.

I checked the CONFIG_STRICT_DEVMEM:
--------------------------------------
hltncra110731:/home/adil # zcat /proc/config.gz | grep CONFIG_STRICT_DEVMEM
# CONFIG_STRICT_DEVMEM is not set
hltncra110731:/home/adil #
--------------------------------------

My running kernel is the one which i have build:
--------------------------------------
adil@hltncra110731:~> uname -a
Linux hltncra110731 2.6.32.12-crash-crash #66 SMP Thu Feb 9 19:58:42
IST 2012 x86_64 x86_64 x86_64 GNU/Linux
adil@hltncra110731:~>
--------------------------------------

Does this problem something related to hardware / bios configuration?
I am providing the details, if by any chance it helps you:

--------------------------------------
adil@hltncra110731:~> cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz
stepping : 2
cpu MHz : 1203.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64
monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm lahf_lm
bogomips : 3591.03
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz
stepping : 2
cpu MHz : 1803.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 10
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
lm constant_tsc arch_perfmon pebs bts rep_good aperfmperf pni dtes64
monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm lahf_lm
bogomips : 3591.07
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:
--------------------------------------

Thanks.

Regards,
Adil

On Fri, Feb 10, 2012 at 9:33 PM, Dave Anderson <anderson@redhat.com> wrote:
>
>
> ----- Original Message -----
>>
>> And lastly, in all cases where a dumpfile cannot be read correctly,
>> first verify that crash works with the live system. *Presuming
>> t, and it was configured CONFIG_STRICT_DEVMEM, try this:
>
> Sorry -- cut-and-paste error -- I meant to state "Presuming that
> the kernel was *NOT* configured with CONFIG_STRICT_DEVMEM".
>
>>
>> * # crash ../linux-2.6.32.12-0.7/vmlinux
>>
>> If that comes up OK, then we can rule out more fundamental
>> failure causes.
>
> If you did configure the kernel with CONFIG_STRICT_DEVMEM,
> then you can try the supplied crash utility memory driver
> as a replacement for /dev/mem:
>
> *# cd <path-to>/crash-6.0.3/memory_driver
> *# make
> *...
> *# insmod crash.ko
>
> and then try running on the live system.
>
> Dave

--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
 
Old 02-13-2012, 07:46 PM
Dave Anderson
 
Default crash tool not working

----- Original Message -----
> Thanks Dave for looking into the problem i am facing.
>
> as suggested, i tried the things. Please see the output below:
>
> --------------------------------------
> hltncra110731:/home/adil # nm -Bn linux-2.6.32.12-0.7/vmlinux | grep
> _stext
> ffffffff82000198 T _stext
> hltncra110731:/home/adil # cat /proc/kallsyms | grep _stext
> ffffffff82000198 T _stext
> hltncra110731:/home/adil # cat /proc/kallsyms | grep -e
> kernel_config_data -e cpu_possible_mask
> ffffffff8281a660 R cpu_possible_mask
> ffffffff82827aa0 r kernel_config_data
> ffffffff82a16ec0 r __ksymtab_cpu_possible_mask
> ffffffff82a28730 r __kcrctab_cpu_possible_mask
> ffffffff82a322b6 r __kstrtab_cpu_possible_mask
> hltncra110731:/home/adil #
> --------------------------------------
>
> --------------------------------------
> hltncra110731:/home/adil # crash linux-2.6.32.12-0.7/vmlinux
>
> crash 5.0.1
> 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"...
> --------------------------------------
> After the above output the machine got freezed. After waiting for
> sometime, i have to hard reboot the machine. There is no crash log
> generated.
>
> I checked the CONFIG_STRICT_DEVMEM:
> --------------------------------------
> hltncra110731:/home/adil # zcat /proc/config.gz | grep
> CONFIG_STRICT_DEVMEM
> # CONFIG_STRICT_DEVMEM is not set
> hltncra110731:/home/adil #
> --------------------------------------
>
> My running kernel is the one which i have build:
> --------------------------------------
> adil@hltncra110731:~> uname -a
> Linux hltncra110731 2.6.32.12-crash-crash #66 SMP Thu Feb 9 19:58:42
> IST 2012 x86_64 x86_64 x86_64 GNU/Linux
> adil@hltncra110731:~>
> --------------------------------------

Your system is running a kernel with a utsname version "2.6.32.12-crash-crash",
but you used a file named "linux-2.6.32.12-0.7/vmlinux"? Are they exactly
the same kernel?

Also, even though you're back to using crash-5.0.1 again, I afraid I can't even
speculate as to what would cause the machine to freeze, nor have I ever seen
such a thing happen before. Perhaps the /dev/mem driver read something it
should not have based upon a faulty virtual address? I don't know...

>
> Does this problem something related to hardware / bios configuration?
> I am providing the details, if by any chance it helps you:

Sorry no, that doesn't help. If you can't even get crash running
on a live system, then I'm running out of suggestions.

Dave





--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
 
Old 02-14-2012, 05:41 AM
Adil Mujeeb
 
Default crash tool not working

Hi Dave,

On Tue, Feb 14, 2012 at 2:16 AM, Dave Anderson <anderson@redhat.com> wrote:
>
>
> ----- Original Message -----
>> Thanks Dave for looking into the problem i am facing.
>>
>> as suggested, i tried the things. Please see the output below:
>>
>> --------------------------------------
>> hltncra110731:/home/adil # nm -Bn linux-2.6.32.12-0.7/vmlinux | grep
>> _stext
>> ffffffff82000198 T _stext
>> hltncra110731:/home/adil # cat /proc/kallsyms | grep _stext
>> ffffffff82000198 T _stext
>> hltncra110731:/home/adil # cat /proc/kallsyms | grep -e
>> kernel_config_data -e cpu_possible_mask
>> ffffffff8281a660 R cpu_possible_mask
>> ffffffff82827aa0 r kernel_config_data
>> ffffffff82a16ec0 r __ksymtab_cpu_possible_mask
>> ffffffff82a28730 r __kcrctab_cpu_possible_mask
>> ffffffff82a322b6 r __kstrtab_cpu_possible_mask
>> hltncra110731:/home/adil #
>> --------------------------------------
>>
>> --------------------------------------
>> hltncra110731:/home/adil # crash linux-2.6.32.12-0.7/vmlinux
>>
>> crash 5.0.1
>> 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"...
>> --------------------------------------
>> After the above output the machine got freezed. After waiting for
>> sometime, i have to hard reboot the machine. There is no crash log
>> generated.
>>
>> I checked the CONFIG_STRICT_DEVMEM:
>> --------------------------------------
>> hltncra110731:/home/adil # zcat /proc/config.gz | grep
>> CONFIG_STRICT_DEVMEM
>> # CONFIG_STRICT_DEVMEM is not set
>> hltncra110731:/home/adil #
>> --------------------------------------
>>
>> My running kernel is the one which i have build:
>> --------------------------------------
>> adil@hltncra110731:~> uname -a
>> Linux hltncra110731 2.6.32.12-crash-crash #66 SMP Thu Feb 9 19:58:42
>> IST 2012 x86_64 x86_64 x86_64 GNU/Linux
>> adil@hltncra110731:~>
>> --------------------------------------
>
> Your system is running a kernel with a utsname version "2.6.32.12-crash-crash",
> but you used a file named "linux-2.6.32.12-0.7/vmlinux"? *Are they exactly
> the same kernel?

Yes they are same.

> Also, even though you're back to using crash-5.0.1 again, I afraid I can't even
> speculate as to what would cause the machine to freeze, nor have I ever seen
> such a thing happen before. *Perhaps the /dev/mem driver read something it
> should not have based upon a faulty virtual address? *I don't know...

Sorry that was my mistake.
i tried with the new crash binaries and result is same. machine is
freezed and i have to hard reboot.
----------------
hltncra110731:/home/adil # ./crash-6.0.3/crash linux-2.6.32.12-0.7/vmlinux

crash 6.0.3
Copyright (C) 2002-2012 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.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 "x86_64-unknown-linux-gnu"...
----------------

I checked the system, no display on screen and keyboard lights are
blinking and no dump generated. No option but to hard reboot.

>>
>> Does this problem something related to hardware / bios configuration?
>> I am providing the details, if by any chance it helps you:
>
> Sorry no, that doesn't help. *If you can't even get crash running
> on a live system, then I'm running out of suggestions.

Even i am giving up now
i should do my work on that machine where crash / kdump is working.
Thanks a lot for all your inputs and showing your patience on my queries

Thanks,
Adil

>
> Dave
>
>
>
>

--
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 07:31 PM.

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