*** This bug is a duplicate of bug 1350480 ***
https://bugs.launchpad.net/bugs/1350480
** This bug has been marked a duplicate of bug 1350480
[REGRESSION] Kernel update renders Intel NUC (i5-3427) unbootable with USB
devices plugged in
--
You received this bug notification because you
The patch has been somewhat reworked and added to the upstream mainline kernel
3.17-rc3, and to the 3.16-stable tree.
https://lkml.org/lkml/2014/8/29/386
http://www.spinics.net/lists/stable/msg59724.html
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Tags added: cherry-pick
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1330530
Title:
[Dell Vostro 430] Regression:
Julius Werner, the author of the commit in question, has found the problem and
created a patch. The problem is in the place that I identified, but specific
regression-triggering details are different that I originally thought. The
patch is available here:
https://lkml.org/lkml/2014/7/8/571
I
I think that I may have found the bug, and since the newest upstream kernel
3.16.0-rc3 has the affected code essentially unmodified, I contacted the
maintainer of the XHCI driver and the author of the problematic commit. I also
asked for help on linux-usb kernel mailing list:
Christopher, due to the nature of this bug, I cannot perform the reverse
bisect. I explained it already in comment #8. Just to be clearer: the
regression has not been fixed upstream. There is no 3.x kernel branch
which would contain the regression and the subsequent fix. The
regression either is
Maciej Puzio, while the initial regression commit is identified, the
upstream fix commit has not been. Could you please provide this?
** Tags added: bisect-done needs-reverse-bisect
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification
** Tags removed: needs-reverse-bisect
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1330530
Title:
[Dell Vostro
I think is a similar problem here
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1333229
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1330530
Title:
[Dell Vostro 430]
After testing this thoroughly, I am confident to say that the regression is
caused by commit usb: xhci: Prefer endpoint context dequeue pointer over
stopped_trb. In ubuntu-precise git repository this is commit
f04e4b02bce3a0ce19f9673bbefde9b8c624c00a.
However, an equivalent commit is part of
I bisected commits between Ubuntu-3.2.0-63.95 and Ubuntu-3.2.0-64.97,
and arrived at a specific xhci-related commit. However, manual
modification of the relevant file to revert the effects of this commit
yielded a kernel that still suffered from a regression. Further
complicating the matter is the
I have tested 28 mainline kernels from 9 branches currently maintained
(3.2, 3.4, 3.10, 3.11, 3.12, 3.13, 3.14, 3.15, 3.16), focusing on those
that were built around the time the problematic commit was introduced
(May-June 2014). The bug appears to affect the 3.2 branch exclusively.
Thus I will
** Summary changed:
- Regression: Kernel 3.2.0-64 problems with USB3 controller
+ [Dell Vostro 430] Regression: Kernel 3.2.0-64 problems with USB3 controller
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I have tested the mainline kernel 3.2.60, and was able to reproduce the
problem, with exactly the same symptoms as with kernel 3.2.0-64 (3.2.59).
Kernel URL: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.60-precise/
I also tested Western Digital My Passport 2TB USB 3.0 drive (Part#
Maciej Puzio, the next step is to fully reverse commit bisect the kernel
in order to identify the offending commit. Could you please do this
following
https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F
?
--
You received this bug notification because you
15 matches
Mail list logo
