On Fri, 6 Jul 2001 23:52:20 -0500,
Nathan Straz <nstraz@xxxxxxx> wrote:
>I was able to grab the system state using magic sysrq and Keith sent me
>a fresh copy of ksymoops that is supposed to handle it. I have included
>the output below, but I don't trust it. Keith, I'm using mangled kernel
>versions which I don't think depmod or ksymoops handles correctly. i.e.
>I specify depfile, generic_stringfile, path[toplevel], etc in
>ksymoops 2.4.2 on i686 2.4.3-SGI_XFS_1.0.1smp. Options used
> -V (default)
> -k /proc/ksyms (default)
> -l /proc/modules (default)
> -o /lib/modules/2.4.3-SGI_XFS_1.0.1smp/ (default)
> -m /usr/src/linux/System.map (default)
>Error (expand_objects): cannot stat(/lib/qla1280.o) for qla1280
>Error (expand_objects): cannot stat(/lib/ncr53c8xx.o) for ncr53c8xx
>Error (expand_objects): cannot stat(/lib/sd_mod.o) for sd_mod
>Error (expand_objects): cannot stat(/lib/scsi_mod.o) for scsi_mod
>Error (pclose_local): find_objects pclose failed 0x100
/proc/ksyms says that the modules were loaded from /lib but ksymoops
cannot find them there. I guess that you are using initrd so /lib is
pointing at the ramdisk /lib, not the real /lib. As a workaround,
grep -v __insmod /proc/ksyms > /var/tmp/ksyms
and run ksymoops with -k /var/tmp/ksyms. It will default to looking in
/lib/modules/2.4.3-SGI_XFS_1.0.1smp/ for module objects instead of
using the misleading names in /proc/ksyms.
>Error (regular_file): read_system_map stat /usr/src/linux/System.map failed
That is more of a problem. Without a valid System.map, ksymoops can
only report using the symbols in ksyms. /proc/ksyms is not complete so
the decoded oops has misleading names like pagebuf_unlock+68ecf/6cdbc.
Run ksymoops with -m pointing to your current System.map.