public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Coulson <david@davidcoulson.net>
To: linux-kernel@vger.kernel.org,
	UML devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: swap_dup/swap_free errors with 2.4.20-pre10
Date: Tue, 15 Oct 2002 12:47:47 +0100	[thread overview]
Message-ID: <3DAC0063.9080701@davidcoulson.net> (raw)

I'm running 2.4.20-pre10 on a Dual PIII system with 2Gb of RAM and three 
2Gb swap logical volumes.

It runs fine for a while, then I get lots of;

Oct 15 12:41:31 maeve kernel: swap_dup: Bad swap file entry 00000020
Oct 15 12:41:31 maeve kernel: swap_dup: Bad swap file entry 00000020
Oct 15 12:41:31 maeve kernel: swap_free: Bad swap file entry 00000020
Oct 15 12:41:31 maeve kernel: swap_free: Bad swap file entry 00000020
Oct 15 12:41:31 maeve kernel: swap_dup: Bad swap file entry 00000020
Oct 15 12:41:31 maeve kernel: swap_dup: Bad swap file entry 00000020
Oct 15 12:41:31 maeve kernel: swap_free: Bad swap file entry 00000020

The address is always 00000020. I've tried the machine without any swap 
space, and I get exactly the same error, so I'm assuming it's either bad 
RAM or a kernel issue. I ran memtest86 on it yesterday, and it didn't 
throw up any errors, but I'm going to swap the RAM out and see if that 
fixes it.

Thanks,
David

-- 
David Coulson                                  http://davidcoulson.net/
d@vidcoulson.com                       http://journal.davidcoulson.net/


             reply	other threads:[~2002-10-15 11:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-15 11:47 David Coulson [this message]
2002-10-16 21:23 ` swap_dup/swap_free errors with 2.4.20-pre10 Marcelo Tosatti
2002-10-16 22:14   ` David Coulson
2002-10-17  2:02     ` [uml-devel] " Jeff Dike
2002-10-17 10:20       ` David Coulson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3DAC0063.9080701@davidcoulson.net \
    --to=david@davidcoulson.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox