From: Pacho Ramos <pacho@gentoo.org>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: bluetoothd: Refusing input device connect: Operation already in progress (114)
Date: Fri, 21 Sep 2012 21:00:18 +0200 [thread overview]
Message-ID: <1348254019.2085.2.camel@belkin4> (raw)
In-Reply-To: <20120921124323.GA14885@x220>
[-- Attachment #1: Type: text/plain, Size: 1948 bytes --]
El vie, 21-09-2012 a las 15:43 +0300, Johan Hedberg escribió:
> Hi,
>
> On Sat, Sep 15, 2012, Pacho Ramos wrote:
> > Downstream we got the following report:
> > https://bugs.gentoo.org/show_bug.cgi?id=431624
> >
> > After adding mouse (via Blueman's "Add device" dialog) it works fine
> > until sleeping or powering off. After that it fails reconnecting.
> > In /var/log/messages appears strings like these:
> >
> > Aug 16 15:40:31 user bluetoothd[3222]: Refusing input device connect:
> > Operation already in progress (114)
> > Aug 16 15:45:13 user bluetoothd[3222]: Refusing input device connect:
> > Operation already in progress (114)
> > Aug 16 15:45:16 user bluetoothd[3222]: Refusing input device connect:
> > Operation already in progress (114)
> > Aug 16 15:45:17 user bluetoothd[3222]: Refusing input device connect:
> > Operation already in progress (114)
> > Aug 16 15:45:19 user bluetoothd[3222]: Refusing input device connect:
> > Operation already in progress (114)
> > Aug 16 15:47:46 user bluetoothd[3222]: Refusing input device connect:
> > Operation already in progress (114)
> >
> > Searching, I found this thread that pointed to the culprit, but I
> > haven't found what finally occurred with it, if patch was reverted or a
> > different fix was pulled in:
> > http://www.spinics.net/lists/linux-bluetooth/msg26442.html
>
> This is a different issue but the cause seems to be similar. You don't
> need to patch bluetoothd though but just disable the mgmt part by
> passing -P mgmtops to bluetoothd. For whatever reason the connection
> state isn't cleaned up with mgmt (which shouldn't be dependent on mgmt
> to begin with) and the input_device_set_channel function returns
> -EALREADY when accepting a connection.
>
> Johan
>
But it sounds like a workaround as mgmt is still broken as compared with
bluetoothd previous above change was committed, no? Thanks for the
info :)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-09-21 19:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-15 10:15 bluetoothd: Refusing input device connect: Operation already in progress (114) Pacho Ramos
2012-09-18 19:01 ` Pacho Ramos
2012-09-21 12:43 ` Johan Hedberg
2012-09-21 19:00 ` Pacho Ramos [this message]
2012-09-21 19:07 ` Johan Hedberg
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=1348254019.2085.2.camel@belkin4 \
--to=pacho@gentoo.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@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).