From owner-freebsd-usb@freebsd.org  Wed Feb  8 17:30:48 2017
Return-Path: <owner-freebsd-usb@freebsd.org>
Delivered-To: freebsd-usb@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id CF114CD69C3
 for <freebsd-usb@mailman.ysv.freebsd.org>;
 Wed,  8 Feb 2017 17:30:48 +0000 (UTC) (envelope-from hps@selasky.org)
Received: from mail.turbocat.net (turbocat.net [88.99.82.50])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 994671A41
 for <freebsd-usb@freebsd.org>; Wed,  8 Feb 2017 17:30:48 +0000 (UTC)
 (envelope-from hps@selasky.org)
Received: from hps2016.home.selasky.org (unknown [62.141.129.119])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by mail.turbocat.net (Postfix) with ESMTPSA id 5828E1FE104;
 Wed,  8 Feb 2017 18:30:42 +0100 (CET)
Subject: Re: I'm experiencing g_vfs_done() error = 5 with more than one
 USB/HDD storage device on 11-STABLE when heavy writing.
To: Jakub Lach <jakub_lach@mailplus.pl>, freebsd-usb@freebsd.org
References: <1486574307023-6166271.post@n6.nabble.com>
From: Hans Petter Selasky <hps@selasky.org>
Message-ID: <b113468b-5de3-6efa-37e4-22d3a77b888a@selasky.org>
Date: Wed, 8 Feb 2017 18:30:03 +0100
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101
 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <1486574307023-6166271.post@n6.nabble.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-usb@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: FreeBSD support for USB <freebsd-usb.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-usb>,
 <mailto:freebsd-usb-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-usb/>
List-Post: <mailto:freebsd-usb@freebsd.org>
List-Help: <mailto:freebsd-usb-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-usb>,
 <mailto:freebsd-usb-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2017 17:30:48 -0000

On 02/08/17 18:18, Jakub Lach wrote:
> As of now, I'm rebuilding system with a GENERIC kernel, what
> should I do to provide as much as possible useful debug?
>
> I think the problem only manifested itself after I've switched to
> much faster internal SSD, that would explain why some mitigate
> it by throttling USB speed.
>

Hi,

Some suggestions:

1) UMASS has a set of debug knobs under hw.usb.umass.debug

2) Stress test a fresh disk, which you don't have any data on with 
/usr/src/tools/tools/usbtest to ensure it is 100% compatible with FreeBSD.

3) usbdump can be used to capture the USB traffic and identify failing 
commands.

--HPS