On Tue, 2014-07-29 at 22:46 +0200, Laszlo T. wrote:
> > Disconnection issues like you are seeing are typical for drawing
> > too much power from the port. Using uas as the dmesg shows you
> > are will allow us to send more commands to the disk at once
> > (which is a good thing, it is faster) and as such will increase
> > power consumption.
>
> Maybe the too much commands freeze the chip.
That is a testable hypothesis.
This patch shows how to manipulate that number.
You can play with the number to see whether there's
a critical value.
Regards
Oliver
>From b4139cf6f95babf922d4b4523f13974e3971f4b3 Mon Sep 17 00:00:00 2001
From: Oliver Neukum <oneukum@xxxxxxx>
Date: Wed, 30 Jul 2014 11:55:29 +0200
Subject: [PATCH] uas: one command at a time
for testing purposes
---
drivers/usb/storage/uas.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/storage/uas.c b/drivers/usb/storage/uas.c
index 511b229..792d9c9 100644
--- a/drivers/usb/storage/uas.c
+++ b/drivers/usb/storage/uas.c
@@ -964,7 +964,7 @@ static struct scsi_host_template uas_host_template = {
.eh_abort_handler = uas_eh_abort_handler,
.eh_device_reset_handler = uas_eh_device_reset_handler,
.eh_bus_reset_handler = uas_eh_bus_reset_handler,
- .can_queue = 65536, /* Is there a limit on the _host_ ? */
+ .can_queue = 1, /* Is there a limit on the _host_ ? */
.this_id = -1,
.sg_tablesize = SG_NONE,
.cmd_per_lun = 1, /* until we override it */
--
1.8.4.5
