Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757975AbYCGHoM (ORCPT ); Fri, 7 Mar 2008 02:44:12 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751578AbYCGHn6 (ORCPT ); Fri, 7 Mar 2008 02:43:58 -0500 Received: from rn-out-0910.google.com ([64.233.170.190]:19691 "EHLO rn-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752272AbYCGHn5 (ORCPT ); Fri, 7 Mar 2008 02:43:57 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Gjc3s/u9bmFQikgQ4ZOEs6x4ZA/nsI1XJMOdiXfitTy/xnPYMjmeXyXw7GAQhpjU6B2y1v3tOMXkUAyI5XLv2lF46SMtUh4fNpefeMvYw/teVgqUGrBtpm+5uwnjrWD+l4F9Tipw2jX7S6RF4iV64UhRx3bWpPnXzwdcYfKhzI4= Message-ID: Date: Fri, 7 Mar 2008 15:43:53 +0800 From: "Dave Young" To: paulmck@linux.vnet.ibm.com Subject: Re: 2.6.25-rc4 rcupreempt.h WARNINGs while suspend/resume Cc: "Jike Song" , "Linux Kernel" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080306022854.GK8728@linux.vnet.ibm.com> <20080306162724.GA9309@linux.vnet.ibm.com> <20080307041940.GB19183@linux.vnet.ibm.com> <20080307065752.GF19183@linux.vnet.ibm.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2804 Lines: 70 On Fri, Mar 7, 2008 at 3:31 PM, Dave Young wrote: > On Fri, Mar 7, 2008 at 2:57 PM, Paul E. McKenney > > > wrote: > > > > On Fri, Mar 07, 2008 at 12:35:26PM +0800, Dave Young wrote: > > > On Fri, Mar 7, 2008 at 12:19 PM, Paul E. McKenney > > > wrote: > > > > On Fri, Mar 07, 2008 at 11:07:48AM +0800, Dave Young wrote: > > > > > On Fri, Mar 7, 2008 at 12:27 AM, Paul E. McKenney > > > > > wrote: > > > > > > On Thu, Mar 06, 2008 at 07:08:55PM +0800, Dave Young wrote: > > > > > > > > > > > My syslog became a 2G size big file yestoday due to the warnings. > > > > > > > How about change the WARN_ON to WARN_ON_ONCE? > > > > > > > > > > > > Hello, Dave, > > > > > > > > > > > > I might be convinced to make this change for 2.6.26, but the condition > > > > > > that the WARN_ON() is complaining about is quite serious, so I don't > > > > > > want to take a chance on it getting lost in the noise in the 2.6.25 > > > > > > series. > > > > > > > > > > > > Seem reasonable? > > > > > > > > > > IMHO, WARN_ON_ONCE is enough for my eyes :) > > > > > > > > I could believe that, but my experience has been that many others > > > > need the condition to be obvious... > > > > > > > > > > > > > > Better yet, is there some sort of time-limited WARN_ON that kicks out > > > > > > a message at most once per second or some such? Enough to definitely > > > > > > be noticed, but not enough to bring the machine to its knees? > > > > > > > > > > Seems there's no such functions/macros, but is is really needed? > > > > > > > > If everyone reports errors when they see isolated WARN_ON()s in their > > > > logfiles, then no. But... > > > > > > Ok, I agree with you. > > > > > > Maybe something like WARN_ON_HZ(condition) or > > > WARN_ON_PERIOD(condition, period_value)? > > > > Makes sense to me! The other benefit of this sort of thing is that > > it lets you know whether the problem was a one-off or whether it > > continued happening -- but without too much log bloat. > > > > I was thinking in terms of once every ten seconds, but am not all > > that hung up on the exact value of the period. > > > > Thoughts? > > Then, WARN_ON_SECS(condition, seconds) ? Sorry, seconds must be a fixed number here, so your 10 secs maybe suitable for it. > > > > > Thanx, Paul > > > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/