From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: Jike Song <albcamus@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.25-rc4 rcupreempt.h WARNINGs while suspend/resume
Date: Thu, 6 Mar 2008 08:27:24 -0800 [thread overview]
Message-ID: <20080306162724.GA9309@linux.vnet.ibm.com> (raw)
In-Reply-To: <a8e1da0803060308o690c1545l1eaffc0c40f2bc7e@mail.gmail.com>
On Thu, Mar 06, 2008 at 07:08:55PM +0800, Dave Young wrote:
> On Thu, Mar 6, 2008 at 11:20 AM, Dave Young <hidave.darkstar@gmail.com> wrote:
> > On Thu, Mar 6, 2008 at 10:28 AM, Paul E. McKenney
> >
> > <paulmck@linux.vnet.ibm.com> wrote:
> > >
> > > On Thu, Mar 06, 2008 at 10:11:26AM +0800, Jike Song wrote:
> > > > On Thu, Mar 6, 2008 at 12:55 AM, Paul E. McKenney
> > > > <paulmck@linux.vnet.ibm.com> wrote:
> > > > > Could you please try applying Karsten Wiese's patch to see if it
> > > > > fixes the WARNINGs? See http://lkml.org/lkml/2008/2/26/386 for
> > > > > the patch.
> > > > >
> > > > > Thanx, Paul
> > > >
> > > > Yes, the WARNING disappears with Karsten's patch applied.
> > > > Thanks.
> >
> > Confirmed
> >
> >
> >
> > >
> > > Good to hear!!! I believe that Karsten's patch is on its way in,
> > > so hopefully that will clear things up.
>
> Hi, paul
>
> 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?
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?
Thanx, Paul
next prev parent reply other threads:[~2008-03-06 16:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 7:24 2.6.25-rc4 rcupreempt.h WARNINGs while suspend/resume Dave Young
2008-03-05 7:35 ` Jike Song
2008-03-05 16:55 ` Paul E. McKenney
2008-03-06 2:11 ` Jike Song
2008-03-06 2:28 ` Paul E. McKenney
2008-03-06 3:20 ` Dave Young
2008-03-06 11:08 ` Dave Young
2008-03-06 16:27 ` Paul E. McKenney [this message]
2008-03-07 3:07 ` Dave Young
2008-03-07 4:19 ` Paul E. McKenney
2008-03-07 4:35 ` Dave Young
2008-03-07 6:57 ` Paul E. McKenney
2008-03-07 7:31 ` Dave Young
2008-03-07 7:43 ` Dave Young
2008-03-07 7:55 ` Dave Young
2008-03-07 14:08 ` Paul E. McKenney
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=20080306162724.GA9309@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=albcamus@gmail.com \
--cc=hidave.darkstar@gmail.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox