From: David Webb <djw-8SE8IwxHpK9aa/9Udqfwiw@public.gmane.org>
To: Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: James Bottomley
<James.Bottomley-JuX6DAaQMKPCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>,
Greg Kroah-Hartman
<gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>,
Gerd Hoffmann <kraxel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] uas: Add a new NO_REPORT_LUNS quirk
Date: Thu, 31 Mar 2016 18:35:48 +0100 [thread overview]
Message-ID: <7977162.W24Fksp8b7@ok64> (raw)
In-Reply-To: <56FD40FE.3030302-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Hi,
> Actually it does support REPORT LUNS, some of the time. When you first
> boot the computer with uas blacklisted for this device, so initialize
> it once with usb-storage, and then reboot with out the blacklist
> (and without removing power to the drive) uas will work with REPORT LUNS
> bit cold-booting directly into uas mode and then doing a REPORT LUNS
> upsets the drive / disk enclosure (this has all been observed by
> David Webb, I do not own such a drive).
Just to confirm what Hans has reported. After power has been removed the
Seagate Expansion usb disk always produces faults unless it has been
blacklisted in some way. Once the disk is working the computer can be powered
off and restarted without the blacklist and, as long as its power has not been
removed, the disk can be reconnected many times without any error.
With Hans's changes the disk mounts correctly with the uas module every time.
My guess is that one of the interface registers is not or cannot be
initialized correctly. If after a failure I try unplugging and reinserting
the usb connector many times it has sometimes connected correctly - which to
me means that some random bit eventually has the right value.
Regards,
David Webb.
--
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
WARNING: multiple messages have this Message-ID (diff)
From: David Webb <djw@noc.ac.uk>
To: Hans de Goede <hdegoede@redhat.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Gerd Hoffmann <kraxel@redhat.com>,
linux-usb@vger.kernel.org, linux-scsi@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] uas: Add a new NO_REPORT_LUNS quirk
Date: Thu, 31 Mar 2016 18:35:48 +0100 [thread overview]
Message-ID: <7977162.W24Fksp8b7@ok64> (raw)
In-Reply-To: <56FD40FE.3030302@redhat.com>
Hi,
> Actually it does support REPORT LUNS, some of the time. When you first
> boot the computer with uas blacklisted for this device, so initialize
> it once with usb-storage, and then reboot with out the blacklist
> (and without removing power to the drive) uas will work with REPORT LUNS
> bit cold-booting directly into uas mode and then doing a REPORT LUNS
> upsets the drive / disk enclosure (this has all been observed by
> David Webb, I do not own such a drive).
Just to confirm what Hans has reported. After power has been removed the
Seagate Expansion usb disk always produces faults unless it has been
blacklisted in some way. Once the disk is working the computer can be powered
off and restarted without the blacklist and, as long as its power has not been
removed, the disk can be reconnected many times without any error.
With Hans's changes the disk mounts correctly with the uas module every time.
My guess is that one of the interface registers is not or cannot be
initialized correctly. If after a failure I try unplugging and reinserting
the usb connector many times it has sometimes connected correctly - which to
me means that some random bit eventually has the right value.
Regards,
David Webb.
next prev parent reply other threads:[~2016-03-31 17:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 12:22 [PATCH] uas: Add a new NO_REPORT_LUNS quirk Hans de Goede
[not found] ` <1459426971-11927-1-git-send-email-hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-03-31 14:17 ` Alan Stern
2016-03-31 14:17 ` Alan Stern
2016-03-31 14:48 ` James Bottomley
2016-03-31 15:03 ` Hans de Goede
[not found] ` <56FD3C27.2050708-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-03-31 15:11 ` James Bottomley
2016-03-31 15:11 ` James Bottomley
2016-03-31 15:23 ` Hans de Goede
[not found] ` <56FD40FE.3030302-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2016-03-31 17:35 ` David Webb [this message]
2016-03-31 17:35 ` David Webb
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=7977162.W24Fksp8b7@ok64 \
--to=djw-8se8iwxhpk9aa/9udqfwiw@public.gmane.org \
--cc=James.Bottomley-JuX6DAaQMKPCXq6kfMZ53/egYHeGw8Jk@public.gmane.org \
--cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
--cc=hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=kraxel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=stable-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.