Olaf Hering wrote: > crash 4.0-3.9 can not read a dump file from an ia64 box running 2.6.5. > Is this supposed to work? > > crash -s boot/System.map-2.6.5-7.267-sn2 boot/Kerntypes-2.6.5-7.267-sn2 dump.3 Well, if it did work, it would be news to me. I've certainly never run crash with a "Kerntypes" file as a substitute for a -g built vmlinux file. A few months ago, one of the SGI guys had contacted me off-line about putting in support for the use of LKCD kerntypes files, in fact I believe he even sent a prototype patch, but I haven't heard from him since. Anyway, I'm amazed that it got as far as it did. Noting the LKCD error message: crash: LKCD machine specific dump header doesn't match crash version: 3b200 761f8 crash: traceback of currently executing threads may not work (and I have no idea what the ": 3b200 761f8" at the end of the string came from, as it's not in the crash source code...) Perhaps that's the reason for the eventual lseek errors that occur when the first reads from the dumpfile are attempted. But the LKCD error message came from a relatively new LKCD-only file called lkcd_fix_mem.c, which Troy Heber posted specifically for ia64 LKCD support. But I don't have any insights into it, I just take his LKCD patches on blind faith. Dave > > > crash: diskdump: dump does not have panic dump header > crash: diskdump: dump does not have panic dump header > dump_header: > dh_magic_number: a8190173618f23ed (DUMP_MAGIC_NUMBER) > dh_version: 9 (LKCD_DUMP_V9) > dh_header_size: 742 > dh_dump_level: 3 (DUMP_LEVEL_HEADER|DUMP_LEVEL_KERN) > dh_page_size: 16384 > dh_memory_size: 20993310 > dh_memory_start: e000000000000000 > dh_memory_end: a8190173618f23ed > dh_num_pages: 336091 > dh_panic_string: sysrq > dh_time: Mon Aug 21 08:32:07 2006 > dh_utsname_sysname: Linux > dh_utsname_nodename: cognac > dh_utsname_release: 2.6.5-7.267-sn2 > dh_utsname_version: #1 SMP Wed Jun 21 10:50:51 UTC 2006 > dh_utsname_machine: ia64 > dh_utsname_domainname: > dh_current_task: e00009b0287a8000 > dh_dump_compress: 2 (DUMP_COMPRESS_GZIP) > dh_dump_flags: 80000004 () > dh_dump_device: 0 > crash: LKCD machine specific dump header doesn't match crash version: 3b200 761f8 > crash: traceback of currently executing threads may not work > > gdb boot/Kerntypes-2.6.5-7.267-sn2 > GNU gdb 6.1 > Copyright 2004 Free Software Foundation, Inc. > GDB 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. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "ia64-unknown-linux-gnu"... > GETBUF(248 -> 0) > GETBUF(1500 -> 1) > > please wait... (patching 20920 gdb minimal_symbol values) ^M ^M FREEBUF(1) > FREEBUF(0) > <readmem: a0000001005fa0d0, KVADDR, "kernel_config_data", 32768, (ROE), 60000000002e8310> > crash: seek error: kernel virtual address: a0000001005fa0d0 type: "kernel_config_data" > WARNING: cannot read kernel_config_data > <readmem: a000000100acea80, KVADDR, "xtime", 16, (FOE), 600000000006fc70> > crash: seek error: kernel virtual address: a000000100acea80 type: "xtime" > > -- > 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
