Date: Mon, 15 Oct 2012 13:51:10 -0400 (EDT) From: AnneHaase@aol.com To: freebsd-usb@freebsd.org Subject: Welcome to Chase Online Message-ID: <16cf3.15ac9dd2.3dada70e@aol.com>
next in thread | raw e-mail | index | archive | help
How do I find out my balance. Margaret a haase From owner-freebsd-usb@FreeBSD.ORG Thu Oct 18 16:01:59 2012 Return-Path: <owner-freebsd-usb@FreeBSD.ORG> Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DF09B2D2 for <freebsd-usb@freebsd.org>; Thu, 18 Oct 2012 16:01:59 +0000 (UTC) (envelope-from peerst@gmail.com) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) by mx1.freebsd.org (Postfix) with ESMTP id A517D8FC18 for <freebsd-usb@freebsd.org>; Thu, 18 Oct 2012 16:01:59 +0000 (UTC) Received: by mail-ie0-f182.google.com with SMTP id k10so18336742iea.13 for <freebsd-usb@freebsd.org>; Thu, 18 Oct 2012 09:01:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=tuWZJkce1/1ihjLTelPD8T7yST6Rm/dSzUNRcJoYPN4=; b=IUVVEggEz0O6oGDk5k/om9IjRkqjjAM4ICIMicFHb34v5deyKLiGgDbSfQxQf41zLl r2FrgBAmt9WnbKDGz4vbMVnL/UTSqN2L+WfmhiavEtt5N4RSKNO7g0DVAdrr4zNhB414 7UZsbAYaKVsdZvAa1x7Ig3plwzunsqrQdltkurc8zIxIs47ID50mk0a2OeRtD84rZHl/ 7dwGcgHWXfq64SL2z2jvlmEgCLm5GQBpzE8OFQeEuOSl8fCM81Fv8Mcy3lNnH7gTLq/G /cX+I46b8ME8zfvQ+yRHrsyKKrYwFzyPqPTVg6vA6G96DtsL2wUNxJFwRqrkmfrnPbh+ T7Zg== MIME-Version: 1.0 Received: by 10.50.188.129 with SMTP id ga1mr5473052igc.6.1350576118868; Thu, 18 Oct 2012 09:01:58 -0700 (PDT) Received: by 10.64.167.137 with HTTP; Thu, 18 Oct 2012 09:01:58 -0700 (PDT) Date: Thu, 18 Oct 2012 18:01:58 +0200 Message-ID: <CA+ervzaoJY5R+AY8FM97opL8Gx8bHziZTi24A_DDG8-VRFjtgg@mail.gmail.com> Subject: USB transfers stuck in kernel/libusb not sent out until next transfer is submitted From: Peer Stritzinger <peerst@gmail.com> To: freebsd-usb <freebsd-usb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: FreeBSD support for USB <freebsd-usb.freebsd.org> List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-usb>, <mailto:freebsd-usb-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 18 Oct 2012 16:02:00 -0000 Hi, I have a embedded system that communicates to gateway devices via just on IN and OUT bulk endpoint. With one kind of gateway devices it works like a charm via High-Speed USB2. Now we've built another gateway thats using Full-Speed USB only (using one of the Atmega CPUS). We were experiencing lost transfers that never reached the gateway. After first suspecting the gateway we now concluded that the gateway is not losing this transfers. I see transfers being submitted to libusb with libusb_submit_transfer(), but they are not showing up in the callback, neither as completed nor as any errors. I'm also watching the USB Bus with a sniffer and I don't see this transfers being sent. What I see however that older transfers that were also missing are sent at the same time I submit a new transfer. This only seems to happen if I send a few OUT transfers consecutively (not sure if waiting in between helps) without any IN transfers in between. The gateway is always ready to receive more OUT transfers, I never see a NAK in the traces. Unfortunately the FreeBSD on these devices is relatively old: FreeBSD triton.stritzinger.com 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:48:17 UTC 2009 root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 It would screw up my deadlines if I need to upgrade the OS to make this work again, so I thought I asked first: * Is this a known problem thats being already fixed in newer FreeBSD's? (so if I loose the time I can be sure it works then) * Is there a workaround to get this running without upgrading first (would help a lot meeting the deadline, then upgrading in my own time) * Any tips how to debug this further? Cheers, -- Peer
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16cf3.15ac9dd2.3dada70e>