From: Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Josua Dietze <digidietze-Pw1IEfbnKvGTBPm/0KVrCA@public.gmane.org>
Cc: linux-usb <linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Add US_FL_NO_ULD_ATTACH usb mass storage unusal dev flag ?
Date: Sun, 04 Apr 2010 23:39:09 +0200 [thread overview]
Message-ID: <4BB906FD.8000207@redhat.com> (raw)
In-Reply-To: <4BB8E0DC.8090606-Pw1IEfbnKvGTBPm/0KVrCA@public.gmane.org>
Hi,
On 04/04/2010 08:56 PM, Josua Dietze wrote:
> Hans de Goede schrieb:
>
>> But one of the variants (usb id 1908:1320) still hits a usb-reset
>> when drivers/scsi/sr.c does a READ_CAPACITY from get_sector_size().
>> After the initial READ_CAPACITY failure and the usb reset, the
>> second READ_CAPACITY succeeds.
>
>
> Did you try to set the AVOID_RESET_QUIRK attribute? This was
> originally targeted at those mode-switching devices, but might be
> useful in this case too.
>
Thanks for the hint. although not really what I was looking for
this has prompted me to investigate this issue further as I was
not completely happy with the NO_ULD_ATTACH solution.
After turning on full debugging in the usb-storage driver it
turns out the out enabling of US_FL_SANE_SENSE was the culprit,
when I explicitly specify US_FL_BAD_SENSE, thus disabling the
auto enabling of SANE_SENSE, things are much better, the
first 2 READ_CAPACITY calls still fail (stalled endpoint), but
no longer result in a full device reset.
I'll do a patch adding these devices to unusual_devs.h with
the US_FL_BAD_SENSE quirk tomorrow.
Thanks all for your input.
Regards,
Hans
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-04-04 21:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-04 14:52 Add US_FL_NO_ULD_ATTACH usb mass storage unusal dev flag ? Hans de Goede
2010-04-04 15:00 ` James Bottomley
[not found] ` <4BB8A7BF.6090908-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-04-04 18:56 ` Josua Dietze
[not found] ` <4BB8E0DC.8090606-Pw1IEfbnKvGTBPm/0KVrCA@public.gmane.org>
2010-04-04 21:39 ` Hans de Goede [this message]
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=4BB906FD.8000207@redhat.com \
--to=hdegoede-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=digidietze-Pw1IEfbnKvGTBPm/0KVrCA@public.gmane.org \
--cc=linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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