Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S264706AbTARRT4>; Sat, 18 Jan 2003 12:19:56 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S264716AbTARRT4>; Sat, 18 Jan 2003 12:19:56 -0500
Received: from BELLINI.MIT.EDU ([18.62.3.197]:12293 "EHLO bellini.mit.edu")
	by vger.kernel.org with ESMTP id <S264706AbTARRTz>;
	Sat, 18 Jan 2003 12:19:55 -0500
From: ghugh Song <ghugh@mit.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel Oops with HIMEM+VM in 2.4.19,20: More INFO
Message-Id: <20030118172841.5236C8AC1@bellini.mit.edu>
Date: Sat, 18 Jan 2003 12:28:41 -0500 (EST)
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org


I wrote:

> Anthony Lau (anthony@greyweasel.com) wrote:
> 
> > It took awhile for the next oops to appear. I modifed my boot
> > procedure by turning off swap with "swapoff -a" and allowed the
> > system to run. I waited until all of my 1.5GB of physical RAM was
> > allocated (cached or in use), and let the system to contiue to
> > run. The system ran stably for 2 days with normal use. I then
> > switch swap back on with "swapon -a".
> 
> Well. In my case, I tried without swap enabled.
> It still crashed when I issued "tar cf usr.tar /usr"
> 
> Regards,
> 
> G. H. S.
> 

Sorry.  My problem and many others' problem with 2.4.21-pre3-ac2 are 
not quite related to that of the original poster.
I was confused when I saw swap-related posting.

Sorry again.

G. H. S.
-
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/