From: Bill Crawford <billc@netcomuk.co.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Linux 2.4.0-ac9
Date: Mon, 15 Jan 2001 01:12:23 +0000 [thread overview]
Message-ID: <3A624E77.634D42AD@netcomuk.co.uk> (raw)
I have a problem here with loopback-mounted filesystem freezing. The
process writing to the filesystem (ext2) gets stuck in uninterruptible
state with WCHAN showing "lock_p" which I believe to be lock_page.
First time I noticed this, the system froze shortly afterwards but I
do not know if this is related (because on another occasion the system
has been fine apart from this wedged process).
Underlying system is also ext2 if that makes any difference.
Machine is AMD K6-III 400, kernel patched also with the DRM code from
XFree86 CVS but otherwise untouched, compiler (possible suspect) is
"(gcc version 2.96 20000731 (Red Hat Linux 7.0))" from gcc-2.96-69.
However the "vanishing (PS/2) mouse and keyboard" problem seems to be
cured with this release (he says ;·).
I also had a problem occasionally with -ac8 printing something like
"Undead swap entry" repeatedly during shutdown recently, not sure if
that's gone yet.
--
/* Bill Crawford, Unix Systems Developer, ebOne, formerly GTS Netcom */
#include "stddiscl.h"
-
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:[~2001-01-15 1:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-15 1:12 Bill Crawford [this message]
2001-01-15 1:47 ` Linux 2.4.0-ac9 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2001-01-14 1:40 Steven Cole
2001-01-14 3:05 ` Karsten Hopp
2001-01-14 3:47 ` Steven Cole
2001-01-14 9:56 ` Christoph Rohland
2001-01-13 23:24 Alan Cox
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=3A624E77.634D42AD@netcomuk.co.uk \
--to=billc@netcomuk.co.uk \
--cc=alan@lxorguk.ukuu.org.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