TSO panic

From: ben wilber <ben_at_desync.com>
Date: Tue, 31 Aug 2010 19:13:14 -0400
Hi,

I just upgraded from r210042 to r212073 and keep getting the panic
introduced in r211317:

panic: tcp_output: len <= tso_segsz

db:0:kdb.enter.default>  bt
Tracing pid 12 tid 100063 td 0xffffff001881b000
kdb_enter() at kdb_enter+0x3d
panic() at panic+0x1c8
tcp_output() at tcp_output+0x1445
tcp_do_segment() at tcp_do_segment+0x252d
tcp_input() at tcp_input+0x1044
ip_input() at ip_input+0x5cd
netisr_dispatch_src() at netisr_dispatch_src+0xc1
netisr_dispatch() at netisr_dispatch+0x11
ether_demux() at ether_demux+0x19a
ether_input() at ether_input+0x36a
mxge_intr() at mxge_intr+0x5be
intr_event_execute_handlers() at intr_event_execute_handlers+0x107
ithread_loop() at ithread_loop+0xb5
fork_exit() at fork_exit+0x147
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffff8810df2cf0, rbp = 0 ---

If there's someone interested in debugging this further, please let me
know what I can do to help.
Received on Tue Aug 31 2010 - 21:14:00 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:06 UTC