On Fri, 14 Dec 2007, Ilpo Järvinen wrote:
> On Thu, 13 Dec 2007, Wolfgang Walter wrote:
>
> > it happened again with your patch applied:
> >
> > WARNING: at net/ipv4/tcp_input.c:1018 tcp_sacktag_write_queue()
> >
> > Call Trace:
> > [] tcp_sacktag_write_queue+0x7d0/0xa60
> > [] add_partial+0x
On Thu, 13 Dec 2007, Wolfgang Walter wrote:
> it happened again with your patch applied:
>
> WARNING: at net/ipv4/tcp_input.c:1018 tcp_sacktag_write_queue()
>
> Call Trace:
> [] tcp_sacktag_write_queue+0x7d0/0xa60
> [] add_partial+0x19/0x60
> [] tcp_ack+0x5a4/0x1d70
> [] tcp_rcv_established+0x
Hello Ilpo,
it happened again with your patch applied:
WARNING: at net/ipv4/tcp_input.c:1018 tcp_sacktag_write_queue()
Call Trace:
[] tcp_sacktag_write_queue+0x7d0/0xa60
[] add_partial+0x19/0x60
[] tcp_ack+0x5a4/0x1d70
[] tcp_rcv_established+0x485/0x7b0
[] tcp_v4_do_rcv+0xed/0x3e0
[] tcp_v4_rc
Am Montag, 3. Dezember 2007 14:34 schrieb Ilpo Järvinen:
> On Mon, 3 Dec 2007, Wolfgang Walter wrote:
> > with kernel 2.6.23.8 we saw a
> >
> > KERNEL: assertion ((int)tcp_packets_in_flight(tp) >= 0) failed at
> > net/ipv4/tcp_input.c (1292)
>
> Is this the only message? Are there any Leak printout
On Mon, 3 Dec 2007, Wolfgang Walter wrote:
> with kernel 2.6.23.8 we saw a
>
> KERNEL: assertion ((int)tcp_packets_in_flight(tp) >= 0) failed at
> net/ipv4/tcp_input.c (1292)
Is this the only message? Are there any Leak printouts?
Any tweaking done to TCP related sysctls?
And for completeness,
Hello,
with kernel 2.6.23.8 we saw a
KERNEL: assertion ((int)tcp_packets_in_flight(tp) >= 0) failed at
net/ipv4/tcp_input.c (1292)
Regards,
Wolfgang Walter
--
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts
--
To unsubscribe from this list: send the line "unsubscribe net
