KERNEL: assertion (tp->lost_out == 0) failed at tcp_input.c(1202):tcp_remove_reno_sacks

From: Kurt Roeckx (Q@ping.be)
Date: Sat Apr 14 2001 - 09:42:54 EST

Next message: Rik van Riel: "Re: PATCH(?): linux-2.4.4-pre2: fork should run child first"
Previous message: Alan Cox: "Re: MO-Drive under 2.4.3"
Next in thread: Kurt Roeckx: "Re: KERNEL: assertion (tp->lost_out == 0) failed at tcp_input.c(1202):tcp_remove_reno_sacks"
Reply: Kurt Roeckx: "Re: KERNEL: assertion (tp->lost_out == 0) failed at tcp_input.c(1202):tcp_remove_reno_sacks"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

While running 2.4.3, I saw the following message a few times:

KERNEL: assertion (tp->lost_out == 0) failed at
tcp_input.c(1202):tcp_remove_reno_sacks

Is that bad, or should I just ignore it?

Kurt

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

Next message: Rik van Riel: "Re: PATCH(?): linux-2.4.4-pre2: fork should run child first"
Previous message: Alan Cox: "Re: MO-Drive under 2.4.3"
Next in thread: Kurt Roeckx: "Re: KERNEL: assertion (tp->lost_out == 0) failed at tcp_input.c(1202):tcp_remove_reno_sacks"
Reply: Kurt Roeckx: "Re: KERNEL: assertion (tp->lost_out == 0) failed at tcp_input.c(1202):tcp_remove_reno_sacks"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Apr 15 2001 - 21:00:23 EST