From owner-freebsd-hackers@freebsd.org Sat Mar 9 15:26:39 2019 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9335B1529B54 for ; Sat, 9 Mar 2019 15:26:39 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (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 A6DD28BE9C for ; Sat, 9 Mar 2019 15:26:38 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id x29FQDfp071741 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 9 Mar 2019 17:26:16 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua x29FQDfp071741 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id x29FQDYo071740; Sat, 9 Mar 2019 17:26:13 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 9 Mar 2019 17:26:13 +0200 From: Konstantin Belousov To: "O'Connor, Daniel" Cc: Hans Petter Selasky , FreeBSD Hackers Subject: Re: USB stack getting confused Message-ID: <20190309152613.GM2492@kib.kiev.ua> References: <3B29D870-41F9-46AF-B9F3-03106DEC417D@dons.net.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3B29D870-41F9-46AF-B9F3-03106DEC417D@dons.net.au> User-Agent: Mutt/1.11.3 (2019-02-01) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FORGED_GMAIL_RCVD,FREEMAIL_FROM, NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tom.home X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Mar 2019 15:26:39 -0000 On Sat, Mar 09, 2019 at 08:59:30PM +1030, O'Connor, Daniel wrote: > > > > On 9 Mar 2019, at 19:30, Hans Petter Selasky wrote: > > On 3/9/19 12:08 AM, O'Connor, Daniel wrote: > >> My program normally runs continually doing acquisitions of data for N seconds, doing some checks and restarting. After a while (~30 1 minute acquisitions or ~8 30 minute ones) my program can't 'see' the device (it uses libusb10) any more (it reconnects each acquisition for $REASONS). Also pretty weirdly usbconfig can't see it either(!). > > > > What is printed in dmesg? Maybe the device has a problem. > > There is nothing in dmesg - no disconnect / reconnect etc. > > If I hold the user space process in gdb 'forever' (eg over night) usbconfig doesn't see the device, but the moment I quit the user space process it can be seen again. Does it mean that the file descriptor opened for ugen has a chance to be closed ? I suspect that usb subsystem tried to destroy the device but some internal refcounting prevents it. Proper use of destroy_dev(_cb)(9) avoids the issue.