From: Jeff Garzik <jeff@garzik.org>
To: Mika.Lansirinne@stonesoft.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] 8139cp dev->tx_timeout
Date: Wed, 27 Jun 2007 04:36:18 -0400 [thread overview]
Message-ID: <46822182.5070002@garzik.org> (raw)
In-Reply-To: <OFC04C6285.18455C26-ONC2257306.00364F82-C2257307.002CFBE9@stonesoft.com>
Mika.Lansirinne@stonesoft.com wrote:
> Hello All,
>
> We have been experimenting a couple of interface hangs with the 8139cp
> driver. It appears that the tx buffer stops transmitting and never starts
> up again in some yet unknown conditions. To be able to circumvent this we
> implemented the missing dev->tx_timeout function which should reset the
> interface and allow it work again.
>
> The problem reoccurs quite seldom and we have yet to be able to confirm
> that the attached patch helps the situation. We though that we should
> submit the patch anyway for reviewing.
>
> The patch is made against 2.6.21.5 kernel.
Seems OK, but I'm definitely interested in hearing test feedback.
Also, all patches need a Signed-off-by line per
Documentation/SubmittingPatches or
http://linux.yyz.us/patch-format.html
Jeff
next prev parent reply other threads:[~2007-06-27 8:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 8:11 [PATCH] 8139cp dev->tx_timeout Mika.Lansirinne
2007-06-27 8:36 ` Jeff Garzik [this message]
2007-06-27 9:49 ` Mika.Lansirinne
2007-06-27 10:27 ` [PATCH 2.6.21.5] 8139cp: dev->tx_timeout Mika.Lansirinne
2007-07-02 12:39 ` Jeff Garzik
2007-07-02 13:30 ` [PATCH 2.6.22-rc7] " Mika.Lansirinne
2007-07-10 16:42 ` Jeff Garzik
2007-07-13 15:26 ` Mika.Lansirinne
2007-07-13 21:04 ` Francois Romieu
2007-07-13 21:05 ` [PATCH 1/1] 8139cp: implement the missing dev->tx_timeout Francois Romieu
2007-07-16 22:30 ` Jeff Garzik
2007-07-17 1:24 ` Arnaldo Carvalho de Melo
2007-06-27 10:43 ` [PATCH] 8139cp dev->tx_timeout Jarek Poplawski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46822182.5070002@garzik.org \
--to=jeff@garzik.org \
--cc=Mika.Lansirinne@stonesoft.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).