1814:0201 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush

[Kim Tyler]

In Trusty, happens continuously 100% of the time after boot/reboot, finally fails, followed by authentication failure. This doesn't happen with 12.04 Precise.

---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: kit284 2043 F.... pulseaudio
 /dev/snd/controlC1: kit284 2043 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=8bc3362d-e136-453f-bb6c-284013a5dd11
InstallationDate: Installed on 2014-04-02 (40 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
MachineType: CLEVO D900K
NonfreeKernelModules: nvidia
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=e838aadc-8afe-436a-a3cb-a2908622ffc4 ro quiet splash
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-24-generic N/A
 linux-backports-modules-3.13.0-24-generic N/A
 linux-firmware 1.127
Tags: trusty
Uname: Linux 3.13.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/06/2005
dmi.bios.vendor: Phoenix
dmi.bios.version: 4.06CJ15
dmi.board.name: D900K
dmi.board.vendor: CLEVO
dmi.board.version: VT8341B
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenix:bvr4.06CJ15:bd12/06/2005:svnCLEVO:pnD900K:pvrVT8341B:rvnCLEVO:rnD900K:rvrVT8341B:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: D900K
dmi.product.version: VT8341B
dmi.sys.vendor: CLEVO

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1318837

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

apport information

[Kim Tyler (ktyler)]

added apport, changed status to "confirmed" as requested via email

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.15 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc5-utopic/

[Kim Tyler (ktyler)]

kernel-fixed-upstream

The kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc5-utopic/ fixes the problem. (no filling of logs with message "ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush".)

  It has other problems, but since it is an RC, will wait for further releases.

(not sure how to add the requisite tag)

[penalvch (penalvch)]

Kim Tyler, the next step is to fully reverse bisect in order to identify the fix commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

[Kim Tyler (ktyler)]

have tried many kernels from mainline kernels

kernels from current, up to and including 3.14.0-rc2 exhibit error as described above.

kernels 3.14.0-rc3 and above DO NOT exhibit error as descibed above.

I have looked at changes log for for 3.14.0-rc3 for obvious changes that may be implicated, and found following candidate (search on "phy") (this may or may not be the solution)

Andrew Lunn (3):
      drivers: phy: Make NULL a valid phy reference
      drivers: phy: Add support for optional phys
      ata: sata_mv: Fix probe failures with optional phys

I'm not sure where to go from here, or if this is helpful. Please advise.

[penalvch (penalvch)]

Kim Tyler, your bisect progress is helpful, but not complete. You would want to continue commit bisecting as per previously mentioned article in order to confirm your results.

[Kim Tyler (ktyler)]

I've tried many of the intructions, but am unable to download the appropriate git kernel sources, and do not know enough about how to manipulate the repositories to be able to be any help.

In the meantime, the current updated kernel 3.13.0-29 still has the same error, but now ubuntu trusty crashes and the machine halts. The /var/log/messages shows the following :-
=========================< start of messages slice >=====================================
Jun 6 13:09:47 pio kernel: [ 2458.080062] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
Jun 6 13:09:52 pio kernel: [ 2462.224039] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
Jun 6 13:09:56 pio kernel: [ 2466.624043] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
Jun 6 13:09:58 pio kernel: [ 2468.260046] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@Jun 6 13:28:25 pio rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="589" x-info="http://www.rsyslog.com"] start
Jun 6 13:28:25 pio rsyslogd: rsyslogd's groupid changed to 104
Jun 6 13:28:25 pio rsyslogd: rsyslogd's userid changed to 101
====================< end of slice >====================================================

also, the appears to be problem during the booting, see following from /var/log/messages :-

