Date: Thu, 18 Sep 2003 09:42:26 -0300 (BRT)
From: Marcelo Tosatti <marcelo@parcelfarce.linux.theplanet.co.uk>
To: Andi Kleen <ak@suse.de>
cc: andrea@suse.de, <linux-kernel@vger.kernel.org>, <sct@redhat.com>
Subject: Re: 2.4.23pre4 VM breaks in LTP
In-Reply-To: <p73llsmlgrx.fsf@oldwotan.suse.de>
Message-ID: <Pine.LNX.4.44.0309180929260.2846-100000@logos.cnet>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1313
Lines: 39


Andrea, do you have any idea of what could cause this? A missing merge may
be the cause, as Andi pointed out. I wont have time to look further into 
it during the weekend and next week (Europe conferences). 

Andi, about the ext3 BUG I'm waiting for Stephen. I remember he knew how
to fix the issue but didnt had the patch ready yet sometime ago.

On 18 Sep 2003, Andi Kleen wrote:


> 
> FYI
> 
> When I run LTP on 2.4.23pre4 the machine deadlocks in mem01.
> It is still pingable, but login etc. do not manage to fork anything.
> 
> mem01 simply allocates all free memory and free swap (as seen
> in /proc/meminfo) and touches a single page in this mapping, then
> exits. 
> 
> I saw the problem on a 1GB RAM + 1GB swap x86-64 box
> 
> (note that on 32bit the limit is 1GB max, so in many cases it will
> not trigger on 32bit)
> 
> When I change mem01 to allocate 10% less memory it does not hang the box.
> And UL -aa kernel also doesn't hang it, so it's probably some half merge.
> 
> Also the ext3 BUG on x86-64 can be also triggered with multiple LTP
> runs.


-
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/