[Bug 1383555] Re: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush

2015-02-14 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete = Expired

-- 
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


[Bug 1383555] Re: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush

2014-12-16 Thread Kim Tyler
Sorry, I still don't understand.  All versions of the kernel are broken.
What would I bisect against?  In any case, the result would still be a
broken kernel, and would be of no help to isolate the problem.  To me,
it would appear to be a waste of time to do this.

-- 
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


[Bug 1383555] Re: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush

2014-12-16 Thread Christopher M. Penalver
Kim Tyler, to reconfirm 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383555/comments/9 :
This was NOT happening in precise, and WAS happening with early versions of 
trusty.

Is this still true?

If so, one would need to bisect from 3.2 to 3.13.

-- 
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


[Bug 1383555] Re: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush

2014-10-26 Thread Christopher M. Penalver
Kim Tyler, no problem. What you have done already is a kernel version
bisect. While this is good progress, as per the bisect article you would
need to continue by bisecting the commits between these kernel versions
to find the specific commit.

-- 
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


[Bug 1383555] Re: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush

2014-10-24 Thread Christopher M. Penalver
Kim Tyler, the next step is to fully commit bisect the kernel in order
to identify the offending commit. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection ?

** Tags added: needs-bisect

-- 
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


[Bug 1383555] Re: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush

2014-10-24 Thread Kim Tyler
Christoper,  I don't quite understand.  All versions of trusty show a
fault, as well as the newest version of upstream kernel.  The early
versions of trusty show the fault at boot, while the later versions show
the fault some time after boot.  What would the basis of the bisection
be?  If it was the change between showing the fault at boot, and then
happening some time later, that was done in bug 1318837. (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.) ie 3.14.0-rc2 has problem at boot, 3.14.0-rc3 has fault
sometime later, eg days after boot.  I'm happy to help, but need further
advice.

-- 
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


[Bug 1383555] Re: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush

2014-10-23 Thread Christopher M. Penalver
Kim Tyler, just to clarify, was there either a prior release (ex.
Precise), or earlier kernel versions in Trusty where this problem did
not exists?

** Changed in: linux (Ubuntu)
   Status: Confirmed = Incomplete

-- 
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


[Bug 1383555] Re: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush

2014-10-23 Thread Kim Tyler
This was NOT happening in precise, and WAS happening with early versions
of trusty.  I had a test partition with trusty to check it, prior to
fresh install of trusty.  It was clear that this was happening with
trusty from boot.  I filed a bug report for trusty, along with upstream
kernels that were checked.  The newest upstream kernels did not show
that errors from boot.  When trusty was updated some time later, and
this error did not present from boot, I took the opportunity to fresh
install trusty, and use that full time.  I reported that the error
seemed to be fixed, and you closed the report. (Bug 1318837 )

(my comment from bug 1318837 follows) :-

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

-- 
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


[Bug 1383555] Re: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush

2014-10-23 Thread Christopher M. Penalver
** Tags added: regression-release

-- 
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


[Bug 1383555] Re: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush

2014-10-23 Thread Christopher M. Penalver
Kim Tyler, just to clarify, focusing on the symptom of your wireless connection 
failing:
+ This did not happen in which kernel version specifically in Precise?
+ You advised in your prior report the problem went away in Trusty. However, it 
is now reproducible in Trusty. Which Trusty kernel specifically introduced this 
problem?

-- 
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


[Bug 1383555] Re: 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush

2014-10-23 Thread Kim Tyler
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 altsys-reqREISUB 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