On Tue, Jun 07, 2016 at 10:30:17AM -0700, Greg KH wrote: > Nothing obvious, can you use 'git bisect' to go from 4.5.0 to 4.6.0 to > find the offending commit? I can. The first round of bisecting let me end up with c8b710b3e4348119924051551b836c94835331b1 as the first bad commit, which is wrong, since c8b710b3e4348119924051551b836c94835331b1^ is bad as well. I am not sure whether things went well since I had to use git bisect skip twice because the resulting kernel wouldn't boot on the pi. A second round of bisecting left me in limbo, since I do not understand this: [45/544]mh@fan[zgchroot kernel64][debian_chroot sid_kernel64]:~/linux/debug/linux$ git bisect reset HEAD is now at 2dcd0af... Linux 4.6 [46/545]mh@fan[zgchroot kernel64][debian_chroot sid_kernel64]:~/linux/debug/linux$ git bisect start [47/546]mh@fan[zgchroot kernel64][debian_chroot sid_kernel64]:~/linux/debug/linux$ git bisect bad [48/547]mh@fan[zgchroot kernel64][debian_chroot sid_kernel64]:~/linux/debug/linux$ git bisect bad c8b710b3e4348119924051551b836c94835331b1^ [49/548]mh@fan[zgchroot kernel64][debian_chroot sid_kernel64]:~/linux/debug/linux$ git bisect good v4.5 Some good revs are not ancestor of the bad rev. git bisect cannot work properly in this case. Maybe you mistook good and bad revs? [50/549]mh@fan[zgchroot kernel64][debian_chroot sid_kernel64]:~/linux/debug/linux$ Do I need to start over completely? Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421 -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
