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: Sat, 20 Feb 2016 21:30:28 +0100 [thread overview]
Message-ID: <20160220213028.35760428@envy.w5.y.home> (raw)
In-Reply-To: <20160220182919.GA2620@t440s.P-661HNU-F1>
Hi Johan,
> > Do you see the same issue if you don't use blueman? (a piece of
> > software I'm not really familiar with).
If I disable or uninstall blueman, the mouse doesn't come back to life
after a suspend/resume (or initial bootup) until I manually issue
"hciconfig hci0 up". This is the case for both pre- and post-2ff1389
kernels.
> > What exactly do you do when you say you "manually disable and then
> > re-enable bluetooth"? "btmgmt power off; btmgmt power on"?
> > bluetoothctl power off/on? Something else?
I right-click the blueman systray icon, and it pops up a meny where I
can select either =C2=ABTurn Bluetooth Off=C2=BB or =C2=ABTurn Bluetooth On=
=C2=BB (only one
of the options are shown, depending on blueman's idea of the current
status).
> > It'd be important to understand what exactly your user space
> > software (blueman) does when you resume. So any logs that you can
> > take of this would be helpful. You could e.g. take a HCI log using
> > btmon and enable kernel debug logs for the bluetooth module (see
> > Documentation/dynamic-debug-howto.txt in the kernel
> > documentation).
I uploaded debug files to http://filebin.net/pfmb8043cx :
- timestamps.$KVER.txt: my notes of the timestamps of when I did
specific actions, for easy cross-referencing with the other files.
- blueman-applet.$KVER.txt: output from "blueman-applet |& ts".
- btmon.$KVER.txt: output from "btmon -T".
- kernel-debug-messages.$KVER.txt: kernel output (journalctl -k), after
having written "module bluetooth +p" to
the /sys/kernel/debug/dynamic_debug/control file.
Where $KVER is either 4.4.0-rc3-00801-gbf943cb (the last rev where the
bluetooth mouse comes back to life automatically after resume) or
4.4.0-rc3-00802-g2ff1389 (the first rev where it doesn't).
> Another thing to try in addition to disabling blueman: Add
> AutoEnable=3Dtrue under the [Policy] section
> in /etc/bluetooth/main.conf. It might make a difference assuming that
> your Bluetooth adapter gets detached and reattached to the USB bus
> when you suspend/resume.
This made no difference. Note that I had to create that file and its
containing directory anew, it didn't already exist on my Fedora 23
system.
Tore
next prev parent reply other threads:[~2016-02-20 20:30 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 [this message]
2016-02-21 7:02 ` Johan Hedberg
2016-02-21 11:13 ` Tore Anderson
2016-03-03 7:51 ` Tore Anderson
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=20160220213028.35760428@envy.w5.y.home \
--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).