[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111103132550.GX2287@linux.vnet.ibm.com>
Date: Thu, 3 Nov 2011 06:25:50 -0700
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Josh Triplett <josh@...htriplett.org>
Cc: linux-kernel@...r.kernel.org, mingo@...e.hu, laijs@...fujitsu.com,
dipankar@...ibm.com, akpm@...ux-foundation.org,
mathieu.desnoyers@...ymtl.ca, niv@...ibm.com, tglx@...utronix.de,
peterz@...radead.org, rostedt@...dmis.org, Valdis.Kletnieks@...edu,
dhowells@...hat.com, eric.dumazet@...il.com, darren@...art.com,
patches@...aro.org
Subject: Re: [PATCH RFC tip/core/rcu 09/28] rcu: Document failing tick as
cause of RCU CPU stall warning
On Wed, Nov 02, 2011 at 08:07:50PM -0700, Josh Triplett wrote:
> On Wed, Nov 02, 2011 at 01:30:30PM -0700, Paul E. McKenney wrote:
> > One of lclaudio's systems was seeing RCU CPU stall warnings from idle.
> > These turned out to be caused by a bug that stopped scheduling-clock
> > tick interrupts from being sent to a given CPU for several hundred seconds.
>
> Out of curiosity, what caused this bug?
If I remember correctly, software/configuration bugs in the clock code.
Thanx, Paul
--
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