.\" This manpage has been automatically generated by docbook2man 
.\" from a DocBook document.  This tool can be found at:
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
.\" Please send any bug reports, improvements, comments, patches, 
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "EI_TX_ERR" "" "06 October 2005" "" ""

.SH NAME
ei_tx_err \- handle transmitter error
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
void ei_tx_err  (struct net_device * \fIdev\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIdev\fB\fR
network device which threw the exception
.SH "DESCRIPTION"
.PP
A transmitter error has happened. Most likely excess collisions (which
is a fairly normal condition). If the error is one where the Tx will
have been aborted, we try and send another one right away, instead of
letting the failed packet sit and collect dust in the Tx buffer. This
is a much better solution as it avoids kernel based Tx timeouts, and
an unnecessary card reset.
.PP
Called with lock held.