Re: multiple oopses with IRDA

[Keith Owens]

On Tue, 04 Jan 2000 11:57:51 +0100, 
Gregor Suhr <[e-mail]> wrote:
>i tried to use my Tekram IR-210B with 2.3.35, but then i try to connect
>to my handy or LaserJet the system hangs.
>
>ksymoops 0.7c on i686 2.3.35.  Options used
>     -v /boot/vmlinuz-devel (specified)
>     -k /proc/ksyms (default)
>     -l /proc/modules (default)
>     -o /lib/modules/2.3.35/ (default)
>     -m /usr/src/linux/System.map (default)
>
>Error (pclose_local): read_nm_symbols pclose failed 0x100
>Warning (read_vmlinux): no kernel symbols in vmlinux, is /boot/vmlinuz-devel a valid vmlinux file?

You cannot feed a vmlinuz (compressed) file to ksymoops, it has to be
the uncompressed vmlinux file from /usr/src/linux.

>Warning (compare_maps): ksyms_base symbol agp_allocate_memory_R__ver_agp_allocate_memory not found in System.map.  Ignoring ksyms_base entry

Lots of errors which say that you have messed up your compile, in
particular the genksyms data is all wrong.  It is not worth looking at
the oops until the symbols are fixed.  Unfortunately the current
Makefiles do not handle genksyms correctly, you need to do this to fix
the problem :-

(1) Save your current config, "mv .config .."
(2) make mrproper, make clean does not clean up genksyms data correctly.
(3) Restore your config, "mv ../.config ."
(4) make oldconfig
(5) make dep clean bzImage modules
(6) Double check that the new kernel has no corrupt genksym entries,
    "nm /usr/src/linux/vmlinux | grep __ver_" should find no __ver_
    symbols.
(7) Clean out the old modules, "rm -rf /lib/modules/2.3.35".  Not
    really necessary but it removes any question about old modules
    lying around.
(8) Install the new kernel and modules, reboot.

If you can reproduce the error and ksymoops does not give any errors or
warning (this time feed it vmlinux, not vlinuz), then mail the new oops
to the list.