On Thu, Feb 16, 2017 at 08:06:04PM +0100, Pavel Machek wrote:
> On Thu 2017-02-16 18:25:35, Pavel Machek wrote:
> > Hi!
> >
> > > > > 4.10-rc4 broken
> > > > > 4.10-rc3 ok
> > > >
> > > > Hmm. If those actually end up being reliable, then there's not a whole
> > > > lot in between them wrt PCI or USB.
> > > >
> > > > What looked like the most likely candidate seems to be xhci-specific, though.
> > > >
> > > > But maybe it's something that isn't directly in drivers/{pci,usb}/ and
> > > > just interacts badly.
> > >
> > > Ok. I _hope_ my tests are ok. Bisect log so far is:
> >
> > And the winner is:
> >
> > pavel@half:/data/l/linux$ git bisect bad
> > 24b91e360ef521a2808771633d76ebc68bd5604b is the first bad commit
> > commit 24b91e360ef521a2808771633d76ebc68bd5604b
> > Author: Frederic Weisbecker <fweisbec@xxxxxxxxx>
> > Date: Wed Jan 4 15:12:04 2017 +0100
> >
> > nohz: Fix collision between tick and other hrtimers
> >
>
> I had to revert 7bdb59f1ad474bd7161adc8f923cdef10f2638d1, too,
> otherwise -rc8 does not compile.
>
> With 24b91e360ef521a28087716 and 7bdb59f1ad474 reverted, it seems to
> boot ok. (I did few tries.)
Do you still have the config that triggered this? I don't have much expectations
about reproducing, this has almost never worked for me, but at least I could narrow
down the context.
Thanks.
