Re: USB: ums driver no longer detects Logitech mouse

Doing some debug I found that USB driver not sense any UICLASS_HID devives 
now probably because of the error below. Who is in charge in our USB code?

ehci_activate_qh: unexpected next ptr
QH(0xc4b33d80) at 0x7dca8d80:
  sqtd=0xc4b34d20 inactivesqtd=0xc4b34d80
  link=0x7dca0182<QH>
  endp=0x80012102
    addr=0x02 inact=0 endpt=1 eps=2 dtc=0 hrecl=0
    mpl=0x1 ctl=0 nrl=8
  endphub=0x41011c01
    smask=0x01 cmask=0x1c huba=0x01 port=2 mult=1
  curqtd=0x00000001<T>
Overlay qTD:
  next=0x7dca9d80<> altnext=0x00000001<T>
  status=0x00000000: toggle=0 bytes=0x0 ioc=0 c_page=0x0
    cerr=0 pid=0 stat=0x0
  buffer[0]=0x00000000
  buffer[1]=0x00000000
  buffer[2]=0x00000000
  buffer[3]=0x00000000
  buffer[4]=0x00000000
QTD(0xc4b34d20) at 0x7dca9d20:
  next=0x7dca9d80<> altnext=0x7dca9d80<>
  status=0x00018d00: toggle=0 bytes=0x1 ioc=1 c_page=0x0
    cerr=3 pid=1 stat=0x0
  buffer[0]=0x015d93cc
  buffer[1]=0x00000000
  buffer[2]=0x00000000
  buffer[3]=0x00000000
  buffer[4]=0x00000000
QTD(0xc4b34d80) at 0x7dca9d80:
  next=0x00000001<T> altnext=0x00000001<T>
  status=0x00000000: toggle=0 bytes=0x0 ioc=0 c_page=0x0
    cerr=0 pid=0 stat=0x0
  buffer[0]=0x00000000
  buffer[1]=0x00000000
  buffer[2]=0x00000000
  buffer[3]=0x00000000
  buffer[4]=0x00000000

On Wed, Jun 04, 2008 at 12:59:08PM +0400, Andrey Chernov wrote:
> Recent ums stops to detect Logitech mouse. Previous kernel from about 
> month ago handle it normally as:
> ums0: <Logitech USB Gaming Mouse, class 0/0, rev 2.00/49.00, addr 2> on uhub7
> ums0: 16 buttons and Z dir.
> uhid0: <Logitech USB Gaming Mouse, class 0/0, rev 2.00/49.00, addr 2> on uhub7
> 
> Now only as generic device:
> ugen0: <vendor 0x046d product 0x0990, class 239/2, rev 2.00/0.05, addr 3> on uhub4
> 
> Here is usbdevs output:
> Controller /dev/usb3:
> addr 1: high speed, self powered, config 1, EHCI root hub(0x0000), Intel(0x0000), rev 1.00, device uhub3
> ...
>   port 4 addr 3: high speed, power 500 mA, config 1, product 0x0990(0x0990), vendor 0x046d(0x046d), rev 0.05, device ugen0
> ...
>  port 4 powered
> ...
> 
> Please fix.
> 
> -- 
> http://ache.pp.ru/
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"


-- 
http://ache.pp.ru/