linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tore Anderson <tore@fud.no>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Gustavo Padovan <gustavo@padovan.org>,
	linux-bluetooth@vger.kernel.org
Subject: Re: PROBLEM: Bluetooth mouse not working after resume since commit 2ff1389
Date: Thu, 3 Mar 2016 08:51:16 +0100	[thread overview]
Message-ID: <20160303085116.0567712b@echo.ms.redpill-linpro.com> (raw)
In-Reply-To: <20160221121322.6a19b1d4@envy.w5.y.home>

* Tore Anderson <tore@fud.no>

> * Johan Hedberg
> 
> > You could have also used src/main.conf from the BlueZ tree as a
> > starting point and removed the '#' from the AutoEnable line:
> > 
> > https://git.kernel.org/cgit/bluetooth/bluez.git/plain/src/main.conf
> > 
> > Are you sure that you restarted bluetoothd after this change? And
> > you've got a BlueZ version greater than 5.35 (where the feature was
> > introduced)?  
> 
> I've got version 5.36, and I had rebooted the system from scratch. I
> experimented a bit more, though, and I found out that with
> AutoEnable=true (and blueman uninstalled), my system behaves exactly
> the same as it did with blueman, that is:
> 
> - with a pre-2ff1389 kernel: the mouse is auto-enabled and works fine
>   after bootup and resume from suspend.
> - with a post-2ff1389 kernel: the mouse is auto-enabled and works fine
>   after bootup, but stops working after resume from suspend (until
>   "hciconfig hci0 up" is issued manually).
> 
> That means we can exclude blueman as a potential cause of the problem,
> so I left it uninstalled when I generated the new debug files with +pf,
> which you can find here: http://filebin.net/wf9edcjbju
> 
> I added a new file too: hciconfig_hci0.$KVER.txt. This shows the
> output of "while sleep .5; do hciconfig hci0; done | ts %H:%M:%.S". I
> noticed something that seems highly relevant, namely that with the
> post-2ff1389 kernel, the hci0 state changes to DOWN a couple of seconds
> after resuming. This does not happen with the pre-2ff1389 kernel.

Hi Johan,

I thought I'd just ping you quickly about this issue - did you get a
chance to look at the log files, and if so did you figure out what's
going on?

If on the other hand you don't have time to look into the issue, let me
know if I should file this issue in the kernel.org bugzilla (or
anywhere else) so as to avoid it being forgotten about (also note that
the logs will be expired from filebin.net after a couple of weeks).

Tore

  reply	other threads:[~2016-03-03  7:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-20 17:12 PROBLEM: Bluetooth mouse not working after resume since commit 2ff1389 Tore Anderson
2016-02-20 18:23 ` Johan Hedberg
2016-02-20 18:29   ` Johan Hedberg
2016-02-20 20:30     ` Tore Anderson
2016-02-21  7:02       ` Johan Hedberg
2016-02-21 11:13         ` Tore Anderson
2016-03-03  7:51           ` Tore Anderson [this message]
2016-03-03  8:42             ` Johan Hedberg
2016-03-03 20:44               ` Tore Anderson
2016-03-04  6:54                 ` Johan Hedberg
2016-03-05  9:09                   ` Tore Anderson

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=20160303085116.0567712b@echo.ms.redpill-linpro.com \
    --to=tore@fud.no \
    --cc=gustavo@padovan.org \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.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).