kernel-packages team mailing list archive

[Fredrik Jacobsson <fredrik@xxxxxxxxxx>]

Public bug reported:

Bluetooth receiver doesn't connect with kernel after sleep/boot-up. The receiver is awake because "kernel: [339132.269449] Bluetooth: hci0 ACL packet for unknown connection handle ##" appears in the system log because I'm shaking the mouse.
Sometimes it takes over 4 minutes of shaking to reconnect the mouse.

I do not know where to report this bug.

Is it the kernel? Because it's the kernel that report that something is happening on the bluetooth receiver.
Is it HCI? Because if I reset hci0, I have to shake the mouse again.
Is it the hardware driver that enter sleep mode incorrectly?
And finally, is it the bluetooth stack?

This machine runs Ubuntu 16.04 but I've had this  problem as long as
I've had this computer. It's a Lenovo G50-45 with a Realtek 8723BE
Wifi/Bluetooth combo HARDCODED into the BIOS (It will not boot if you
change the network card to something else, like Intel 7260).

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  Bluetooth receiver doesn't connect with kernel after sleep/boot-up. The receiver is awake because"kernel: [339132.269449] Bluetooth: hci0 ACL packet for unknown connection handle ##" appears in the system log because I'm shaking the mouse.
  Sometimes it takes over 4 minutes of shaking to reconnect the mouse.
  
  I do not know where to report this bug.
  
  Is it the kernel? Because it's the kernel that report that something is happening on the bluetooth receiver.
  Is it HCI? Because if I reset hci0, I have to shake the mouse again.
  Is it the hardware driver that enter sleep mode incorrectly?
  And finally, is it the bluetooth stack?
  
  This machine runs Ubuntu 16.04 but I've had this  problem as long as
- I've had this computer. It's a Lenovo G50-45 with a Realttek 8723BE
+ I've had this computer. It's a Lenovo G50-45 with a Realtek 8723BE
  Wifi/Bluetooth combo HARDCODED into the BIOS (It will not boot if you
  change the network card to something else, like Intel 7260).

** Description changed:

- Bluetooth receiver doesn't connect with kernel after sleep/boot-up. The receiver is awake because"kernel: [339132.269449] Bluetooth: hci0 ACL packet for unknown connection handle ##" appears in the system log because I'm shaking the mouse.
+ Bluetooth receiver doesn't connect with kernel after sleep/boot-up. The receiver is awake because "kernel: [339132.269449] Bluetooth: hci0 ACL packet for unknown connection handle ##" appears in the system log because I'm shaking the mouse.
  Sometimes it takes over 4 minutes of shaking to reconnect the mouse.
  
  I do not know where to report this bug.
  
  Is it the kernel? Because it's the kernel that report that something is happening on the bluetooth receiver.
  Is it HCI? Because if I reset hci0, I have to shake the mouse again.
  Is it the hardware driver that enter sleep mode incorrectly?
  And finally, is it the bluetooth stack?
  
  This machine runs Ubuntu 16.04 but I've had this  problem as long as
  I've had this computer. It's a Lenovo G50-45 with a Realtek 8723BE
  Wifi/Bluetooth combo HARDCODED into the BIOS (It will not boot if you
  change the network card to something else, like Intel 7260).

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1548317

Title:
  kernel: [some.number] Bluetooth: hci0 ACL packet for unknown
  connection handle ##

Status in linux package in Ubuntu:
  New

Bug description:
  Bluetooth receiver doesn't connect with kernel after sleep/boot-up. The receiver is awake because "kernel: [339132.269449] Bluetooth: hci0 ACL packet for unknown connection handle ##" appears in the system log because I'm shaking the mouse.
  Sometimes it takes over 4 minutes of shaking to reconnect the mouse.

  I do not know where to report this bug.

  Is it the kernel? Because it's the kernel that report that something is happening on the bluetooth receiver.
  Is it HCI? Because if I reset hci0, I have to shake the mouse again.
  Is it the hardware driver that enter sleep mode incorrectly?
  And finally, is it the bluetooth stack?

  This machine runs Ubuntu 16.04 but I've had this  problem as long as
  I've had this computer. It's a Lenovo G50-45 with a Realtek 8723BE
  Wifi/Bluetooth combo HARDCODED into the BIOS (It will not boot if you
  change the network card to something else, like Intel 7260).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548317/+subscriptions