From: Jarek Poplawski <jarkao2@o2.pl>
To: Jeff Garzik <jeff@garzik.org>
Cc: Mika.Lansirinne@stonesoft.com, netdev@vger.kernel.org,
Jean-Baptiste Vignaud <vignaud@xandmail.fr>,
"marcin\.slusarz" <marcin.slusarz@gmail.com>,
shemminger <shemminger@linux-foundation.org>
Subject: Re: [PATCH] 8139cp dev->tx_timeout
Date: Wed, 27 Jun 2007 12:43:55 +0200 [thread overview]
Message-ID: <20070627104355.GB3438@ff.dom.local> (raw)
In-Reply-To: <46822182.5070002@garzik.org>
(second try! sorry)
On 27-06-2007 10:36, Jeff Garzik wrote:
> 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.
Hi!
I think maybe there are too many similar problems under 2.6.21
to be individual, and there could be something common to fix?
So, I "link" here a few probably interested souls to cc:
Subject: Re: 2.6.20->2.6.21 - networking dies after random time
...
On Tue, Jun 26, 2007 at 04:24:07PM +0200, Jean-Baptiste Vignaud wrote:
> Hello, i have a very similar problem with 2.6.21 also;
>
> 2 3com NICs and they are failling randomly.
>
> The kernel is a basic fedora 7 kernel (2.6.21-1.3228.fc7)
> I found a bug report and added details here : https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=243960
>
> I'm not subcribed on this list, so please cc me if there is any questions.
>
> JB
>
> > On Tue, Jun 26, 2007 at 08:10:17AM +0200, Marcin Ślusarz wrote:
> > ...
> > > I reproduced it on minimal config:
...
> > We know your hardware should be OK - since it was fine with 2.6.20.
...
It looks like there is something common in the air...
Marcin: ne2k_pci with 8390, Jean: 3com, and now I see
similar problem with 8139cp too (plus some ideas):
http://marc.info/?l=linux-netdev&m=118293314109648&w=2
So, you probably should wait a little & look for new patches here.
Cheers,
Jarek P.
prev parent reply other threads:[~2007-06-27 10:35 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
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 ` Jarek Poplawski [this message]
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=20070627104355.GB3438@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=Mika.Lansirinne@stonesoft.com \
--cc=jeff@garzik.org \
--cc=marcin.slusarz@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
--cc=vignaud@xandmail.fr \
/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).