public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: rt2400-devel@lists.sourceforge.net
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
	Iwo Mergler <iwo@call-direct.com.au>,
	Paul Eddington <eddingtonpaul@googlemail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [Rt2400-devel] Bug in rt2x00 rt73usb driver in latest git kernel
Date: Fri, 26 Sep 2008 20:53:39 +0200	[thread overview]
Message-ID: <200809262053.39930.IvDoorn@gmail.com> (raw)
In-Reply-To: <200809262024.57874.IvDoorn@gmail.com>

On Friday 26 September 2008, Ivo van Doorn wrote:
> On Friday 26 September 2008, Rafael J. Wysocki wrote:
> > On Friday, 26 of September 2008, Iwo Mergler wrote:
> > > Paul Eddington wrote:
> > > > Hi,
> > > > 
> > > > While running the latest git kernel (linus' tree) and using a usb wifi
> > > > card, I got this error in dmesg:;
> > > > 
> > > > phy2 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry
> > > > in the non-full queue 2.
> > > > Please file bug report to http://rt2x00.serialmonkey.com.
> > > > 
> > > > This is not reproducible easily, but it has occurred on two occasions
> > > > both while connected to a WEP encrypted AP with a 40-bit key and
> > > > performing many file samba transfers at full speed 54mbits.
> > > > 
> > > > I tried to report the bug there but was unable to register and edit
> > > > the bug reports wiki page.
> > > > If there is any more information or help required to debug this,
> > > > please let me know.
> > > > 
> > > > Regards,
> > > > Paul
> > > > --
> > > 
> > > Hi Paul,
> > > 
> > > the rt2x00 drivers are currently a very fast moving target. You may want
> > > to experiment with the rt2x00 kernel tree instead - it gets the patches
> > > (and the bugs) earlier. ;-)
> > > 
> > > http://git.kernel.org/?p=linux/kernel/git/ivd/rt2x00.git;a=summary
> > > 
> > > I added the rt2x00 mailing list to CC.
> > 
> > Well, according to the information I've received from Paul this particular
> > problem is a regression from 2.6.26, so it's been added to the list of recent
> > regressions.
> 
> Seriously, this error message is the most annoying rt2x00 error message _ever_.
> It should have been fixed 3 kernels ago, but it keeps popping up again and again.
> 
> Paul, what is the git commit id with which you encountered this bug?

Oh and please test rt2x00.git as well, since some patches which should fix this issue
are in there (and in wireless-testing.git) but not in Linus' tree since they are scheduled
for 2.6.28.

Ivo

  reply	other threads:[~2008-09-26 18:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24 18:02 Bug in rt2x00 rt73usb driver in latest git kernel Paul Eddington
2008-09-26  5:29 ` Iwo Mergler
2008-09-26 12:52   ` Rafael J. Wysocki
2008-09-26 18:24     ` [Rt2400-devel] " Ivo van Doorn
2008-09-26 18:53       ` Ivo van Doorn [this message]
2008-09-26 19:04         ` John W. Linville
2008-09-26 19:22           ` Ivo van Doorn
2008-09-26 20:48             ` John W. Linville

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=200809262053.39930.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=eddingtonpaul@googlemail.com \
    --cc=iwo@call-direct.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=rt2400-devel@lists.sourceforge.net \
    /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