From: John Levon <moz@compsoc.man.ac.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: VM: Bad swap entry 0044cb00
Date: Tue, 28 Aug 2001 01:23:09 +0100 [thread overview]
Message-ID: <20010828012308.A36433@compsoc.man.ac.uk> (raw)
In-Reply-To: <Pine.NEB.4.33.0108280204430.13898-100000@mimas.fachschaften.tu-muenchen.de> <Pine.LNX.4.21.0108271946300.7385-100000@freak.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0108271946300.7385-100000@freak.distro.conectiva>
On Mon, Aug 27, 2001 at 07:46:56PM -0300, Marcelo Tosatti wrote:
> > I upgraded my kernel from 2.4.8ac10 to 2.4.9ac2 some hours ago and I found
> > the following message in my syslog file (I've never seen something like
> > this before):
> >
> > Aug 27 22:40:46 r063144 kernel: VM: Bad swap entry 0044cb00
> >
> >
> > What does this mean (my machine seems to run fine)?
>
> Did you turned any swap file/partition off? (with swapoff)
fwiw, this seems to be a common characteristic of hardware problems with
2.4 kernels. I've had bad RAM (discovered by memtest86) which was producing
this error without any swapoff. Once it only occurred after an entire night
of kernel compiles (memtest86 found it easily however)
regards
john
--
"Premature generalization is the root of all evil."
- Karl Fogel
next prev parent reply other threads:[~2001-08-28 0:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-28 0:07 Adrian Bunk
2001-08-27 22:46 ` Marcelo Tosatti
2001-08-28 0:20 ` Adrian Bunk
2001-08-28 0:23 ` John Levon [this message]
2001-08-27 23:03 ` Marcelo Tosatti
2001-08-28 0:32 ` Alan Cox
2001-08-29 15:30 ` Adrian Bunk
2001-08-28 0:31 ` Alan Cox
2001-08-28 12:59 ` Hugh Dickins
2001-08-29 15:30 ` Adrian Bunk
2001-08-28 8:25 Christian Borntraeger
2001-08-28 12:15 Christian Borntraeger
2001-08-28 14:01 Christian Borntraeger
2001-08-28 15:02 ` Hugh Dickins
2001-08-29 10:47 Christian Borntraeger
2001-08-29 14:07 ` Hugh Dickins
2001-08-29 13:14 Christian Borntraeger
2001-08-29 15:20 Christian Borntraeger
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=20010828012308.A36433@compsoc.man.ac.uk \
--to=moz@compsoc.man.ac.uk \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®