Hi all
I m using a Logitech MX 5000 keyboard with an included MX 1000 mouse,
both bluetooth using the same USB reciever.
When the USB reciever is already plugged-in at boot-time and the
Bluetooth service fires-up I get this message:
=======================
BUG: warning: (value > m) at
drivers/usb/input/hid-core.c:793/implement() (Tainted: P )
[<c0405018>] dump_trace+0x69/0x1b6
[<c040517d>] show_trace_log_lvl+0x18/0x2c
[<c0405778>] show_trace+0xf/0x11
[<c0405875>] dump_stack+0x15/0x17
[<c05993c0>] hid_output_report+0x23c/0x2e7
[<c05994b7>] hid_submit_ctrl+0x4c/0x1d9
[<c05997fd>] hid_submit_report+0x134/0x15f
[<c059bd09>] hiddev_ioctl+0x327/0x88a
[<c04802c8>] do_ioctl+0x4c/0x62
[<c0480528>] vfs_ioctl+0x24a/0x25c
[<c0480586>] sys_ioctl+0x4c/0x66
[<c040404b>] syscall_call+0x7/0xb
[<005b5402>] 0x5b5402
=======================
At this point both the keyboard and mouse do not work. I simply have to
remove/replug the reciever to make them work properly... Here is the
dmesg associated with the replug:
usb 2-2: USB disconnect, address 3
usb 2-2.1: USB disconnect, address 6
usb 2-2.2: USB disconnect, address 4
usb 2-2.3: USB disconnect, address 5
usb 2-2: new full speed USB device using uhci_hcd and address 7
usb 2-2: configuration #1 chosen from 1 choice
hub 2-2:1.0: USB hub found
hub 2-2:1.0: 3 ports detected
usb 2-2.2: new full speed USB device using uhci_hcd and address 8
usb 2-2.2: configuration #1 chosen from 1 choice
input: Logitech Logitech BT Mini-Receiver as /class/input/input6
input: USB HID v1.11 Keyboard [Logitech Logitech BT Mini-Receiver] on
usb-0000:00:1d.1-2.2
usb 2-2.3: new full speed USB device using uhci_hcd and address 9
usb 2-2.3: configuration #1 chosen from 1 choice
input: Logitech Logitech BT Mini-Receiver as /class/input/input7
input,hiddev96: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver]
on usb-0000:00:1d.1-2.3
Kernel: 2.6.19 on i686
I have attached the lsusb output and dmesg.
- vin
On Fri, 16 Feb 2007, Fortier,Vincent [Montreal] wrote:
> I m using a Logitech MX 5000 keyboard with an included MX 1000 mouse,
> both bluetooth using the same USB reciever.
> When the USB reciever is already plugged-in at boot-time and the
> Bluetooth service fires-up I get this message:
> =======================
> BUG: warning: (value > m) at
> drivers/usb/input/hid-core.c:793/implement() (Tainted: P )
> [<c0405018>] dump_trace+0x69/0x1b6
> [<c040517d>] show_trace_log_lvl+0x18/0x2c
> [<c0405778>] show_trace+0xf/0x11
> [<c0405875>] dump_stack+0x15/0x17
> [<c05993c0>] hid_output_report+0x23c/0x2e7
> [<c05994b7>] hid_submit_ctrl+0x4c/0x1d9
> [<c05997fd>] hid_submit_report+0x134/0x15f
> [<c059bd09>] hiddev_ioctl+0x327/0x88a
> [<c04802c8>] do_ioctl+0x4c/0x62
> [<c0480528>] vfs_ioctl+0x24a/0x25c
> [<c0480586>] sys_ioctl+0x4c/0x66
> [<c040404b>] syscall_call+0x7/0xb
> [<005b5402>] 0x5b5402
> =======================
(added Marcel to CC)
This means that something (I guess that it's hid2hci command?) is trying
to pass through hiddev a value in a field that is greater than a given
bitmask (and is not going to fit into the bitfield).
Vincent, does the problem go away when you don't use bluetooth (both
keyboard and mouse is switched to HID mode, if they support it)?
Marcel, do you have any idea how this could happen?
Thanks,
--
Jiri Kosina
Hi Jiri,
> > I m using a Logitech MX 5000 keyboard with an included MX 1000 mouse,
> > both bluetooth using the same USB reciever.
> > When the USB reciever is already plugged-in at boot-time and the
> > Bluetooth service fires-up I get this message:
> > =======================
> > BUG: warning: (value > m) at
> > drivers/usb/input/hid-core.c:793/implement() (Tainted: P )
> > [<c0405018>] dump_trace+0x69/0x1b6
> > [<c040517d>] show_trace_log_lvl+0x18/0x2c
> > [<c0405778>] show_trace+0xf/0x11
> > [<c0405875>] dump_stack+0x15/0x17
> > [<c05993c0>] hid_output_report+0x23c/0x2e7
> > [<c05994b7>] hid_submit_ctrl+0x4c/0x1d9
> > [<c05997fd>] hid_submit_report+0x134/0x15f
> > [<c059bd09>] hiddev_ioctl+0x327/0x88a
> > [<c04802c8>] do_ioctl+0x4c/0x62
> > [<c0480528>] vfs_ioctl+0x24a/0x25c
> > [<c0480586>] sys_ioctl+0x4c/0x66
> > [<c040404b>] syscall_call+0x7/0xb
> > [<005b5402>] 0x5b5402
> > =======================
>
> (added Marcel to CC)
>
> This means that something (I guess that it's hid2hci command?) is trying
> to pass through hiddev a value in a field that is greater than a given
> bitmask (and is not going to fit into the bitfield).
>
> Vincent, does the problem go away when you don't use bluetooth (both
> keyboard and mouse is switched to HID mode, if they support it)?
>
> Marcel, do you have any idea how this could happen?
we understand the original CSR HID proxy dongles, but for the Logitech
ones, it is wild guesses. The current support in hid2hci has been tested
on Logitech diNovo first generation and I have no other Logitech
hardware to verify it with. We might simply need the full HID report
descriptor to see who is at fault.
Regards
Marcel
On Mon, 19 Feb 2007, Marcel Holtmann wrote:
> we understand the original CSR HID proxy dongles, but for the Logitech
> ones, it is wild guesses. The current support in hid2hci has been tested
> on Logitech diNovo first generation and I have no other Logitech
> hardware to verify it with. We might simply need the full HID report
> descriptor to see who is at fault.
Vincent,
from the stacktrace it seems that you are using pre-2.6.20 kernel. Could
you please compile kernel with the following changes in
drivers/usb/input/hid-core.c
- comment the #undef DEBUG and #undef DEBUG_DATA
- add #define DEBUG and #define DEBUG_DATA
and send us the output?
--
Jiri Kosina
On Mon, 19 Feb 2007, Marcel Holtmann wrote:
> we understand the original CSR HID proxy dongles, but for the Logitech
> ones, it is wild guesses. The current support in hid2hci has been tested
> on Logitech diNovo first generation and I have no other Logitech
> hardware to verify it with. We might simply need the full HID report
> descriptor to see who is at fault.
As far as I can see from a quick look, the device IDs are unchanged
(0x046d/0xc70e for the keyboard), but the report descriptor seems to
differ from the one you have at
http://www.holtmann.org/linux/bluetooth/logitech.html - that seems pretty
sad.
What puzzles me a bit is a fact that both the bugreporters seem to state
pretty clearly that this started happening after some update, am I right?
Or did the hardware before work all the time in the HID mode, without even
being attempted to switch to HCI (which seems to cause the bug)?
--
Jiri Kosina
>
> we understand the original CSR HID proxy dongles, but for the Logitech
> ones, it is wild guesses. The current support in hid2hci has been
> tested on Logitech diNovo first generation and I have no other
> Logitech hardware to verify it with. We might simply need
> the full HID report descriptor to see who is at fault.
>
> As far as I can see from a quick look, the device IDs are
> unchanged (0x046d/0xc70e for the keyboard), but the report
> descriptor seems to differ from the one you have at
> http://www.holtmann.org/linux/bluetooth/logitech.html - that
> seems pretty sad.
>
> What puzzles me a bit is a fact that both the bugreporters
> seem to state pretty clearly that this started happening
> after some update, am I right?
>
> Or did the hardware before work all the time in the HID mode,
> without even being attempted to switch to HCI (which seems to
> cause the bug)?
>
Actually it's the first time I'm trying this keyboard and mouse.
- vin
Hi Jiri,
Actually I don't know... Let me test this.
Here is the scenario:
1) If I plug my USB dongle after my system has booted, everything works fine (except that the keyboard repeats a few keys somethimes..)
2) If the dongle is already plugged at boot-time, there is a BUG echo in the dmesg when the bluetooth service fires up. This make both the mouse and keyboard unresponsive until I finally unplug / replug the dongle hence going back at state 1)
I never run the hid2hci command manually but the bluetooth init script seems to do so.
Quick test:
1- unplug/plug back the dongle to get back to state 1)
The keyboard and mouse do work has expected...
2- Now run the hid2hci command has root
[root@localhost init.d]# hid2hci
Switching device 046d:c70a to HCI mode was successful
Switching device 046d:c70e to HCI mode was successful
DMESG:
input: Logitech Logitech BT Mini-Receiver as /class/input/input15
input,hiddev96: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:1d.7-6.2.2.1.2.3
BUG: warning: (value > m) at drivers/usb/input/hid-core.c:793/implement() (Tainted: P )
[<c0405018>] dump_trace+0x69/0x1b6
[<c040517d>] show_trace_log_lvl+0x18/0x2c
[<c0405778>] show_trace+0xf/0x11
[<c0405875>] dump_stack+0x15/0x17
[<c05993c0>] hid_output_report+0x23c/0x2e7
[<c05994b7>] hid_submit_ctrl+0x4c/0x1d9
[<c05997fd>] hid_submit_report+0x134/0x15f
[<c059bd09>] hiddev_ioctl+0x327/0x88a
[<c04802c8>] do_ioctl+0x4c/0x62
[<c0480528>] vfs_ioctl+0x24a/0x25c
[<c0480586>] sys_ioctl+0x4c/0x66
[<c040404b>] syscall_call+0x7/0xb
[<001e8402>] 0x1e8402
=======================
BUG: warning: ....
3) Now repeat step 1):
=======================
usb 4-6.2.2.1.2.1: new full speed USB device using ehci_hcd and address 24
usb 4-6.2.2.1.2.1: configuration #1 chosen from 1 choice
usb 4-6.2.2.1.2: USB disconnect, address 21
usb 4-6.2.2.1.2.1: USB disconnect, address 24
usb 4-6.2.2.1.2.2: USB disconnect, address 22
usb 4-6.2.2.1.2.3: USB disconnect, address 23
usb 4-6.2.2.1.2: new full speed USB device using ehci_hcd and address 25
usb 4-6.2.2.1.2: configuration #1 chosen from 1 choice
hub 4-6.2.2.1.2:1.0: USB hub found
hub 4-6.2.2.1.2:1.0: 3 ports detected
usb 4-6.2.2.1.2.1: new full speed USB device using ehci_hcd and address 26
usb 4-6.2.2.1.2.1: configuration #1 chosen from 1 choice
usb 4-6.2.2.1.2.2: new full speed USB device using ehci_hcd and address 27
usb 4-6.2.2.1.2.2: configuration #1 chosen from 1 choice
input: Logitech Logitech BT Mini-Receiver as /class/input/input16
input: USB HID v1.11 Keyboard [Logitech Logitech BT Mini-Receiver] on usb-0000:00:1d.7-6.2.2.1.2.2
usb 4-6.2.2.1.2.3: new full speed USB device using ehci_hcd and address 28
usb 4-6.2.2.1.2.3: configuration #1 chosen from 1 choice
input: Logitech Logitech BT Mini-Receiver as /class/input/input17
input,hiddev96: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:1d.7-6.2.2.1.2.3
So yes, it looks like a hid2hci BUG or kernel BUG initiated by the hid2hci command.
- vin
> -----Message d'origine-----
> De : Jiri Kosina [mailto:[email protected]]
> Envoy? : 27 f?vrier 2007 11:15
> ? : Fortier,Vincent [Montreal]
> Objet : RE: Boot time Bluetooth BUG: warning: (value > m) at
> hid-core.c:793
>
> On Tue, 27 Feb 2007, Fortier,Vincent [Montreal] wrote:
>
> > Actually it's the first time I'm trying this keyboard and mouse.
>
> And I guess when you use it in HID mode (i.e. when the
> hid2hci command is not run), then keyboard and mouse work
> with no errors reported in the kernel logs, and all the
> buttons work correctly, am I right?
>
> --
> Jiri Kosina
>