From owner-freebsd-usb@freebsd.org Wed May 18 16:18:57 2016 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 200D7B417DB for ; Wed, 18 May 2016 16:18:57 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (mail.turbocat.net [IPv6:2a01:4f8:d16:4514::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 CFCE4112E for ; Wed, 18 May 2016 16:18:56 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.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 523371FE024; Wed, 18 May 2016 18:18:54 +0200 (CEST) Subject: Re: Oddity with ugen To: Karl Denninger , freebsd-usb@freebsd.org References: <46bd6efe-5335-f659-0b07-5107b0e9a326@selasky.org> <8dfad53f-e8a6-68b7-37e2-d5cd95768ceb@denninger.net> From: Hans Petter Selasky Message-ID: <10288d18-6da5-f5e8-e8ec-57d59b32ca7a@selasky.org> Date: Wed, 18 May 2016 18:22:14 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <8dfad53f-e8a6-68b7-37e2-d5cd95768ceb@denninger.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 May 2016 16:18:57 -0000 On 05/18/16 17:53, Karl Denninger wrote: > This is being seen on a Pi2 / 11-Current. > > I'm reasonably sure that the Pi2 itself and the base USB code is ok, > however, because there is another USB device also in use by the same > software (it emulates a serial port and so attaches on the serial > driver; it exposes itself as a /dev/cua.... device) which has never > exhibited repeated frames although it too talks using interrupt mode, > and also has a packet style of communication, so if it was doing the > same sort of thing my code would have been yelling about it, > particularly since that other device also generates sequence numbers on > the packets for use by the software in implementing a callback stack > (this one doesn't.) Hi, Is this reproducable on a PC w/ EHCI/OHCI/UHCI/XHCI ? Can you check the USB speed of the two different devices? LOW/HIGH/FULL The RPi2 drives most of the USB controller in software, which might influence some of the timing. Further there is quirk for USB interrupt endpoints in the DWC OTG driver, but I'm not sure if that is the cause of the problem. What is the exact time between these spurious packets as seen by usbdump? --HPS