System-kernel-versionxx.map not getting loaded from /boot but only when copied to / Reproducible: Always Steps to Reproduce: 1. Copy NOT a symlink , but copy it, System.map-kernel-version.map in / to fix 2. 3. Actual Results: the Kerenel at boot up detects the system.map and loads it Expected Results: it should work and be detected in /boot but it is not I'm not sure how this was overlooked but the System.map does not get loaded in Gentoo in /boot and the System-kernel-version.map needs to be copied to / in order to get loaded and working properly. Syslog will report this happening in the log /var/log/messages and syslog
System.map is essentially useless. See the other bug. *** This bug has been marked as a duplicate of 97290 ***
System.map is a "map" of your kernel. It contains info about the entry points of the functions you compiled into your kernel, and de-bug information. The kernel itself knows the addresses and entry-points, but that file is needed for some programs which need info about kernel entry points. I'm sorry but someone is terribly wrong in saying that the System.map is useless.
Seems like you need to read the other bug more carefully. <snip> System.map is never used by the kernel. It is generated at compile time but unused. System.map is used by tools like sysklogd and ksymoops. However, both those tools are now pretty useless as the kernel automatically resolves and maps the addresses to names in its own error messages, even without accessing the map-file. </snip> That's what a Gentoo kernel maintainer has to say to this. The "problem" with the message you are seeing in the log is explained in Bug 97290 as well. *** This bug has been marked as a duplicate of 97290 ***
Closing this bug.
I have a correct compiled kernel and correct /paths for /usr/src and the kernel is not finding System.map either if it was finding it in either /usr/src/linux or /boot then the Kernel dmesg at bootup would not mention that it can't find it in the logs /var/log/messages or syslog The fact that I do have things correctly built on this box and the kernel is saying it can't find it, shows that something is not correct in Gentoo over this and needs looking at. Someone mentions this below: System.map is only used in case of a kernel oops. The file /boot/System.map is identical to the one located at /usr/src/linux/System.map and klogd/syslogd has this path hardcoded and will check for it if /boot is not mounted. Yes it might be hardcoded in BUT that still does not excuse the fact the kernel says it can't find the System.map My kernel logs are not saying it can't find it in any SPECIFIC location it is just saying it can't find it, as in anywhere, both /boot and /usr/src/linux the kernel is not finding it in either locations. P.S. I read the other bug and nothing there applies to what I am saying here I have all these areas covered and my system correct therefore IF it is correct then the kernel detects the System.map at boot up like anything other Linux distro IF it is not then what has Gentoo done that it won't? Are we saying Gentoo has done something special over other Linux distros so that the System.map is being overlooked?
It might not be used much but that does not make it useless, and again I have it in /usr/src/linux and in /boot but locations are reported as not being found in the logs this is not correct. So I hope your not going to tell me the bug is closed and we don't need it anymore, and if so what has Gentoo replaced with this? Thank you
The linux kernel does not depend on *any* external files at all. System.map is used by some other tools. You state that your kernel says it can't find System map. Please elaborate - where does it say this? How? In what context? What sequence of events causes it to tell you this?
No response from user. Reopen once you have answered the questions in comment #7.
