Re: UAS errors with Jmicron

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2014-07-31 9:54 GMT+02:00 Oliver Neukum <oneukum@xxxxxxx>:
> On Thu, 2014-07-31 at 00:39 +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.
>>
>> I tested with lot of values. I'm not totally sure but it looks the 31
>> is max number where it is still stable to create an ext4 filesystem.
>
> So we have a number. What is unclear to me from the available
> information is whether we are dealing with a limitation of the
> drive or of the enclosure.
> Did you happen to test the enclosure with another drive?
>

Unfortunately I don't have another notebook disk but I can use without
the enclosure in the PC if it helps something.

I guess this number could be the NCQ queue depth.

Br,
Laszlo
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux