Adrian Bunk <[EMAIL PROTECTED]> writes:
> I think I got your problem: > > After rebooting, you do "git bisect [bad|good]" *once*. > > Then recompile the kernel from the current tree, reboot, and again > *once* "git bisect [bad|good]". > > etc. Sounds right. Someone else doing the bisect suggested that 0475ac0845f9295bc5f69af45f58dff2c104c8d1 is the problem commit. Unfortunately I can't see anything wrong there. Sid when you get that far if you can confirm or deny that 0475ac0845f9295bc5f69af45f58dff2c104c8d1 is the problem commit I would appreciate the extra data point. Having two people report the problem at the exact same place would confirm for me that we actually have a good trace, and that I really am blind. Eric - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
