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 08-09-2010, 12:59 AM
Mark Goodwin
 
Default crash fails to start with RHEL4/ia64 vmcore

[re-send now that I'm subscribed]

Any help would be appreciated - I have an IA64 vmcore
from a RHEL4 system, and crash doesn't like it :

# file vmcore
vmcore: ELF 64-bit LSB core file IA-64, version 1 (SYSV), SVR4-style, from 'vmlinux'

# crash usr__2.6.9-89.EL/lib/debug/lib/modules/2.6.9-89.EL/vmlinux vmcore

crash 5.0.6
.. copyright stuff omitted ..
GNU gdb (GDB) 7.0
...
WARNING: invalid linux_banner pointer: 8a653075c6c36178
crash: usr__2.6.9-89.EL/lib/debug/lib/modules/2.6.9-89.EL/vmlinux and vmcore do
not match!

Usage: ...

I've tried hacking the 5.0.6 src to avoid the linux_banner check,
but it just breaks further down the track :

WARNING: boot command line memory limit: 59ab0c85d99b2fa9
crash: ia64_VTOP(b929ee8856a6b891): unexpected region 5 address

So I'm stuck. The customer assures me the vmcore is from their 2.6.9-89.EL
ia64 system. At the very least it would help if I could extract some or all
of the dmesg buffer.

Dave, the vmcore is on an internal Red Hat RHEL4/ia64 system - I can
give you access details off-list if you think it will help.

Thanks
-- Mark Goodwin


--
Crash-utility mailing list
Crash-utility@redhat.com
https://www.redhat.com/mailman/listinfo/crash-utility
 
Old 08-09-2010, 12:45 PM
Dave Anderson
 
Default crash fails to start with RHEL4/ia64 vmcore

----- "Mark Goodwin" <mgoodwin@redhat.com> wrote:

> [re-send now that I'm subscribed]
>
> Any help would be appreciated - I have an IA64 vmcore
> from a RHEL4 system, and crash doesn't like it :
>
> # file vmcore
> vmcore: ELF 64-bit LSB core file IA-64, version 1 (SYSV), SVR4-style, from 'vmlinux'
>
> # crash usr__2.6.9-89.EL/lib/debug/lib/modules/2.6.9-89.EL/vmlinux vmcore
>
> crash 5.0.6
> .. copyright stuff omitted ..
> GNU gdb (GDB) 7.0
> ...
> WARNING: invalid linux_banner pointer: 8a653075c6c36178
> crash: usr__2.6.9-89.EL/lib/debug/lib/modules/2.6.9-89.EL/vmlinux and vmcore do not match!
> Usage: ...
>
> I've tried hacking the 5.0.6 src to avoid the linux_banner check,
> but it just breaks further down the track :
>
> WARNING: boot command line memory limit: 59ab0c85d99b2fa9
> crash: ia64_VTOP(b929ee8856a6b891): unexpected region 5 address
>
> So I'm stuck. The customer assures me the vmcore is from their 2.6.9-89.EL
> ia64 system. At the very least it would help if I could extract some or all
> of the dmesg buffer.

It appears that there's simply a mismatch between the vmlinux and vmcore file.
If it's not a compressed diskdump vmcore, you can verify that easily enough by
just doing:

$ strings vmlinux | grep "Linux version"
$ strings vmcore | grep "Linux version"

and comparing the output.

> Dave, the vmcore is on an internal Red Hat RHEL4/ia64 system - I can
> give you access details off-list if you think it will help.

Sure -- if the strings output doesn't give you a clue, please point me to the files.

Thanks,
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 08:36 PM.

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