linux-kernel - Re: Bug in rt2x00 rt73usb driver in latest git kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 26 Sep 2008 14:52:27 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Iwo Mergler <iwo@...l-direct.com.au>
Cc:	Paul Eddington <eddingtonpaul@...glemail.com>,
	linux-kernel@...r.kernel.org, rt2400-devel@...ts.sourceforge.net
Subject: Re: Bug in rt2x00 rt73usb driver in latest git kernel

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.

Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/