From: Ondrej Zary <linux@rainbow-software.org>
To: Sergio Callegari <sergio.callegari@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IDE Floppy support for IOMEGA Zip Drive broken in 3.16 -> 3.17 transition
Date: Thu, 2 Jul 2015 18:11:40 +0200 [thread overview]
Message-ID: <201507021811.40632.linux@rainbow-software.org> (raw)
In-Reply-To: <loom.20150625T225317-840@post.gmane.org>
On Thursday 25 June 2015 22:58:58 Sergio Callegari wrote:
> Hi,
>
> I have an Iomega IDE Zip drive as in:
>
> /dev/sda:
>
> Model=IOMEGA ZIP 100 ATAPI Floppy, FwRev=12.A, SerialNo=
> Config={ SpinMotCtl Removeable nonMagnetic }
> RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
> BuffType=unknown, BuffSize=unknown, MaxMultSect=0
> (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
> IORDY=on/off, tPIO={min:500,w/IORDY:180}
> PIO modes: pio0 pio1 pio2 pio3
> AdvancedPM=no
>
> * signifies the current active mode
>
>
> ATAPI Direct-access device, with removable media
> Model Number: IOMEGA ZIP 100 ATAPI Floppy
> Serial Number:
> Firmware Revision: 12.A
> Standards:
> Likely used: 4
> Configuration:
> DRQ response: <=10ms with INTRQ
> Packet size: 12 bytes
> cache/buffer size = unknown
> Capabilities:
> LBA, IORDY(can be disabled)
> DMA: not supported
> PIO: pio0 pio1 pio2 pio3
> Cycle time: no flow control=500ns IORDY flow control=180ns
> Removable Media Status Notification feature set supported
> Security:
> supported
> enabled
> not locked
> not frozen
> not expired: security count
>
> supported: enhanced erase
>
> Security level high
>
> The drive used to work just fine up to 3.16. After a kernel upgrade, the
> drive started giving issues. Some checks let me be sure that the issue
> does not exist with 3.16 and exists with 3.17.
>
> The problem manifests with IOWAIT all of a sudden jumping high (approx 50%)
> and staying high, even with the Iomega Zip drive unmounted. When this
> happens any activity having to do with the drive hangs (even hdparm -i
> /dev/sda). No related message in syslog apart from the indication of hung
> processes. Detaching the drive makes the machine behave properly.
>
> What has changed wrt IDE in 3.16->3.17 transition? Why is the issue present
> even when the drive is not used (unmounted)? How can I help diagnosing?
You're probably using libata and not the old IDE layer.
Just tested this one:
Model=IOMEGA ZIP 100 ATAPI, FwRev=03.H, SerialNo=
Config={ SpinMotCtl Removeable nonMagnetic }
RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=unknown, BuffSize=unknown, MaxMultSect=0
(maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
IORDY=on/off, tPIO={min:500,w/IORDY:180}, tDMA={min:150,rec:150}
PIO modes: pio0 pio1 pio2 pio3
DMA modes: mdma0 *mdma1
AdvancedPM=no
* signifies the current active mode
in 4.0.0-next-20150415 and it seems to work fine. Mounted, unmounted, read
complete disk using dd without any problems.
--
Ondrej Zary
next prev parent reply other threads:[~2015-07-02 16:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-25 20:58 IDE Floppy support for IOMEGA Zip Drive broken in 3.16 -> 3.17 transition Sergio Callegari
2015-06-25 21:31 ` Borislav Petkov
2015-08-18 7:44 ` Sergio Callegari
2015-08-20 8:08 ` Christoph Hellwig
2015-08-20 15:08 ` Sergio Callegari
2015-08-24 17:07 ` "scsi: convert host_busy to atomic_t" series causes regressions for some hardware configurations Sergio Callegari
2015-08-25 11:00 ` Christoph Hellwig
2015-08-26 7:14 ` Sergio Callegari
2015-08-30 10:54 ` Sergio Callegari
2015-09-07 7:31 ` Sergio Callegari
2015-09-07 17:51 ` Christoph Hellwig
2015-07-02 16:11 ` Ondrej Zary [this message]
2015-07-03 6:50 ` IDE Floppy support for IOMEGA Zip Drive broken in 3.16 -> 3.17 transition Sergio Callegari
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=201507021811.40632.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sergio.callegari@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).