public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Iwo Mergler <iwo@call-direct.com.au>
To: Paul Eddington <eddingtonpaul@googlemail.com>
Cc: linux-kernel@vger.kernel.org, rt2400-devel@lists.sourceforge.net
Subject: Re: Bug in rt2x00 rt73usb driver in latest git kernel
Date: Fri, 26 Sep 2008 15:29:47 +1000	[thread overview]
Message-ID: <48DC734B.8070805@call-direct.com.au> (raw)
In-Reply-To: <762793250809241102n61ea8f00kca8138bc3c8df2e6@mail.gmail.com>

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.

Kind regards,

Iwo


  reply	other threads:[~2008-09-26  5:30 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 [this message]
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
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=48DC734B.8070805@call-direct.com.au \
    --to=iwo@call-direct.com.au \
    --cc=eddingtonpaul@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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