Re: PROBLEM: crashes of 2.4.31hf2.6 kernel (oops included)
From: Willy Tarreau
Date: Tue Jul 04 2006 - 06:58:57 EST
On Tue, Jul 04, 2006 at 06:24:25AM +0000, Chris Morrow wrote:
>
>
> On Tue, 4 Jul 2006 morrowc+kernel@xxxxxxxxxxxxxx wrote:
> >
> >On Tue, 4 Jul 2006, Willy Tarreau wrote:
> >
> >>On Tue, Jul 04, 2006 at 02:22:00AM +0000, morrowc+kernel@xxxxxxxxxxxxxx
> >>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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/