system.map
After compiling new kernel, it doesn`t load System.map file. In kernel messages I can find:
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.
I have support for modules compiled.
I add config file of my kenrel.
http://sniffergg.port5.com/config.txt
uname -a shows
conexion1:~# uname -a Linux conexion1 2.6.12-cko2nexus #1 Fri Jul 8 18:24:04 CEST 2005 i686 GNU/Linux
I installed kernel using command installkernel
conexion1:~# installkernel Usage: installkernel <version> <zImage> <System.map> <directory>
to make sure that System.map file will match the kernel version.
Please help me,
Jacek Jablonski
Quoted 9 lines
After compiling new kernel, it doesn`t load System.map file. In kernel messages I can find:
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 modulesnotenabled.
I get the same, but somehow, my symbols are loaded. (When it oopses, derefs a NULL pointer, etc. for example.)
(My syms file is at /boot/System.map-uname -r and "works" equally well to yours.)
Jan Engelhardt
A message that is not in the archive (sent off-list or not yet received): [email protected]
Dnia środa, 13 lipca 2005 12:44, napisałeś:
Quoted 28 lines
In standard distribution kernel (2.4), it loaded some symblos:
Inspecting/boot/System.map-2.4.27-2-k7Jul 6 09:32:37 localhost kernel: Loaded 17895 symbols from /boot/System.map-2.4 .27-2-k7. Jul 6 09:32:37 localhost kernel: Symbols match kernel version 2.4.27. Jul 6 09:32:37 localhost kernel: Loaded 618 symbols from 21 modules.Maybe the link will help:
http://www.linuxsa.org.au/pipermail/linuxsa/2003-December/063669.htmlQuoted 17 lines
Quoted 8 lines
After compiling new kernel, it doesn`t load System.map file. In kernel messages I can find:
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.I get the same, but somehow, my symbols are loaded. (When it oopses, derefs a NULL pointer, etc. for example.)
(My syms file is at
/boot/System.map-uname -rand "works" equally well to yours.)Jan Engelhardt
Quoted 11 lines · Jan Engelhardt
Quoted 8 lines
After compiling new kernel, it doesn`t load System.map file. In kernel messages I can find:
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 modulesnotenabled.
I get the same, but somehow, my symbols are loaded. (When it oopses, derefs a NULL pointer, etc. for example.)
the kernel does not read or use system.map.
so whatever is spewing that is something else, but not the kernel.
Quoted 7 lines
Quoted 5 lines
Quoted 5 lines
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 modulesnotenabled.
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.
Maybe some more info helps (from /var/log/boot.msg, a copy of dmesg):
Inspecting /boot/System.map-2.6.13-TP1 Loaded 24854 symbols from /boot/System.map-2.6.13-TP1. Symbols match kernel version 2.6.13. No module symbols loaded - kernel modules not enabled. klogd 1.4.1, log source = ksyslog started. 20: 00000000000e8000 - 00000000000ea000 (reserved) <4> BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) .... BIOS-lots of more <5>255MB LOWMEM available. <7>On node 0 totalpages: 65520 <7> DMA zone: 4096 pages, LIFO batch:1 ...
klogd.
Jan Engelhardt
Quoted 11 lines · Jan Engelhardt
Quoted 7 lines
Quoted 5 lines
Quoted 5 lines
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 modulesnotenabled.
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.
Signature · 3 lines
Russell King Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/ maintainer of: 2.6 Serial core
Quoted 11 lines · Jan Engelhardt
Quoted 7 lines
Quoted 5 lines
Quoted 5 lines
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 modulesnotenabled.
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.
do they actually appear in dmesg?
Quoted 2 lines
Maybe some more info helps (from
/var/log/boot.msg, a copy of dmesg):
or... is syslog itself printing this into the log at startup?
Quoted 2 lines
Inspecting /boot/System.map-2.6.13-TP1