On Mon, Oct 07, 2013 at 05:17:20PM +0800, Fengguang Wu wrote:
> On Mon, Oct 07, 2013 at 10:49:57AM +0200, Peter Zijlstra wrote:
> The numbers in the below two lines mean
> 
> > > git bisect good c31eeaced22ce8bd61268a3c595d542bb38c0a4f  # 21:59    450+  Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
> > > git bisect  bad a0cf1abc25ac197dd97b857c0f6341066a8cb1cf  # 21:59      0-  Add linux-next specific files for 20130927
> 
> 21:59 => wall time
> 
> 450+  => this bisect test finishes after 450 good boots; suffix "+" means bisect test result is GOOD
>          (collected large enough samples to claim it a GOOD kernel/commit)
> 
> 0-    => this bisect test finishes after   0 good boots; suffix "-" means bisect test result is BAD
>          (it sees the message "BUG: unable to handle kernel ..." on the first boot)
> 
> Since all the BAD commits see only 0, 1, or 2 good boots (the lines
> with "0-", "1-", "2-") before see the bug message, it means the
> problem is pretty reproducible.

But the reported bad commit was: 0c44c2d0f459cd7e275242b72f500137c4fa834d
which is not the same number as your last BAD line.