sysklogd 1.5.0 segfault,1.4.1 works well.

Bruce Dubbs bruce.dubbs at gmail.com
Wed May 5 09:34:27 PDT 2010


xinglp wrote:
> strace result is like below
> 
> [pid   440] read(2, "\n<GMT-8>-8\n", 2048) = 11
> [pid   440] close(2)                    = 0
> [pid   440] munmap(0xb7723000, 4096)    = 0
> [pid   440] write(1, "<6>May  5 21:58:10 kernel: klogd 1.5.0, log source =
> /proc/kmsg started.\0", 73) = 73
> [pid   440] uname({sys="Linux", node="3.4.lfs.6.5", ...}) = 0
> [pid   440] open("/boot/System.map-2.6.33.3", O_RDONLY) = -1 ENOENT (No such
> file or directory)
> [pid   440] open("/boot/System.map", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> [pid   440] open("/System.map-2.6.33.3", O_RDONLY) = -1 ENOENT (No such file
> or directory)
> [pid   440] open("/System.map", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> [pid   440] open("/usr/src/linux/System.map-2.6.33.3", O_RDONLY) = -1 ENOENT
> (No such file or directory)
> [pid   440] open("/usr/src/linux/System.map", O_RDONLY) = -1 ENOENT (No such
> file or directory)
> [pid   440] time(NULL)                  = 1273067890
> [pid   440] stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=127,
> ...}) = 0
> [pid   440] write(1, "<4>May  5 21:58:10 kernel: Cannot find map file.\0",
> 49) = 49
> [pid   440] open("/proc/kallsyms", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> [pid   440] time(NULL)                  = 1273067890
> [pid   440] stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=127,
> ...}) = 0
> [pid   440] write(1, "<6>May  5 21:58:10 kernel: No module symbols loaded -
> kernel modules not enabled.\n\0", 83) = 83
> [pid   440] --- SIGSEGV (Segmentation fault) @ 0 (0) ---

It would be easy enough for you to copy th e System.map from your build 
to "/boot/System.map-2.6.33.3" to avoid those messages.  klogd is the 
only thing that uses it.

System.map has not been really required before.  It's generally only 
been a one line message in the log.  You might want to try enabling 
kernel modules.  I don't use many, but I think the kernel really wants 
them to be enabled.

   -- Bruce



More information about the lfs-support mailing list