Bug 1013027 - rt2x00queue_write_tx_frame error
Summary: rt2x00queue_write_tx_frame error
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 19
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: fedora-kernel-wireless-ralink
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-27 15:54 UTC by Mário Sousa
Modified: 2014-09-29 12:43 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-15 10:12:37 UTC
Type: Bug


Attachments (Terms of Use)

Description Mário Sousa 2013-09-27 15:54:48 UTC
Description of problem:

My computer wireless keeps failing both at home and at work.
Right now I am managing with ethernet cable but...

I have a HP Envy with Windows 8 (which is rarely used) that doesn't have this problem and I have Fedora 19 installed.

After searching bugzilla, only bugs 966838 and 753648 had any information about this and it were old Fedora versions so I am reporting the bug again.

As asked I try to report the bug to http://rt2x00.serialmonkey.com but I was told that here might be faster.



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
dmesg
...
[16735.333008] wlo1: direct probe to 00:26:5b:90:73:d8 (try 1/3)
[16735.533988] wlo1: direct probe to 00:26:5b:90:73:d8 (try 2/3)
[16735.735150] wlo1: direct probe to 00:26:5b:90:73:d8 (try 3/3)
[16735.936251] wlo1: authentication with 00:26:5b:90:73:d8 timed out
[16735.946325] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0
Please file bug report to http://rt2x00.serialmonkey.com
...

Comment 1 Stanislaw Gruszka 2013-09-30 11:04:16 UTC
Maybe this is same issue as in bug 1010431 . Does the problem happen also on kernel-3.11.2-201.fc19 or latter.

Comment 2 Mário Sousa 2014-09-29 12:43:47 UTC
No longer a problem in fedora 20.


Note You need to log in before you can comment on or make changes to this bug.