From: Ishikawa <ishikawa@yk.rim.or.jp>
To: linux-kernel@vger.kernel.org
Subject: Re: Swap Corruption in 2.4.3 ?
Date: Sun, 15 Apr 2001 12:13:17 +0900 [thread overview]
Message-ID: <3AD911CD.55F1CDA3@yk.rim.or.jp> (raw)
On 10 Apr 2001, Richard Russon wrote:
> VM: Undead swap entry 000bb300
> VM: Undead swap entry 00abb300
> VM: Undead swap entry 016fb300
I have seen similar mysterious crashes of X server
when I began accessing large web page using Netscape
navigator. It was reproducible the first few times I noticed.
Today, a similar problem occurred and luckily I noticed
console messages printed on a virtual console.
There ware many lines like the following.
swap_free: Trying to freee non-existent swap page
Bad Swap Entry: 00000008
Bad Swap Entry: 0000008
...
VM: Kiling process jserver
Swap_free: Trying to free non-existent swap page
...
It seems that there was some sort of kernel data corruption.
(In my case, the kernel could not find the swap page and
failed to swap out memory and thus the
VM's selective process killer was invoked to free up memory?)
Then eventually I got
Unable to handle kernel NULL pointer defreence at ...
message and the system crashed.
(I was also typing Alt+SysReq+keystroke to see if I could sync disk.)
.
Anyway, this probem seems to be in 2.4.2, too from what I recall about
the
first mysterious X server crash.
On Apri 20 Rik van Riel wrote:
>Known bug ... unknown cause ;(
>
>http://www.linux-mm.org/bugzilla.shtml has it already listed
The symptom there didn't match mine, but I do suspect
a (new) problem in VM of 2.4.3 (2.4.2, too. 2.4.1, I am not sure.).
Happy Hacking
next reply other threads:[~2001-04-14 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-15 3:13 Ishikawa [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-10 3:20 Swap Corruption in 2.4.3 ? Richard Russon
2001-04-10 15:55 ` Rik van Riel
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=3AD911CD.55F1CDA3@yk.rim.or.jp \
--to=ishikawa@yk.rim.or.jp \
--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