From: Phillip Susi <psusi@cfl.rr.com>
To: Marc Perkel <marc@perkel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Segfault Error - what does this mean?
Date: Mon, 11 Sep 2006 17:04:49 -0400 [thread overview]
Message-ID: <4505CF71.1070605@cfl.rr.com> (raw)
In-Reply-To: <4505B788.1030803@perkel.com>
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.
>
prev parent reply other threads:[~2006-09-11 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 19:22 Segfault Error - what does this mean? Marc Perkel
2006-09-11 19:55 ` Jesper Juhl
2006-09-11 21:04 ` Phillip Susi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4505CF71.1070605@cfl.rr.com \
--to=psusi@cfl.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc@perkel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox