From: Tejun Heo <htejun@gmail.com>
To: Stanislav Brabec <sbrabec@novell.com>
Cc: albertl@mail.com, jeff@garzik.org, bzolnier@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 20:58:03 +0900 [thread overview]
Message-ID: <45F7E34B.6020206@gmail.com> (raw)
In-Reply-To: <45F7DA2B0200002D0001585E@emea5-mh.id5.novell.com>
Stanislav Brabec wrote:
> 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
I don't think usb 5-1 is related to ide-floppy problem.
> 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.
I see.
> 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.
If that's the case, libata should work too as long as the HSM problem is
fixed.
--
tejun
next prev parent reply other threads:[~2007-03-14 11:58 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 [this message]
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
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=45F7E34B.6020206@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertl@mail.com \
--cc=bzolnier@gmail.com \
--cc=chrubis@suse.cz \
--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).