[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1205211540010.10940@router.home>
Date: Mon, 21 May 2012 15:41:30 -0500 (CDT)
From: Christoph Lameter <cl@...ux.com>
To: Dave Jones <davej@...hat.com>
cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel <linux-kernel@...r.kernel.org>,
linux-mm@...ck.org,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Stephen Wilson <wilsons@...rt.ca>,
Mel Gorman <mgorman@...e.de>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: 3.4-rc7 numa_policy slab poison.
On Mon, 21 May 2012, Dave Jones wrote:
> On Mon, May 21, 2012 at 03:18:38PM -0500, Christoph Lameter wrote:
>
> > Its always an mput on a freed memory policy. Slub recovery keeps my system
> > up at least. I just get the errors dumped to dmesg.
> >
> > Is there any way to get the trinity tool to stop when the kernel writes
> > errors to dmesg? That way I could see the parameters passed to mbind?
>
> another way might be to remove the -q argument, and use -p which inserts
> a pause() after each syscall.
Without -q it does not trigger anymore. Output is slow so I guess there is
some race condition that does not occur when things occur with less
frequency.
--
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