* Andrew Morton <[EMAIL PROTECTED]> wrote: > > # bad: [6f37ac793d6ba7b35d338f791974166f67fdd9ba] Merge branch 'master' of > > master.kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6 > > git-bisect bad 6f37ac793d6ba7b35d338f791974166f67fdd9ba > > # good: [2f1f53bdc6531696934f6ee7bbdfa2ab4f4f62a3] CRISv10 fasttimer: Scrap > > INLINE and name timeval_cmp better > > git-bisect good 2f1f53bdc6531696934f6ee7bbdfa2ab4f4f62a3
> I'm struggling to see how any of those could have broken block device > mounting on alpha. Are you sure you bisected right? the bisection log looks healthy so far - with nicely alternating good/bad bisection points. Barring the possibility that the bug is non-deterministic, i'd guess the bisection points are OK, at least judging from their statistical properties. but ... i went over the diffs too, and i fail to see how they could affect the bootup path of an Alpha box, which i suspect has no networking dependency up to the failure point. Ingo - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html