On Sat, Nov 17, 2012 at 01:06:42PM -0800, Greg KH wrote:
[...]
> Yes, but again, that has nothing to do with the USB subsystem at all, so
> I think you got a false-positive here somehow.
>
Thanks for the feedback, I did it again.
So, it seems I've no beginners luck, in fact it looks like I took a wrong
turn, in the first try.
New bisect log is:
Bisecting: 5071 revisions left to test after this (roughly 13 steps)
[b13bc8dda81c54a66a1c84e66f60b8feba659f28] Merge tag 'staging-3.6-rc1' of
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging
Bisecting: 2384 revisions left to test after this (roughly 12 steps)
[3c4cfadef6a1665d9cd02a543782d03d3e6740c6] Merge
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next
Bisecting: 1118 revisions left to test after this (roughly 10 steps)
[9fc377799bc9bfd8d5cb35d0d1ea2e2458cbdbb3] Merge tag 'usb-3.6-rc1' of
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb
Bisecting: 670 revisions left to test after this (roughly 9 steps)
[f14121ab35912e3d2e57ac9a4ce1f9d4b7baeffb] Merge tag 'dt-for-3.6' of
git://sources.calxeda.com/kernel/linux
Bisecting: 340 revisions left to test after this (roughly 8 steps)
[801b03653fc04de2cc5bc83c06de504d41345b63] Merge
git://git.kernel.org/pub/scm/linux/kernel/git/steve/gfs2-3.0-nmw
Bisecting: 170 revisions left to test after this (roughly 7 steps)
[b015cb79ce84944076a8a849055f898f2a4d6be8] USB: EHCI: return void instead of 0
Bisecting: 85 revisions left to test after this (roughly 7 steps)
[94c122ab01f84332c371dc4ae0f5b70e879173d6] [SCSI] ufs: fix incorrect return
value about SUCCESS and FAILED
Bisecting: 42 revisions left to test after this (roughly 6 steps)
[d81a5d1956731c453b85c141458d4ff5d6cc5366] USB: add
USB_VENDOR_AND_INTERFACE_INFO() macro
Bisecting: 19 revisions left to test after this (roughly 5 steps)
[6470cbc486652942dcf6c4b6420e3a521e766bbf] Merge tag 'for-usb-next-2012-07-11'
of git://git.kernel.org/pub/scm/linux/kernel/git/sarah/xhci into usb-next
Bisecting: 11 revisions left to test after this (roughly 4 steps)
[569b394f53f0abd177cc665c9b4ace89e3f4c7fb] USB: EHCI: always scan each
interrupt QH
Bisecting: 5 revisions left to test after this (roughly 3 steps)
[55934eb3b9fa52eb53b9d7342267fc73c38206aa] USB: EHCI: use hrtimer for (s)iTD
deallocation
Bisecting: 2 revisions left to test after this (roughly 2 steps)
[3c273a056bf46167f0a1309c2ba72282a17d2541] USB: EHCI: unlink multiple async QHs
together
Bisecting: 0 revisions left to test after this (roughly 1 step)
[361aabf395e4a23cf554cf4ec0c0c6963b8beb01] USB: EHCI: don't lose events during
a scan
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[32830f207691176234b4c4dd17f0d7ab6d87d94b] USB: EHCI: use hrtimer for unlinking
empty async QHs
32830f207691176234b4c4dd17f0d7ab6d87d94b is the first bad commit
commit 32830f207691176234b4c4dd17f0d7ab6d87d94b
Author: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
Date: Wed Jul 11 11:22:53 2012 -0400
USB: EHCI: use hrtimer for unlinking empty async QHs
This patch (as1583) changes ehci-hcd to use an hrtimer event for
unlinking empty (unused) async QHs instead of using a kernel timer.
The check for empty QHs is moved to a new routine, where it doesn't
require going through an entire scan of both the async and periodic
schedules. And it can unlink multiple QHs at once, unlike the current
code.
Signed-off-by: Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
:040000 040000 9767ca0f3b8c9fa0530e90730dc3106420412822
6b567d1137df3cdec9f19f835ea7c546491d9ca8 M drivers
Which looks like to me more consistent with the problem.
Your turn again,
bye,
--
piergiorgio
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
