From: <tcm@nac.net>
To: linux-kernel@vger.kernel.org
Subject: Swap error message I've seen in 2.4.5-ac17
Date: Tue, 26 Jun 2001 18:38:09 -0400 [thread overview]
Message-ID: <20010626183808.A905@debian> (raw)
In-Reply-To: <20010623222954.A9031@debian>
In-Reply-To: <20010623222954.A9031@debian>
Yep, me again. I've been playing around with ac17 on my old 486 machine
for a few days (it seems strange that the 486 works fine while the K6
doesn't, but I digress) and I noticed today something that made my hair
stand on end:
Jun 26 16:17:27 debian kernel: VM: Bad swap entry 0033da00
Jun 26 16:17:27 debian kernel: Unused swap offset entry in swap_count
0033da00
Jun 26 16:17:27 debian kernel: Unused swap offset entry in swap_count
0033da00
Jun 26 16:38:16 debian -- MARK --
Jun 26 16:53:13 debian kernel: PPP BSD Compression module registered
Jun 26 16:53:14 debian kernel: PPP Deflate Compression module registered
Jun 26 16:53:24 debian kernel: VM: Bad swap entry 0033da00
Now I have been told by Rik Van Riel that this is a kernel bug - I
initially figured it was a bad disk, thanks to him I can breathe now...
Anyway, at the time the kernel did these messages I was just stopping
playing quake on my K6-III (486 handles packets to/from the modem) and
was reloading the compression modules, changing the mtu of my modem's
interface to 1500 from 576, and starting fetchmail. And about one
minute later I decided to simply disconnect.
I can't seem to find a way to reproduce this problem all the time like I
can with the freezing bug, but I will reply to this thread if I see it
again and/or can repeatedly reproduce it.
next prev parent reply other threads:[~2001-06-26 22:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-24 2:29 Possible freezing bug located after ac13 tcm
2001-06-24 2:54 ` Rik van Riel
2001-06-26 22:38 ` tcm [this message]
2001-06-28 0:33 ` Freezing bug in all kernels greater than 2.4.5-ac13 *AND* 2.4.6-pre2 tcm
2001-06-27 23:11 ` Marcelo Tosatti
2001-06-27 23:25 ` Marcelo Tosatti
2001-07-01 5:08 ` tcm
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=20010626183808.A905@debian \
--to=tcm@nac.net \
--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