Date: Sat, 9 Mar 2019 20:59:30 +1030 From: "O'Connor, Daniel" <darius@dons.net.au> To: Hans Petter Selasky <hps@selasky.org> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: USB stack getting confused Message-ID: <3B29D870-41F9-46AF-B9F3-03106DEC417D@dons.net.au> In-Reply-To: <f3e6e30b-8b62-546b-2b51-e841f2e645bd@selasky.org> References: <E0371188-FD0A-47E1-8378-40239F5C6622@dons.net.au> <f3e6e30b-8b62-546b-2b51-e841f2e645bd@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 9 Mar 2019, at 19:30, Hans Petter Selasky <hps@selasky.org> 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(!). >=20 > 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. -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B29D870-41F9-46AF-B9F3-03106DEC417D>