From: Jonathan Nieder <jrnieder@gmail.com>
To: "Mike ." <mike-bugreport@hotmail.com>
Cc: eric.dumazet@gmail.com, ben@decadent.org.uk, kirjanov@gmail.com,
netdev@vger.kernel.org, benoit.mortier@opensides.be,
herbert@gondor.apana.org.au
Subject: Re: Sundance network driver (D-Link DFE-580TX) timeouts rendering interface unusable
Date: Fri, 16 Mar 2012 17:04:13 -0500 [thread overview]
Message-ID: <20120316220413.GA31359@burratino> (raw)
In-Reply-To: <SNT141-W2773C07AA4E8276F3E1E4496730@phx.gbl>
Hi again,
Mike . wrote:
>> Oh well, we also must make sure we held np->lock in TX completion when
>> doing our test to eventually call netif_wake_queue(), I missed it was
>> released too early.
>>
>> here is a more complete patch.
>
> I applied the patch, recompiled the module, loaded it into the kernel and
> started testing traffic on the interface with the following result :
>
> [ 1124.008030] ------------[ cut here ]------------
> [ 1124.008101] WARNING: at /build/buildd-linux-2.6_3.2.1-2-i386-4wAPNj/linux-2.6-3.2.1/debian/build/source_i386_none/net/sched/sch_generic.c:255 dev_watchdog+0xb1/0x104()
> [ 1124.008201] Hardware name:
> [ 1124.008252] NETDEV WATCHDOG: eth1 (sundance): transmit queue 0 timed out
[...]
> After this the same repeat of transmit timeouts (as posted earlier) in the
> log untill I down the interface.
Thanks. I assume current 3.3 release candidates behave the same way.
Based on [2], it looks like v2.6.25-rc9~99^2~24 ([NET]: Add preemption
point in qdisc_run, 2008-03-28) made this easier to trip.
As for the next step: I'd suggest posting a summary of the symptoms,
which kernel versions you have tested, and a link to [1] at
http://bugzilla.kernel.org/, product Drivers, component Network, and
letting us know the bug number so we can track it without forgetting
what has already been learned.
Hope that helps,
Jonathan
[1] http://thread.gmane.org/gmane.linux.network/219101
next prev parent reply other threads:[~2012-03-16 22:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <SNT141-W3553B2629FBBC84A5A140596860@phx.gbl>
[not found] ` <1327205171.8004.96.camel@deadeye>
[not found] ` <SNT141-W5087B9A5022955EA5564DB96890@phx.gbl>
[not found] ` <20120126220640.GO12704@decadent.org.uk>
[not found] ` <SNT141-W58AC5ADD0BC9DE29AFA00D968E0@phx.gbl>
2012-01-29 4:23 ` Sundance network driver (D-Link DFE-580TX) timeouts rendering interface unusable Ben Hutchings
2012-01-29 4:32 ` Ben Hutchings
2012-01-30 9:51 ` Denis Kirjanov
2012-01-30 10:14 ` Bug#656476: " Eric Dumazet
2012-01-30 10:36 ` Eric Dumazet
2012-01-30 14:05 ` Ben Hutchings
2012-01-30 14:28 ` Eric Dumazet
2012-01-30 14:41 ` Ben Hutchings
2012-01-30 14:57 ` Eric Dumazet
2012-01-30 15:21 ` Eric Dumazet
2012-02-01 14:42 ` Bug#656476: " Mike .
2012-03-16 22:04 ` Jonathan Nieder [this message]
2012-03-16 22:11 ` Jonathan Nieder
2012-04-23 15:34 ` Bug#656476: " Mike .
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=20120316220413.GA31359@burratino \
--to=jrnieder@gmail.com \
--cc=ben@decadent.org.uk \
--cc=benoit.mortier@opensides.be \
--cc=eric.dumazet@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=kirjanov@gmail.com \
--cc=mike-bugreport@hotmail.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).