public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Seyfried <seife@suse.de>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] bug report: trouble reconnecting keyboard	after timeout
Date: Thu, 15 May 2008 17:55:35 +0200	[thread overview]
Message-ID: <482C5CF7.1070306@suse.de> (raw)
In-Reply-To: <1210860904.7025.50.camel@violet.holtmann.net>

Marcel Holtmann wrote:
> Hi Dick,
> =

>> I upgraded bluez-utils and bluez-libs (3.31) and it didn't help.
>>
>> I've attached a logfile, I hope it's sufficient.
>>
>> My mouse and keyboard couldn't connect, I've reconnected them by
>> manually disconnecting them in bluetooth-applet.
> =

> if I am not mistaken, then the attached kernel patch will fix this
> issue.

Partly. It works fine with my mouse, but my keyboard, that was happy before
now after some "roundtrips" gets unhappy and does no longer reconnect. (i
changed the idle timeout to 30 seconds to test).

I got stuff like that in hcidump:
2008-05-15 17:23:44.288599 > ACL data: handle 11 flags 0x02 dlen 12
   L2CAP(s): Connect req: psm 19 scid 0x005c
2008-05-15 17:23:44.288640 < ACL data: handle 11 flags 0x02 dlen 16
   L2CAP(s): Connect rsp: dcid 0x0000 scid 0x005c result 4 status 0
     Connection refused - no resources available

And then my dongle spontaneously disconnected itself from the USB bus and
reconnected.

I have not seen this again since then, but maybe it is something to watch o=
ut for.
-- =

Stefan Seyfried
R&D Team Mobile Devices            |              "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg | "Well, surrounding them's out."

This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG N=FCrnberg)

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft =

Defy all challenges. Microsoft(R) Visual Studio 2008. =

http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2008-05-15 15:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14 17:34 [Bluez-devel] bug report: trouble reconnecting keyboard after timeout Dick
2008-05-15 14:15 ` Marcel Holtmann
2008-05-15 15:55   ` Stefan Seyfried [this message]
2008-05-17  7:32   ` Dick
2008-05-30  5:03   ` Didier Link
2008-05-30  6:49     ` Dick
  -- strict thread matches above, loose matches on Subject: below --
2008-05-12 16:45 Dick
2008-05-12 17:19 ` Marcel Holtmann
2008-05-13 19:29   ` Dick

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=482C5CF7.1070306@suse.de \
    --to=seife@suse.de \
    --cc=bluez-devel@lists.sourceforge.net \
    /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