From: Douglas Gilbert <dgilbert@interlog.com>
To: Hans de Goede <hdegoede@redhat.com>,
daveiro@hotmail.com, tuxoko@gmail.com,
sumit.tiwari1943@gmail.com, wolput@on.nl,
claudio.bizzarri@gmail.com
Cc: linux-usb <linux-usb@vger.kernel.org>,
SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: Updated linux uas driver, please test
Date: Wed, 10 Sep 2014 16:54:32 -0400 [thread overview]
Message-ID: <5410BA88.9090508@interlog.com> (raw)
In-Reply-To: <54104070.20606@redhat.com>
On 14-09-10 08:13 AM, Hans de Goede wrote:
> Hi All,
>
> I'm mailing all of you because you've reported various problems
> with the new uas support in kernel 3.16 and later.
>
> I've been working on making the uas driver more resilient to
> errors, as well as improved logging so we can easier figure
> out the cause of errors.
>
> I would like to ask you all to test a standalone version of
> the new uas driver with the devices you've been having
> trouble with before, and report the results to me.
>
> Testing instructions:
>
> 1) Remove any usb-storage.quirks= setting from the kernel commandline,
> and remove any /etc/modprobe.conf* files doing the same, boot your
> machine without the uas device attached.
>
> 2) Make sure your machine is set up for building kernel modules,
> usually this means installing kernel-devel and gcc packages, see
> your distributions documentation for more info
>
> 3) Download all files from here:
> https://fedorapeople.org/~jwrdegoede/uas/
> And put them all in a single directory, named e.g. uas
>
> 4) Start a terminal, cd into the uas directory
>
> 5) Run the following commands:
> make
> sudo rmmod uas
> sudo insmod ./uas.ko
>
> 6) Connect your uas device
>
> 7) Wait for the disk to show up (wait circa 1 minute max), then do:
>
> dmesg > dmesg.log
> lsusb -v > lsusb.log
>
> 8) Test the uas disk
>
> Once done please send me a mail, in this mail please
>
> 1) Describe how the disk worked, did it show up in a reasonable time,
> and did it work?
>
> 2) Attach dmesg.log and lsusb.log
Could you give some sort of indication of the dd throughput
time (on READs) with UAS given a recent SATA SSD that can
source data faster than 300 MB/sec (say)?
My ASM1051 based dock under W7 got an underwhelming maximum
of 42 MB/sec with such a SATA SSD. And I saw enough stupid
meta-data from SCSI commands to suggest that product should
be binned.
Doug Gilbert
next prev parent reply other threads:[~2014-09-10 20:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 12:13 Updated linux uas driver, please test Hans de Goede
2014-09-10 20:54 ` Douglas Gilbert [this message]
[not found] ` <5410BA88.9090508-qazKcTl6WRFWk0Htik3J/w@public.gmane.org>
2014-09-11 8:07 ` 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=5410BA88.9090508@interlog.com \
--to=dgilbert@interlog.com \
--cc=claudio.bizzarri@gmail.com \
--cc=daveiro@hotmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sumit.tiwari1943@gmail.com \
--cc=tuxoko@gmail.com \
--cc=wolput@on.nl \
/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