LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Amedee Van Gasse <amedee@amedee.be>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Boot time Bluetooth BUG: warning: (value > m) at hid-core.c:793
Date: Mon, 05 Mar 2007 20:19:12 +0100	[thread overview]
Message-ID: <1173122352.19761.33.camel@saruman> (raw)

[-- Attachment #1: Type: text/plain, Size: 3264 bytes --]

On Tue, 27 Feb 2007 16:54:27 +0100 (CET), Jiri Kosina <> wrote:
> 
> 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)?

It _appears_ that the bug reports started after an update of
bluez-utils, but this remains to be confirmed. It could be
coincidence/temporal correlation (which does not imply causation).

As for myself, I have a Logitech MX5000 keyboard/mouse with usb dongle,
and I can confirm that the keyboard/mouse have always worked in HID.
But in HID mode, no other bluetooth functions are possible (like pairing
with a smartphone).
It's possible to switch from HID to HCI and have a working mouse
+bluetooth receiver, but in that case the keyboard can't pair.

I used this script to get functional bluetooth (and unresponsive
keyboard):

hid2hci --tohci
sleep 1
/etc/init.d/bluetooth restart
sleep 1
# connect with the mouse
hidd -i hci0 --connect 00:07:61:48:71:DE
# connect with the keyboard
hidd -i hci0 --connect 00:07:61:3F:DA:41

I think the "-i hci0" isn't even needed, but it can't hurt.

This triggers a lot of occurences of the following in my logs:

BUG: at drivers/hid/hid-core.c:785 implement()
 [<f8d59608>] hid_output_report+0x288/0x300 [hid]
 [<f8d7d4c8>] hid_submit_ctrl+0x58/0x200 [usbhid]
 [schedule_timeout+83/208] schedule_timeout+0x53/0xd0
 [finish_wait+45/112] finish_wait+0x2d/0x70
 [<f8d7d78b>] usbhid_submit_report+0x11b/0x1b0 [usbhid]
 [autoremove_wake_function+0/80] autoremove_wake_function+0x0/0x50
 [<f8d7f9d6>] hiddev_ioctl+0x446/0xb40 [usbhid]
 [filemap_nopage+753/928] filemap_nopage+0x2f1/0x3a0
 [kmap_atomic+134/160] kmap_atomic+0x86/0xa0
 [kunmap_atomic+107/112] kunmap_atomic+0x6b/0x70
 [__handle_mm_fault+633/2624] __handle_mm_fault+0x279/0xa40
 [nameidata_to_filp+53/64] nameidata_to_filp+0x35/0x40
 [do_ioctl+120/144] do_ioctl+0x78/0x90
 [vfs_ioctl+92/672] vfs_ioctl+0x5c/0x2a0
 [sys_ioctl+114/144] sys_ioctl+0x72/0x90
 [sysenter_past_esp+105/169] sysenter_past_esp+0x69/0xa9
 =======================

There are a few Ubuntu bug reports that describe the problem, with some
log files and other useful info:
https://bugs.launchpad.net/ubuntu/+source/bluez-utils/+bug/32415
https://launchpad.net/ubuntu/+source/bluez-utils/+bug/66884/
I have found similar descriptions in other distros.

I have exactly the same experience as Vincent Fortier described
(keyboard working at boot, some keys repeating sometimes, keyboard
unresponsive when bluetooth comes up, keyboard works again after dongle
unplug/replug, but no bluetooth)

Anyway, is this a kernel problem or is bluez-utils to blame?


PS: I bumped into this topic when googling for "046d:c70e". I'm not a
developer (I'm what they call "a user"), but I'm not afraid to get my
hands dirty. If you want me to run debug versions or patched kernels, I
can do that. After all, I have the hardware and I might give you
valuable information (even if I wouldn't recognise it when it spat me in
the face).

-- 
Amedee Van Gasse
amedee@amedee.be

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2007-03-05 19:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-05 19:19 Amedee Van Gasse [this message]
2007-03-05 21:54 ` Jiri Kosina
     [not found]   ` <1173191358.9292.4.camel@saruman>
2007-03-06 14:44     ` Jiri Kosina
2007-03-23  9:15 ` Jiri Kosina
  -- strict thread matches above, loose matches on Subject: below --
2007-02-20  2:11 Fwd: " Veronique & Vincent
2007-02-20  8:02 ` Jiri Kosina
2007-02-22  2:50   ` Pete Zaitcev
2007-02-22  8:04     ` Jiri Kosina
2007-02-22 10:38     ` Veronique & Vincent
2007-02-22 10:46       ` Jiri Kosina
2007-02-16 12:03 [KJ][PATCH] is_power_of_2 in ia64mm Vignesh Babu BM
2007-02-16 15:02 ` [KJ] [PATCH] " Richard Knutsson
2007-02-16 15:27   ` Boot time Bluetooth BUG: warning: (value > m) at hid-core.c:793 Fortier,Vincent [Montreal]
2007-02-18 21:23     ` Jiri Kosina
2007-02-19  0:25       ` Marcel Holtmann
2007-02-19  9:36         ` Jiri Kosina
2007-02-27 15:54         ` Jiri Kosina
2007-02-27 16:12           ` Fortier,Vincent [Montreal]
     [not found]             ` <Pine.LNX.4.64.0702271713220.10496@twin.jikos.cz>
2007-02-27 20:35               ` Fortier,Vincent [Montreal]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1173122352.19761.33.camel@saruman \
    --to=amedee@amedee.be \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Boot time Bluetooth BUG: warning: (value > m) at hid-core.c:793' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).