From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Claudio Bizzarri <claudio.bizzarri@gmail.com>,
Matt <jackdachef@gmail.com>,
kraxel@redhat.com, Linux Kernel <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
"Nyman, Mathias" <mathias.nyman@intel.com>
Subject: Re: Kernel 3.16.0 USB crash
Date: Thu, 14 Aug 2014 15:07:40 -0700 [thread overview]
Message-ID: <20140814220740.GA32475@xanatos> (raw)
In-Reply-To: <53EC8579.1030008@redhat.com>
Adding Mathias Nyman. He is now the USB 3.0 maintainer.
Sarah Sharp
On Thu, Aug 14, 2014 at 11:46:33AM +0200, Hans de Goede wrote:
> Hi,
>
> On 08/14/2014 10:39 AM, Claudio Bizzarri wrote:
> > Ciao,
> >
> > thank you very much for replay, you are right: it's UAS module. Now I'm
> > using Ubuntu 14.04 with kernel 3.16.1 from
> > http://kernel.ubuntu.com/~kernel-ppa/mainline/, there is no /proc/config.gz,
> > but but there is a config file in /boot:
> >
> > b0@hp850ssd:~⟫ grep USB_UAS /boot/config-3.16.1-031601-generic
> > CONFIG_USB_UAS=m
> >
> > When I attach my external USB disk I've 30 seconds before my laptop freeze,
> > here is my dmesg output, disk is not mounted:
>
> Hmm, this sounds like a similar problem we've been having with JMicron UAS
> bridges over USB-2.
>
> Can you collect "lsusb -v" output for the drive in question when connected
> through an usb-3 port (the uas module does not need to be loaded).
>
> Also can you try the following patch, and see if that makes uas work ? :
>
> diff --git a/drivers/usb/storage/uas.c b/drivers/usb/storage/uas.c
> index 511b229..6cdc1b9 100644
> --- a/drivers/usb/storage/uas.c
> +++ b/drivers/usb/storage/uas.c
> @@ -1033,6 +1033,7 @@ static int uas_configure_endpoints(struct uas_dev_info *devinfo)
> 3, 256, GFP_NOIO);
> if (devinfo->qdepth < 0)
> return devinfo->qdepth;
> + devinfo->qdepth = 32;
> devinfo->use_streams = 1;
> }
>
>
> This is in essence the fix we've done for using these devices with uas over usb-2,
> I would have expected this to not be be necessary at superspeed since there the number
> of streams the device supports is part of the usb descriptors, but maybe the device
> claims to support more streams then it can actually handle.
>
> Note I'm on vacation next week, so don't expect another reply from me in this thread
> for at least a week.
>
> Regards,
>
> Hans
next prev parent reply other threads:[~2014-08-14 22:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-13 20:24 Kernel 3.16.0 USB crash Matt
2014-08-13 21:36 ` Matt
[not found] ` <CAKszPgvjBE5y35guVRXu7kp3nVZa4KPgh=AezVL-UXq=idRc-Q@mail.gmail.com>
2014-08-14 8:42 ` Fwd: " Claudio Bizzarri
2014-08-14 9:46 ` Hans de Goede
2014-08-14 22:07 ` Sarah Sharp [this message]
2014-08-15 7:44 ` Claudio Bizzarri
2014-08-22 18:26 ` Hans de Goede
2014-08-23 7:37 ` Claudio Bizzarri
2014-08-23 10:07 ` Claudio Bizzarri
2014-09-09 6:47 ` Claudio Bizzarri
[not found] <CAKszPguooNOt_o=22sTvxKqa=XX-hzt+6UL1LbAx4TvS35CgCA@mail.gmail.com>
2014-08-04 7:28 ` Claudio Bizzarri
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=20140814220740.GA32475@xanatos \
--to=sarah.a.sharp@linux.intel.com \
--cc=claudio.bizzarri@gmail.com \
--cc=hdegoede@redhat.com \
--cc=jackdachef@gmail.com \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.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