* Re: [sched] WARNING: CPU: 0 PID: 0 at kernel/time/hrtimer.c:802 hrtimer_forward()
[not found] <20150501044713.GA4365@wfg-t540p.sh.intel.com>
@ 2015-05-01 10:10 ` Peter Zijlstra
0 siblings, 0 replies; only message in thread
From: Peter Zijlstra @ 2015-05-01 10:10 UTC (permalink / raw)
To: Fengguang Wu; +Cc: Thomas Gleixner, Ben Segall, LKP, linux-kernel
On Fri, May 01, 2015 at 12:47:13PM +0800, Fengguang Wu wrote:
> commit 77a4d1a1b9a122ca1fa3507bd30aec1520d7a8a4
> sched: Cleanup bandwidth timers
> [ 64.000438] WARNING: CPU: 0 PID: 0 at kernel/time/hrtimer.c:802 hrtimer_forward+0x71/0x189()
Argh, yes of course. The problem is that the timer can be re-started
before the handler acquires the lock, and therefore the hrtimer_forwards
in the handler will trigger that WARN.
Lemme try and go convince this heap of snot that's occupying my brain
cavity to produce coherent thought and come up with a nice fix for that.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2015-05-01 10:10 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20150501044713.GA4365@wfg-t540p.sh.intel.com>
2015-05-01 10:10 ` [sched] WARNING: CPU: 0 PID: 0 at kernel/time/hrtimer.c:802 hrtimer_forward() Peter Zijlstra
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®