<!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html> Marc Milgram wrote: <blockquote TYPE=CITE>I tried to use crash on a 2.6.19.2 dump, but it failed with the following complaint: crash: cannot resolve "system_utsname" I found that there is no longer a symbol by that name in 2.6.19.2. It appears to be referenced by init_urs_ns->name, but I didn't investigate fully. The important issue for me is that crash doesn't work. -Marc <tt></tt> </blockquote> <tt>What version of crash? The crash changelog refers to a fix</tt> <tt>for that quite some time ago:</tt><tt></tt> <tt>4.0-2.31 - Bumped crash-internal NR_CPUS for x86 and ia64; added a warning</tt> <tt> message to "recompile crash" and forced an initialization failure</tt> <tt> when the kernel's configured NR_CPUS is greater than the maximum</tt> <tt> allowed NR_CPUS value compiled into crash.</tt> <tt> (maneesh@in.ibm.com, anderson@redhat.com)</tt><tt></tt> <tt> - Fix for initialization failure indicating a kernel/memory-source</tt> <tt> mismatch when x86 kernel configures its physical memory start</tt> <tt> address higher than the traditional 1MB starting point.</tt> <tt> (anderson@redhat.com)</tt><tt></tt> <tt> - Fix for kernels that have replaced the "system_utsname" data</tt> <tt> structure with contents of the "init_uts_ns" data structure.</tt> <tt> This fixes a "crash: cannot resolve system_utsname" initialization</tt> <tt> failure. (pbadari@us.ibm.com, anderson@redhat.com)</tt> <tt> </tt> <tt> ...</tt> <tt></tt> <tt></tt> </html>