For the record, though the error message from klogd is both misleading and (for some) a bit scary, the fact that klogd isn't loading System.map appears to be completely harmless for us.
Our kernels are built with KALLSYMS=y, so we're getting symbol names in stack traces anyway, despite klogd's inability to do the lookups itself.
For the record, though the error message from klogd is both misleading and (for some) a bit scary, the fact that klogd isn't loading System.map appears to be completely harmless for us.
Our kernels are built with KALLSYMS=y, so we're getting symbol names in stack traces anyway, despite klogd's inability to do the lookups itself.