Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: Possible regression due to "tick: broadcast: Prevent livelock from event handler"
Date: Fri, 3 Jul 2015 15:19:40 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.11.1507031511180.3916@nanos> (raw)
In-Reply-To: <20150703105441.GF1521@katana>

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

  parent reply	other threads:[~2015-07-03 13:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03  2:40 Possible regression due to "tick: broadcast: Prevent livelock from event handler" Simon Horman
2015-07-03  6:46 ` Geert Uytterhoeven
2015-07-03  9:23   ` Thomas Gleixner
2015-07-03 10:54 ` Wolfram Sang
2015-07-03 11:02   ` Russell King - ARM Linux
2015-07-03 11:07     ` Wolfram Sang
2015-07-03 11:13       ` Russell King - ARM Linux
2015-07-03 11:41         ` Wolfram Sang
2015-07-03 13:19   ` Thomas Gleixner [this message]
2015-07-03 13:32     ` Wolfram Sang
2015-07-03 14:17       ` Thomas Gleixner
2015-07-03 14:37         ` Wolfram Sang
2015-07-03 14:45           ` Sudeep Holla
2015-07-03 14:54             ` Thomas Gleixner
2015-07-03 14:57               ` Sudeep Holla
2015-07-03 14:53           ` Thomas Gleixner
2015-07-03 15:09             ` Wolfram Sang
2015-07-03 15:23               ` Thomas Gleixner
2015-07-03 15:40                 ` Wolfram Sang
2015-07-03 15:53                   ` Thomas Gleixner
2015-07-03 16:00                     ` Wolfram Sang
2015-07-06  4:42               ` Magnus Damm
2015-07-29  2:23             ` Simon Horman
2015-07-03 17:02           ` Geert Uytterhoeven
2015-07-06  4:45             ` Magnus Damm

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.11.1507031511180.3916@nanos \
    --to=tglx@linutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox