Excerpt from KSYMOOPS.LOG:
>You did not tell me where to find symbol information. I will assume
>that the log matches the kernel and modules that are running right now
>and I'll use the default options above for symbol resolution.
>If the current kernel and/or modules do not match the log, you can get
>more accurate output by telling me the kernel version and where to find
>map, modules, ksyms etc. ksymoops -h explains the options.
>EIP: c206028e <END_OF_CODE+3462e/????>
^^^^^^^^^^^
You managed to confuse ksymoops quite a bit. Seems that it wasnt able to
read the modules symbol information - of course not, the module wasn't
properly loaded at that time, it crashed insmod while loading. Maybe
produce a symbol map for the module, by using insmod -m ? This together
with the call trace from the actual oops might help..
Gruss,
Matthias
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/