Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754561AbbGCGu2 (ORCPT ); Fri, 3 Jul 2015 02:50:28 -0400 Received: from mail-wg0-f45.google.com ([74.125.82.45]:34936 "EHLO mail-wg0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754611AbbGCGuV (ORCPT ); Fri, 3 Jul 2015 02:50:21 -0400 Message-ID: <559630A9.5020804@gmail.com> Date: Fri, 03 Jul 2015 08:50:17 +0200 From: Sergio Callegari User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Ondrej Zary CC: linux-kernel@vger.kernel.org Subject: Re: IDE Floppy support for IOMEGA Zip Drive broken in 3.16 -> 3.17 transition References: <201507021811.40632.linux@rainbow-software.org> In-Reply-To: <201507021811.40632.linux@rainbow-software.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2108 Lines: 49 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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/