[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
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
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
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
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,
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
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,
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
** 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
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
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
11 matches
Mail list logo
