linux-kernel - Re: Boot time Bluetooth BUG: warning: (value

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 19 Feb 2007 01:25:33 +0100
From:	Marcel Holtmann <marcel@...tmann.org>
To:	Jiri Kosina <jikos@...os.cz>
Cc:	"Fortier,Vincent [Montreal]" <Vincent.Fortier1@...GC.CA>,
	linux-kernel@...r.kernel.org
Subject: Re: Boot time Bluetooth BUG: warning: (value > m) at hid-core.c:793

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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/