** This bug is no longer a duplicate of bug 1449090
1814:3290 wifi broken on RT3290 [ieee80211 phy0: rt2x00queue_flush_queue:
Warning - Queue 2 failed to flush]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
*** This bug is a duplicate of bug 1449090 ***
https://bugs.launchpad.net/bugs/1449090
** This bug has been marked a duplicate of bug 1449090
wifi insufficient on RT3290 [ieee80211 phy0: rt2x00queue_flush_queue:
Warning - Queue 2 failed to flush]
--
You received this bug notification be
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
Actually happens with queue 2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318837
Title:
1814:0201 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0
failed to flush
To manage notificat
Started to see this on an eeepc after upgrade to utopic, that basically
made the wifi so fragile that the laptop cannot be used.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318837
Title:
1814:020
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 lin
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:2
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1360410
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1318837
Title:
1814:0201 ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 0
faile
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 th
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:
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
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
--
You received this bug notification because you are a member
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 crashe
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.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
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, an
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
?
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You
16 matches
Mail list logo
