From: "John W. Linville" <linville@tuxdriver.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Ralf Baechle <ralf@linux-mips.org>,
netdev@vger.kernel.org, Stefan Rompf <stefan@loplof.de>,
Zhu Yi <yi.zhu@intel.com>,
James Ketrenos <jketreno@linux.intel.com>,
Patrick McHardy <kaber@trash.net>, jamal <hadi@cyberus.ca>
Subject: Re: ipw2200: Driver lockup
Date: Wed, 19 Jul 2006 22:58:10 -0400 [thread overview]
Message-ID: <20060720025810.GA5901@tuxdriver.com> (raw)
In-Reply-To: <1153356597.2542.7.camel@localhost.localdomain>
On Wed, Jul 19, 2006 at 08:49:57PM -0400, Dan Williams wrote:
> On Wed, 2006-07-19 at 10:28 -0400, Ralf Baechle wrote:
> > I got the driver to die several times under the extreme condition at the
> > KS / OLS with dozens to hundreds of other machines in the same room. The
> > last kernel message I got from about the time when wireless died was
> >
> > eth1: NETDEV_TX_BUSY returned; driver should report queue full via ieee_device->is_queue_full.
>
> I actually get this quite a bit too, at least a couple times per day.
> Sometimes the device goes down and you have to rmmod ipw2200, other
> times it recovers. But quite annoying anyway.
>
> Anyone know exactly what that message means, and possibly how to fix it?
For what it is worth, there was a patch for this posted back
in January. It stirred-up a kerfluffle, so it never got merged.
FWIW, it touches on 802.11e QoS and multiple TX queues -- my personal
favorite wireless subject...NOT!
The thread is available here (first post not connected to follow-up
thread for some reason):
http://marc.theaimsgroup.com/?l=linux-netdev&m=113809246102858&w=2
http://marc.theaimsgroup.com/?l=linux-netdev&m=113814103024576&w=2
Given that half a year has passed, does anyone have any better ideas
now? Should I merge the patch? Or is the cure worse than the disease?
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2006-07-20 3:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 14:28 ipw2200: Driver lockup Ralf Baechle
2006-07-20 0:49 ` Dan Williams
2006-07-20 2:58 ` John W. Linville [this message]
2006-07-20 5:22 ` Zhu Yi
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=20060720025810.GA5901@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=dcbw@redhat.com \
--cc=hadi@cyberus.ca \
--cc=jketreno@linux.intel.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=stefan@loplof.de \
--cc=yi.zhu@intel.com \
/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).