From: Boris Bezlaj <boris@gajba.net>
To: Paul Mackerras <paulus@samba.org>
Cc: Mikael Pettersson <mikpe@user.it.uu.se>, linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.4.x swim3 performance problem on PM4400 identified
Date: Sat, 29 Mar 2003 16:55:01 +0100 [thread overview]
Message-ID: <20030329155501.GA587@gajba.net> (raw)
In-Reply-To: <16005.35950.570218.844672@nanango.paulus.ozlabs.org>
On Sat, Mar 29, 2003 at 11:07:10PM +1100, Paul Mackerras wrote:
>
> This finally prodded me to look at the mach driver. I've hacked the
> linux swim3 driver to do things in a more similar fashion to what the
> mach driver does. It now seems to not get stuck on the dreaded 04
> error and generally seems a lot more robust. Try this patch and let
> me know how it goes.
With a good floppy the driver works well reading and writing. No more
positioning errors..good work Paul 8)
Bad floppy case:
| kista:/tmp# dd if=swimmer of=/dev/fd0 bs=512 count=2880
| swim3: timeout reading sector 2647
| end_request: I/O error, dev 02:00 (floppy), sector 2647 <--bad sector
| dd: writing `/dev/fd0': Input/output error
| 2647+0 records in
| 2646+0 records out
| 1354752 bytes transferred in 134.614549 seconds (10064 bytes/sec)
after the error at sector 2647, swim3 seems to move the heads to sector 0
and write? another 2647 sectors. Any particular reason for that ?
Most importantly, when changing the floppy, it still works (not the
case with the unpatched driver).
--
Boris
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-03-29 15:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 15:40 2.4.x swim3 performance problem on PM4400 identified Mikael Pettersson
2003-03-28 15:49 ` Benjamin Herrenschmidt
2003-03-28 21:25 ` Boris Bezlaj
[not found] ` <200303281813.31378.remco@rvt.com>
2003-03-29 8:58 ` Boris Bezlaj
2003-03-29 12:07 ` Paul Mackerras
2003-03-29 15:55 ` Boris Bezlaj [this message]
2003-03-30 1:50 ` Paul Mackerras
2003-03-30 8:28 ` Boris Bezlaj
2003-04-14 9:39 ` mikpe
2003-04-14 10:02 ` Benjamin Herrenschmidt
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=20030329155501.GA587@gajba.net \
--to=boris@gajba.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mikpe@user.it.uu.se \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.