On Sun, Jun 12, 2016 at 06:47:56PM +0200, Marc Haber wrote: > On Sat, Jun 11, 2016 at 02:55:04PM +0200, Marc Haber wrote: > > 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. > > The kernel panic on boot is caused by bugs in the parport part. I > worked around these by disabling PARPORT in the kernel configuration. May I ask which bug in parport are you reffering to? There was a bad commit in ppdev which caused boot failure and that was reverted. But in parport?? regards sudip -- 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
