[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140812160840.GD4752@linux.vnet.ibm.com>
Date: Tue, 12 Aug 2014 09:08:40 -0700
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Amit Shah <amit.shah@...hat.com>
Cc: linux-kernel@...r.kernel.org, riel@...hat.com, mingo@...nel.org,
laijs@...fujitsu.com, dipankar@...ibm.com,
akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com,
josh@...htriplett.org, tglx@...utronix.de, peterz@...radead.org,
rostedt@...dmis.org, dhowells@...hat.com, edumazet@...gle.com,
dvhart@...ux.intel.com, fweisbec@...il.com, oleg@...hat.com,
sbw@....edu
Subject: Re: [PATCH tip/core/rcu 1/2] rcu: Parallelize and economize NOCB
kthread wakeups
On Tue, Aug 12, 2014 at 10:57:26AM +0530, Amit Shah wrote:
> On (Mon) 11 Aug 2014 [13:34:21], Paul E. McKenney wrote:
> > On Tue, Aug 12, 2014 at 01:48:45AM +0530, Amit Shah wrote:
[ . . . ]
> > > > In addition "sendkey alt-sysrq-t" at the "(qemu)" prompt dumps all tasks'
> > > > stacks, which would also likely be useful information.
> > >
> > > Nah, this doesn't work -- the guest's totally locked up. I need a way
> > > to continuously dump buffers till the lockup happens, I suppose.
> >
> > That is a bit surprising. Is it possible that the system is OOMing
> > quickly due to grace periods not proceeding? If so, maybe giving the
> > VM more memory would help.
>
> I bumped it up to 1G and then 2G, same result.
OK. I am then back at making the system dump core.
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