[Bug 204275] bluetoothd consumes 100% cpu on keyboard disconnect

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.kernel.org/show_bug.cgi?id=204275

--- Comment #3 from Steven Newbury (steve@xxxxxxxxxxxxxxx) ---
Ahhh...

I was already aware that on first connect the HID input device wasn't created,
but I hadn't realised it's part of the same bug.

What's happening is that on initial connect:

 dev->sec_watch = g_io_add_watch(idev->intr_io, G_IO_OUT,
                                                        encrypt_notify, idev);

creates the notify callback.  But it never triggers.  On second connection the
callback gets triggered, but the connect code gets run again so another
refcount is added.  This means the intr channel never gets closed which means
it's stuck on the last event.

-- 
You are receiving this mail because:
You are the assignee for the bug.



[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux