Date: Thu, 3 Jan 2019 09:31:53 +0100 From: Hans Petter Selasky <hps@selasky.org> To: freebsd-usb@freebsd.org Subject: Re: r342378: usbconfig takes 3-5 minutes to read the bus Message-ID: <5950d771-ffa9-9325-b102-295fd092052e@selasky.org> In-Reply-To: <20190103060431.GA2711@c720-r342378> References: <20190101135156.GA3557@c720-r342378> <3ac801b2-899a-ee09-1398-ecab6ec7130a@selasky.org> <20190102104853.GA2622@c720-r342378> <4bf80067-8e3a-572f-c1b5-ae83b1c40c22@selasky.org> <20190102154701.GA13702@c720-r342378> <2f013cf9-b073-04fd-9932-079f86fa24b1@selasky.org> <d0f569af-342f-dac8-8f6d-4fc0ff21924e@selasky.org> <20190103060431.GA2711@c720-r342378>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/3/19 7:04 AM, Matthias Apitz wrote: > I think, we should isolate the problem from PCSC and focus (first) on the > question why are calls to usbconfig(8) are not answered anymore > *without* any kind of PCSC software being involved as I wrote in the > originating email of this thread. Here it is again in case in got lost > while talking about PCSC: Hi, Usually this happens if a user-space component is not closing its device handle while enumeration happens. Can you run pcsd in the foreground with debugging enabled and show what it prints while you plug unplug the device. Also try setting the hw.usb.uhub.debug=16 sysctl and collect messages in dmesg. --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5950d771-ffa9-9325-b102-295fd092052e>