From owner-freebsd-usb@freebsd.org  Fri Feb 10 08:43:57 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 860F1CD93A7
 for <freebsd-usb@mailman.ysv.freebsd.org>;
 Fri, 10 Feb 2017 08:43:57 +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 4E14B1C34
 for <freebsd-usb@freebsd.org>; Fri, 10 Feb 2017 08:43:56 +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 9C6371FE104;
 Fri, 10 Feb 2017 09:43:47 +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>
 <b113468b-5de3-6efa-37e4-22d3a77b888a@selasky.org>
 <1486576714123-6166280.post@n6.nabble.com>
 <1486586486956-6166339.post@n6.nabble.com>
 <69849996-b3a0-8a3f-1647-f7b49b3455dc@selasky.org>
 <1486590017635-6166351.post@n6.nabble.com>
 <1486628358271-6166438.post@n6.nabble.com>
 <1486670714530-6166615.post@n6.nabble.com>
From: Hans Petter Selasky <hps@selasky.org>
Message-ID: <dcc497e0-cdad-fcbc-13c6-38bee3fc413a@selasky.org>
Date: Fri, 10 Feb 2017 09:43:12 +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: <1486670714530-6166615.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: Fri, 10 Feb 2017 08:43:57 -0000

On 02/09/17 21:05, Jakub Lach wrote:
> For some reason, samsung/jmicron one is prone to disconnecting
> itself, which could explain some errors, as in usbdump.
>
> However, under GENERIC, I was able to use dump twice time
> on touro s without problems (4h+ of disk writes).
>
> _BUT_ as soon as I've returned to my usual kernel config, the
> problem reappeared.
>
> http://pastebin.ca/3765981
>
> So I blame kernel config now. Is it possible that usb related modules
> behave differently than in kernel default ones?
>

Hi,

What options are different between these two kernel configurations?

There is also:
hw.usb.umass.throttle

to throttle USB UMASS traffic.

--HPS