All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Chris Morrow <morrowc@ops-netman.net>
Cc: morrowc+kernel@ops-netman.net, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: crashes of 2.4.31hf2.6  kernel (oops included)
Date: Tue, 4 Jul 2006 12:52:17 +0200	[thread overview]
Message-ID: <20060704105217.GA19642@1wt.eu> (raw)
In-Reply-To: <Pine.LNX.4.61.0607040620390.23681@arb-h2.bcf-argzna.arg>

On Tue, Jul 04, 2006 at 06:24:25AM +0000, Chris Morrow wrote:
> 
> 
> On Tue, 4 Jul 2006 morrowc+kernel@ops-netman.net wrote:
> >
> >On Tue, 4 Jul 2006, Willy Tarreau wrote:
> >
> >>On Tue, Jul 04, 2006 at 02:22:00AM +0000, morrowc+kernel@ops-netman.net 
> >>wrote:
> >>Do all the oops report a crash in tcp_synack_timer() ? This one got a
> >>wrong pointer for the call to req->class->rtx_syn_ack(). This really
> 
> apologies, I didn't catch the EIP pointer in your message, looking at the 
> included 06/29 oops/ksymoops output I see:
> 
> grep -i EIP output-ksymoops-06-29-02
> 00000000 <_EIP>:
> 00000000 <_EIP>:
> 
> So, no relevant output on that one :( Looking all all after 06/15:
> 
> output-ksymoops-06-24:EIP:    0010:[<30246c8b>]    Not tainted
> output-ksymoops-06-24:>>EIP; 30246c8b Before first symbol   <=====
> output-ksymoops-06-25-01:EIP:    0010:[<c0122485>]    Not tainted
> output-ksymoops-06-25-01:>>EIP; c0122485 <add_timer+55/110>   <=====
> output-ksymoops-06-25-01:00000000 <_EIP>:
> output-ksymoops-06-27-2006:00000000 <_EIP>:
> output-ksymoops-06-27-2006:00000000 <_EIP>:
> output-ksymoops-06-29-01:EIP:    0010:[<c0122f20>]    Not tainted
> output-ksymoops-06-29-01:>>EIP; c0122f20 <count_active_tasks+20/50> <=====
> output-ksymoops-06-29-02:00000000 <_EIP>:
> output-ksymoops-06-29-02:00000000 <_EIP>:
> output-ksymoops-2006-07-03-01.txt:EIP:    0010:[<c024b03f>]    Not tainted
> output-ksymoops-2006-07-03-01.txt:>>EIP; c024b03f <tcp_synack_timer+ff/1f0> 
> <=====
> output-ksymoops-2006-07-03-01.txt:00000000 <_EIP>:
> output-ksymoops-2006-07-03-01.txt:   5:   0f 85 8b 00 00 00         jne   
> 96 <_EIP+0x96>
> 
> only the 07/03-01 points at synack-timer. This might mean it's more memory 
> related than anything else, eh?

Yes, it really looks like !
I'm fairly confident that you'll only have to replace a bad memory stick
or a power supply to fix the problem.

Cheers,
Willy


      reply	other threads:[~2006-07-04 11:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-04  2:22 PROBLEM: crashes of 2.4.31hf2.6 kernel (oops included) morrowc+kernel
2006-07-04  4:09 ` Willy Tarreau
2006-07-04  6:18   ` morrowc+kernel
2006-07-04  6:24     ` Chris Morrow
2006-07-04 10:52       ` Willy Tarreau [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=20060704105217.GA19642@1wt.eu \
    --to=w@1wt.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=morrowc+kernel@ops-netman.net \
    --cc=morrowc@ops-netman.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.