Christopher,
I will do that.
I also wanted to note that I originally reported this as only occurring
on certain systems with AMD processors and nVidia chipsets. However, in
the meantime this has been duplicated on other hardware configurations
as well.
--
You received this bug notification
Christopher,
Here is the URL to my e-mail.
http://marc.info/?l=linux-usbm=143257694904313w=2
--
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/1456837
Title:
USB drive errors with kernel
Gary Dalmadge, just to clarify, you tested one commit behind the
suspected regression commit and there were no USB drive errors?
** Tags removed: needs-bisect
** Tags added: bisect-done
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Christopher,
I'm sorry if I was not clear. I see the errors with this commit:
==
commit d215f919d9f1c348b5df2eb40e867698e8a59e14 Ubuntu-3.13.0-35.62
Author: James Bottomley jbottom...@parallels.com
Date: Thu Jul 3 19:17:34 2014 +0200
scsi: handle flush errors properly
==
Gary Dalmadge, the issue you are reporting is an upstream one. Could you
please report this problem to the appropriate mailing list (linux-usb)
by following the instructions verbatim at
https://wiki.ubuntu.com/Bugs/Upstream/kernel ?
Please provide a direct URL to your e-mail to the mailing list
Christopher,
I have completed this as you requested.
Here is the output of the last git bisect command:
git bisect bad
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[d215f919d9f1c348b5df2eb40e867698e8a59e14] scsi: handle flush errors properly
I have also attached the output
Gary Dalmadge, the next step is to fully commit bisect from kernel 3.11
to 3.13 in order to identify the last good kernel commit, followed
immediately by the first bad one. This will allow for a more expedited
analysis of the root cause of your issue. Could you please do this
following
Gary Dalmadge, thank you for reporting this and helping make Ubuntu
better. Just to advise, there is a de-emphasis of support for 32-bit
operating systems upstream. Hence, is this reproducible in an x64
environment via http://cdimage.ubuntu.com/daily-live/current/vivid-
desktop-amd64.iso ?
**
Gary Dalmadge, could you please test the latest mainline kernel 4.1-rc4
and advise to the results?
** Tags added: vivid
** Changed in: linux (Ubuntu)
Importance: Low = Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Christopher,
I am able to duplicate the issue with the x64 mainline kernel 4.1-rc4 .
I do not see any changes in behavior.
Please let me know if you need more information or if I can try anything
else.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Christopher,
I should have mentioned in my original report that I had duplicated the
issue in x64 Trusty.
I also tried x64 Vivid via the link that you sent and have again
duplicated the issue.
I do not see any difference in behavior in either 64-bit or 32-bit
versions.
Again please let me know
11 matches
Mail list logo
