From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263662AbTDDNxE (for ); Fri, 4 Apr 2003 08:53:04 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263574AbTDDNuC (for ); Fri, 4 Apr 2003 08:50:02 -0500 Received: from meryl.it.uu.se ([130.238.12.42]:23424 "EHLO meryl.it.uu.se") by vger.kernel.org with ESMTP id S263647AbTDDNr0 (for ); Fri, 4 Apr 2003 08:47:26 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16013.36763.845498.611262@gargle.gargle.HOWL> Date: Fri, 4 Apr 2003 15:58:51 +0200 From: mikpe@csd.uu.se To: Andi Kleen Cc: linux-kernel@vger.kernel.org Subject: Re: 2.5.66 x86_64 oops when swapoff via IA32 emulation In-Reply-To: <20030403182922.GB2232@wotan.suse.de> References: <16012.19359.948383.217572@enequist.it.uu.se> <20030403151642.GB2062@wotan.suse.de> <16012.26449.528594.682130@gargle.gargle.HOWL> <20030403182922.GB2232@wotan.suse.de> X-Mailer: VM 6.90 under Emacs 20.7.1 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Andi Kleen writes: > On Thu, Apr 03, 2003 at 06:54:41PM +0200, mikpe@csd.uu.se wrote: > > Andi Kleen writes: > > > On Thu, Apr 03, 2003 at 04:56:31PM +0200, mikpe@csd.uu.se wrote: > > > > I got this oops from swapoff when shutting down 2.5.66 on > > > > x86_64 with 32-bit user-space (RH8.0). This was from the first > > > > run with 2.5.66, I wasn't able to reproduce it in later runs. > > > > > > Is this on the Simulator or on a real Opteron/Athlon64? > > > > Simics. > > Don't know what it could be then. Can you reproduce it ? Eventually I was able to reproduce it. The oops was the same as before, from swapoff at shutdown. What I did this time was to boot with mem=32M, and just run a silly 'cd /; tar cf - . --totals > /dev/null' command. /proc/swaps showed no swap usage before shutdown, but apparently something bad happended anyway. (Running under Simics is slow enough that I don't build the kernels or anything else on the "box" itself. So it only sees brief boot-and- see-if-it-works-then-shutdown usage.) /Mikael