From: Hans de Goede <hdegoede-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Darrick J. Wong"
<darrick.wong-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>,
Gerd Hoffmann <kraxel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
usb-storage-ijkIwGHArpdIPJnuZ7Njw4oP9KaGy4wf@public.gmane.org
Subject: Re: UAS crash with Apricorn USB3 SATA bridge
Date: Wed, 10 Dec 2014 09:19:04 +0100 [thread overview]
Message-ID: <548801F8.8080207@redhat.com> (raw)
In-Reply-To: <20141209193116.GA25163-PTl6brltDGh4DFYR7WNSRA@public.gmane.org>
Hi,
On 09-12-14 20:31, Darrick J. Wong wrote:
> Hi,
>
> I have an Apricorn USB 3 disk dongle thing that claims to support UAS.
> However, the kernel crashes when I plug it in[1].
Yes there are some known issues with uas error handling which are fixed
in 3.18, can you try with a 3.18 kernel please ?
Note that the device will likely still not work, but it should no
longer crash things. When running 3.18 please collect the output of
"dmesg" after plugging in the drive and send that to me, then we'll see
if we can get it to work from there.
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
next prev parent reply other threads:[~2014-12-10 8:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 19:31 UAS crash with Apricorn USB3 SATA bridge Darrick J. Wong
[not found] ` <20141209193116.GA25163-PTl6brltDGh4DFYR7WNSRA@public.gmane.org>
2014-12-10 8:19 ` Hans de Goede [this message]
2014-12-10 9:04 ` Darrick J. Wong
2014-12-10 10:15 ` Darrick J. Wong
2014-12-10 10:29 ` Darrick J. Wong
2014-12-11 1:41 ` Darrick J. Wong
[not found] ` <20141211014154.GB21944-PTl6brltDGh4DFYR7WNSRA@public.gmane.org>
2014-12-11 8:37 ` Darrick J. Wong
2014-12-12 10:40 ` Hans de Goede
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=548801F8.8080207@redhat.com \
--to=hdegoede-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=darrick.wong-QHcLZuEGTsvQT0dZR+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=usb-storage-ijkIwGHArpdIPJnuZ7Njw4oP9KaGy4wf@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;
as well as URLs for NNTP newsgroup(s).