RPI3, usbconfig: could not open device: No error: 0

[Ian Lepore]

On Mon, 2020-03-02 at 09:35 +0100, Hans Petter Selasky wrote:
> On 2020-03-01 20:25, bob prohaska wrote:
> > While trying to unstick a pl2303 usb-serial adapter that wasn't
> > showing up on a Pi3 I tried
> > 
> > root at www:/home/bob # usbconfig reset
> > usbconfig: could not open device: No error: 0
> > 
> > That seemed odd, so I tried:
> > root at www:/home/bob # uname -a
> > FreeBSD www.zefox.org 13.0-CURRENT FreeBSD 13.0-CURRENT r349799
> > GENERIC  arm64
> > root at www:/home/bob # usbconfig
> > ugen0.1: <DWCOTG OTG Root HUB> at usbus0, cfg=0 md=HOST spd=HIGH
> > (480Mbps) pwr=SAVE (0mA)
> > ugen0.2: <vendor 0x0424 product 0x9514> at usbus0, cfg=0 md=HOST
> > spd=HIGH (480Mbps) pwr=SAVE (2mA)
> > ugen0.3: <vendor 0x0424 product 0xec00> at usbus0, cfg=0 md=HOST
> > spd=HIGH (480Mbps) pwr=ON (2mA)
> > ugen0.4: <vendor 0x413c product 0x3010> at usbus0, cfg=0 md=HOST
> > spd=LOW (1.5Mbps) pwr=ON (100mA)
> > ugen0.5: <Logitech Logitech USB Keyboard> at usbus0, cfg=0 md=HOST
> > spd=LOW (1.5Mbps) pwr=ON (100mA)
> > 
> > which looks quite normal.
> > 
> > IIRC this is the first time I've tried the "usbconfig reset"
> > command,
> > so I've no baseline for what to expect.
> > 
> > The machine has been reverted to r349799 for sanity
> > checking, if the behavior is correct or fixed please
> > accept apologies for the noise. If it's wrong is it
> > worth a bug report?
> > 
> 
> If you don't specify a device, all devices will be reset. This
> simply won't work!
> 
> 

What do you mean, it won't work?  Doesn't your first sentence describe
how it's supposed to work (and how it has always worked for me)?

When I do 'usbconfig reset' I see all devices detach, starting with the
root hub and propogating outwards.  Once everything is detached it all
attaches again.  Then the last thing it says is:

  usbconfig: could not open device: No error: 0

That last line is fairly recent, it didn't used to do that.

-- Ian