Linux bluetooth development
 help / color / mirror / Atom feed
From: etsang <Edwin.Tsang@ca.flextronics.com>
To: "Keng-Yü Lin" <kengyu@ubuntu.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Bug: bluetooth not working after suspend/resume
Date: Tue, 27 Sep 2011 09:52:11 -0400	[thread overview]
Message-ID: <1317131531.2158.7.camel@etsang-laptop> (raw)
In-Reply-To: <CADXHx7Z=9EFEweZ+LouXWdRePu6OBrj36uGA78=BMKjo0oMEJQ@mail.gmail.com>

Hi Kenyu,
  I am working on a similar BT issue. But it is on Android Gingerbread
kernel 2.6.25.7+.  After a idle for a while the BT was not return any
inquiry result (if it was not), if turn off BT then it will not turn
again until a power cycle. On the kernal log it was showing problem
loading into the TI wl327x. 
---
TIinit_7.2.31.bts
no proper response during fw download.
Do you you have a similar fw download failure when attempt to turn on
BT. Or might be a different issue?

Ed
On Tue, 2011-09-27 at 16:25 +0800, Keng-Yü Lin wrote:
> Hi all:
>   Since kernel.org/bugzilla is dead for a while, I sent the bug report
> here in hope to get more insight.
> 
>   This is a long-lasting bug and happens across several distros with
> different combinations of bluez/kernel verisions but shares much the
> same symptom that bluetooth is not working after the resume. As seen
> in the bug report below, it happens on a variety of different laptops
> too.
> 
>   Redhat:
>     https://bugzilla.redhat.com/show_bug.cgi?id=727106
> 
>   Debian:
>     http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614929
> 
>   Ubuntu:
>     https://launchpad.net/bugs/824144
>     https://launchpad.net/bugs/824633
>     https://launchpad.net/bugs/823467
>     https://launchpad.net/bugs/822705
> 
>   Personally I did some investigation on the issue and found that
> bluetoothd does not receive the HCI commands of read_bd_addr,
> read_local_version, read_local_features, nor read_local_name. So in
> bluez.plugins/hciops.c:device_devup_setup(), init_adapter() is not
> called at resume.
> 
>   It can be further confirmed by the attached patch of bluez. It is
> ugly but can work around the bug as reported in some of the bug
> trackers above.
> 
>   I am looking for any advice to get it move on,  for the debugging
> and the fixing.
> 
>   Thanks,
> -kengyu


 
Legal Disclaimer:
The information contained in this message may be privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete or destroy any copy of this message


  reply	other threads:[~2011-09-27 13:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-27  8:25 Bug: bluetooth not working after suspend/resume Keng-Yü Lin
2011-09-27 13:52 ` etsang [this message]
2011-09-27 13:55   ` sunil.kumar5
2011-10-13  1:35 ` [RFC] Bluez: Fix the adapter is not initialised after resume Keng-Yu Lin
2011-10-13  7:35   ` Luiz Augusto von Dentz
2011-10-13 11:23     ` Luiz Augusto von Dentz
2011-10-19 10:30       ` Keng-Yü Lin

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=1317131531.2158.7.camel@etsang-laptop \
    --to=edwin.tsang@ca.flextronics.com \
    --cc=kengyu@ubuntu.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