From: Douglas Gilbert <dougg@torque.net>
To: linux-kernel@vger.kernel.org, Zdenek Kabelac <kabi@fi.muni.cz>
Subject: Re: Oops with 2.4.0-test13pre3 - swapoff
Date: Wed, 20 Dec 2000 09:16:51 -0500 [thread overview]
Message-ID: <3A40BF53.400EF44B@torque.net> (raw)
Zdenek Kabelac wrote:
> This is oops I've got when rebooting after some heavy disk activity on
> my SMP system:
>
> Written by hand:
>
> kernel BUG swap_state.c:78!
[snip]
Same here during a halt of a RH 6.2 based K6-2 500 MHz
UP machine running lk240t13p3. The machine had been on
for a while and had built a kernel amongst other things.
Lead up was:
$ halt
.....
Sending all processes the KILL signal [OK]
Turning off swap VM: __lru_cache_del, found unknown page ?!
kernel BUG at swap_state.c:78
....
Doug Gilbert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-20 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-20 14:16 Douglas Gilbert [this message]
2000-12-20 15:45 ` Oops with 2.4.0-test13pre3 - swapoff Zdenek Kabelac
2000-12-21 17:01 ` Marcelo Tosatti
2000-12-22 10:31 ` Christoph Rohland
-- strict thread matches above, loose matches on Subject: below --
2000-12-19 12:28 Zdenek Kabelac
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=3A40BF53.400EF44B@torque.net \
--to=dougg@torque.net \
--cc=kabi@fi.muni.cz \
--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