Re: bluetooth mouse and keyboard stop working after some time

2019-11-20 Thread Federico Beffa
Thanks for the suggestions.

After some more experiments I think that it's not a timeout/power
problem, but it's probably a bug related to suspend/resume.



Re: bluetooth mouse and keyboard stop working after some time

2019-11-18 Thread Jonas Smedegaard
Hi Federico,

Quoting Federico Beffa (2019-11-18 20:54:37)
> I recently purchased bluetooth mouse and keyboard to use with a Debian 
> 9 machine.  I could pair the devices without problems and they do work 
> for some time. However, after some time they stop working.  I suspect 
> that some timeout triggers. (After a reboot they start working again 
> for some time.)
> 
> I'm using kernel linux-image-4.19.0-0.bpo.6-amd6.
> 
> Below is an excerpt from /var/log/syslog showing that the Bluetooth 
> module is shutting down.
> 
> Any suggestions?

Try disable power management for the bluetooth device driver.

Easiest to play with that is probably to install and use powertop, which 
hints at what it changes so that (if succesful) you can transfer those 
changes to e.g. lines in a new file /etc/sysctl.d/local-powersave.conf

NB! You may need to disable power management not only from device driver 
but also drivers of underlying bus.  You can get a topological view of 
the USB bus with this command:

  lsusb --tree

...and a topological view of your whole machine with this:

  lshw | less


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature


bluetooth mouse and keyboard stop working after some time

2019-11-18 Thread Federico Beffa
Hi,

I recently purchased bluetooth mouse and keyboard to use with a Debian
9 machine.  I could pair the devices without problems and they do work
for some time. However, after some time they stop working.  I suspect
that some timeout triggers. (After a reboot they start working again
for some time.)

I'm using kernel linux-image-4.19.0-0.bpo.6-amd6.

Below is an excerpt from /var/log/syslog showing that the Bluetooth
module is shutting down.

Any suggestions?

Nov 18 15:03:23 lupo NetworkManager[717]:   [1574085803.9156]
device (wlp2s0): set-hw-addr: set MAC address to EA:9D:A4:E8:88:99
(scanning)
Nov 18 15:03:23 lupo kernel: [ 6888.646262] IPv6: ADDRCONF(NETDEV_UP):
wlp2s0: link is not ready
Nov 18 15:03:23 lupo NetworkManager[717]:   [1574085803.9227]
device (wlp2s0): supplicant interface state: inactive -> disabled
Nov 18 15:03:23 lupo NetworkManager[717]:   [1574085803.9463]
device (wlp2s0): supplicant interface state: disabled -> inactive
Nov 18 15:03:23 lupo wpa_supplicant[1140]: wlp2s0: Reject scan trigger
since one is already pending
Nov 18 15:05:44 lupo kernel: [ 7029.363271] usb 1-4: USB disconnect,
device number 3
Nov 18 15:05:44 lupo systemd[1]: Starting Load/Save RF Kill Switch Status...
Nov 18 15:05:44 lupo systemd[1]: bluetooth.target: Unit not needed
anymore. Stopping.
Nov 18 15:05:44 lupo systemd[1]: Stopped target Bluetooth.
Nov 18 15:05:44 lupo systemd[1]: Started Load/Save RF Kill Switch Status.
Nov 18 15:05:44 lupo /usr/lib/gdm3/gdm-x-session[1292]: (II)
config/udev: removing device MX Master 3 Keyboard
Nov 18 15:05:44 lupo /usr/lib/gdm3/gdm-x-session[1292]: (**) Option "fd" "50"
Nov 18 15:05:44 lupo /usr/lib/gdm3/gdm-x-session[1292]: (II)
UnloadModule: "libinput"
Nov 18 15:05:44 lupo /usr/lib/gdm3/gdm-x-session[1292]: (II)
systemd-logind: releasing fd for 13:85
Nov 18 15:05:44 lupo /usr/lib/gdm3/gdm-x-session[1292]: (II)
config/udev: removing device MX Master 3 Mouse
Nov 18 15:05:44 lupo /usr/lib/gdm3/gdm-x-session[1292]: (**) Option "fd" "51"
Nov 18 15:05:44 lupo /usr/lib/gdm3/gdm-x-session[1292]: (II)
UnloadModule: "libinput"
Nov 18 15:05:44 lupo /usr/lib/gdm3/gdm-x-session[1292]: (II)
systemd-logind: releasing fd for 13:86
Nov 18 15:05:44 lupo /usr/lib/gdm3/gdm-x-session[1292]: (II)
config/udev: removing device MX Keys Keyboard
Nov 18 15:05:44 lupo /usr/lib/gdm3/gdm-x-session[1292]: (**) Option "fd" "54"

Thanks,
Fede