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:	Tue, 27 Feb 2007 16:54:27 +0100 (CET)
From:	Jiri Kosina <jikos@...os.cz>
To:	Marcel Holtmann <marcel@...tmann.org>
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

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
-
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/