[Bug 198953] New: hci_bcm: Streamline runtime PM code change for 4.16 kernel breaks bluetooth on ASUS T100TA

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.kernel.org/show_bug.cgi?id=198953

            Bug ID: 198953
           Summary: hci_bcm: Streamline runtime PM code    change for 4.16
                    kernel breaks bluetooth on ASUS T100TA
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.16-rc3
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Bluetooth
          Assignee: linux-bluetooth@xxxxxxxxxxxxxxx
          Reporter: rhowell@xxxxxxxx
        Regression: No

Created attachment 274481
  --> https://bugzilla.kernel.org/attachment.cgi?id=274481&action=edit
Patch to add ASUS T100TAM and Toshiba Encore device info to hci_bcm.c

The patch "Bluetooth: hci_bcm: Streamline runtime PM code" by Lukas Wunner,
posted at <https://www.spinics.net/lists/linux-bluetooth/msg73529.html>, and
incorporated in 4.16-rc3 (and probably rc1 and 2) breaks bluetooth on the ASUS
T100TA, T100TAM, and Toshiba Encore computers.  All are Baytrail machines. 
Reverting that single patch fixes the problem.  

Bluetooth comes up OK initially, but after about 5 seconds of use seems to die.
 Turning power to the bluetooth controller off then on, either in bluetoothctl
or in via a system GUI, fixes the problem for about another 5 seconds, but then
bluetooth dies again.  The problem happens both with a Logitech MX2 mouse and a
bluetooth keyboard.  No error messages seem to be produced in dmesg or
elsewhere, but the system stops responding to the mouse or keyboard.

I've also experimented with reverting the series of 13 later patches also be
Lukas Wunner posted at
<https://www.spinics.net/lists/linux-bluetooth/msg73757.html> but those do NOT
seem to have any effect one way or the other on the problem.  The single
critical patch is the one listed above, and luckily it can be reverted
independently of the other 13.

While bluetooth has been working (before 4.16) on the T100TA with the stock
kernel, to make it work for the T100TAM and the Encore I've always needed to
add them to the device quirk table (which already includes the T100TA), and for
the Encore I need to add the BCM2E38 device ID to the ACPI table.  I've
attached a patch which adds that T100TAM and Encore information.  If there is
any way it could be incorporated in the mainline code, that would be great.  In
any case, you'll need to apply it to the 4.16-rc3 stock hci_bcm.c file if you
do want to test for this bug with the T100TAM or the Encore.  You don't need it
to test with the T100TA.

-- 
You are receiving this mail because:
You are the assignee for the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux