On Sat, Nov 17, 2012 at 10:24:19AM -0800, Greg KH wrote: > On Sat, Nov 17, 2012 at 06:40:07PM +0100, Piergiorgio Sartor wrote: > > Hi all, > > > > I followed this instructions: http://wiki.gentoo.org/wiki/Kernel_git-bisect > > The result, unless I did something incorrect, is: > > > > Bisecting: a merge base must be tested > > [28a33cbc24e4256c143dce96c7d93bf423229f92] Linux 3.5 > > Bisecting: 5128 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: 559 revisions left to test after this (roughly 9 steps) > > [07c7f79ee1c7e6288c614ba88005a8de6dbaadff] staging:iio:imu:adis16400 drop sysfs interface for manual device reset. > > Bisecting: 279 revisions left to test after this (roughly 8 steps) > > [a2b520b7867c964bb629633c1f909f6ac901f91b] staging: comedi: rtd520: remove RtdInterruptClear macro > > Bisecting: 139 revisions left to test after this (roughly 7 steps) > > [b94cea48ab8428ae803f4e27131367574295853d] staging: comedi: adl_pci7296: remove the private data > > Bisecting: 69 revisions left to test after this (roughly 6 steps) > > [f2a64902e3c2ffa34b52e6ad13e8e3c40f6919c7] staging: comedi: dyna_pci10xx: fix detach > > Bisecting: 34 revisions left to test after this (roughly 5 steps) > > [f58bfd88be490c0f9e25d980abe1976ceef00647] staging: csr: remove CsrUtf16String typedef > > Bisecting: 17 revisions left to test after this (roughly 4 steps) > > [6a4f6d38a34a992f8fd1572fc8d5706c11089d5e] staging: csr: remove CsrStrChr() > > Bisecting: 8 revisions left to test after this (roughly 3 steps) > > [4fe9db37104f833972486355fe86d7dcd29279b5] staging: csr: remove CsrMemFree() and CsrMemFreeDma() > > Bisecting: 4 revisions left to test after this (roughly 2 steps) > > [55a27055b9ea5aabf8206ed6b7777c79f4e840c3] staging: csr: remove CsrPmemFree() > > Bisecting: 2 revisions left to test after this (roughly 1 step) > > [eaae2e9223e859cd968b58bd3173a3f17b50538d] staging: csr: remove csr_pmem.h > > Bisecting: 0 revisions left to test after this (roughly 1 step) > > [419e9266884fa853179ab726c27a63a9d3ae46e3] staging: csr: delete a bunch of unused library functions > > b13bc8dda81c54a66a1c84e66f60b8feba659f28 is the first bad commit > > > > Now is your turn... :-) > > Are you using the csr driver? I somehow doubt that, given that I know > what hardware that supports, and it isn't USB. No, the "csr" has nothing to do with it, since the kernel with the "csr" modifications are working. Commit b13bc8dda81c54a66a1c84e66f60b8feba659f28 was the first bisect step, that would be: 'staging-3.6-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging If I'm not wrong. > How did you test each kernel for failure or not? Did you install it and > boot with it? Of course (and it lasted forever). The first bisect was giving *immediately* the error, all the others were fine. I do not think I took the wrong branch, since that should have delivered, if I get it correctly, always error. The test was always the same: start the system, attach the USB chain, access all the disks in parallel. This was stopping with error -110 in the first pass, all the others were, as wrote above, fine. What was exactly commit b13bc8dda81c54a66a1c84e66f60b8feba659f28 ? 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
