From: Wolfram Sang <wsa@the-dreams.de>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: Possible regression due to "tick: broadcast: Prevent livelock from event handler"
Date: Fri, 03 Jul 2015 13:32:45 +0000 [thread overview]
Message-ID: <20150703133245.GA19284@katana> (raw)
In-Reply-To: <alpine.DEB.2.11.1507031511180.3916@nanos>
[-- Attachment #1: Type: text/plain, Size: 2031 bytes --]
> So with high res timers it boots. Can you please provide the output of
> /proc/timer_list for that case?
Sure:
Timer List Version: v0.7
HRTIMER_MAX_CLOCK_BASES: 4
now at 40752899169 nsecs
cpu: 0
clock 0:
.base: c03aa990
.index: 0
.resolution: 1 nsecs
.get_time: ktime_get
.offset: 0 nsecs
active timers:
#0: tick_cpu_sched, tick_sched_timer, S:01
# expires at 40760000000-40760000000 nsecs [in 7100831 to 7100831 nsecs]
#1: sched_clock_timer, sched_clock_poll, S:01
# expires at 21474836475000000-21474836475000000 nsecs [in 21474795722100831 to 21474795722100831 nsecs]
clock 1:
.base: c03aa9c8
.index: 1
.resolution: 1 nsecs
.get_time: ktime_get_real
.offset: 0 nsecs
active timers:
clock 2:
.base: c03aaa00
.index: 2
.resolution: 1 nsecs
.get_time: ktime_get_boottime
.offset: 0 nsecs
active timers:
clock 3:
.base: c03aaa38
.index: 3
.resolution: 1 nsecs
.get_time: ktime_get_clocktai
.offset: 0 nsecs
active timers:
.expires_next : 40760000000 nsecs
.hres_active : 1
.nr_events : 770
.nr_retries : 29
.nr_hangs : 0
.max_hang_time : 0 nsecs
.nohz_mode : 2
.last_tick : 40400000000 nsecs
.tick_stopped : 0
.idle_jiffies : 4294941337
.idle_calls : 378
.idle_sleeps : 354
.idle_entrytime : 40743316650 nsecs
.idle_waketime : 40743316650 nsecs
.idle_exittime : 40743377685 nsecs
.idle_sleeptime : 37586425789 nsecs
.iowait_sleeptime: 0 nsecs
.last_jiffies : 4294941368
.next_jiffies : 4294941389
.idle_expires : 40930000000 nsecs
jiffies: 4294941371
Tick Device: mode: 1
Per CPU device: 0
Clock Event Device: e0180000.timer
max_delta_ns: 131071523464982
min_delta_ns: 61035
mult: 70369
shift: 31
mode: 3
next_event: 40760000000 nsecs
set_next_event: em_sti_clock_event_next
set_mode: em_sti_clock_event_mode
event_handler: hrtimer_interrupt
retries: 0
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: wsa@the-dreams.de (Wolfram Sang)
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:32:45 +0200 [thread overview]
Message-ID: <20150703133245.GA19284@katana> (raw)
In-Reply-To: <alpine.DEB.2.11.1507031511180.3916@nanos>
> So with high res timers it boots. Can you please provide the output of
> /proc/timer_list for that case?
Sure:
Timer List Version: v0.7
HRTIMER_MAX_CLOCK_BASES: 4
now at 40752899169 nsecs
cpu: 0
clock 0:
.base: c03aa990
.index: 0
.resolution: 1 nsecs
.get_time: ktime_get
.offset: 0 nsecs
active timers:
#0: tick_cpu_sched, tick_sched_timer, S:01
# expires at 40760000000-40760000000 nsecs [in 7100831 to 7100831 nsecs]
#1: sched_clock_timer, sched_clock_poll, S:01
# expires at 21474836475000000-21474836475000000 nsecs [in 21474795722100831 to 21474795722100831 nsecs]
clock 1:
.base: c03aa9c8
.index: 1
.resolution: 1 nsecs
.get_time: ktime_get_real
.offset: 0 nsecs
active timers:
clock 2:
.base: c03aaa00
.index: 2
.resolution: 1 nsecs
.get_time: ktime_get_boottime
.offset: 0 nsecs
active timers:
clock 3:
.base: c03aaa38
.index: 3
.resolution: 1 nsecs
.get_time: ktime_get_clocktai
.offset: 0 nsecs
active timers:
.expires_next : 40760000000 nsecs
.hres_active : 1
.nr_events : 770
.nr_retries : 29
.nr_hangs : 0
.max_hang_time : 0 nsecs
.nohz_mode : 2
.last_tick : 40400000000 nsecs
.tick_stopped : 0
.idle_jiffies : 4294941337
.idle_calls : 378
.idle_sleeps : 354
.idle_entrytime : 40743316650 nsecs
.idle_waketime : 40743316650 nsecs
.idle_exittime : 40743377685 nsecs
.idle_sleeptime : 37586425789 nsecs
.iowait_sleeptime: 0 nsecs
.last_jiffies : 4294941368
.next_jiffies : 4294941389
.idle_expires : 40930000000 nsecs
jiffies: 4294941371
Tick Device: mode: 1
Per CPU device: 0
Clock Event Device: e0180000.timer
max_delta_ns: 131071523464982
min_delta_ns: 61035
mult: 70369
shift: 31
mode: 3
next_event: 40760000000 nsecs
set_next_event: em_sti_clock_event_next
set_mode: em_sti_clock_event_mode
event_handler: hrtimer_interrupt
retries: 0
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150703/f70827a7/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Simon Horman <horms@verge.net.au>,
Kevin Hilman <khilman@kernel.org>,
Tyler Baker <tyler.baker@linaro.org>,
Borislav Petkov <bp@alien8.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
linux-sh@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: Possible regression due to "tick: broadcast: Prevent livelock from event handler"
Date: Fri, 3 Jul 2015 15:32:45 +0200 [thread overview]
Message-ID: <20150703133245.GA19284@katana> (raw)
In-Reply-To: <alpine.DEB.2.11.1507031511180.3916@nanos>
[-- Attachment #1: Type: text/plain, Size: 2031 bytes --]
> So with high res timers it boots. Can you please provide the output of
> /proc/timer_list for that case?
Sure:
Timer List Version: v0.7
HRTIMER_MAX_CLOCK_BASES: 4
now at 40752899169 nsecs
cpu: 0
clock 0:
.base: c03aa990
.index: 0
.resolution: 1 nsecs
.get_time: ktime_get
.offset: 0 nsecs
active timers:
#0: tick_cpu_sched, tick_sched_timer, S:01
# expires at 40760000000-40760000000 nsecs [in 7100831 to 7100831 nsecs]
#1: sched_clock_timer, sched_clock_poll, S:01
# expires at 21474836475000000-21474836475000000 nsecs [in 21474795722100831 to 21474795722100831 nsecs]
clock 1:
.base: c03aa9c8
.index: 1
.resolution: 1 nsecs
.get_time: ktime_get_real
.offset: 0 nsecs
active timers:
clock 2:
.base: c03aaa00
.index: 2
.resolution: 1 nsecs
.get_time: ktime_get_boottime
.offset: 0 nsecs
active timers:
clock 3:
.base: c03aaa38
.index: 3
.resolution: 1 nsecs
.get_time: ktime_get_clocktai
.offset: 0 nsecs
active timers:
.expires_next : 40760000000 nsecs
.hres_active : 1
.nr_events : 770
.nr_retries : 29
.nr_hangs : 0
.max_hang_time : 0 nsecs
.nohz_mode : 2
.last_tick : 40400000000 nsecs
.tick_stopped : 0
.idle_jiffies : 4294941337
.idle_calls : 378
.idle_sleeps : 354
.idle_entrytime : 40743316650 nsecs
.idle_waketime : 40743316650 nsecs
.idle_exittime : 40743377685 nsecs
.idle_sleeptime : 37586425789 nsecs
.iowait_sleeptime: 0 nsecs
.last_jiffies : 4294941368
.next_jiffies : 4294941389
.idle_expires : 40930000000 nsecs
jiffies: 4294941371
Tick Device: mode: 1
Per CPU device: 0
Clock Event Device: e0180000.timer
max_delta_ns: 131071523464982
min_delta_ns: 61035
mult: 70369
shift: 31
mode: 3
next_event: 40760000000 nsecs
set_next_event: em_sti_clock_event_next
set_mode: em_sti_clock_event_mode
event_handler: hrtimer_interrupt
retries: 0
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-07-03 13:32 UTC|newest]
Thread overview: 75+ 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 2:40 ` Simon Horman
2015-07-03 2:40 ` Simon Horman
2015-07-03 6:46 ` Geert Uytterhoeven
2015-07-03 6:46 ` Geert Uytterhoeven
2015-07-03 6:46 ` Geert Uytterhoeven
2015-07-03 9:23 ` Thomas Gleixner
2015-07-03 9:23 ` Thomas Gleixner
2015-07-03 9:23 ` Thomas Gleixner
2015-07-03 10:54 ` Wolfram Sang
2015-07-03 10:54 ` Wolfram Sang
2015-07-03 10:54 ` Wolfram Sang
2015-07-03 11:02 ` Russell King - ARM Linux
2015-07-03 11:02 ` Russell King - ARM Linux
2015-07-03 11:02 ` Russell King - ARM Linux
2015-07-03 11:07 ` Wolfram Sang
2015-07-03 11:07 ` Wolfram Sang
2015-07-03 11:07 ` Wolfram Sang
2015-07-03 11:13 ` Russell King - ARM Linux
2015-07-03 11:13 ` Russell King - ARM Linux
2015-07-03 11:13 ` Russell King - ARM Linux
2015-07-03 11:41 ` Wolfram Sang
2015-07-03 11:41 ` Wolfram Sang
2015-07-03 11:41 ` Wolfram Sang
2015-07-03 13:19 ` Thomas Gleixner
2015-07-03 13:19 ` Thomas Gleixner
2015-07-03 13:19 ` Thomas Gleixner
2015-07-03 13:32 ` Wolfram Sang [this message]
2015-07-03 13:32 ` Wolfram Sang
2015-07-03 13:32 ` Wolfram Sang
2015-07-03 14:17 ` Thomas Gleixner
2015-07-03 14:17 ` Thomas Gleixner
2015-07-03 14:17 ` Thomas Gleixner
2015-07-03 14:37 ` Wolfram Sang
2015-07-03 14:37 ` Wolfram Sang
2015-07-03 14:37 ` Wolfram Sang
2015-07-03 14:45 ` Sudeep Holla
2015-07-03 14:45 ` Sudeep Holla
2015-07-03 14:45 ` Sudeep Holla
2015-07-03 14:54 ` Thomas Gleixner
2015-07-03 14:54 ` Thomas Gleixner
2015-07-03 14:54 ` Thomas Gleixner
2015-07-03 14:57 ` Sudeep Holla
2015-07-03 14:57 ` Sudeep Holla
2015-07-03 14:57 ` Sudeep Holla
2015-07-03 14:53 ` Thomas Gleixner
2015-07-03 14:53 ` Thomas Gleixner
2015-07-03 14:53 ` Thomas Gleixner
2015-07-03 15:09 ` Wolfram Sang
2015-07-03 15:09 ` Wolfram Sang
2015-07-03 15:09 ` Wolfram Sang
2015-07-03 15:23 ` Thomas Gleixner
2015-07-03 15:23 ` Thomas Gleixner
2015-07-03 15:23 ` Thomas Gleixner
2015-07-03 15:40 ` Wolfram Sang
2015-07-03 15:40 ` Wolfram Sang
2015-07-03 15:40 ` Wolfram Sang
2015-07-03 15:53 ` Thomas Gleixner
2015-07-03 15:53 ` Thomas Gleixner
2015-07-03 15:53 ` Thomas Gleixner
2015-07-03 16:00 ` Wolfram Sang
2015-07-03 16:00 ` Wolfram Sang
2015-07-03 16:00 ` Wolfram Sang
2015-07-06 4:42 ` Magnus Damm
2015-07-06 4:42 ` Magnus Damm
2015-07-06 4:42 ` Magnus Damm
2015-07-29 2:23 ` Simon Horman
2015-07-29 2:23 ` Simon Horman
2015-07-29 2:23 ` Simon Horman
2015-07-03 17:02 ` Geert Uytterhoeven
2015-07-03 17:02 ` Geert Uytterhoeven
2015-07-03 17:02 ` Geert Uytterhoeven
2015-07-06 4:45 ` Magnus Damm
2015-07-06 4:45 ` Magnus Damm
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=20150703133245.GA19284@katana \
--to=wsa@the-dreams.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.