Re: system.map

Russell King
2005-07-13T11:28:46Z

On Wed, Jul 13, 2005 at 01:04:38PM +0200, Jan Engelhardt wrote:
> >> >Jul 11 12:18:48 localhost kernel: Inspecting /boot/System.map
> >> >Jul 11 12:18:48 localhost kernel: Loaded 28063 symbols from /boot/System.map.
> >> >Jul 11 12:18:48 localhost kernel: Symbols match kernel version 2.6.12.
> >> >Jul 11 12:18:48 localhost kernel: No module symbols loaded - kernel modules
> >> >notenabled.
> >
> >so whatever is spewing that is something else, but not the kernel.
>
> These four messages are the first four ones that appear after the boot loader
> set EIP to the kernel entry point. The first four printks, if you want so. And
> apparently, the first four appearing in dmesg, obviously.

They have absolutely nothing to do with the kernel, nor printk.
They're to do with klogd, the process which reads kernel messages and
writes them via a socket to syslogd.

If klogd is started with out -x, it will want to read the System.map
file and do the broken lookup of things it thinks are addresses in
kernel messages. This is not recommended practice. For kernels with
kallsyms enabled, klogd should be started with -x.

After your kernel has booted, login and run dmesg. You'll notice that
the first 4 lines are not as you expect.

--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core