Re: kernel panics at google

• Next message: Andrea Arcangeli: "Re: static int's for proc_change_penalty and tlb_flush_penalty"
• Previous message: almesber@lrc.di.epfl.ch: "Re: [slightly off-topic] Network booting - Coda"
• In reply to: David desJardins: "kernel panics at google"
• Next in thread: David desJardins: "Re: kernel panics at google"
• Reply: David desJardins: "Re: kernel panics at google"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

David desJardins wrote:
>
>
> If I'm interpreting the kernel oops correctly, the error occurs in
> tcp_retrans_try_collapse. I've attached below the oops, after
> attempting to run it through ksymoops. (I think I got the right
> symbols, but I'm not absolutely certain.)
>
How much memory is installed?
I assume 256 MB or more.

> These systems are running 2.2.13 with some patches.

>
> >>EIP: c0158892 <tcp_retrans_try_collapse+3a/208>
> Trace: c01462cb <__kfree_skb+97/a0>
> Trace: c0158be7 <tcp_retransmit_skb+a3/164>
> Trace: c0158d0d <tcp_xmit_retransmit_queue+65/e4>

tcp_retransmit_try_collapse is called with

        skb->next == NULL

tcp_retrans_try_collapse dereferences skb->next --> oops.

Unfortunately, I have no idea why this happened.

--
	Manfred
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

• Next message: Andrea Arcangeli: "Re: static int's for proc_change_penalty and tlb_flush_penalty"
• Previous message: almesber@lrc.di.epfl.ch: "Re: [slightly off-topic] Network booting - Coda"
• In reply to: David desJardins: "kernel panics at google"
• Next in thread: David desJardins: "Re: kernel panics at google"
• Reply: David desJardins: "Re: kernel panics at google"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Jan 23 2000 - 21:00:23 EST