mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ian Eure <ieure@insynq.com>
To: linux-kernel@vger.kernel.org
Subject: loop problems continue in 2.4.3
Date: Sat, 7 Apr 2001 15:04:37 -0700	[thread overview]
Message-ID: <15055.36597.353681.125824@pyramid.insynq.com> (raw)

i'm still having loopback problems with linux 2.4.3, even though they
were supposed to be fixed. it doesn't deadlock my maching right away
anymore, but instead causes a kernel panic after 4-6 uses of the loop
device.

the message i get is: "Kernel panic: Invalid blocksize passed to
set_blocksize"

100% reproducable. has anyone else seen this?

i did compile with gcc 2.92.3, and i have hedrick's ide patches
applied.

anyone else see this?

p.s. please cc: me in any replies, i'm not on the list.

-- 
 ___________________________________
| Ian Eure - <ieure@insynq.com>     | "You're living in a facist world...
|         -  Developer -            | Freedom is a luxury." -Front Line
|        -  InsynQ, Inc. -          | Assembly, "Digital Tension Dementia"
| Your Internet Utility Company.tm  |________________________________________

             reply	other threads:[~2001-04-07 22:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-07 22:04 Ian Eure [this message]
2001-04-09  7:56 ` Jens Axboe
2001-04-11 19:04 ` Ian Eure
2001-04-13 12:56   ` Jens Axboe
2001-04-16 16:17   ` Ian Eure
2001-04-16 20:53     ` Jens Axboe
2001-04-14  3:35 Arthur Pedyczak
2001-04-14  7:54 ` Jens Axboe
2001-04-14 12:46   ` Arthur Pedyczak
2001-04-14 12:58     ` Ola Garstad
2001-04-14 16:31 Aaron Lunansky
2001-04-14 20:15 ` Arthur Pedyczak
2001-04-16 23:02   ` David Woodhouse
     [not found] <3AD7EE80.5AADA578@mandrakesoft.com>
2001-04-16  1:08 ` Arthur Pedyczak
2001-04-16  1:37   ` Arthur Pedyczak
2001-04-16  8:49   ` Jens Axboe
2001-04-16  9:30     ` Alexander Viro
2001-04-16 10:10       ` Mircea Damian
2001-04-16 16:38         ` Jens Axboe
2001-04-16 16:37       ` Jens Axboe

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=15055.36597.353681.125824@pyramid.insynq.com \
    --to=ieure@insynq.com \
    --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
all inboxes | Powered by JetHome®