* [Bluez-users] Lost connections - mouse and keyboard
@ 2007-11-25 16:43 Brad Smith
2007-11-26 5:49 ` Marcel Holtmann
0 siblings, 1 reply; 13+ messages in thread
From: Brad Smith @ 2007-11-25 16:43 UTC (permalink / raw)
To: BlueZ users
[-- Attachment #1.1: Type: text/plain, Size: 702 bytes --]
Greetings -
I have a Logitech mouse and keyboard that use bluetooth (dinovo). I
have enabled bluetooth on this Fedora 8 system and both work well with
two problems.
(1) When I lock the system and return later the mouse no longer works.
I have to open a terminal window and issue an hidd --connect command.
(2) When I log out, both the mouse and keyboard stop working. I have to
connect a USB mouse and USB keyboard to enter the authentication
information. Once logged in the bluetooth devices usually work,
although I sometimes have to issue an hidd --connect command to enable
the keyboard.
Any suggestions on resolving these issues would be appreciated.
Thank you,
Brad
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 228 bytes --]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bluez-users] Lost connections - mouse and keyboard
2007-11-25 16:43 [Bluez-users] Lost connections - mouse and keyboard Brad Smith
@ 2007-11-26 5:49 ` Marcel Holtmann
2007-11-29 3:03 ` Brad Smith
0 siblings, 1 reply; 13+ messages in thread
From: Marcel Holtmann @ 2007-11-26 5:49 UTC (permalink / raw)
To: bgsmith, BlueZ users
Hi Brad,
> I have a Logitech mouse and keyboard that use bluetooth (dinovo). I
> have enabled bluetooth on this Fedora 8 system and both work well with
> two problems.
>
> (1) When I lock the system and return later the mouse no longer works.
> I have to open a terminal window and issue an hidd --connect command.
>
> (2) When I log out, both the mouse and keyboard stop working. I have to
> connect a USB mouse and USB keyboard to enter the authentication
> information. Once logged in the bluetooth devices usually work,
> although I sometimes have to issue an hidd --connect command to enable
> the keyboard.
>
> Any suggestions on resolving these issues would be appreciated.
not using hidd and using bluetoothd-input-service instead is one thing.
For input devices to re-connect you have to have a daemon running that
handles this. The input service is the best way to achieve this. Check
the BlueZ wiki for details.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bluez-users] Lost connections - mouse and keyboard
2007-11-26 5:49 ` Marcel Holtmann
@ 2007-11-29 3:03 ` Brad Smith
2007-11-29 8:06 ` Dave Young
0 siblings, 1 reply; 13+ messages in thread
From: Brad Smith @ 2007-11-29 3:03 UTC (permalink / raw)
To: BlueZ users
[-- Attachment #1.1: Type: text/plain, Size: 2548 bytes --]
Thank you for the reply Marvel. I use the gnome bluetooth client which
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
Brad
On Mon, 2007-11-26 at 06:49 +0100, Marcel Holtmann wrote:
> Hi Brad,
>
> > I have a Logitech mouse and keyboard that use bluetooth (dinovo). I
> > have enabled bluetooth on this Fedora 8 system and both work well with
> > two problems.
> >
> > (1) When I lock the system and return later the mouse no longer works.
> > I have to open a terminal window and issue an hidd --connect command.
> >
> > (2) When I log out, both the mouse and keyboard stop working. I have to
> > connect a USB mouse and USB keyboard to enter the authentication
> > information. Once logged in the bluetooth devices usually work,
> > although I sometimes have to issue an hidd --connect command to enable
> > the keyboard.
> >
> > Any suggestions on resolving these issues would be appreciated.
>
> not using hidd and using bluetoothd-input-service instead is one thing.
> For input devices to re-connect you have to have a daemon running that
> handles this. The input service is the best way to achieve this. Check
> the BlueZ wiki for details.
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 309 bytes --]
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bluez-users] Lost connections - mouse and keyboard
2007-11-29 3:03 ` Brad Smith
@ 2007-11-29 8:06 ` Dave Young
2007-11-29 20:19 ` Marcel Holtmann
0 siblings, 1 reply; 13+ messages in thread
From: Dave Young @ 2007-11-29 8:06 UTC (permalink / raw)
To: bgsmith, BlueZ users; +Cc: Marcel Holtmann, LKML
On Nov 29, 2007 11:03 AM, Brad Smith <bgsmith@bendcable.com> wrote:
>
> Thank you for the reply Marvel. I use the gnome bluetooth client which
Marcel
> 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.
Please dont mind to add lkml as cc.
Regards
dave
> Brad
>
>
>
> On Mon, 2007-11-26 at 06:49 +0100, Marcel Holtmann wrote:
> > Hi Brad,
> >
> > > I have a Logitech mouse and keyboard that use bluetooth (dinovo). I
> > > have enabled bluetooth on this Fedora 8 system and both work well with
> > > two problems.
> > >
> > > (1) When I lock the system and return later the mouse no longer works.
> > > I have to open a terminal window and issue an hidd --connect command.
> > >
> > > (2) When I log out, both the mouse and keyboard stop working. I have to
> > > connect a USB mouse and USB keyboard to enter the authentication
> > > information. Once logged in the bluetooth devices usually work,
> > > although I sometimes have to issue an hidd --connect command to enable
> > > the keyboard.
> > >
> > > Any suggestions on resolving these issues would be appreciated.
> >
> > not using hidd and using bluetoothd-input-service instead is one thing.
> > For input devices to re-connect you have to have a daemon running that
> > handles this. The input service is the best way to achieve this. Check
> > the BlueZ wiki for details.
>
> -------------------------------------------------------------------------
> SF.Net email is sponsored by: The Future of Linux Business White Paper
> from Novell. From the desktop to the data center, Linux is going
> mainstream. Let it simplify your IT future.
> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bluez-users] Lost connections - mouse and keyboard
2007-11-29 8:06 ` Dave Young
@ 2007-11-29 20:19 ` Marcel Holtmann
2007-11-29 20:43 ` Jiri Kosina
0 siblings, 1 reply; 13+ messages in thread
From: Marcel Holtmann @ 2007-11-29 20:19 UTC (permalink / raw)
To: Dave Young; +Cc: bgsmith, BlueZ users, LKML
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
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bluez-users] Lost connections - mouse and keyboard
2007-11-29 20:19 ` Marcel Holtmann
@ 2007-11-29 20:43 ` Jiri Kosina
2007-11-30 1:06 ` Dave Young
0 siblings, 1 reply; 13+ messages in thread
From: Jiri Kosina @ 2007-11-29 20:43 UTC (permalink / raw)
To: Marcel Holtmann; +Cc: Dave Young, bgsmith, BlueZ users, LKML
On Thu, 29 Nov 2007, Marcel Holtmann wrote:
> > >Nov 28 18:53:39 pico kernel: WARNING: at drivers/hid/hid-core.c:784
[ ... ]
> > 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.
Absolutely.
This particular warning means, that someone (usually indeed hid2hci)
passed usage through hiddev that was out of bounds, with respect to the
device's report descriptor.
This usually means that hid2hci has chosen the wrong method to switch the
modes. Unfortunately, it's not easy to implement always the switching
properly, if we don't know the vendor-specific packet that has to be sent.
--
Jiri Kosina
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bluez-users] Lost connections - mouse and keyboard
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
0 siblings, 2 replies; 13+ messages in thread
From: Dave Young @ 2007-11-30 1:06 UTC (permalink / raw)
To: Jiri Kosina; +Cc: Marcel Holtmann, bgsmith, BlueZ users, LKML
On Nov 30, 2007 4:43 AM, Jiri Kosina <jikos@jikos.cz> wrote:
> On Thu, 29 Nov 2007, Marcel Holtmann wrote:
>
> > > >Nov 28 18:53:39 pico kernel: WARNING: at drivers/hid/hid-core.c:784
> [ ... ]
>
> > > 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.
>
> Absolutely.
>
> This particular warning means, that someone (usually indeed hid2hci)
> passed usage through hiddev that was out of bounds, with respect to the
> device's report descriptor.
Is this behaviour the normal one? IMHO, userspace program should not
cause kernel warnings like this no mater what input from users.
>
> This usually means that hid2hci has chosen the wrong method to switch the
> modes. Unfortunately, it's not easy to implement always the switching
> properly, if we don't know the vendor-specific packet that has to be sent.
>
> --
> Jiri Kosina
>
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bluez-users] Lost connections - mouse and keyboard
2007-11-30 1:06 ` Dave Young
@ 2007-11-30 9:15 ` Jiri Kosina
2007-12-07 23:42 ` Didier Link
1 sibling, 0 replies; 13+ messages in thread
From: Jiri Kosina @ 2007-11-30 9:15 UTC (permalink / raw)
To: Dave Young; +Cc: Marcel Holtmann, bgsmith, BlueZ users, LKML
On Fri, 30 Nov 2007, Dave Young wrote:
> > This particular warning means, that someone (usually indeed hid2hci)
> > passed usage through hiddev that was out of bounds, with respect to
> > the device's report descriptor.
> Is this behaviour the normal one? IMHO, userspace program should not
> cause kernel warnings like this no mater what input from users.
It has been on my todo list to convert that WARN_ON() to something that
won't scare users that much, especially the stacktrace shouldn't certainly
be there. I will do it.
--
Jiri Kosina
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bluez-users] Lost connections - mouse and keyboard
2007-11-30 1:06 ` Dave Young
2007-11-30 9:15 ` Jiri Kosina
@ 2007-12-07 23:42 ` Didier Link
2007-12-08 10:25 ` Fabrice Ménard
1 sibling, 1 reply; 13+ messages in thread
From: Didier Link @ 2007-12-07 23:42 UTC (permalink / raw)
To: BlueZ users; +Cc: LKML
[-- Attachment #1: Type: text/plain, Size: 2198 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le Fri, 30 Nov 2007 09:06:52 +0800,
"Dave Young" <hidave.darkstar@gmail.com> a écrit :
> On Nov 30, 2007 4:43 AM, Jiri Kosina <jikos@jikos.cz> wrote:
> > On Thu, 29 Nov 2007, Marcel Holtmann wrote:
> >
Hi all,
Just for add something on this bug report, I've the same hardware
(Logitech dinovo keyboard+mouse), connected with bluetooth
hcid/bluetoothd-service-input
First of all, this work very well at first run and all the time I
interact with keyboard and mouse, very good job of the bluez stack
developpers !
But, like Brad, after an amount of inactivity (about 20 minutes
I think ...) the devices go to sleep mode and never reconnect. I need to
restart the bluetooth service at all, with another usb keyboard. My
kernel log contain the same warnings as Brad each time the service is
restarted.
Some times I've a kernel oops that kill khidp and I never can use
keyboard and mouse, need to reboot the computer ... of course I've
tried to unload the modules concerned but it's impossible.
I attach the lines of this oops for kernel hackers.
My kernel is the last 2.6.23 and I run a Gentoo up to date (bluez-libs
and utils 3.22), on an AMD64 dual core processor with 2GB of ram. The
kernel is tainted by the nvidia proprietary driver, sorry :-/ ...
the result of 'cat /proc/bus/input/devices' for the bt devices is also
attached.
I will try to use the latest patch (2.6.23-mh1) from the bluez download
site tomorrow.
This problem is present since monthes for me but just a service restart
isn't so hard to do ... but the oppsses are so annoying and more
frequent these days !!
Thanks for your attention, I hope you can solve this issue easily and
if you need some more datas and results of tests just ask me !
Best regards.
Didier LINK
- --
Didier Link <didier@famille-link.fr>
Jabber : didier_link@jabber.fr
MSN : zanfib@hotmail.fr
SIP : Zanfib@ekiga.net
Clé GPG : 75BAC9EE
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQFHWdpvkyPwinW6ye4RApiTAJ0XX2jUzT1wAT9se7jQIzHejQ5DPgCfeYF3
YCsIEHHPGM6/NoOxQd7hEQc=
=1D17
-----END PGP SIGNATURE-----
[-- Attachment #2: oops-khidp.txt --]
[-- Type: text/plain, Size: 21501 bytes --]
Dec 7 22:56:28 neutrino kernel: Unable to handle kernel paging request at 0000000000100100 RIP:
Dec 7 22:56:28 neutrino kernel: [<ffffffff8806971f>] :evdev:evdev_disconnect+0x7e/0xb8
Dec 7 22:56:28 neutrino kernel: PGD 7730f067 PUD 77cb5067 PMD 0
Dec 7 22:56:28 neutrino kernel: Oops: 0000 [1] PREEMPT SMP
Dec 7 22:56:28 neutrino kernel: CPU 0
Dec 7 22:56:28 neutrino kernel: Modules linked in: nls_utf8 ntfs nls_iso8859_1 nls_cp437 vfat fat w83627hf hwmon_vid eeprom hci_usb nfsd exportfs lockd nfs_acl auth_rpcgss sunrpc ipv6 aes ieee80211_crypt_ccmp ipt_LOG xt_limit xt_tcpudp xt_state xt_multiport iptable_filter iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nfnetlink ip_tables x_tables snd_seq_midi snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_emul snd_pcm_oss snd_mixer_oss snd_seq_oss snd_seq_midi_event snd_seq uinput ppp_generic slhc rfcomm hidp l2cap bluetooth dm_mod forcedeth af_packet snd_usb_audio snd_usb_lib usblp usbhid hid usb_storage nvidia(P) snd_emu10k1 snd_rawmidi snd_ac97_codec ac97_bus bcm43xx snd_pcm firmware_class snd_seq_device snd_timer snd_page_alloc ieee80211softmac ohci1394 snd_util_mem ieee80211 snd_hwdep 8250_pnp ieee1394 ide_cd cdrom k8temp evdev 8250 hwmon snd sky2 ieee80211_crypt serial_core emu10k1_gp gameport i2c_nforce2 ohci_hcd ehci_hcd soundcore unix
Dec 7 22:56:28 neutrino kernel: Pid: 9281, comm: khidpd_046db003 Tainted: P 2.6.23-gentoo-r3 #1
Dec 7 22:56:28 neutrino kernel: RIP: 0010:[<ffffffff8806971f>] [<ffffffff8806971f>] :evdev:evdev_disconnect+0x7e/0xb8
Dec 7 22:56:28 neutrino kernel: RSP: 0018:ffff81006721fdf0 EFLAGS: 00010216
Dec 7 22:56:28 neutrino kernel: RAX: 0000000000000000 RBX: 00000000000ffae8 RCX: ffff810003012f80
Dec 7 22:56:28 neutrino kernel: RDX: 0000000000000000 RSI: ffff810071031040 RDI: ffff810003012f80
Dec 7 22:56:28 neutrino kernel: RBP: ffff81007ae83c00 R08: ffff81006721e000 R09: ffff810003010f68
Dec 7 22:56:28 neutrino kernel: R10: 0000000000000002 R11: ffffffffffffffff R12: ffff81007ae83c88
Dec 7 22:56:28 neutrino kernel: R13: ffff81007ae83c98 R14: ffff810066cc0400 R15: ffff810071177878
Dec 7 22:56:28 neutrino kernel: FS: 00002b0e6d46e6f0(0000) GS:ffffffff81365000(0000) knlGS:0000000000000000
Dec 7 22:56:28 neutrino kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
Dec 7 22:56:28 neutrino kernel: CR2: 0000000000100100 CR3: 0000000077818000 CR4: 00000000000006e0
Dec 7 22:56:28 neutrino kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Dec 7 22:56:28 neutrino kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Dec 7 22:56:28 neutrino kernel: Process khidpd_046db003 (pid: 9281, threadinfo ffff81006721e000, task ffff810071031040)
Dec 7 22:56:28 neutrino kernel: Stack: ffffffff81122783 ffff81007de5a000 ffff81007de5a910 ffff81007de5a938
Dec 7 22:56:28 neutrino kernel: ffff81006ed4e800 ffffffff811d74a4 ffff81007318f9c0 ffff810074989890
Dec 7 22:56:28 neutrino kernel: ffff810074989890 ffffffff8886a2a3 0000000000000000 ffff8100711777c0
Dec 7 22:56:28 neutrino kernel: Call Trace:
Dec 7 22:56:28 neutrino kernel: [<ffffffff81122783>] kobject_release+0x0/0x9
Dec 7 22:56:28 neutrino kernel: [<ffffffff811d74a4>] input_unregister_device+0x70/0x105
Dec 7 22:56:28 neutrino kernel: [<ffffffff8886a2a3>] :hid:hidinput_disconnect+0x3d/0x56
Dec 7 22:56:28 neutrino kernel: [<ffffffff888dd7ea>] :hidp:hidp_session+0x495/0x573
Dec 7 22:56:28 neutrino kernel: [<ffffffff8102e4a2>] default_wake_function+0x0/0xe
Dec 7 22:56:28 neutrino kernel: [<ffffffff8102e4a2>] default_wake_function+0x0/0xe
Dec 7 22:56:28 neutrino kernel: [<ffffffff8100c5a8>] child_rip+0xa/0x12
Dec 7 22:56:28 neutrino kernel: [<ffffffff888dd355>] :hidp:hidp_session+0x0/0x573
Dec 7 22:56:28 neutrino kernel: [<ffffffff8100c59e>] child_rip+0x0/0x12
Dec 7 22:56:28 neutrino kernel:
Dec 7 22:56:28 neutrino kernel:
Dec 7 22:56:28 neutrino kernel: Code: 48 8b 83 18 06 00 00 0f 18 08 48 8d 83 18 06 00 00 4c 39 e0
Dec 7 22:56:28 neutrino kernel: RIP [<ffffffff8806971f>] :evdev:evdev_disconnect+0x7e/0xb8
Dec 7 22:56:28 neutrino kernel: RSP <ffff81006721fdf0>
Dec 7 22:56:28 neutrino kernel: CR2: 0000000000100100
Dec 7 23:35:49 neutrino kernel: WARNING: at drivers/hid/hid-core.c:784 implement()
Dec 7 23:35:49 neutrino kernel:
Dec 7 23:35:49 neutrino kernel: Call Trace:
Dec 7 23:35:49 neutrino kernel: [<ffffffff888692da>] :hid:hid_output_report+0x1a4/0x215
Dec 7 23:35:49 neutrino kernel: [<ffffffff88871445>] :usbhid:hid_submit_ctrl+0x60/0x1df
Dec 7 23:35:49 neutrino kernel: [<ffffffff8887172e>] :usbhid:usbhid_submit_report+0x16a/0x19d
Dec 7 23:35:49 neutrino kernel: [<ffffffff88873a38>] :usbhid:hiddev_ioctl+0x34d/0x8f5
Dec 7 23:35:49 neutrino kernel: [<ffffffff81124ca8>] __up_read+0x13/0x8a
Dec 7 23:35:49 neutrino kernel: [<ffffffff810227d7>] do_page_fault+0x3e0/0x735
Dec 7 23:35:49 neutrino kernel: [<ffffffff8107bcdd>] chrdev_open+0x0/0x1bf
Dec 7 23:35:49 neutrino kernel: [<ffffffff81084d6d>] do_ioctl+0x55/0x6b
Dec 7 23:35:49 neutrino kernel: [<ffffffff81084fb6>] vfs_ioctl+0x233/0x24c
Dec 7 23:35:49 neutrino kernel: [<ffffffff81085028>] sys_ioctl+0x59/0x79
Dec 7 23:35:49 neutrino kernel: [<ffffffff8100b75e>] system_call+0x7e/0x83
Dec 7 23:35:49 neutrino kernel:
Dec 7 23:35:49 neutrino kernel: WARNING: at drivers/hid/hid-core.c:784 implement()
Dec 7 23:35:49 neutrino kernel:
Dec 7 23:35:49 neutrino kernel: Call Trace:
Dec 7 23:35:49 neutrino kernel: [<ffffffff888692da>] :hid:hid_output_report+0x1a4/0x215
Dec 7 23:35:49 neutrino kernel: [<ffffffff88871445>] :usbhid:hid_submit_ctrl+0x60/0x1df
Dec 7 23:35:49 neutrino kernel: [<ffffffff8887172e>] :usbhid:usbhid_submit_report+0x16a/0x19d
Dec 7 23:35:49 neutrino kernel: [<ffffffff88873a38>] :usbhid:hiddev_ioctl+0x34d/0x8f5
Dec 7 23:35:49 neutrino kernel: [<ffffffff81124ca8>] __up_read+0x13/0x8a
Dec 7 23:35:49 neutrino kernel: [<ffffffff810227d7>] do_page_fault+0x3e0/0x735
Dec 7 23:35:49 neutrino kernel: [<ffffffff8107bcdd>] chrdev_open+0x0/0x1bf
Dec 7 23:35:49 neutrino kernel: [<ffffffff81084d6d>] do_ioctl+0x55/0x6b
Dec 7 23:35:49 neutrino kernel: [<ffffffff81084fb6>] vfs_ioctl+0x233/0x24c
Dec 7 23:35:49 neutrino kernel: [<ffffffff81085028>] sys_ioctl+0x59/0x79
Dec 7 23:35:49 neutrino kernel: [<ffffffff8100b75e>] system_call+0x7e/0x83
Dec 7 23:35:49 neutrino kernel:
Dec 7 23:35:49 neutrino kernel: WARNING: at drivers/hid/hid-core.c:784 implement()
Dec 7 23:35:49 neutrino kernel:
Dec 7 23:35:49 neutrino kernel: Call Trace:
Dec 7 23:35:49 neutrino kernel: [<ffffffff888692da>] :hid:hid_output_report+0x1a4/0x215
Dec 7 23:35:49 neutrino kernel: [<ffffffff88871445>] :usbhid:hid_submit_ctrl+0x60/0x1df
Dec 7 23:35:49 neutrino kernel: [<ffffffff8887172e>] :usbhid:usbhid_submit_report+0x16a/0x19d
Dec 7 23:35:49 neutrino kernel: [<ffffffff88873a38>] :usbhid:hiddev_ioctl+0x34d/0x8f5
Dec 7 23:35:49 neutrino kernel: [<ffffffff81124ca8>] __up_read+0x13/0x8a
Dec 7 23:35:49 neutrino kernel: [<ffffffff810227d7>] do_page_fault+0x3e0/0x735
Dec 7 23:35:49 neutrino kernel: [<ffffffff8107bcdd>] chrdev_open+0x0/0x1bf
Dec 7 23:35:49 neutrino kernel: [<ffffffff81084d6d>] do_ioctl+0x55/0x6b
Dec 7 23:35:49 neutrino kernel: [<ffffffff81084fb6>] vfs_ioctl+0x233/0x24c
Dec 7 23:35:49 neutrino kernel: [<ffffffff81085028>] sys_ioctl+0x59/0x79
Dec 7 23:35:49 neutrino kernel: [<ffffffff8100b75e>] system_call+0x7e/0x83
Dec 7 23:35:49 neutrino kernel:
Dec 7 23:35:49 neutrino kernel: WARNING: at drivers/hid/hid-core.c:784 implement()
Dec 7 23:35:49 neutrino kernel:
Dec 7 23:35:49 neutrino kernel: Call Trace:
Dec 7 23:35:49 neutrino kernel: [<ffffffff888692da>] :hid:hid_output_report+0x1a4/0x215
Dec 7 23:35:49 neutrino kernel: [<ffffffff88871445>] :usbhid:hid_submit_ctrl+0x60/0x1df
Dec 7 23:35:49 neutrino kernel: [<ffffffff8887172e>] :usbhid:usbhid_submit_report+0x16a/0x19d
Dec 7 23:35:49 neutrino kernel: [<ffffffff88873a38>] :usbhid:hiddev_ioctl+0x34d/0x8f5
Dec 7 23:35:49 neutrino kernel: [<ffffffff81124ca8>] __up_read+0x13/0x8a
Dec 7 23:35:49 neutrino kernel: [<ffffffff810227d7>] do_page_fault+0x3e0/0x735
Dec 7 23:35:49 neutrino kernel: [<ffffffff8107bcdd>] chrdev_open+0x0/0x1bf
Dec 7 23:35:49 neutrino kernel: [<ffffffff81084d6d>] do_ioctl+0x55/0x6b
Dec 7 23:35:49 neutrino kernel: [<ffffffff81084fb6>] vfs_ioctl+0x233/0x24c
Dec 7 23:35:49 neutrino kernel: [<ffffffff81085028>] sys_ioctl+0x59/0x79
Dec 7 23:35:49 neutrino kernel: [<ffffffff8100b75e>] system_call+0x7e/0x83
Dec 7 23:35:49 neutrino kernel:
Dec 7 23:35:49 neutrino kernel: WARNING: at drivers/hid/hid-core.c:784 implement()
Dec 7 23:35:49 neutrino kernel:
Dec 7 23:35:49 neutrino kernel: Call Trace:
Dec 7 23:35:49 neutrino kernel: [<ffffffff888692da>] :hid:hid_output_report+0x1a4/0x215
Dec 7 23:35:49 neutrino kernel: [<ffffffff88871445>] :usbhid:hid_submit_ctrl+0x60/0x1df
Dec 7 23:35:49 neutrino kernel: [<ffffffff8887172e>] :usbhid:usbhid_submit_report+0x16a/0x19d
Dec 7 23:35:49 neutrino kernel: [<ffffffff88873a38>] :usbhid:hiddev_ioctl+0x34d/0x8f5
Dec 7 23:35:49 neutrino kernel: [<ffffffff81124ca8>] __up_read+0x13/0x8a
Dec 7 23:35:49 neutrino kernel: [<ffffffff810227d7>] do_page_fault+0x3e0/0x735
Dec 7 23:35:49 neutrino kernel: [<ffffffff8107bcdd>] chrdev_open+0x0/0x1bf
Dec 7 23:35:49 neutrino kernel: [<ffffffff81084d6d>] do_ioctl+0x55/0x6b
Dec 7 23:35:49 neutrino kernel: [<ffffffff81084fb6>] vfs_ioctl+0x233/0x24c
Dec 7 23:35:49 neutrino kernel: [<ffffffff81085028>] sys_ioctl+0x59/0x79
Dec 7 23:35:49 neutrino kernel: [<ffffffff8100b75e>] system_call+0x7e/0x83
Dec 7 23:35:49 neutrino kernel:
Dec 7 23:35:49 neutrino kernel: WARNING: at drivers/hid/hid-core.c:784 implement()
Dec 7 23:35:49 neutrino kernel:
Dec 7 23:35:49 neutrino kernel: Call Trace:
Dec 7 23:35:49 neutrino kernel: [<ffffffff888692da>] :hid:hid_output_report+0x1a4/0x215
Dec 7 23:35:49 neutrino kernel: [<ffffffff88871445>] :usbhid:hid_submit_ctrl+0x60/0x1df
Dec 7 23:35:49 neutrino kernel: [<ffffffff8887172e>] :usbhid:usbhid_submit_report+0x16a/0x19d
Dec 7 23:35:49 neutrino kernel: [<ffffffff88873a38>] :usbhid:hiddev_ioctl+0x34d/0x8f5
Dec 7 23:35:49 neutrino kernel: [<ffffffff81124ca8>] __up_read+0x13/0x8a
Dec 7 23:35:49 neutrino kernel: [<ffffffff810227d7>] do_page_fault+0x3e0/0x735
Dec 7 23:35:49 neutrino kernel: [<ffffffff8107bcdd>] chrdev_open+0x0/0x1bf
Dec 7 23:35:49 neutrino kernel: [<ffffffff81084d6d>] do_ioctl+0x55/0x6b
Dec 7 23:35:49 neutrino kernel: [<ffffffff81084fb6>] vfs_ioctl+0x233/0x24c
Dec 7 23:35:49 neutrino kernel: [<ffffffff81085028>] sys_ioctl+0x59/0x79
Dec 7 23:35:49 neutrino kernel: [<ffffffff8100b75e>] system_call+0x7e/0x83
Dec 7 23:35:49 neutrino kernel:
Dec 7 23:35:49 neutrino kernel: WARNING: at drivers/hid/hid-core.c:784 implement()
Dec 7 23:35:49 neutrino kernel:
Dec 7 23:35:49 neutrino kernel: Call Trace:
Dec 7 23:35:49 neutrino kernel: [<ffffffff888692da>] :hid:hid_output_report+0x1a4/0x215
Dec 7 23:35:49 neutrino kernel: [<ffffffff88871445>] :usbhid:hid_submit_ctrl+0x60/0x1df
Dec 7 23:35:49 neutrino kernel: [<ffffffff8887172e>] :usbhid:usbhid_submit_report+0x16a/0x19d
Dec 7 23:35:49 neutrino kernel: [<ffffffff88873a38>] :usbhid:hiddev_ioctl+0x34d/0x8f5
Dec 7 23:35:49 neutrino kernel: [<ffffffff81124ca8>] __up_read+0x13/0x8a
Dec 7 23:35:49 neutrino kernel: [<ffffffff810227d7>] do_page_fault+0x3e0/0x735
Dec 7 23:35:49 neutrino kernel: [<ffffffff8107bcdd>] chrdev_open+0x0/0x1bf
Dec 7 23:35:49 neutrino kernel: [<ffffffff81084d6d>] do_ioctl+0x55/0x6b
Dec 7 23:35:49 neutrino kernel: [<ffffffff81084fb6>] vfs_ioctl+0x233/0x24c
Dec 7 23:35:49 neutrino kernel: [<ffffffff81085028>] sys_ioctl+0x59/0x79
Dec 7 23:35:49 neutrino kernel: [<ffffffff8100b75e>] system_call+0x7e/0x83
Dec 7 23:35:49 neutrino kernel:
Dec 7 23:35:49 neutrino kernel: WARNING: at drivers/hid/hid-core.c:784 implement()
Dec 7 23:35:49 neutrino kernel:
Dec 7 23:35:49 neutrino kernel: Call Trace:
Dec 7 23:35:49 neutrino kernel: [<ffffffff888692da>] :hid:hid_output_report+0x1a4/0x215
Dec 7 23:35:49 neutrino kernel: [<ffffffff88871445>] :usbhid:hid_submit_ctrl+0x60/0x1df
Dec 7 23:35:49 neutrino kernel: [<ffffffff8887172e>] :usbhid:usbhid_submit_report+0x16a/0x19d
Dec 7 23:35:49 neutrino kernel: [<ffffffff88873a38>] :usbhid:hiddev_ioctl+0x34d/0x8f5
Dec 7 23:35:49 neutrino kernel: [<ffffffff81124ca8>] __up_read+0x13/0x8a
Dec 7 23:35:49 neutrino kernel: [<ffffffff810227d7>] do_page_fault+0x3e0/0x735
Dec 7 23:35:49 neutrino kernel: [<ffffffff8107bcdd>] chrdev_open+0x0/0x1bf
Dec 7 23:35:49 neutrino kernel: [<ffffffff81084d6d>] do_ioctl+0x55/0x6b
Dec 7 23:35:49 neutrino kernel: [<ffffffff81084fb6>] vfs_ioctl+0x233/0x24c
Dec 7 23:35:49 neutrino kernel: [<ffffffff81085028>] sys_ioctl+0x59/0x79
Dec 7 23:35:49 neutrino kernel: [<ffffffff8100b75e>] system_call+0x7e/0x83
Dec 7 23:35:49 neutrino kernel:
Dec 7 23:36:25 neutrino kernel: WARNING: at drivers/hid/hid-core.c:784 implement()
Dec 7 23:36:25 neutrino kernel:
Dec 7 23:36:25 neutrino kernel: Call Trace:
Dec 7 23:36:25 neutrino kernel: [<ffffffff888692da>] :hid:hid_output_report+0x1a4/0x215
Dec 7 23:36:25 neutrino kernel: [<ffffffff88871445>] :usbhid:hid_submit_ctrl+0x60/0x1df
Dec 7 23:36:25 neutrino kernel: [<ffffffff8887172e>] :usbhid:usbhid_submit_report+0x16a/0x19d
Dec 7 23:36:25 neutrino kernel: [<ffffffff88873a38>] :usbhid:hiddev_ioctl+0x34d/0x8f5
Dec 7 23:36:25 neutrino kernel: [<ffffffff812543cd>] preempt_schedule+0x4f/0x7f
Dec 7 23:36:25 neutrino kernel: [<ffffffff81255e64>] __up_wakeup+0x35/0x67
Dec 7 23:36:25 neutrino kernel: [<ffffffff81084d6d>] do_ioctl+0x55/0x6b
Dec 7 23:36:25 neutrino kernel: [<ffffffff81084fb6>] vfs_ioctl+0x233/0x24c
Dec 7 23:36:25 neutrino kernel: [<ffffffff81085028>] sys_ioctl+0x59/0x79
Dec 7 23:36:25 neutrino kernel: [<ffffffff8100b75e>] system_call+0x7e/0x83
Dec 7 23:36:25 neutrino kernel:
Dec 7 23:36:25 neutrino kernel: WARNING: at drivers/hid/hid-core.c:784 implement()
Dec 7 23:36:25 neutrino kernel:
Dec 7 23:36:25 neutrino kernel: Call Trace:
Dec 7 23:36:25 neutrino kernel: [<ffffffff888692da>] :hid:hid_output_report+0x1a4/0x215
Dec 7 23:36:25 neutrino kernel: [<ffffffff88871445>] :usbhid:hid_submit_ctrl+0x60/0x1df
Dec 7 23:36:25 neutrino kernel: [<ffffffff8887172e>] :usbhid:usbhid_submit_report+0x16a/0x19d
Dec 7 23:36:25 neutrino kernel: [<ffffffff88873a38>] :usbhid:hiddev_ioctl+0x34d/0x8f5
Dec 7 23:36:25 neutrino kernel: [<ffffffff812543cd>] preempt_schedule+0x4f/0x7f
Dec 7 23:36:25 neutrino kernel: [<ffffffff81255e64>] __up_wakeup+0x35/0x67
Dec 7 23:36:25 neutrino kernel: [<ffffffff81084d6d>] do_ioctl+0x55/0x6b
Dec 7 23:36:25 neutrino kernel: [<ffffffff81084fb6>] vfs_ioctl+0x233/0x24c
Dec 7 23:36:25 neutrino kernel: [<ffffffff81085028>] sys_ioctl+0x59/0x79
Dec 7 23:36:25 neutrino kernel: [<ffffffff8100b75e>] system_call+0x7e/0x83
Dec 7 23:36:25 neutrino kernel:
Dec 7 23:36:25 neutrino kernel: WARNING: at drivers/hid/hid-core.c:784 implement()
Dec 7 23:36:25 neutrino kernel:
Dec 7 23:36:25 neutrino kernel: Call Trace:
Dec 7 23:36:25 neutrino kernel: [<ffffffff888692da>] :hid:hid_output_report+0x1a4/0x215
Dec 7 23:36:25 neutrino kernel: [<ffffffff88871445>] :usbhid:hid_submit_ctrl+0x60/0x1df
Dec 7 23:36:25 neutrino kernel: [<ffffffff8887172e>] :usbhid:usbhid_submit_report+0x16a/0x19d
Dec 7 23:36:25 neutrino kernel: [<ffffffff88873a38>] :usbhid:hiddev_ioctl+0x34d/0x8f5
Dec 7 23:36:25 neutrino kernel: [<ffffffff812543cd>] preempt_schedule+0x4f/0x7f
Dec 7 23:36:25 neutrino kernel: [<ffffffff81255e64>] __up_wakeup+0x35/0x67
Dec 7 23:36:25 neutrino kernel: [<ffffffff81084d6d>] do_ioctl+0x55/0x6b
Dec 7 23:36:25 neutrino kernel: [<ffffffff81084fb6>] vfs_ioctl+0x233/0x24c
Dec 7 23:36:25 neutrino kernel: [<ffffffff81085028>] sys_ioctl+0x59/0x79
Dec 7 23:36:25 neutrino kernel: [<ffffffff8100b75e>] system_call+0x7e/0x83
Dec 7 23:36:25 neutrino kernel:
Dec 7 23:36:25 neutrino kernel: WARNING: at drivers/hid/hid-core.c:784 implement()
Dec 7 23:36:25 neutrino kernel:
Dec 7 23:36:25 neutrino kernel: Call Trace:
Dec 7 23:36:25 neutrino kernel: [<ffffffff888692da>] :hid:hid_output_report+0x1a4/0x215
Dec 7 23:36:25 neutrino kernel: [<ffffffff88871445>] :usbhid:hid_submit_ctrl+0x60/0x1df
Dec 7 23:36:25 neutrino kernel: [<ffffffff8887172e>] :usbhid:usbhid_submit_report+0x16a/0x19d
Dec 7 23:36:25 neutrino kernel: [<ffffffff88873a38>] :usbhid:hiddev_ioctl+0x34d/0x8f5
Dec 7 23:36:25 neutrino kernel: [<ffffffff812543cd>] preempt_schedule+0x4f/0x7f
Dec 7 23:36:25 neutrino kernel: [<ffffffff81255e64>] __up_wakeup+0x35/0x67
Dec 7 23:36:25 neutrino kernel: [<ffffffff81084d6d>] do_ioctl+0x55/0x6b
Dec 7 23:36:25 neutrino kernel: [<ffffffff81084fb6>] vfs_ioctl+0x233/0x24c
Dec 7 23:36:25 neutrino kernel: [<ffffffff81085028>] sys_ioctl+0x59/0x79
Dec 7 23:36:25 neutrino kernel: [<ffffffff8100b75e>] system_call+0x7e/0x83
Dec 7 23:36:25 neutrino kernel:
Dec 7 23:36:25 neutrino kernel: WARNING: at drivers/hid/hid-core.c:784 implement()
Dec 7 23:36:25 neutrino kernel:
Dec 7 23:36:25 neutrino kernel: Call Trace:
Dec 7 23:36:25 neutrino kernel: [<ffffffff888692da>] :hid:hid_output_report+0x1a4/0x215
Dec 7 23:36:25 neutrino kernel: [<ffffffff88871445>] :usbhid:hid_submit_ctrl+0x60/0x1df
Dec 7 23:36:25 neutrino kernel: [<ffffffff8887172e>] :usbhid:usbhid_submit_report+0x16a/0x19d
Dec 7 23:36:25 neutrino kernel: [<ffffffff88873a38>] :usbhid:hiddev_ioctl+0x34d/0x8f5
Dec 7 23:36:25 neutrino kernel: [<ffffffff812543cd>] preempt_schedule+0x4f/0x7f
Dec 7 23:36:25 neutrino kernel: [<ffffffff81255e64>] __up_wakeup+0x35/0x67
Dec 7 23:36:25 neutrino kernel: [<ffffffff81084d6d>] do_ioctl+0x55/0x6b
Dec 7 23:36:25 neutrino kernel: [<ffffffff81084fb6>] vfs_ioctl+0x233/0x24c
Dec 7 23:36:25 neutrino kernel: [<ffffffff81085028>] sys_ioctl+0x59/0x79
Dec 7 23:36:25 neutrino kernel: [<ffffffff8100b75e>] system_call+0x7e/0x83
Dec 7 23:36:25 neutrino kernel:
Dec 7 23:36:25 neutrino kernel: WARNING: at drivers/hid/hid-core.c:784 implement()
Dec 7 23:36:25 neutrino kernel:
Dec 7 23:36:25 neutrino kernel: Call Trace:
Dec 7 23:36:25 neutrino kernel: [<ffffffff888692da>] :hid:hid_output_report+0x1a4/0x215
Dec 7 23:36:25 neutrino kernel: [<ffffffff88871445>] :usbhid:hid_submit_ctrl+0x60/0x1df
Dec 7 23:36:25 neutrino kernel: [<ffffffff8887172e>] :usbhid:usbhid_submit_report+0x16a/0x19d
Dec 7 23:36:25 neutrino kernel: [<ffffffff88873a38>] :usbhid:hiddev_ioctl+0x34d/0x8f5
Dec 7 23:36:25 neutrino kernel: [<ffffffff81256118>] __down+0xbf/0x101
Dec 7 23:36:25 neutrino kernel: [<ffffffff8102e4a2>] default_wake_function+0x0/0xe
Dec 7 23:36:25 neutrino kernel: [<ffffffff81255db6>] __down_failed+0x35/0x3a
Dec 7 23:36:25 neutrino kernel: [<ffffffff81084d6d>] do_ioctl+0x55/0x6b
Dec 7 23:36:25 neutrino kernel: [<ffffffff81084fb6>] vfs_ioctl+0x233/0x24c
Dec 7 23:36:25 neutrino kernel: [<ffffffff81085028>] sys_ioctl+0x59/0x79
Dec 7 23:36:25 neutrino kernel: [<ffffffff8100b75e>] system_call+0x7e/0x83
Dec 7 23:36:25 neutrino kernel:
Dec 7 23:36:25 neutrino kernel: WARNING: at drivers/hid/hid-core.c:784 implement()
Dec 7 23:36:25 neutrino kernel:
Dec 7 23:36:25 neutrino kernel: Call Trace:
Dec 7 23:36:25 neutrino kernel: [<ffffffff888692da>] :hid:hid_output_report+0x1a4/0x215
Dec 7 23:36:25 neutrino kernel: [<ffffffff88871445>] :usbhid:hid_submit_ctrl+0x60/0x1df
Dec 7 23:36:25 neutrino kernel: [<ffffffff8887172e>] :usbhid:usbhid_submit_report+0x16a/0x19d
Dec 7 23:36:25 neutrino kernel: [<ffffffff88873a38>] :usbhid:hiddev_ioctl+0x34d/0x8f5
Dec 7 23:36:25 neutrino kernel: [<ffffffff81256118>] __down+0xbf/0x101
Dec 7 23:36:25 neutrino kernel: [<ffffffff8102e4a2>] default_wake_function+0x0/0xe
Dec 7 23:36:25 neutrino kernel: [<ffffffff81255db6>] __down_failed+0x35/0x3a
Dec 7 23:36:25 neutrino kernel: [<ffffffff81084d6d>] do_ioctl+0x55/0x6b
Dec 7 23:36:25 neutrino kernel: [<ffffffff81084fb6>] vfs_ioctl+0x233/0x24c
Dec 7 23:36:25 neutrino kernel: [<ffffffff81085028>] sys_ioctl+0x59/0x79
Dec 7 23:36:25 neutrino kernel: [<ffffffff8100b75e>] system_call+0x7e/0x83
Dec 7 23:36:25 neutrino kernel:
Dec 7 23:36:25 neutrino kernel: WARNING: at drivers/hid/hid-core.c:784 implement()
Dec 7 23:36:25 neutrino kernel:
Dec 7 23:36:25 neutrino kernel: Call Trace:
Dec 7 23:36:25 neutrino kernel: [<ffffffff888692da>] :hid:hid_output_report+0x1a4/0x215
Dec 7 23:36:25 neutrino kernel: [<ffffffff88871445>] :usbhid:hid_submit_ctrl+0x60/0x1df
Dec 7 23:36:25 neutrino kernel: [<ffffffff8887172e>] :usbhid:usbhid_submit_report+0x16a/0x19d
Dec 7 23:36:25 neutrino kernel: [<ffffffff88873a38>] :usbhid:hiddev_ioctl+0x34d/0x8f5
Dec 7 23:36:25 neutrino kernel: [<ffffffff81256118>] __down+0xbf/0x101
Dec 7 23:36:25 neutrino kernel: [<ffffffff8102e4a2>] default_wake_function+0x0/0xe
Dec 7 23:36:25 neutrino kernel: [<ffffffff81255db6>] __down_failed+0x35/0x3a
Dec 7 23:36:25 neutrino kernel: [<ffffffff81084d6d>] do_ioctl+0x55/0x6b
Dec 7 23:36:25 neutrino kernel: [<ffffffff81084fb6>] vfs_ioctl+0x233/0x24c
Dec 7 23:36:25 neutrino kernel: [<ffffffff81085028>] sys_ioctl+0x59/0x79
Dec 7 23:36:25 neutrino kernel: [<ffffffff8100b75e>] system_call+0x7e/0x83
Dec 7 23:36:25 neutrino kernel:
[-- Attachment #3: input-devices-bt.txt --]
[-- Type: text/plain, Size: 1500 bytes --]
I: Bus=0003 Vendor=046d Product=c70b Version=0111
N: Name="Logitech Logitech BT Mini-Receiver"
P: Phys=usb-0000:00:02.0-8.2/input0
S: Sysfs=/devices/pci0000:00/0000:00:02.0/usb1/1-8/1-8.2/1-8.2:1.0/input/input3
U: Uniq=00076145BEDD
H: Handlers=kbd event3
B: EV=120003
B: KEY=1000000000007 ff800000000007ff febeffdfffefffff fffffffffffffffe
B: LED=1f
I: Bus=0003 Vendor=046d Product=c70c Version=0111
N: Name="Logitech Logitech BT Mini-Receiver"
P: Phys=usb-0000:00:02.0-8.3/input0
S: Sysfs=/devices/pci0000:00/0000:00:02.0/usb1/1-8/1-8.3/1-8.3:1.0/input/input4
U: Uniq=00076145BEDD
H: Handlers=kbd mouse0 event4
B: EV=f
B: KEY=7fff00ac3027 bf00444400000000 fff0001 f808a37c000 667bfad941dfed 9e000000000000 0
B: REL=1c3
B: ABS=100000000
I: Bus=0005 Vendor=046d Product=b307 Version=2307
N: Name="Logitech diNovo Keyboard"
P: Phys=00:07:61:45:BE:DD
S: Sysfs=/devices/pci0000:00/0000:00:02.0/usb1/1-8/1-8.1/1-8.1:1.0/hci0/acl0007613FB98C/input/input5
U: Uniq=00:07:61:3F:B9:8C
H: Handlers=kbd event5
B: EV=10000f
B: KEY=7fff00ac3027 bf00444400000000 1 10f808a37c007 ffe67bfad941dfff febeffdfffefffff fffffffffffffffe
B: REL=40
B: ABS=30100000000
I: Bus=0005 Vendor=046d Product=b003 Version=4310
N: Name="Logitech MX1000 mouse"
P: Phys=00:07:61:45:BE:DD
S: Sysfs=/devices/pci0000:00/0000:00:02.0/usb1/1-8/1-8.1/1-8.1:1.0/hci0/acl0007613E1CB1/input/input6
U: Uniq=00:07:61:3E:1C:B1
H: Handlers=mouse1 event6
B: EV=7
B: KEY=ffff0000 0 0 0 0
B: REL=143
[-- Attachment #4: Type: text/plain, Size: 277 bytes --]
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
[-- Attachment #5: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bluez-users] Lost connections - mouse and keyboard
2007-12-07 23:42 ` Didier Link
@ 2007-12-08 10:25 ` Fabrice Ménard
2007-12-08 12:57 ` Didier Link
0 siblings, 1 reply; 13+ messages in thread
From: Fabrice Ménard @ 2007-12-08 10:25 UTC (permalink / raw)
To: BlueZ users
On Saturday 08 December 2007 00:42:39 Didier Link wrote:
> Hi all,
>
> Just for add something on this bug report, I've the same hardware
> (Logitech dinovo keyboard+mouse), connected with bluetooth
> hcid/bluetoothd-service-input
>
> First of all, this work very well at first run and all the time I
> interact with keyboard and mouse, very good job of the bluez stack
> developpers !
>
> But, like Brad, after an amount of inactivity (about 20 minutes
> I think ...) the devices go to sleep mode and never reconnect. I need to
> restart the bluetooth service at all, with another usb keyboard. My
> kernel log contain the same warnings as Brad each time the service is
> restarted.
I had a similar problem, see my post for a possible solution (it works for =
me):
http://article.gmane.org/gmane.linux.bluez.user/12988/match=3Ddinovo
Regards,
Fabrice M=E9nard
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bluez-users] Lost connections - mouse and keyboard
2007-12-08 10:25 ` Fabrice Ménard
@ 2007-12-08 12:57 ` Didier Link
2007-12-09 16:45 ` Fabrice Ménard
0 siblings, 1 reply; 13+ messages in thread
From: Didier Link @ 2007-12-08 12:57 UTC (permalink / raw)
To: BlueZ users
LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBMQ0KDQpMZSBTYXQs
IDggRGVjIDIwMDcgMTE6MjU6MDMgKzAxMDAsDQpGYWJyaWNlIE3DqW5hcmQgPG1lbmFyZC5mYWJy
aWNlQG9yYW5nZS5mcj4gYSDDqWNyaXQgOg0KDQo+IE9uIFNhdHVyZGF5IDA4IERlY2VtYmVyIDIw
MDcgMDA6NDI6MzkgRGlkaWVyIExpbmsgd3JvdGU6DQo+ID4gSGkgYWxsLA0KPiA+DQo+ID4gSnVz
dCBmb3IgYWRkIHNvbWV0aGluZyBvbiB0aGlzIGJ1ZyByZXBvcnQsIEkndmUgdGhlIHNhbWUgaGFy
ZHdhcmUNCj4gPiAoTG9naXRlY2ggZGlub3ZvIGtleWJvYXJkK21vdXNlKSwgY29ubmVjdGVkIHdp
dGggYmx1ZXRvb3RoDQo+ID4gaGNpZC9ibHVldG9vdGhkLXNlcnZpY2UtaW5wdXQNCj4gPg0KPiA+
IEZpcnN0IG9mIGFsbCwgdGhpcyB3b3JrIHZlcnkgd2VsbCBhdCBmaXJzdCBydW4gYW5kIGFsbCB0
aGUgdGltZSBJDQo+ID4gaW50ZXJhY3Qgd2l0aCBrZXlib2FyZCBhbmQgbW91c2UsIHZlcnkgZ29v
ZCBqb2Igb2YgdGhlIGJsdWV6IHN0YWNrDQo+ID4gZGV2ZWxvcHBlcnMgIQ0KPiA+DQo+ID4gQnV0
LCBsaWtlIEJyYWQsIGFmdGVyIGFuIGFtb3VudCBvZiBpbmFjdGl2aXR5IChhYm91dCAyMCBtaW51
dGVzDQo+ID4gSSB0aGluayAuLi4pIHRoZSBkZXZpY2VzIGdvIHRvIHNsZWVwIG1vZGUgYW5kIG5l
dmVyIHJlY29ubmVjdC4gSQ0KPiA+IG5lZWQgdG8gcmVzdGFydCB0aGUgYmx1ZXRvb3RoIHNlcnZp
Y2UgYXQgYWxsLCB3aXRoIGFub3RoZXIgdXNiDQo+ID4ga2V5Ym9hcmQuIE15IGtlcm5lbCBsb2cg
Y29udGFpbiB0aGUgc2FtZSB3YXJuaW5ncyBhcyBCcmFkIGVhY2ggdGltZQ0KPiA+IHRoZSBzZXJ2
aWNlIGlzIHJlc3RhcnRlZC4NCg0KSGkgRmFicmljZSwNCg0KPiANCj4gSSBoYWQgYSBzaW1pbGFy
IHByb2JsZW0sIHNlZSBteSBwb3N0IGZvciBhIHBvc3NpYmxlIHNvbHV0aW9uIChpdA0KPiB3b3Jr
cyBmb3IgbWUpOg0KPiBodHRwOi8vYXJ0aWNsZS5nbWFuZS5vcmcvZ21hbmUubGludXguYmx1ZXou
dXNlci8xMjk4OC9tYXRjaD1kaW5vdm8NCg0KVGhhbmtzIGZvciB0aGlzIGxpbmssIEkndmUgbWlz
c2VkIHlvdXIgbWVzc2FnZSBhbmQgSSdtIG5vdCBhbG9uZQ0KYmVjYXVzZSBub2JvZHkgZnJvbSBi
bHVleiBkZXZlbG9wZXJzIGhhdmUgY29tbWVudGVkIHlvdSBwb3N0IC4uLiA6KA0KDQpJIGtub3cg
Ymx1ZXogaXMgYSBsb3Qgb2Ygd29yayBmb3IgTWFyY2VsIGFuZCBvdGhlcnMgYnV0IEkgdGhpbmsg
dGhpcw0KaXNzdWUgaXMgaW1wb3J0YW50IGZvciBhbGwgZGlub3ZvIHVzZXJzLCBhbmQgbWF5YmUg
b3RoZXJzIGtleWJvYXJkIHNldA0KZnJvbSBMb2dpdGVjaCA/DQoNCkFzIERhdmUgWW91bmcgcG9p
bnRlZCBiZWZvcmUsIEkgdGhpbmsgdGhpcyB3YXJuaW5nIChhbmQgdGhlIG9vcHNlIEkNCnBvc3Rl
ZCkgbmVlZCB0byBiZSBmaXhlZCBmb3IgaW1wcm92ZSBrZXJuZWwgc3RhYmlsaXR5Lg0KDQpGaW5h
bGx5LCBGYWJyaWNlLCB5b3VyIHBhdGNoZXMgYXJlbid0IGFjY2Vzc2libGUgd2l0aCB0aGUgc291
cmNlZm9yZ2UNCmFuZCBnbWFuZSBhcmNoaXZlcyBvZiB0aGUgbGlzdCwgY2FuIHlvdSByZXNlbmQg
b3IgcHV0IGl0IG9uIHBhc3RlYmluIG9yDQpvdGhlciB3ZWIgbG9jYXRpb24gcGxlYXNlID8/DQoN
ClRoYW5rcyBhIGxvdCBmb3IgdGhlIGdvb2Qgd29yayBhbmQgYmVzdCByZWdhcmRzLg0KDQpEaWRp
ZXIgTGluaw0KDQpwczogdGhlIGxhc3QgLW1oMSBwYXRjaCBmb3Iga2VybmVsIDIuNi4yMyBkb2Vz
bid0IHNvbHZlIHRoZQ0Kc2xlZXAvcmVjb25uZWN0IGlzc3VlLg0KDQotIC0tIA0KRGlkaWVyIExp
bmsgPGRpZGllckBmYW1pbGxlLWxpbmsuZnI+DQpKYWJiZXIgOiBkaWRpZXJfbGlua0BqYWJiZXIu
ZnINCk1TTiA6IHphbmZpYkBob3RtYWlsLmZyDQpTSVAgOiBaYW5maWJAZWtpZ2EubmV0DQoNCkNs
w6kgR1BHIDogNzVCQUM5RUUNCi0tLS0tQkVHSU4gUEdQIFNJR05BVFVSRS0tLS0tDQpWZXJzaW9u
OiBHbnVQRyB2MS40LjcgKEdOVS9MaW51eCkNCg0KaUQ4REJRRkhXcFRIa3lQd2luVzZ5ZTRSQXBX
a0FKOUtORWdDdFJCUU1uTHpSZkRRRUtQRG1Jbk5MQUNmYlBkMQ0KQUdpcUdxZVZVNzRseHhCdHNV
VXFSOFU9DQo9V0hOWQ0KLS0tLS1FTkQgUEdQIFNJR05BVFVSRS0tLS0tDQotLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tClNGLk5ldCBlbWFpbCBpcyBzcG9uc29yZWQgYnk6CkNoZWNrIG91dCB0aGUgbmV3IFNvdXJj
ZUZvcmdlLm5ldCBNYXJrZXRwbGFjZS4KSXQncyB0aGUgYmVzdCBwbGFjZSB0byBidXkgb3Igc2Vs
bCBzZXJ2aWNlcyBmb3IKanVzdCBhYm91dCBhbnl0aGluZyBPcGVuIFNvdXJjZS4KaHR0cDovL3Nv
dXJjZWZvcmdlLm5ldC9zZXJ2aWNlcy9idXkvaW5kZXgucGhwCl9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fCkJsdWV6LXVzZXJzIG1haWxpbmcgbGlzdApCbHVl
ei11c2Vyc0BsaXN0cy5zb3VyY2Vmb3JnZS5uZXQKaHR0cHM6Ly9saXN0cy5zb3VyY2Vmb3JnZS5u
ZXQvbGlzdHMvbGlzdGluZm8vYmx1ZXotdXNlcnMK
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bluez-users] Lost connections - mouse and keyboard
2007-12-08 12:57 ` Didier Link
@ 2007-12-09 16:45 ` Fabrice Ménard
2007-12-10 12:36 ` Didier Link
0 siblings, 1 reply; 13+ messages in thread
From: Fabrice Ménard @ 2007-12-09 16:45 UTC (permalink / raw)
To: BlueZ users
[-- Attachment #1: Type: text/plain, Size: 323 bytes --]
On Saturday 08 December 2007 13:57:43 Didier Link wrote:
> Le Sat, 8 Dec 2007 11:25:03 +0100,
>
>
> Hi Fabrice,
Hi
> Finally, Fabrice, your patches aren't accessible with the sourceforge
> and gmane archives of the list, can you resend or put it on pastebin or
> other web location please ??
Sure! Here it is.
Fabrice
[-- Attachment #2: hid2hci.patch --]
[-- Type: text/x-patch, Size: 441 bytes --]
--- bluez-utils-3.19/tools/hid2hci.c 2007-09-16 09:57:40.000000000 +0200
+++ bluez-utils-3.19/tools/hid2hci.c.new 2007-10-18 11:25:40.000000000 +0200
@@ -138,7 +138,7 @@ static int send_report(int fd, const cha
uref.field_index = 0;
uref.usage_index = i;
uref.usage_code = 0xff000001;
- uref.value = buf[i];
+ uref.value = buf[i] & 0x000000ff;
err = ioctl(fd, HIDIOCSUSAGE, &uref);
if (err < 0)
return err;
[-- Attachment #3: xserver.patch --]
[-- Type: text/x-patch, Size: 408 bytes --]
--- xorg-server-1.4/hw/xfree86/common/xf86Helper.c 2007-08-23 21:04:53.000000000 +0200
+++ xorg-server-1.4/hw/xfree86/common/xf86Helper.c.new 2007-10-12 22:42:00.000000000 +0200
@@ -388,7 +388,7 @@ xf86DeleteInput(InputInfoPtr pInp, int f
p->next = pInp->next;
/* Else the entry wasn't in the xf86InputDevs list (ignore this). */
}
- xfree(pInp);
+/* xfree(pInp); */
}
_X_EXPORT Bool
[-- Attachment #4: x11-input.fdi --]
[-- Type: application/xml, Size: 735 bytes --]
[-- Attachment #5: Type: text/plain, Size: 277 bytes --]
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
[-- Attachment #6: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: [Bluez-users] Lost connections - mouse and keyboard
2007-12-09 16:45 ` Fabrice Ménard
@ 2007-12-10 12:36 ` Didier Link
0 siblings, 0 replies; 13+ messages in thread
From: Didier Link @ 2007-12-10 12:36 UTC (permalink / raw)
To: BlueZ users
LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBMQ0KDQpMZSBTdW4s
IDkgRGVjIDIwMDcgMTc6NDU6NDAgKzAxMDAsDQpGYWJyaWNlIE3DqW5hcmQgPG1lbmFyZC5mYWJy
aWNlQG9yYW5nZS5mcj4gYSDDqWNyaXQgOg0KDQoNCj4gU3VyZSEgSGVyZSBpdCBpcy4NCg0KSGkg
RmFicmljZSwgdGhhbmtzIGEgbG90ICENCg0KSSB3aWxsIHRlc3QgaXQgYXMgc29vbiBhcyBwb3Nz
aWJsZSA7KQ0KDQpBbnkgY29tbWVudHMgZnJvbSB0aGUgYmx1ZXogdGVhbSBhYm91dCB0aGUgaGlk
MmhjaSBwYXRjaCA/Pw0KDQpCZXN0IHJlZ2FyZHMuDQoNCkRpZGllciBMaW5rDQoNCi0gLS0gDQpE
aWRpZXIgTGluayA8ZGlkaWVyQGZhbWlsbGUtbGluay5mcj4NCkphYmJlciA6IGRpZGllcl9saW5r
QGphYmJlci5mcg0KTVNOIDogemFuZmliQGhvdG1haWwuZnINClNJUCA6IFphbmZpYkBla2lnYS5u
ZXQNCg0KQ2zDqSBHUEcgOiA3NUJBQzlFRQ0KLS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0N
ClZlcnNpb246IEdudVBHIHYxLjQuNyAoR05VL0xpbnV4KQ0KDQppRDhEQlFGSFhUTEFreVB3aW5X
NnllNFJBZzlzQUo5cnROK3gwSU84bXJFRkpMS3BQQk1nR2dTSlhnQ2RIMTl3DQpwTnp1bG8yWEx1
OHlZU3l1ak00M01oTT0NCj1vb1ZoDQotLS0tLUVORCBQR1AgU0lHTkFUVVJFLS0tLS0NCi0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0KU0YuTmV0IGVtYWlsIGlzIHNwb25zb3JlZCBieToKQ2hlY2sgb3V0IHRoZSBu
ZXcgU291cmNlRm9yZ2UubmV0IE1hcmtldHBsYWNlLgpJdCdzIHRoZSBiZXN0IHBsYWNlIHRvIGJ1
eSBvciBzZWxsIHNlcnZpY2VzIGZvcgpqdXN0IGFib3V0IGFueXRoaW5nIE9wZW4gU291cmNlLgpo
dHRwOi8vc291cmNlZm9yZ2UubmV0L3NlcnZpY2VzL2J1eS9pbmRleC5waHAKX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KQmx1ZXotdXNlcnMgbWFpbGluZyBs
aXN0CkJsdWV6LXVzZXJzQGxpc3RzLnNvdXJjZWZvcmdlLm5ldApodHRwczovL2xpc3RzLnNvdXJj
ZWZvcmdlLm5ldC9saXN0cy9saXN0aW5mby9ibHVlei11c2Vycwo=
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2007-12-10 12:36 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-11-25 16:43 [Bluez-users] Lost connections - mouse and keyboard Brad Smith
2007-11-26 5:49 ` Marcel Holtmann
2007-11-29 3:03 ` Brad Smith
2007-11-29 8:06 ` Dave Young
2007-11-29 20:19 ` Marcel Holtmann
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
2007-12-08 10:25 ` Fabrice Ménard
2007-12-08 12:57 ` Didier Link
2007-12-09 16:45 ` Fabrice Ménard
2007-12-10 12:36 ` Didier Link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox