From: Mark Hounschell <markh@compro.net>
To: linux-kernel@vger.kernel.org
Subject: Unable to format or use floppies since 2.6.28
Date: Thu, 10 Dec 2009 14:46:15 -0500 [thread overview]
Message-ID: <4B215007.4030703@compro.net> (raw)
I have many boxes. They all do the same thing. Running different versions of SuSE, 10.3-11.2. Any kernel at or above 2.6.28 fails to fdformat a floppy. These same machines, using the same floppies and drives, running kernels older than 2.6.28 work just fine. I googled and found other such reports but no solution. I know better than to just assume it's a kernel bug but it sure looks like it could be so I'm inquiring about it here.
# fdformat /dev/fd0u1440
Double-sided, 80 tracks, 18 sec/track. Total capacity 1440 kB.
Formatting ... done
Verifying ... Problem reading cylinder 1, expected 18432, read 2048
dmesg from 2.6.32:
Dec 10 14:24:21 harley kernel: end_request: I/O error, dev fd0, sector 45
Dec 10 14:24:21 harley kernel: Buffer I/O error on device fd0, logical block 5
Dec 10 14:24:23 harley kernel: end_request: I/O error, dev fd0, sector 72
Dec 10 14:24:23 harley kernel: Buffer I/O error on device fd0, logical block 9
Dec 10 14:24:26 harley kernel: end_request: I/O error, dev fd0, sector 117
Dec 10 14:24:26 harley kernel: Buffer I/O error on device fd0, logical block 14
Dec 10 14:24:28 harley kernel: end_request: I/O error, dev fd0, sector 127
Dec 10 14:24:28 harley kernel: Buffer I/O error on device fd0, logical block 15
Dec 10 14:24:30 harley kernel: end_request: I/O error, dev fd0, sector 45
Dec 10 14:24:30 harley kernel: Buffer I/O error on device fd0, logical block 5
Dec 10 14:24:32 harley kernel: end_request: I/O error, dev fd0, sector 144
Dec 10 14:24:32 harley kernel: Buffer I/O error on device fd0, logical block 18
Dec 10 14:24:34 harley kernel: end_request: I/O error, dev fd0, sector 189
Dec 10 14:24:34 harley kernel: Buffer I/O error on device fd0, logical block 23
Dec 10 14:24:36 harley kernel: end_request: I/O error, dev fd0, sector 216
Dec 10 14:24:36 harley kernel: Buffer I/O error on device fd0, logical block 27
Dec 10 14:24:39 harley kernel: end_request: I/O error, dev fd0, sector 261
Dec 10 14:24:39 harley kernel: Buffer I/O error on device fd0, logical block 32
Dec 10 14:24:41 harley kernel: end_request: I/O error, dev fd0, sector 288
Dec 10 14:24:41 harley kernel: Buffer I/O error on device fd0, logical block 36
Dec 10 14:24:43 harley kernel: end_request: I/O error, dev fd0, sector 333
Dec 10 14:24:43 harley kernel: Buffer I/O error on device fd0, logical block 41
Dec 10 14:24:45 harley kernel: end_request: I/O error, dev fd0, sector 360
Dec 10 14:24:45 harley kernel: Buffer I/O error on device fd0, logical block 45
# rpm -qf /usr/sbin/fdformat
util-linux-2.16-4.5.1.i586
Again, on this very machine, running 2.6.27.41 all is fine....
Thanks in advance
Mark
next reply other threads:[~2009-12-10 19:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 19:46 Mark Hounschell [this message]
2009-12-12 9:33 ` Unable to format or use floppies since 2.6.28 ael
2009-12-17 9:04 ` Américo Wang
2009-12-17 9:19 ` Tejun Heo
2009-12-17 8:30 ` Dan Carpenter
2009-12-17 10:07 ` Mark Hounschell
2009-12-17 10:35 ` Mark Hounschell
2009-12-17 10:36 ` Alain Knaff
2009-12-17 10:45 ` Mark Hounschell
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=4B215007.4030703@compro.net \
--to=markh@compro.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