Clarifying :-
+This particular problem never happened in precise.
+All trusty kernels have had this problem to some extent, the initial
release of trusty had this problem from boot, then sometime later
(sometime just before the time that bug 1318837 was closed - 28/8/14) it
changed to be intermittent.
The first version of trusty that I used in a separate bootable partition
(about 1 week after trusty was released) showed the symptom of giving
the log error of "ieee80211 phy0: rt2x00queue_flush_queue: Warning -
Queue 0 failed to flush" immediately after boot.
I continued to boot into this partition from time to time (about once
per week) to install updates and check on progress of this problem. My
main distro for general use was precise.
Some time later, I registered this bug, and did the investigation work
as bug 1318837.
Some time later, still booting in trusty about once per week and
installing updates etc, even though my main distro was precise, I
noticed that the errors did not occur immediately after boot in the
logs. I left it running for a day or so, and there was still no error
messages in the logs. I then put the entry in launchpad to say that it
seemed to be fixed, after which the bug was closed.
I then did a fresh install of trusty as my main distro, and I have been
running it ever since. This bug does not occur directly after reboot,
but sometimes more than several days after reboot. ( I generally don't
reboot for a week or weeks, unless I have to)
Currently, my uptime is about 30 hours, and the bug does not appear. I
rebooted when the above errors were flooding my logs.
The oldest date I have in /var/log/messages is October 1.
ls -laF /var/log/messages*
-rw-r----- 1 syslog adm 7166430 Oct 24 15:03 /var/log/messages
-rw-r----- 1 syslog adm 6681922 Oct 19 07:40 /var/log/messages.1
-rw-r----- 1 syslog adm 281449 Oct 13 08:03 /var/log/messages.2.gz
-rw-r----- 1 syslog adm 152830 Oct 5 08:03 /var/log/messages.3.gz
grep "ieee80211 phy0:" /var/log/messages{,.1}|wc -l
101843
zgrep "ieee80211 phy0:" /var/log/messages*gz | wc -l
28346
which is about 130,000 lines of errors.
I mainly leave my wireless turned off to avoid these errors, unless I have no
LAN available.
Sometimes when the wireless is turned on, and these errors are being logged,
the wireless will freeze up, then over a period of about 30 minutes, the PC
becomes increasingly uncontrollable/slower, then finally freezes, and only
power cycle or <alt><sys-req>REISUB can gain control again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1383555
Title:
1814:0201 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0
failed to flush
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383555/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
