On Fri, 07 Feb 2003 09:37:59 -0600,
"Foris, Jim (MED)" <[EMAIL PROTECTED]> wrote:
>>>[1]kdb> bt
>>>ESP EIP Function (args)
>>>0xc46cde28 0xc01ed880 <unknown>+0xc01ed880
>>> kernel <unknown> 0x0 0x0 0x0
>>>0xc46cde2c 0xc46cdde0 <unknown>+0xc46cdde0
>>> kernel <unknown> 0x0 0x0 0x0
>>
>>
>> That is wierd. grep kallsyms System.map and insmod -nm some_module_name.
>
>c03a01a3 A __start___kallsyms
>c03a01a3 A __stop___kallsyms
There is the problem, your kernel has no data in the kallasyms section
(__start___kallsyms == __stop___kallsyms). The empty kernel kallsyms
in turn stops modules from loading kallsyms. This is a build problem
with your system, it works for other people.
Make sure that you have the current version of modules (2.4.22), that
your build is not overriding the KALLSYMS environment variable and that
kallsyms is being run as part of the vmlinux build. If there is no
obvious problem, edit the top level Makefile and delete this line
@rm -f $(TMPPREFIX).tmp_vmlinux* $(TMPPREFIX).tmp_kallsyms*
make vmlinux then ls -l .tmp_vmlinux* .tmp_kallsyms*
