RELENG_6 regression: ums0: X report 0x0002 not supported

[Ulrich Spoerlein]

Hi,

after updating an Intel S5000PAL system from 6.2 to 6.3, ums(4) is no
longer attaching correctly.

Here's an dmesg diff between 6.2 and 6.3

 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
 uhub3: 2 ports with 2 removable, self powered
 ehci0: <EHCI (generic) USB 2.0 controller> mem 0xe8d00000-0xe8d003ff
irq 23 at device 29.7 on pci0
 ehci0: [GIANT-LOCKED]
 usb4: EHCI version 1.0
 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
 usb4: <EHCI (generic) USB 2.0 controller> on ehci0
 usb4: USB revision 2.0
 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
 uhub4: 8 ports with 8 removable, self powered
 ukbd0: Avocent Avocent Embedded DVC 1.0, rev 2.00/0.00, addr 2, iclass 3/1
 kbd2 at ukbd0
 ums0: Avocent Avocent Embedded DVC 1.0, rev 2.00/0.00, addr 2, iclass 3/1
-ums0: 3 buttons and Z dir.
-uhid0: Avocent Avocent Embedded DVC 1.0, rev 2.00/0.00, addr 2, iclass 3/1
-uhid0: could not read endpoint descriptor
-device_attach: uhid0 attach returned 6
+ums0: X report 0x0002 not supported
+device_attach: ums0 attach returned 6

Attached is the full 6.3 dmesg. Looks weird to me, anything I can try
on this hardware?

Uli
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dmesg.boot
Type: application/octet-stream
Size: 8389 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20080514/dbf548a7/dmesg.obj