Date: Wed, 6 Jun 2012 18:21:04 +0200 From: Hans Petter Selasky <hselasky@c2i.net> To: Mark Felder <feld@feld.me> Cc: freebsd-usb@freebsd.org Subject: Re: usb power output issues Message-ID: <201206061821.04306.hselasky@c2i.net> In-Reply-To: <op.wfhob6s934t2sn@tech304> References: <op.wfhm2uot34t2sn@tech304> <201206061758.32133.hselasky@c2i.net> <op.wfhob6s934t2sn@tech304>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 06 June 2012 18:05:56 Mark Felder wrote: > On Wed, 06 Jun 2012 10:58:32 -0500, Hans Petter Selasky <hselasky@c2i.net> > > wrote: > > Hi, > > > > Can you try pressing CTRL+ALT+F1, then CTRL+ALT+F9. Sometimes I see > > something > > similar, and switching back and forth between the console helps. > > The keyboard goes *completely* dead, so even switching VTs like that isn't > possible. > > I worked around the issue by plugging in a powered USB hub. So currently > if I plug in my keyboard directly, it won't work. > > > You can try to get dmesg, and also run: > > > > usbconfig dump_device_desc dump_curr_config_desc > > > > If your device times out on the command above, something is wrong in > > USB. Else > > it is a problem in the interaction with X11. > > It doesn't appear to time out when I collect that info, and it can't be an > X11 issue because I can kill X11 completely and the problem persists. > > > FYI: CAPS-LOCK-LED and NUM-LOCK-LED are software controlled by the USB > > stack. > > I suspected as much. > > > See attached. Attachments look OK. Are any other USB devices being used at the time this failure happens? --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201206061821.04306.hselasky>