sysklogd 1.5.0 segfault,1.4.1 works well.

xinglp xinglp at gmail.com
Tue May 4 22:57:12 PDT 2010


I'm sorry.My mistake. sysklog works well. klogd segfault.
I'm running 32-bit. VMWARE 7.0.1 , using pvscsi and vmxnet3. kernel is 2.6.33.3.

klogd[424]: segfualt at 46  ip b778aea8 sp bxxxxxxx error 4 in
libc-2.10.1.so[b7xxxxxx+16c000]

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

Is System.map necessary?

2010/5/5 Bruce Dubbs <bruce.dubbs at gmail.com>:
> xinglp wrote:
>> I tested it on both LFS-SVN and LFS-6.5. Do I have to turn on
>> something in the kernel.
>
> You're a little short of info here.  Does klogd run OK?  Do you get any
> errors when you build?  I don't know of anything different in the
> kernel, but which kernel are you using?  Do you get any sysklog output
> at all, or does it segfault immediately?   Does  /etc/syslog.conf exist?
> What is your hardware?  Are you running 32-bit or 64-bit?
>
> sysklogd 1.5.0 seems to run fine for me on a 64-bit system.
>
>   -- Bruce
> --
> http://linuxfromscratch.org/mailman/listinfo/lfs-support
> FAQ: http://www.linuxfromscratch.org/lfs/faq.html
> Unsubscribe: See the above information page
>



More information about the lfs-support mailing list