From: Marcel Holtmann <marcel@holtmann.org>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: bgsmith@bendcable.com,
"BlueZ users" <bluez-users@lists.sourceforge.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [Bluez-users] Lost connections - mouse and keyboard
Date: Thu, 29 Nov 2007 21:19:03 +0100 [thread overview]
Message-ID: <6EE8D368-C303-400A-B4FE-811228391639@holtmann.org> (raw)
In-Reply-To: <a8e1da0711290006x4bd3cc45x1ae8dcaa9c0ab462@mail.gmail.com>
Hi Dave,
>> apparently does manage bluetooth devices using bluetooth-input-
>> service.
>> I still have the problem of the devices disappearing if idle for too
>> long such as when i lock the desktop or log out for a long period.
>> Sometimes I can re-enable the devices, but sometimes I cannot.
>> This is
>> frustrating.
>>
>> I see a the following several times in the system log if i restart
>> bluetooth:
>> Nov 28 18:53:39 pico kernel: WARNING: at drivers/hid/hid-core.c:784
>> implement() (Tainted: P )
>> Nov 28 18:53:39 pico kernel:
>> Nov 28 18:53:39 pico kernel: Call Trace:
>> Nov 28 18:53:39 pico kernel: [<ffffffff811d8549>] hid_output_report
>> +0x1c5/0x232
>> Nov 28 18:53:39 pico kernel: [<ffffffff811ddaf1>] hid_submit_ctrl
>> +0x60/0x24b
>> Nov 28 18:53:39 pico kernel: [<ffffffff811dde45>]
>> usbhid_submit_report
>> +0x169/0x19e
>> Nov 28 18:53:39 pico kernel: [<ffffffff811e030b>] hiddev_ioctl
>> +0x368/0x919
>> Nov 28 18:53:39 pico kernel: [<ffffffff810f54c5>] inode_has_perm
>> +0x65/0x72
>> Nov 28 18:53:39 pico kernel: [<ffffffff81120c17>] __up_read
>> +0x19/0x7f
>> Nov 28 18:53:39 pico kernel: [<ffffffff8125eecc>] do_page_fault
>> +0x490/0x7e4
>> Nov 28 18:53:39 pico kernel: [<ffffffff810a7399>] do_ioctl+0x55/0x6b
>> Nov 28 18:53:39 pico kernel: [<ffffffff810a75f2>] vfs_ioctl
>> +0x243/0x25c
>> Nov 28 18:53:39 pico kernel: [<ffffffff810a7664>] sys_ioctl
>> +0x59/0x79
>> Nov 28 18:53:39 pico kernel: [<ffffffff8100bd45>] tracesys+0xd5/0xda
>>
>
> Does bluetooth input devices have something to do with usbhid? I don't
> know, perhaps this is another problem in kernel.
in case you have a HID proxy dongle the usbhid driver can be involved.
And since this is hiddev, then it will be caused by the hid2hci program.
Regards
Marcel
next prev parent reply other threads:[~2007-11-29 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1196009038.14897.6.camel@pico>
[not found] ` <1196056187.4217.54.camel@aeonflux>
[not found] ` <1196305426.23029.12.camel@pico>
2007-11-29 8:06 ` [Bluez-users] Lost connections - mouse and keyboard Dave Young
2007-11-29 20:19 ` Marcel Holtmann [this message]
2007-11-29 20:43 ` Jiri Kosina
2007-11-30 1:06 ` Dave Young
2007-11-30 9:15 ` Jiri Kosina
2007-12-07 23:42 ` Didier Link
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=6EE8D368-C303-400A-B4FE-811228391639@holtmann.org \
--to=marcel@holtmann.org \
--cc=bgsmith@bendcable.com \
--cc=bluez-users@lists.sourceforge.net \
--cc=hidave.darkstar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).