Re: IDE Floppy support for IOMEGA Zip Drive broken in 3.16 -> 3.17 transition
Hi Christoph, thanks for your answer! Any clue on how to help/speed up this? Was there any exchange with them when you first provided your patch back in 2014? Can it be restarted? My feeling is that the issue fixed with 045065d8a300a37218c548e9aa7becd581c6a0e8 was in fact the real paper over the bug. As distros start picking kernels with 045065d8a300a37218c548e9aa7becd581c6a0e8 the issue is like to bite more and more. And it is a subtle bug. In some cases takes ages before revealing, making one feel confident on a system that is in fact broken. And takes ages to bisect (took me almost 7 days). Best, Sergio On 20/08/2015 10:08, Christoph Hellwig wrote: Hi Sergio, On Tue, Aug 18, 2015 at 09:44:28AM +0200, Sergio Callegari wrote: Hi, I have bisected the issue down to [045065d8a300a37218c548e9aa7becd581c6a0e8] [SCSI] fix qemu boot hang problem Bisecting has been a painful job due to the fact that the bug may show only many hours after the system boot. The commit above in fact is not the culprit, but a fix to an issue that was hiding the real bug on my system. See http://marc.info/?l=linux-kernel=143973820612978=2 The real issue is with sata host lock and seems to be biting a few other people as well https://bbs.archlinux.org/viewtopic.php?id=189324 A patch fixing the issue was sent to the LKML back in Nov 2014 by Christoph Hellwig (who is reading in CC) https://lkml.org/lkml/2014/11/20/581 I have tested the patch and it works for me. What is expected to happen now? As mentioned in that thread we need more input from the libata people on what kind of race this is papering over. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: IDE Floppy support for IOMEGA Zip Drive broken in 3.16 -> 3.17 transition
Hi Sergio, On Tue, Aug 18, 2015 at 09:44:28AM +0200, Sergio Callegari wrote: > Hi, > > I have bisected the issue down to > > [045065d8a300a37218c548e9aa7becd581c6a0e8] [SCSI] fix qemu boot hang problem > > Bisecting has been a painful job due to the fact that the bug may show only > many hours after the system boot. > > The commit above in fact is not the culprit, but a fix to an issue that was > hiding the real bug on my system. See > > http://marc.info/?l=linux-kernel=143973820612978=2 > > The real issue is with sata host lock and seems to be biting a few other > people as well > > https://bbs.archlinux.org/viewtopic.php?id=189324 > > A patch fixing the issue was sent to the LKML back in Nov 2014 by Christoph > Hellwig (who is reading in CC) > > https://lkml.org/lkml/2014/11/20/581 > > I have tested the patch and it works for me. > > What is expected to happen now? As mentioned in that thread we need more input from the libata people on what kind of race this is papering over. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: IDE Floppy support for IOMEGA Zip Drive broken in 3.16 - 3.17 transition
Hi Christoph, thanks for your answer! Any clue on how to help/speed up this? Was there any exchange with them when you first provided your patch back in 2014? Can it be restarted? My feeling is that the issue fixed with 045065d8a300a37218c548e9aa7becd581c6a0e8 was in fact the real paper over the bug. As distros start picking kernels with 045065d8a300a37218c548e9aa7becd581c6a0e8 the issue is like to bite more and more. And it is a subtle bug. In some cases takes ages before revealing, making one feel confident on a system that is in fact broken. And takes ages to bisect (took me almost 7 days). Best, Sergio On 20/08/2015 10:08, Christoph Hellwig wrote: Hi Sergio, On Tue, Aug 18, 2015 at 09:44:28AM +0200, Sergio Callegari wrote: Hi, I have bisected the issue down to [045065d8a300a37218c548e9aa7becd581c6a0e8] [SCSI] fix qemu boot hang problem Bisecting has been a painful job due to the fact that the bug may show only many hours after the system boot. The commit above in fact is not the culprit, but a fix to an issue that was hiding the real bug on my system. See http://marc.info/?l=linux-kernelm=143973820612978w=2 The real issue is with sata host lock and seems to be biting a few other people as well https://bbs.archlinux.org/viewtopic.php?id=189324 A patch fixing the issue was sent to the LKML back in Nov 2014 by Christoph Hellwig (who is reading in CC) https://lkml.org/lkml/2014/11/20/581 I have tested the patch and it works for me. What is expected to happen now? As mentioned in that thread we need more input from the libata people on what kind of race this is papering over. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: IDE Floppy support for IOMEGA Zip Drive broken in 3.16 - 3.17 transition
Hi Sergio, On Tue, Aug 18, 2015 at 09:44:28AM +0200, Sergio Callegari wrote: Hi, I have bisected the issue down to [045065d8a300a37218c548e9aa7becd581c6a0e8] [SCSI] fix qemu boot hang problem Bisecting has been a painful job due to the fact that the bug may show only many hours after the system boot. The commit above in fact is not the culprit, but a fix to an issue that was hiding the real bug on my system. See http://marc.info/?l=linux-kernelm=143973820612978w=2 The real issue is with sata host lock and seems to be biting a few other people as well https://bbs.archlinux.org/viewtopic.php?id=189324 A patch fixing the issue was sent to the LKML back in Nov 2014 by Christoph Hellwig (who is reading in CC) https://lkml.org/lkml/2014/11/20/581 I have tested the patch and it works for me. What is expected to happen now? As mentioned in that thread we need more input from the libata people on what kind of race this is papering over. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: IDE Floppy support for IOMEGA Zip Drive broken in 3.16 -> 3.17 transition
Hi, I have bisected the issue down to [045065d8a300a37218c548e9aa7becd581c6a0e8] [SCSI] fix qemu boot hang problem Bisecting has been a painful job due to the fact that the bug may show only many hours after the system boot. The commit above in fact is not the culprit, but a fix to an issue that was hiding the real bug on my system. See http://marc.info/?l=linux-kernel=143973820612978=2 The real issue is with sata host lock and seems to be biting a few other people as well https://bbs.archlinux.org/viewtopic.php?id=189324 A patch fixing the issue was sent to the LKML back in Nov 2014 by Christoph Hellwig (who is reading in CC) https://lkml.org/lkml/2014/11/20/581 I have tested the patch and it works for me. What is expected to happen now? The original patch appeared to have been dropped and did not make it to the mainline kernel (is there any reason why, some contraindication?), but seems to be important because without it the linux kernel is broken on some systems. Is there anything that can be done for the patch be accepted in mainline and stabilization kernels? Best regards, Sergio On 25/06/2015 23:31, Borislav Petkov wrote: On Thu, Jun 25, 2015 at 08:58:58PM +, Sergio Callegari wrote: 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? Here's what went into ide in 3.17: $ git log -p v3.16..v3.17 drivers/ide/ commit a53dae49b2fea43d8f4ec5aeca0e288bbc8d6895 Author: Christoph Jaeger Date: Wed Apr 9 09:28:01 2014 +0200 ide: use module_platform_driver() Eliminate boilerplate code by using module_platform_driver(). Signed-off-by: Christoph Jaeger Signed-off-by: David S. Miller diff --git a/drivers/ide/au1xxx-ide.c b/drivers/ide/au1xxx-ide.c index 259786ca8b75..07ea58084068 100644 --- a/drivers/ide/au1xxx-ide.c +++ b/drivers/ide/au1xxx-ide.c ... and that driver doesn't have anything to do with zip drives. So problem is either somewhere else in the kernel or maybe something's missing from the 3.17 config or somewhere completely different. You could bisect the kernels between 3.16 and 3.17 - unless someone has a better idea... -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: IDE Floppy support for IOMEGA Zip Drive broken in 3.16 - 3.17 transition
Hi, I have bisected the issue down to [045065d8a300a37218c548e9aa7becd581c6a0e8] [SCSI] fix qemu boot hang problem Bisecting has been a painful job due to the fact that the bug may show only many hours after the system boot. The commit above in fact is not the culprit, but a fix to an issue that was hiding the real bug on my system. See http://marc.info/?l=linux-kernelm=143973820612978w=2 The real issue is with sata host lock and seems to be biting a few other people as well https://bbs.archlinux.org/viewtopic.php?id=189324 A patch fixing the issue was sent to the LKML back in Nov 2014 by Christoph Hellwig (who is reading in CC) https://lkml.org/lkml/2014/11/20/581 I have tested the patch and it works for me. What is expected to happen now? The original patch appeared to have been dropped and did not make it to the mainline kernel (is there any reason why, some contraindication?), but seems to be important because without it the linux kernel is broken on some systems. Is there anything that can be done for the patch be accepted in mainline and stabilization kernels? Best regards, Sergio On 25/06/2015 23:31, Borislav Petkov wrote: On Thu, Jun 25, 2015 at 08:58:58PM +, Sergio Callegari wrote: 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? Here's what went into ide in 3.17: $ git log -p v3.16..v3.17 drivers/ide/ commit a53dae49b2fea43d8f4ec5aeca0e288bbc8d6895 Author: Christoph Jaeger christophjae...@linux.com Date: Wed Apr 9 09:28:01 2014 +0200 ide: use module_platform_driver() Eliminate boilerplate code by using module_platform_driver(). Signed-off-by: Christoph Jaeger christophjae...@linux.com Signed-off-by: David S. Miller da...@davemloft.net diff --git a/drivers/ide/au1xxx-ide.c b/drivers/ide/au1xxx-ide.c index 259786ca8b75..07ea58084068 100644 --- a/drivers/ide/au1xxx-ide.c +++ b/drivers/ide/au1xxx-ide.c ... and that driver doesn't have anything to do with zip drives. So problem is either somewhere else in the kernel or maybe something's missing from the 3.17 config or somewhere completely different. You could bisect the kernels between 3.16 and 3.17 - unless someone has a better idea... -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: IDE Floppy support for IOMEGA Zip Drive broken in 3.16 -> 3.17 transition
On 02/07/2015 18:11, Ondrej Zary wrote:
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.
Also mine 'seems' to work fine. I can boot the machine, mount, unmount, read
the disk without problems *for some time*.
The issue is that, if I boot *with no disk in the drive* after about 2-3 hours I
use the machine the iowait jumps high, the kernel starts to complain about hung
processes, any command related to the zip drive starts hanging, the machine
cannot be shut down cleanly, any kernel install process starts to hang at the
ramdisk generation or grub install.
If I detach the drive or downgrade to 3.16, all is fine.
Clearly, the items above make 'uninformed' bisecting quite hard, particularly
because it is unclear to me at this point if the machine load has any influence
on triggering the issue.
Now, it is obvious that one can live without a zip drive today, but if this is
the case, it would be better to blacklist it from the kernel altogether, because
something has surely got wrong in the 3.16->3.17 transition and there is a
serious regression with regard to this now rarely used piece of hardware. Also I
wonder if there is around some other "ide-floppy" device that may be affected.
Regards,
Sergio
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: IDE Floppy support for IOMEGA Zip Drive broken in 3.16 - 3.17 transition
On 02/07/2015 18:11, Ondrej Zary wrote:
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.
Also mine 'seems' to work fine. I can boot the machine, mount, unmount, read
the disk without problems *for some time*.
The issue is that, if I boot *with no disk in the drive* after about 2-3 hours I
use the machine the iowait jumps high, the kernel starts to complain about hung
processes, any command related to the zip drive starts hanging, the machine
cannot be shut down cleanly, any kernel install process starts to hang at the
ramdisk generation or grub install.
If I detach the drive or downgrade to 3.16, all is fine.
Clearly, the items above make 'uninformed' bisecting quite hard, particularly
because it is unclear to me at this point if the machine load has any influence
on triggering the issue.
Now, it is obvious that one can live without a zip drive today, but if this is
the case, it would be better to blacklist it from the kernel altogether, because
something has surely got wrong in the 3.16-3.17 transition and there is a
serious regression with regard to this now rarely used piece of hardware. Also I
wonder if there is around some other ide-floppy device that may be affected.
Regards,
Sergio
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: IDE Floppy support for IOMEGA Zip Drive broken in 3.16 -> 3.17 transition
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: IDE Floppy support for IOMEGA Zip Drive broken in 3.16 - 3.17 transition
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
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: IDE Floppy support for IOMEGA Zip Drive broken in 3.16 -> 3.17 transition
On Thu, Jun 25, 2015 at 08:58:58PM +, Sergio Callegari wrote: > 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? Here's what went into ide in 3.17: $ git log -p v3.16..v3.17 drivers/ide/ commit a53dae49b2fea43d8f4ec5aeca0e288bbc8d6895 Author: Christoph Jaeger Date: Wed Apr 9 09:28:01 2014 +0200 ide: use module_platform_driver() Eliminate boilerplate code by using module_platform_driver(). Signed-off-by: Christoph Jaeger Signed-off-by: David S. Miller diff --git a/drivers/ide/au1xxx-ide.c b/drivers/ide/au1xxx-ide.c index 259786ca8b75..07ea58084068 100644 --- a/drivers/ide/au1xxx-ide.c +++ b/drivers/ide/au1xxx-ide.c ... and that driver doesn't have anything to do with zip drives. So problem is either somewhere else in the kernel or maybe something's missing from the 3.17 config or somewhere completely different. You could bisect the kernels between 3.16 and 3.17 - unless someone has a better idea... -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. -- -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
IDE Floppy support for IOMEGA Zip Drive broken in 3.16 -> 3.17 transition
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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
IDE Floppy support for IOMEGA Zip Drive broken in 3.16 - 3.17 transition
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?
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: IDE Floppy support for IOMEGA Zip Drive broken in 3.16 - 3.17 transition
On Thu, Jun 25, 2015 at 08:58:58PM +, Sergio Callegari wrote: 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? Here's what went into ide in 3.17: $ git log -p v3.16..v3.17 drivers/ide/ commit a53dae49b2fea43d8f4ec5aeca0e288bbc8d6895 Author: Christoph Jaeger christophjae...@linux.com Date: Wed Apr 9 09:28:01 2014 +0200 ide: use module_platform_driver() Eliminate boilerplate code by using module_platform_driver(). Signed-off-by: Christoph Jaeger christophjae...@linux.com Signed-off-by: David S. Miller da...@davemloft.net diff --git a/drivers/ide/au1xxx-ide.c b/drivers/ide/au1xxx-ide.c index 259786ca8b75..07ea58084068 100644 --- a/drivers/ide/au1xxx-ide.c +++ b/drivers/ide/au1xxx-ide.c ... and that driver doesn't have anything to do with zip drives. So problem is either somewhere else in the kernel or maybe something's missing from the 3.17 config or somewhere completely different. You could bisect the kernels between 3.16 and 3.17 - unless someone has a better idea... -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. -- -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
