From: Mike Fedyk <mfedyk@matchmail.com>
To: Chris Sykes <chris@sykes.uklinux.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: floppy in 2.4.17
Date: Sat, 23 Feb 2002 19:05:28 -0800 [thread overview]
Message-ID: <20020224030528.GQ20060@matchmail.com> (raw)
In-Reply-To: <20020223160544.A1905@werewolf.able.es> <20020223184916.GA1518@chiara.cavy.de> <20020223220007.A461@cooper>
In-Reply-To: <20020223220007.A461@cooper>
On Sat, Feb 23, 2002 at 10:00:07PM +0000, Chris Sykes wrote:
> On Sat, Feb 23, 2002 at 07:49:16PM +0100, Heinz Diehl wrote:
> > On Sat Feb 23 2002, J.A. Magallon wrote:
> >
> > > I am getting problems with floppy drive in 2.4.17.
> > > All started with floppy not working in 18-rc4, went back to 17
> > > and still does not work. Just plain 2.4.17, no patching.
> >
> > > mkfs -v -t ext2 /dev/fd0 gives:
> >
> > > mke2fs 1.26 (3-Feb-2002)
> > > mkfs.ext2: bad blocks count - /dev/fd0
> >
> > Exactly the same thing here.
>
> Yet another meetoo.
>
> I also experience hard lockups when writing to the floppy drive (fdformat,
> dd etc.) , nothing in my logs though.
>
I've seen this a couple times also, but not on the -ac series recently.
I notice this in 2.4.18-pre9-ac1:
o Fix floppy reservation ranges (Anton Altaparmakov)
So, can you guys stress the -ac patch to see if it's fixed there?
Mike
next prev parent reply other threads:[~2002-02-24 3:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-23 15:05 floppy in 2.4.17 J.A. Magallon
2002-02-23 15:59 ` Mr. James W. Laferriere
2002-02-23 16:04 ` Mr. James W. Laferriere
2002-02-23 17:10 ` Pierre Rousselet
2002-02-24 2:09 ` Mr. James W. Laferriere
2002-02-23 18:49 ` Heinz Diehl
2002-02-23 22:00 ` Chris Sykes
2002-02-24 3:05 ` Mike Fedyk [this message]
2002-02-24 13:46 ` Heinz Diehl
2002-02-24 20:00 ` Pierre Rousselet
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=20020224030528.GQ20060@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=chris@sykes.uklinux.net \
--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