[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1181299844.4404.303.camel@chaos>
Date: Fri, 08 Jun 2007 12:50:44 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Daniel Thaler <daniel@...aler.de>
Cc: Chris Wright <chrisw@...s-sol.org>, linux-kernel@...r.kernel.org,
stable@...nel.org, torvalds@...ux-foundation.org,
Justin Forbes <jmforbes@...uxtx.org>,
Zwane Mwaikambo <zwane@....linux.org.uk>,
Theodore Ts'o <tytso@....edu>,
Randy Dunlap <rdunlap@...otime.net>,
Dave Jones <davej@...hat.com>,
Chuck Wolber <chuckw@...ntumlinux.com>,
Chris Wedgwood <reviews@...cw.f00f.org>,
Michael Krufky <mkrufky@...uxtv.org>,
Chuck Ebbert <cebbert@...hat.com>,
Domenico Andreoli <cavokz@...il.com>,
akpm@...ux-foundation.org, alan@...rguk.ukuu.org.uk,
Greg Kroah-Hartman <gregkh@...e.de>
Subject: Re: [patch 03/54] NOHZ: Rate limit the local softirq pending
warning output
On Fri, 2007-06-08 at 12:34 +0200, Daniel Thaler wrote:
> Chris Wright wrote:
> > -stable review patch. If anyone has any objections, please let us know.
> > ---------------------
> >
> > From: Thomas Gleixner <tglx@...utronix.de>
> >
> > The warning in the NOHZ code, which triggers when a CPU goes idle with
> > softirqs pending can fill up the logs quite quickly. Rate limit the output
> > until we found the root cause of that problem.
>
> Isn't the root cause found and fixed with "[patch 09/54] Prevent going
> idle with softirq pending"?
Yes, still we want the printk there to find places, which go into idle
with softirqs pending. There is at least one problem in the SLIP code,
which triggers this. OTOH we do not want those messages to flood the
syslog.
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