git bisect goes wild?

[Jan Kara <jack@suse.cz>]

  Hi,

  I've been bisecting some change in Linux kernel. The output of
"git bisect log" is:
git-bisect start
# good: [bbf25010f1a6b761914430f5fca081ec8c7accd1] Linux 2.6.23
git-bisect good bbf25010f1a6b761914430f5fca081ec8c7accd1
# bad: [49914084e797530d9baaf51df9eda77babc98fa8] Linux 2.6.24
git-bisect bad 49914084e797530d9baaf51df9eda77babc98fa8
# bad: [fe071d7e8aae5745c009c808bb8933f22a9e305a] oom: add
# oom_kill_allocating_task sysctl
git-bisect bad fe071d7e8aae5745c009c808bb8933f22a9e305a
# good: [117494a1b65183f0e3fcc817b07944bc5c465050] Merge
# master.kernel.org:/pub/scm/linux/kernel/git/gregkh/usb-2.6
git-bisect good 117494a1b65183f0e3fcc817b07944bc5c465050
# bad: [419217cb1d0266f62cbea6cdc6b1d1324350bc34] Merge branch
# 'v2.6.24-lockdep' of
# git://git.kernel.org/pub/scm/linux/kernel/git/peterz/linux-2.6-lockdep
git-bisect bad 419217cb1d0266f62cbea6cdc6b1d1324350bc34
# good: [c8c55bcb43d790d97790cfa319d80045a71fde39] Merge
# git://git.infradead.org/mtd-2.6
git-bisect good c8c55bcb43d790d97790cfa319d80045a71fde39
# good: [3e9830dcabdeb3656855ec1b678b6bcf3b50261c] sched: run
# sched_domain_debug() if CONFIG_SCHED_DEBUG=y
git-bisect good 3e9830dcabdeb3656855ec1b678b6bcf3b50261c

  But after the last command, I was sent to commit
9ec76fbf7d6da3e98070a7059699d0ca019b0c9b which is far outside the window
between the last good and bad commit. How come? git version is 1.5.6.
  Thanks for any suggestions.

								Honza

PS: Please CC me since I'm not on the list.
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR