----- Original Message ----- > > > ----- Original Message ----- > > Dave, > > > > On both RHEL 5.2 X64 and RHEL 5.5 X64, it showed: (Additional > > argument such as System.map does not make any difference.) > > > > # crash vmlinux-2.6.5-7.321-bigsmp dump-pts02504 > > ... > > WARNING: machine type mismatch: > > crash utility: X86_64 > > vmlinux-2.6.5-7.321-bigsmp: X86 > > > > crash: vmlinux-2.6.5-7.321-bigsmp: not a supported file format > > Right, as the message states, you're trying to analyze a 32-bit > x86 vmlinux/vmcore with the x86_64 version of the crash utility. > > So just get the 32-bit x86 crash utility. If you can't find > one, then you can try building one on your x86_64 host: > > $ wget http://people.redhat.com/anderson/crash-6.1.4.tar.gz > ... > $ cd crash-6.1.4 > $ make target=X86 > ... > $ ./crash vmlinux-2.6.5-7.321-bigsmp dump-pts02504 I missed the part below about the Kerntypes file, which would also have to be added to the command line above. I forgot about Suse's use of "Kerntype" files as an optional source of debuginfo data. And if the vmlinux-2.6.5-7.321-bigsmp file is not exactly the kernel that crashed, then you can try adding the System.map file onto the command line as well. Although I don't know if that's possible with this Suse setup. Surely somebody this mailing list can be of some help here? Dave > > If the build fails, you can wget the crash-6.1.4-0.src.rpm > file from the same location, and the rpmbuild -ba will alert > you to the additional packages you need. > > Dave > > > > > > > > > > > On an RHEL 4.7 X86, it showed: > > > > # crash vmlinux-2.6.5-7.321-bigsmp dump-pts02504 > > ... > > crash: vmlinux-2.6.5-7.321-bigsmp: no debugging data available > > > > > > # crash vmlinux-2.6.5-7.321-bigsmp dump-pts02504 > > System.map-2.6.5-7.321-bigsmp > > ... > > crash: vmlinux-2.6.5-7.321-bigsmp: no debugging data available > > > > > > # crash vmlinux-2.6.5-7.321-bigsmp dump-pts02504 > > Kerntypes-2.6.5-7.321-bigsmp > > ... > > crash: cannot resolve "_stext" > > > > > > Thanks. > > > > Eugene > > > > > > -----Original Message----- > > From: Dave Anderson [mailto:anderson@xxxxxxxxxx] > > Sent: Tuesday, March 05, 2013 5:22 PM > > To: Ku, Eugene > > Cc: Discussion list for crash utility usage, maintenance and > > development > > Subject: Re: SLES 9 Dump > > > > > > > > ----- Original Message ----- > > > Dave, > > > > > > Thank you for getting back to me so quickly. > > > > > > I have tried different ways to start crash but none is working. > > > I > > > have downloaded kernel-bigsmp-2.6.5-7.321.i586.rpm from Novell to > > > match the version of the dump. This package includes the > > > following > > > files: > > > > > > config-2.6.5-7.321-bigsmp System.map-2.6.5-7.321-bigsmp > > > Kerntypes-2.6.5-7.321-bigsmp vmlinux-2.6.5-7.321-bigsmp > > > symtypes-2.6.5-7.321-bigsmp vmlinuz-2.6.5-7.321-bigsmp > > > symvers-2.6.5-7.321-i386-bigsmp > > > > > > I don't believe Novell provides a kernel-debuginfo package for > > > SLES > > > 9 > > > or earlier version and I could not find it on their web site. > > > > > > What I have tried so far are all done on RHEL systems because > > > SLES > > > 9 > > > does not come with crash. Do I need to run crash against an SLES > > > dump on a compatible SLES system? A compatible system I mean the > > > same architecture. When I tried it on RHEL X64, it complained > > > machine type mismatch. > > > > What is the mismatch error message? > > > > Dave > > > > -- > Crash-utility mailing list > Crash-utility@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/crash-utility > -- Crash-utility mailing list Crash-utility@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/crash-utility