From owner-freebsd-usb@freebsd.org Mon May 22 12:59:02 2017 Return-Path: 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 C57F7D789E3 for ; Mon, 22 May 2017 12:59:02 +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 83BC91594; Mon, 22 May 2017 12:59:02 +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 61A0F260823; Mon, 22 May 2017 14:58:59 +0200 (CEST) Subject: Re: Ippon Back Power Pro LCD connection flickers To: lev@FreeBSD.org, freebsd-usb@freebsd.org References: <1af248e4-50dd-8268-c378-bd5063929310@FreeBSD.org> <2e73775f-1d81-1e09-22fe-4d46c800b157@FreeBSD.org> From: Hans Petter Selasky Message-ID: <3ac65ccf-d75d-df65-df53-a0b6137b54c2@selasky.org> Date: Mon, 22 May 2017 14:57:00 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: <2e73775f-1d81-1e09-22fe-4d46c800b157@FreeBSD.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2017 12:59:02 -0000 Hi, On 05/22/17 14:23, Lev Serebryakov wrote: > 15:21:08.960407 usbus1.2 > DONE-INTR-EP=00000081,SPD=LOW,NFR=1,SLEN=0,IVAL=100,ERR=IOERROR What is the occurrence rate of this IOERROR? Once per attach/detach. Did you try to connect the USB device to a different port and/or USB HUB. It might also be that the user-space driver tries to reset the device when it sees this error. To figure that out you'll need to enable debugging in the UPS software package. --HPS