On Fri, 3 Jul 2015, Wolfram Sang wrote: > Hi Simon, > > > I have observed what appears to be a regression while testing next-20150702 > > which seems to be caused by 2951d5c031a3 ("tick: broadcast: Prevent > > livelock from event handler"). > > Does reverting help? I see a similar case with your branch > renesas-devel-20150629-v4.1 which does not include both commits.
This branch has actually none of the clockevent/tick related changes which are in next/linus tree. So 2951d5c031a3 is hardly the culprit. > For this branch, if I select CONFIG_NO_HZ_IDLE and *no* > CONFIG_HIGH_RES_TIMERS, So with high res timers it boots. Can you please provide the output of /proc/timer_list for that case? Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/