usb2 moused issue

I just rebuild my kernel after flipping the switch to usb2 in my kernel
config file:

  diff -r 657f71f9e39c -r 82c23c5ef94e sys/i386/conf/KOBE
  --- a/sys/i386/conf/KOBE        Mon Feb 16 02:52:01 2009 +0200
  +++ b/sys/i386/conf/KOBE        Mon Feb 16 03:01:42 2009 +0200
  _at__at_ -179,17 +179,18 _at__at_
   #options       ALTQ_NOPCC      # Required if the TSC is unusable
   #options       ALTQ_DEBUG

  -# USB support
  -device         uhci            # UHCI PCI->USB interface
  -device         ohci            # OHCI PCI->USB interface
  -device         ehci            # EHCI PCI->USB interface (USB 2.0)
  -device         usb             # USB Bus (required)
  -#device                udbp            # USB Double Bulk Pipe devices
  -device         ugen            # Generic
  -device         uhid            # "Human Interface Devices"
  -device         ukbd            # Keyboard
  -device         umass           # Disks/Mass storage - Requires scbus and da
  -device         ums             # Mouse
  -# USB Serial devices
  -device         ucom            # Generic com ttys
  -device         u3g             # USB-based 3G modems (Option, Huawei, Sierra)
  +# USB core support
  +device          usb2_core
  +# USB controller support
  +device         usb2_controller
  +device         usb2_controller_ehci
  +device         usb2_controller_ohci
  +device         usb2_controller_uhci
  +# USB mass storage support
  +device         usb2_storage
  +device         usb2_storage_mass
  +# USB input device support
  +device         usb2_input
  +device         usb2_input_hid
  +device         usb2_input_kbd
  +device         usb2_input_ms

The external USB mouse seems to be recognized file:

  [ dmesg output with hw.usb2.ums.debug=1 ]
  Feb 16 16:19:00 kobe kernel: ugen4.2: <Microsoft> at usbus4
  Feb 16 16:19:00 kobe kernel: ums0: <Microsoft Wireless Optical Mouse 3000 (Model 1056), class 0/0, rev 2.00/0.07, addr 2> on usbus4
  Feb 16 16:19:00 kobe kernel: ums0: 5 buttons and [XYZ] coordinates
  Feb 16 16:19:00 kobe kernel: ums_attach:582: sc=0xc63c7000
  Feb 16 16:19:00 kobe kernel: ums_attach:583: X  48/8
  Feb 16 16:19:00 kobe kernel: ums_attach:584: Y  56/8
  Feb 16 16:19:00 kobe kernel: ums_attach:585: Z  64/8
  Feb 16 16:19:00 kobe kernel: ums_attach:586: T  0/0
  Feb 16 16:19:00 kobe kernel: ums_attach:587: W  0/0
  Feb 16 16:19:00 kobe kernel: ums_attach:591: B1 40/1
  Feb 16 16:19:00 kobe kernel: ums_attach:591: B2 41/1
  Feb 16 16:19:00 kobe kernel: ums_attach:591: B3 42/1
  Feb 16 16:19:00 kobe kernel: ums_attach:591: B4 43/1
  Feb 16 16:19:00 kobe kernel: ums_attach:591: B5 44/1
  Feb 16 16:19:00 kobe kernel: ums_attach:593: size=2, id=19
  Feb 16 16:19:00 kobe kernel: Symlink: ums0 -> usb4.2.0.16

I have enabled `moused_nondefault_enable' in my rc.conf too, and I see
that moused is launched for the external usb mouse:

  [rc.conf]
  moused_nondefault_enable="YES"
  moused_enable="YES"
  moused_flags="-3"
  moused_ums0_flags=""
  moused_port="/dev/psm0"
  moused_type="auto"

  [processes running]
  # ps xauww | sed -n -e 1p -e '/ sed/d' -e /moused/p
  USER       PID %CPU %MEM   VSZ   RSS  TT  STAT STARTED      TIME COMMAND
  root      1309  0.0  0.0  3376  1484  ??  Ss    3:54PM   0:05.01 /usr/sbin/moused -3 -p /dev/psm0 -t auto
  root      1773  0.0  0.0  3376  1492  ??  Is    3:59PM   0:00.00 /usr/sbin/moused -p /dev/ums0 -t auto -I /var/run/moused.ums0.pid

But moving the usb mouse doesn't result in any pointer movement, either
in a console tty or under X11.

Is this a known bug of usb2 mouse support, or just a local config error?