Public bug reported:
Currently package zfsutils-linux contains systemd target file
/lib/systemd/system/zfs.target that specifies following dependencies:
Requires=zfs-mount.service
Requires=zfs-share.service
Wants=zed.service
zfs-share.service is not essential in setups where file sharing is not
Joseph, thank you for pointing my attention to this bug. On my hardware
(bug 1330530) the problem is not reproducible with kernel 3.13.y, so
unfortunately I can neither confirm nor deny whether your test kernel
fixes it. However, I would very much like to see the patch being
backported to 3.2.y.
The patch has been added to the upstream mainline kernel 3.17-rc3, and
to the 3.16-stable tree. Please see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1330530/comments/16
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
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
Problem has been identified and patch created. Please see the following link
for details:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1330530/comments/15
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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
This is interesting:
[ 4650.205313] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with
disabled ep f3133600
[ 4650.205329] xhci_hcd :05:00.0: xHCI xhci_drop_endpoint called with
disabled ep f313362c
I am getting the same errors with most USB 3.0 devices that I tried. These
errors
** 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
Roman, compared to bugs 1330530 and 1328984, you have a similar USB 3.0
controller: ASM1042 (this bug) vs ASM1042A (other bugs). So this may be
the same issue. Would you be able to test the regression with other USB
devices?
--
You received this bug notification because you are a member of
I'm trying to find similarities between this bug and the bugs I reported.
Speaking about the devices mentioned above, but only those that cause problems:
1. Is any a USB 3.0 device?
2. If you boot with any of the problematic devices plugged in, do you
experience boot problems of any kind (stuck,
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
tl;dr: This bug report is a duplicate of bug 1330530.
I am going to focus my efforts on bug 1330530, and I do not intend to do
any work on this bug report until bug 1330530 is resolved. This is
because doing the same work twice is not a good use of time and effort
of anybody involved. Please do
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
I have tested kernels 3.16.0-031600rc1-generic and 3.2.60-030260-generic. On
the former, the problem does not appear, on the latter, the bug is replicated
with similar symptoms as on 3.2.0-64. I used a flash drive with a vanilla
Ubuntu 12.04 desktop install for all tests. To summarize kernels
** Tags removed: kernel-fixed-upstream-3.16
** Tags added: kernel-fixed-upstream-3.16-rc1
--
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/1328984
Title:
[Dell PowerEdge R510] Regression:
** 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/1328984
Title:
[Dell PowerEdge R510] Regression: Kernel 3.2.0-64 fails
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#
Public bug reported:
This bug report is a follow-up to bug 1328984, describing a successful
attempt to replicate that bug on another hardware. As advised, I am
opening a new bug to avoid mixing information related to two hardware
configurations.
Conditions triggering this bug:
As the original
** Attachment added: Result of apport-cli
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1330530/+attachment/4132664/+files/bug1330530.apport
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
A few notes regarding the contents of the apport file submitted above:
1. Times logged in syslog are incorrect and do not reflect the 18-minute delay.
It appears that rsyslog is started after the delay and logs its startup time,
not the real time of events.
2. Nouveau segfaults are not related
I have created a new bug report describing this problem replicated on another
hardware: bug 1330530
As that is a test machine entirely devoted to this issue, I will test the
upstream kernel on it and post the results in bug 1330530.
Regarding testing of the upstream kernel on PowerEdge
I'm attaching the file generated by command:
apport-cli -f -p linux --save bug1328984.apport
This was done with the machine running 12.04 Server with kernel 3.2.0-63.
May I ask for the reply to my question about the results of testing the
problem on a different hardware? (The regression has been
I am unable to submit apport-collected data due to what appears to be
numerous bugs in apport tools:
1. Submitting data directly from the affected machine is not possible
due to apport not being able to connect through a proxy.
2. Following instructions on referenced page to submit previously
** Project changed: software-center = linux-meta (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1328984
Title:
Regression: Kernel 3.2.0-64 fails to boot with USB3
I am unable to run the apport-collect command for two reasons:
1. The bug in question renders the machine unbootable. To boot the
machine and run apport-collect, it is necessary to change either the
software or hardware configuration. This would create an environment in
which bug is not
28 matches
Mail list logo
