linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Stanislav Brabec <sbrabec@novell.com>
Cc: albertl@mail.com, jeff@garzik.org, htejun@gmail.com,
	alan@lxorguk.ukuu.org.uk, paul@paulbristow.net, chrubis@suse.cz,
	linux-ide@vger.kernel.org
Subject: Re: regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive
Date: Wed, 14 Mar 2007 14:42:09 +0100	[thread overview]
Message-ID: <200703141442.09754.bzolnier@gmail.com> (raw)
In-Reply-To: <45F7DA2B0200002D0001585E@emea5-mh.id5.novell.com>


On Wednesday 14 March 2007, Stanislav Brabec wrote:
> Albert Lee wrote:
> > Tejun Heo wrote:
> 
> > > Hmmm... weird.  Your drive bears the same model name as Stanislav's.  I
> > > don't think the low level driver is causing the difference.  They both
> > > use the standard libata HSM implementation.  Any ideas?  Stanislav, can
> > > you try to connect that zip drive to another IDE controller?
> 
> > Maybe it's also worth a try to replace the medium, cable or even the
> > drive itself to rule out the possibility of hardware problem.
> 
> I'll try it. I cannot replace the drive, I don't have any spare one, but
> my colleague has. He will try it on his machine. So let's wait for
> result.
> 
> Looking at the syslog in Novell bug 232086 in detail, following line may
> indicate hardware failure:
> usb 5-1: string descriptor 0 read error: -22
> 
> My drive is a slave on bus, where master is a modern Seagate ST3160812A.
> 
> On my system I see two regressions:
> - One between year 2002 kernels and SuSE Linux 10.0:
>   Delay with "packet command initiated yet DRQ isn't asserted" before
>   first read access, then the read will succeed.
>   I did not yet reproduce this regression just now on my hardware.
> - Second between SuSE 10.1 and 10.2:
>   Delay with "packet command initiated yet DRQ isn't asserted" before
>   any attempt to access, then it will fail.
>   This regression is reproducible just now on my hardware, but still may
>   be caused by hardware problems raised by a slightly different
>   initialization order.

It is reproduceable, SuSE 10.1 kernel is "good" and SuSE 10.2 is "bad".
So even if this is caused by some hardware problems or different
initialization order git-bisect on 2.6.16-2.6.20 should tell us what
change caused the problem.

PS Tejun, I praise efforts to make ATA floppy drives work with libata
but this is IMO a _future_ work (won't help et all for existing
systems/distributions) and we need to have ide-floppy fixed _now_.

Bart

> Tejun Heo wrote:
> > [libata]
> > And, as the device requires custom high level driver, libata fails
> > miserably.  Would it be worth to try support these devices?  Or are
> > they just too outdated to put the effort in?
> 
> As far as I remember, it was working without any special driver with
> ide-scsi.
> 
> -- 
> Best Regards,
> 
> Stanislav Brabec
> software developer
> ---------------------------------------------------------------------
> SUSE LINUX, s. r. o.                          e-mail: sbrabec@suse.cz
> Lihovarska 1060/12                            tel: +420 284 028 966
> 190 00 Praha 9                                fax: +420 284 028 951
> Czech Republic                                http://www.suse.cz/

  parent reply	other threads:[~2007-03-14 13:35 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-14 10:19 regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive Stanislav Brabec
2007-03-14 11:58 ` Tejun Heo
2007-03-14 13:30   ` Mark Lord
2007-03-14 13:48     ` Tejun Heo
2007-03-15 22:12       ` IOMEGA IDE ZIP (ATAPI) drive Mark Lord
2007-03-16 14:30         ` Albert Lee
2007-03-16 14:37           ` Mark Lord
2007-03-16 15:13           ` Mark Lord
2007-03-16 17:21             ` Albert Lee
2007-03-16 21:17               ` Mark Lord
2007-03-17  3:19                 ` Albert Lee
2007-03-19 15:25                   ` Mark Lord
2007-03-20 10:16                     ` Albert Lee
2007-03-14 17:42     ` regression: ide-floppy doesn't work with IOMEGA IDE ZIP drive Jeff Garzik
2007-03-14 13:42 ` Bartlomiej Zolnierkiewicz [this message]
2007-03-14 13:44   ` Tejun Heo
2007-03-14 18:27     ` Mark Lord
2007-03-15  2:08       ` Tejun Heo
     [not found] ` <45F80841.EMEA5.EMEA5-1.100.1396E6E.1.3873.1@1:7.EMEA5.EMEA5-1.100.0.1.0.1@16>
2007-03-14 20:41   ` Stanislav Brabec
2007-03-15  4:29     ` Albert Lee
2007-03-15 19:58     ` Bartlomiej Zolnierkiewicz
  -- strict thread matches above, loose matches on Subject: below --
2007-03-13 11:17 Stanislav Brabec
2007-03-13 12:14 ` Tejun Heo
2007-03-13 13:42   ` Alan Cox
2007-03-13 14:24     ` Tejun Heo
2007-03-12 12:23 Tejun Heo
2007-03-12 13:27 ` Sergei Shtylyov
2007-03-13 11:50   ` Bartlomiej Zolnierkiewicz
2007-03-12 14:05 ` Jeff Garzik
2007-03-14  8:03   ` Albert Lee
2007-03-14  8:15     ` Tejun Heo
2007-03-14  9:01       ` Albert Lee

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=200703141442.09754.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=albertl@mail.com \
    --cc=chrubis@suse.cz \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=paul@paulbristow.net \
    --cc=sbrabec@novell.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).