[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1507031511180.3916@nanos>
Date: Fri, 3 Jul 2015 15:19:40 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Wolfram Sang <wsa@...-dreams.de>
cc: Simon Horman <horms@...ge.net.au>,
Kevin Hilman <khilman@...nel.org>,
Tyler Baker <tyler.baker@...aro.org>,
Borislav Petkov <bp@...en8.de>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Magnus Damm <magnus.damm@...il.com>, linux-sh@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: Possible regression due to "tick: broadcast: Prevent livelock
from event handler"
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 majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists