Thanks, I built the latest version of crash, but was using an old version. Oops. Now I am past that problem. Unfortunately, now I get System.map and /dev/crash do not match! I probably built the kernel incorrectly for crash. I will investigate. -Marc On Mon, 2007-01-15 at 17:18 -0500, Dave Anderson wrote: > Marc Milgram wrote: > > 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 > > > > > What version of crash? The crash changelog refers to a fix > for that quite some time ago: > > 4.0-2.31 - Bumped crash-internal NR_CPUS for x86 and ia64; added a > warning > message to "recompile crash" and forced an initialization > failure > when the kernel's configured NR_CPUS is greater than the > maximum > allowed NR_CPUS value compiled into crash. > (maneesh@xxxxxxxxxx, anderson@xxxxxxxxxx) > > - Fix for initialization failure indicating a > kernel/memory-source > mismatch when x86 kernel configures its physical memory > start > address higher than the traditional 1MB starting point. > (anderson@xxxxxxxxxx) > > - Fix for kernels that have replaced the "system_utsname" > data > structure with contents of the "init_uts_ns" data > structure. > This fixes a "crash: cannot resolve system_utsname" > initialization > failure. (pbadari@xxxxxxxxxx, anderson@xxxxxxxxxx) > > ... > > > > -- > 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
