From owner-freebsd-usb@freebsd.org Wed Feb 8 19:21:15 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 B4609CD5C02 for ; Wed, 8 Feb 2017 19:21:15 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::2]) (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 7F5B6190C for ; Wed, 8 Feb 2017 19:21:15 +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 8ED991FE104; Wed, 8 Feb 2017 20:21:11 +0100 (CET) Subject: Re: USB device not working on FreeBSD To: Mike Tancsa , freebsd-usb@freebsd.org References: <7ebf8e83-4dad-5035-83a6-f11c59d7fcbe@selasky.org> <3a733012-3bca-e262-0e25-f9f3607af80d@sentex.net> <8abcf130-bf80-a922-a9d0-1d1e8b5d0a74@selasky.org> <3540190e-c51a-d706-14c4-a0093d7e6571@sentex.net> <8045756a-be33-4ad3-658c-10545a251772@selasky.org> <64baf2ce-b9f7-7efa-9172-0c88c0cee02c@sentex.net> From: Hans Petter Selasky Message-ID: Date: Wed, 8 Feb 2017 20:20:32 +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: <64baf2ce-b9f7-7efa-9172-0c88c0cee02c@sentex.net> 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2017 19:21:15 -0000 On 02/08/17 19:08, Mike Tancsa wrote: > On 2/8/2017 12:55 PM, Hans Petter Selasky wrote: >> On 02/08/17 18:38, Mike Tancsa wrote: >>> Hi, >>> It works without issue on Linux. >>> What information from usbdump would be helpful from usbdump ? >> >> Hi, >> >> If there are any transaction errors, like non successful USB transfers. > Hi, > This is with UQ_NO_STRINGS set. I start the dump, start up apcupsd, > when a couple of seconds then do an apcaccess to query the daemon > > ---Mike > Hi, After your device receives the following control endpoint request it becomes unrecoverable: > 13:05:50.860195 usbus0.4 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 > frame[0] WRITE 8 bytes > 0000 A1 01 52 03 00 00 03 00 -- -- -- -- -- -- -- -- |..R..... | ^^ USB read interface class (A1) ^^ GET_REPORT (01) ^^ feature (03) ^^ length (3 bytes) > frame[1] READ 3 bytes > 13:05:50.860938 usbus0.4 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=0,IVAL=0,ERR=IOERROR > frame[0] WRITE 8 bytes > frame[1] READ 0 bytes Can you disable devd, and launch the apcupsd manually? Can you figure out which application is doing this request? If you don't start apcupsd, is this request then issued? If you stop other daemons like hald, webcamd ... ? Is the request still there when you plug the device? Are you using the latest version of apcupsd ? BTW: The manufacturer should be let aware of this issue. It's like a zero-day to stop the device from working properly. --HPS