RT3290 Wifi (rt2800pci) disconnect after a while...

Bug #1239814 reported by Camilo Gonzalez
44
This bug affects 8 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

Description: Ubuntu Saucy Salamander (development branch)
Release: 13.10
linux-image-generic: 3.11.0.12.13

What you expected to happen:

To use mi wifi normally...

What happened instead:

The wifi connection crash after a while, next you can't use wifi until reboot

Here's the dmesg output when this happens:

[ 290.271086] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
[ 290.431232] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 290.591389] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
[ 290.751542] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 291.972703] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
[ 292.132859] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 296.969490] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
[ 297.129644] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 297.289742] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
[ 297.449946] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 298.670982] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
[ 298.831267] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 303.671908] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
[ 303.831996] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush

It seems this bug as been already fixed in the kernel mainline check this please:

https://bbs.archlinux.org/viewtopic.php?pid=1329394#p1329394
https://bugzilla.kernel.org/show_bug.cgi?id=61621

Please add this fix...

Revision history for this message
Camilo Gonzalez (yhwh-aggro) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Camilo Gonzalez, please do not mark this report a duplicate of another or vice versa.

Revision history for this message
penalvch (penalvch) wrote :

Camilo Gonzalez, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: needs-kernel-logs
removed: kernel-bug network rt2800pci rt3290 wifi
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Charles Wright (wrighrc) wrote :

Hello
    I just upgraded to 12.04.4
I have an asus x401a laptop with a
RT5390 Wireless 802.11n 1T/1R PCIe

It spews :
[ 53.374514] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush

Does anyone know if
https://bugzilla.kernel.org/show_bug.cgi?id=61621

Has been or will be back ported into ubuntu?

root@x5:~# uname -a
Linux x5 3.11.0-15-generic #25~precise1-Ubuntu SMP Thu Jan 30 17:39:31 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

Thanks.

Changed in linux (Ubuntu):
status: Expired → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Charles Wright, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
no longer affects: linux
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.