A segfault means the program tried to touch a part of memory in a way
that it is not allowed. In this case, the address was 0, which would
indicate that exim attempted to dereference a null pointer. It would
appear this is a bug in exim, not the kernel.
Marc Perkel wrote:
Just put a new server online trying out the new AMD AM2 processor. I
compiled a custom kernel because the regular Fedora Core kernels aren't
yet compatible with my Asus M2NPV-VM motherboard using the nVidia chipset.
I compiled 2.6.18rc6 and got segfault errors. So I tried the 2.6.17.13
kernel and same thing. About every 20 minutes or so I get one of these.
Sep 11 12:05:18 pascal kernel: exim[19840]: segfault at 0000000000000000
rip 0000003f53e73ee0 rsp 00007fff9e561d18 error 4
At one point the server locked up. Before I put it online I did several
days of memory testing with no errors. I believe the Exim code is solid
as it has been running flawlessly on all my other servers.
It's probably hardware or some incompatibility but I'm not sure where to
start looking. Trying to understand what this error means. What is Error
4? How do I track this down?
Thanks in advance.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]