From: Ingo Molnar <mingo@elte.hu>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Mike Galbraith <efault@gmx.de>, Oleg Nesterov <oleg@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: x86-tip.today: flood of WARNING: at include/linux/sched.h:2238 run_posix_cpu_timers+0xea/0x79f()
Date: Wed, 11 Feb 2009 13:53:40 +0100 [thread overview]
Message-ID: <20090211125340.GK16535@elte.hu> (raw)
In-Reply-To: <1234280251.23438.73.camel@twins>
* Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> On Fri, 2009-02-06 at 15:01 +0100, Ingo Molnar wrote:
> > * Mike Galbraith <efault@gmx.de> wrote:
> >
> > > Greetings,
> > >
> > > Futzing with kerneltop this morning, I fired up amarok to give it
> > > something light to monitor while I hunt missing events. Something bad
> > > happened, and when I finally (SysRq-E took minutes) got control of box
> > > back, dmesg was full of a steady stream of the below.
> > >
> > > That warning can be kinda unfriendly.
> > >
> > >
> > > [ 9964.600004] ------------[ cut here ]------------
> > > [ 9964.600006] WARNING: at include/linux/sched.h:2238 run_posix_cpu_timers+0xea/0x79f()
> >
> > ah, that's Peter's stuff:
> >
> > 4cd4c1b: timers: split process wide cpu clocks/timers
> > 32bd671: signal: re-add dead task accumulation stats.
> >
> > The discussion with Oleg resulted in the conclusion i
> > think that the warning is spurious and should be removed.
> >
> > I've commited the minimal fix below to tip:master. There's
> > more fixes needed too but this should solve the warning
> > flood at least.
>
> I think this is the 'minimal' paranoia version.
applied to tip:timers/urgent, thanks Peter!
Ingo
prev parent reply other threads:[~2009-02-11 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 8:56 Mike Galbraith
2009-02-06 14:01 ` Ingo Molnar
2009-02-10 15:37 ` Peter Zijlstra
2009-02-11 10:53 ` [PATCH] timers: fix TIMER_ABSTIME for process wide cpu timers Peter Zijlstra
2009-02-11 12:52 ` Ingo Molnar
2009-02-11 12:53 ` Ingo Molnar [this message]
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=20090211125340.GK16535@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®