mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesper Juhl" <jesper.juhl@gmail.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 21:55:30 +0200	[thread overview]
Message-ID: <9a8748490609111255w2961d34bo63fb0db7d0d4190a@mail.gmail.com> (raw)
In-Reply-To: <4505B788.1030803@perkel.com>

On 11/09/06, Marc Perkel <marc@perkel.com> 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?
>

Hi, I don't have a solution to your problem unfortunately, just want
to give you a bit of advice.

1) Try searching the archives and google a bit for info before posting
(and when you do post, make it clear that you've done so). As it turns
out this problem has surfaced before and there are several
interresting threads on the subject - here are a few I found (there
are others) :
http://lkml.org/lkml/2005/9/8/4
http://linux.derkeiler.com/Mailing-Lists/Kernel/2005-06/3234.html
http://www.mhonarc.org/archive/html/procmail/2006-06/msg00140.html

2) If you find previous posts related to your problem you'll often see
requests for specific info in them (like Andi asking "... catch a
crash in gdb and type x/i $pc what do you see?" in
http://lkml.org/lkml/2005/9/8/17 ). Try to provide such info in your
initial post - it'll greatly enhance your chances of getting useful
replies (and/or getting the bug fixed).

3) Please read the REPORTING-BUGS document in the root of the kernel
source dir and provide the info it outlines - usually saves a bunch of
ping-pong mails back and forth asking for more info.

4) Try to add people who may have an insight into the problem to Cc: -
looking at previous threads on the subject and finding the people who
have previously shown an interrest is usually a good starting point.
The right people may miss your report if you only send to LKML.


-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  reply	other threads:[~2006-09-11 19:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-11 19:22 Marc Perkel
2006-09-11 19:55 ` Jesper Juhl [this message]
2006-09-11 21:04 ` Phillip Susi

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=9a8748490609111255w2961d34bo63fb0db7d0d4190a@mail.gmail.com \
    --to=jesper.juhl@gmail.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

all inboxes | Powered by JetHome®