On Wed, May 22 2013, Jens Axboe wrote: > On Wed, May 22 2013, Edoardo Comar wrote: > > > > > > It would help a lot if you could do a git bisect and reliably find out > > > which commit caused the problem. The procedure is something like this, > > > assuming you are in the fio git repository: > > > > > > You continue this process until it tells you which one is the offending > > > commit. Then you mail that here :-) > > > > > > -- > > > Jens Axboe > > > > > > > Thanks for the detailed explanataion > > please find the log below, > > Edo > > > > [ecomar@edow500 fio]$ git bisect bad > > Bisecting: 0 revisions left to test after this (roughly 0 steps) > > [78c1111eacdb594e0488d5adc508091fc2a3af88] Fix variable type warning > > > > [ecomar@edow500 fio]$ git bisect log > > git bisect start > > # good: [ffa93ca9d8d37ef795904773a22bf4ea77f58373] Fio 2.0.13 > > git bisect good ffa93ca9d8d37ef795904773a22bf4ea77f58373 > > # bad: [4728b3c82f07612d64b79a67adc31dd9ca3c79fc] fusion atomic: retrieve > > all capabilities and support larger writes > > git bisect bad 4728b3c82f07612d64b79a67adc31dd9ca3c79fc > > # good: [73cfb8a7da365c37253662477edb54ecc19575df] Merge branch 'gfio' of > > ssh://brick.kernel.dk/data/git/fio into gfio > > git bisect good 73cfb8a7da365c37253662477edb54ecc19575df > > # bad: [44583e022320424d145dbf01d51480e4c9a71126] Fixup commit error in > > 56c796 > > git bisect bad 44583e022320424d145dbf01d51480e4c9a71126 > > # bad: [fd112d34a2cfdc2d9efcd394e38b6d87b357c23d] Fix percentile_list > > option > > git bisect bad fd112d34a2cfdc2d9efcd394e38b6d87b357c23d > > # bad: [cfd94f79c362da249d22a59b6ede367ce3d2ba1d] configure: fixup Windows > > git bisect bad cfd94f79c362da249d22a59b6ede367ce3d2ba1d > > # bad: [17f0fd39d8b1f8edb420721c38302bd46254db03] axmap: clear > > map->first_free when we reset it > > git bisect bad 17f0fd39d8b1f8edb420721c38302bd46254db03 > > # bad: [c81f9347e5849a6b97a02f215f1c474e27c79f1a] Add CONFIG_64BIT_LLP64, > > CONFIG_POSIX_FALLOCATE and CONFIG_LINUX_FALLOCATE to Makefile. > > git bisect bad c81f9347e5849a6b97a02f215f1c474e27c79f1a > > # bad: [d537c08b0eacdeb05835ee8c5f269b872239713a] Add a check avoid > > segfault > > git bisect bad d537c08b0eacdeb05835ee8c5f269b872239713a > > # bad: [67bf982340d95ca98098ea050b54b4c7adb116c0] Add configure script > > git bisect bad 67bf982340d95ca98098ea050b54b4c7adb116c0 > > [ecomar@edow500 fio]$ > > So 67bf982340d95ca98098ea050b54b4c7adb116c0 is the first bad commit, > funky. Ah I think I see what it is, hang on. http://git.kernel.dk/?p=fio.git;a=commit;h=4b20c6814d4742e27a68f8a740a955283869fbcd If you git pull, you'll get that. Please see if that makes it behave like 2.0.13 for you. -- Jens Axboe -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
