public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Luciano Miguel Ferreira Rocha <strange@nsk.yi.org>
To: linux-kernel@vger.kernel.org
Subject: Loop dev & 2.4.2
Date: Thu, 22 Feb 2001 12:34:10 -0500	[thread overview]
Message-ID: <20010222123410.A3527@nsk.yi.org> (raw)


Hello!

I want to report a constant problem I'm having with the loopback block driver
in the new releases of the 2.4.x series of the Linux kernel.

The problem is that when that when trying to use a loop device the process
hangs (whether it is mount/mke2fs, etc, but not losetup). And it can't be
killed...

It only started doing that in the 2.4.1-ac18, it worked fine in the 2.4.0 and
2.4.1 versions. I didn't said anything before because I expected the problem
to go way (or to never show up) in the 2.4.2 version.

Btw, the kernel shows no error messages whatsoever.

Here's some info:
2 systems tested, all running redhat 7.0, kernel compiled wi
gcc-2.91.66/egcs-1.1.2 (kgcc)

Celeron/Mendocino			Celeron/Coppermine
450MHz (orig 300 :)			666
256, sometimes 512 Mb RAM		128
mb 440 BX				VIA VT82C691/VT82C59[68]?

Relevant upgrades for 2.4.x series:
util-linux-2.10p-4			util-linux-2.10p-4
mount-2.10r-2				modutils-2.4.2-1
modutils-2.4.2-1			binutils-2.10.1.0.4-1
binutils-2.10.1.0.4-1

(tried 2.4.0,2.4.1 + int/crypto: OK	(2.4.1: OK, 2.4.2: not ok)
2.4.1-ac18/ac-19, 2.4.2, not ok (w/o int)

I hope this helps...

Also, I'm not subscribed in the lkml, so please CC: me.

hugs
	Luciano Rocha (strange@nsk.yi.org)

             reply	other threads:[~2001-02-22 12:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-22 17:34 Luciano Miguel Ferreira Rocha [this message]
     [not found] ` <9731di$s6o$1@lennie.clouddancer.com>
2001-02-22 17:16   ` Loop dev & 2.4.2 Colonel

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=20010222123410.A3527@nsk.yi.org \
    --to=strange@nsk.yi.org \
    --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