ex_tx_done

My up filter is crashing with the following error. What does the error
message mean?

io-net: ex_tx_done BAD3
Program received signal SIGSEGV, Segmentation fault.
[Switching to process 136377408]
0xb0374d08 in m_freem () from /lib/dll/npm-tcpip.so
(gdb) bt
#0 0xb0374d08 in m_freem () from /lib/dll/npm-tcpip.so
#1 0xb035fa0a in tcpip_receive_loop () from /lib/dll/npm-tcpip.so
(gdb) x/i $pc
0xb0374d08 <m_freem+32>: movzbw 0x10(%edi),%dx
(gdb) p/x $edi
$1 = 0xffffffff

Thanks,
Shaun

It’s basically memory corruption.

ion->tx_done() was passed what was supposedly
a down headed packet, however; it appears that
someone called ion->reg_tx_done() on the packet
with an invalid hdl. There is a check for this
in ion->reg_tx_done(), thus the corruption. The
cause could really be anything.

-seanb

Shaun Jackman <sjackman@nospam.vortek.com> wrote:
: My up filter is crashing with the following error. What does the error
: message mean?

: io-net: ex_tx_done BAD3
: Program received signal SIGSEGV, Segmentation fault.
: [Switching to process 136377408]
: 0xb0374d08 in m_freem () from /lib/dll/npm-tcpip.so
: (gdb) bt
: #0 0xb0374d08 in m_freem () from /lib/dll/npm-tcpip.so
: #1 0xb035fa0a in tcpip_receive_loop () from /lib/dll/npm-tcpip.so
: (gdb) x/i $pc
: 0xb0374d08 <m_freem+32>: movzbw 0x10(%edi),%dx
: (gdb) p/x $edi
: $1 = 0xffffffff

: Thanks,
: Shaun