Jun 6 13:28:25 pio kernel: [ 14.463208] ------------[ cut here ]------------
Jun 6 13:28:25 pio kernel: [ 14.463217] WARNING: CPU: 1 PID: 329 at /home/apw/COD/linux/drivers/pnp/pnpacpi/core.c:97 pnpacpi_set_resources+
0x12f/0x140()
Jun 6 13:28:25 pio kernel: [ 14.463219] Modules linked in: nsc_ircc(+) shpchp mac_hid video irda crc_ccitt parport_pc ppdev lp parport pata_
acpi psmouse firewire_ohci r8169 firewire_core sata_via pata_via mii crc_itu_t
Jun 6 13:28:25 pio kernel: [ 14.463236] CPU: 1 PID: 329 Comm: systemd-udevd Not tainted 3.14.0-031400rc3-generic #201402201029
Jun 6 13:28:25 pio kernel: [ 14.463238] Hardware name: CLEVO D900K/D900K, BIOS 4.06CJ15 12/06/2005
Jun 6 13:28:25 pio kernel: [ 14.463241] 0000000000000061 ffff88003660dac8 ffffffff817592e6 00000000000022b4
Jun 6 13:28:25 pio kernel: [ 14.463245] 0000000000000000 ffff88003660db08 ffffffff8106ab8c ffff88003660db40
Jun 6 13:28:25 pio kernel: [ 14.463248] ffff88007c252400 ffffffffa00c8100 ffff88007d01bac8 0000000000000000
Jun 6 13:28:25 pio kernel: [ 14.463251] Call Trace:
Jun 6 13:28:25 pio kernel: [ 1...

[penalvch (penalvch)]

Kim Tyler, as per https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_bisect_the_upstream_kernel.3F one would want to download the git kernel source via:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

[Kim Tyler (ktyler)]

I don't know how to download the particular versions 3.14.0-RC2 and 3.14.0-RC3, as RC2 is bad and RC3 is good (relatively).

eg, what version number do I put in for the following example, given the about versions? :-

git bisect good v3.13-rc4

How do I list the available kernels in git?

I can't use the standard nouveau drivers, as my machine will shutdown after an indeterminate time, with (sometimes) the following as the last entry in logs :- (eg)
--------------------------------------
Jun 19 14:31:54 pio kernel: [ 1502.785768] nouveau [ PTHERM][0000:02:00.0] temperature (95 C) hit the 'downclock' threshold
--------------------------------------

If I use the proprietary nvidia drivers, the screen will go "black" at different times, for different lengths of time, and also have "crazy" patterns that eventually clear to normal. I use dual screen, and sometimes the extension screen goes "black" and I have to "pan" around on primary screen to get to windows. Also, when booting into the new kernel, the DKMS doesn't work, so I have to use the nouveau drivers, with the above problem.

All in all, it seems is too much trouble for me to debug.

As the wireless is broken, and the video is not working with standard open drivers or proprietary drivers, it looks as though trusty is a flakey release, and is not worth the considerable trouble to fix.

So, since this LTS is no good on my hardware, and little prospect of being fixed in the near future, it looks like I'll have to wait for the next LTS before I upgrade.

*sigh*

[Luca Lesinigo (luca404)]

This is affecting me too, on a system that worked perfectly with some older Ubuntu release (I guess it was 12.04 LTS but not 100% sure about it, sorry).

I did not see it mentioned anywhere on this BR but afaik the kernel bug is this - maybe could be helpful to narrow down the search for the fix:
  https://bugzilla.kernel.org/show_bug.cgi?id=61621

I tested some kernels on my system with these results:
- 3.13.0-30-generic (Trusty's stock kernel) is affected
- 3.13.11-03131104 is affected (and so are a few other 3.13.x that I tested)
- 3.14.1-031401 works (and so do all 3.14.x at least up to 3.14.9-031409)
- 3.15.4-031504 works
- 3.16.0-031600rc2 and rc4 both work

[penalvch (penalvch)]

Luca Lesinigo, 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 the default Ubuntu 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

[Serhiy (xintx-ua)]

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1360410

[Kim Tyler (ktyler)]

After latest updates, problem has gone away. I will continue to use it for a while to ensure that wireless doesn't freeze as it had beofre. If, I will open new problem.

For me, please assume that this problem is fixed.

uname gives :- Linux host 3.13.0-34-generic #60-Ubuntu SMP Wed Aug 13 15:45:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

[penalvch (penalvch)]

Kim Tyler, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1318837/comments/30 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[Sergio Callegari (callegar)]

Started to see this on an eeepc after upgrade to utopic, that basically made the wifi so fragile that the laptop cannot be used.

[Sergio Callegari (callegar)]

Actually happens with queue 2

[penalvch (penalvch)]

Sergio Callegari, thank you for your comment. Unfortunately, as this bug report is closed, it is not scoped to you, or your problem. 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 the default Ubuntu 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.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

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