Bug 11714

Summary:

Intel AC 7260 Bluetooth interface stops responding after disabling Bluetooth

Product:

[Build System, Metadata & Runtime] BSPs

Reporter:

Jair Gonzalez <jair.de.jesus.gonzalez.plascencia>

Component:

bsps-meta-intel

Assignee:

Saul Wold <sgw>

Status:

RESOLVED WORKSFORME

QA Contact:

Severity:

normal

Priority:

Medium+

CC:

sgw, yp.kernel.watcher, yp.watcher

Version:

2.4

Target Milestone:

2.5 M2

Hardware:

x86

OS:

Multiple

Whiteboard:

OS type for building Yocto:

---

Type of Regression:

---

Verified:

Documentation change:

Don't know

Attachments:

Description	Flags
MTurbot_bluetooth_failure.log	none
MMAX-Lure-AC7260_TA-H42623-004_failure.log	none
MMAX-Lure-AC7260_TA-H53062-002_failure.log	none
MTurbot-Lure-AC7260_TA-H42623-004_failure.log	none
test_7260.sh	none

Description Jair Gonzalez 2017-06-23 21:40:38 UTC

Created attachment 3843 [details]
MTurbot_bluetooth_failure.log

STATUS: FAILED
BUILD: 2017-06-22_02-28-09-build-212
ENVIRONMENT: intel-corei7-64 - on MinnowBoard Turbot 64bit
EXPANSION BOARD: Silverjaw Lure (SKU 1000)
WIRELESS MODULE: Intel Dual Band Wireless-AC 7260 - 7260HMW
STEPS TO REPRODUCE: 

    With Bluetooth already enabled, execute the following commands:

    connmanctl disable bluetooth

    connmanctl enable bluetooth

EXPECTED OUTCOME: 

    Bluetooth is enabled and the hci0 interface responds to HCI commands.

ACTUAL:

    After disabling Bluetooth, the next error appears on the Kernel buffer:

    [ 421.158820] Bluetooth: hci0: turning off Intel device LED failed (-61)

    Following the error, the hci0 interface stops responding and any attempt to bring the interface up times out until the DUT is rebooted.

ADDITIONAL NOTES:

    Reloading the btusb module throws the following output to the kernel buffer:

    [  502.420138] usbcore: deregistering interface driver btusb
    [  511.156381] usbcore: registered new interface driver btusb
    [  513.165857] Bluetooth: hci0 command 0x0c03 tx timeout
    [  521.615945] Bluetooth: hci0 sending initial HCI reset command failed (-110)

    This issue also occurs on the Meta-Intel build 2.3_M3_meta_intel_rc1.

    Similar occurrence on Red Hat: https://bugzilla.redhat.com/show_bug.cgi?id=1290011

Comment 1 Saul Wold 2017-07-31 16:15:03 UTC

Please re-test this with latest meta-intel (will be part of M2 meta-intel BSP)

http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/commit/?id=1811a41d6f891784b2a5b65d60626add51f3d13e

Along with additional patches enable the out of Tree iwlwifi driver, which should resolve this.

It it does not, please re-open this issue

Comment 2 Jair Gonzalez 2017-09-08 20:19:42 UTC

Created attachment 3998 [details]
MMAX-Lure-AC7260_TA-H42623-004_failure.log

Comment 3 Jair Gonzalez 2017-09-08 20:20:50 UTC

Created attachment 3999 [details]
MMAX-Lure-AC7260_TA-H53062-002_failure.log

Comment 4 Jair Gonzalez 2017-09-08 20:21:23 UTC

Created attachment 4000 [details]
MTurbot-Lure-AC7260_TA-H42623-004_failure.log

Comment 5 Jair Gonzalez 2017-09-08 20:22:16 UTC

Re-opening the ticket as the issue is still present using the meta-intel build: http://yocto-ab-master.jf.intel.com/pub/nightly-meta-intel/20170906-1/machines/intel-corei7-64/

Tested again with three different Minnowboards (two MMAX and one Turbot) in conjunction with three Silverjaw Lure and Intel AC 7260 pairs. The issue was reproduced on the three DUTs. However, after further testing I could confirm the issue sometimes requires several tries of disabling and enabling the Bluetooth using connmanctl, in order to reproduce.

I also could observe there is a different TA code on the label from one of the DUTs (H53062-002) than the one on the other two (H42623-004). Also, the SPS code (784639-005) is absent on the DUT with TA H53062-002.

For more reference, I have attached the logs of console test sessions where the failure was reproduced on each of the DUTs.

Comment 6 Saul Wold 2017-11-16 19:04:54 UTC

I know have the hardware here, and have been attempting to reproduce the issue and have not been able to.

Comment 7 Jair Gonzalez 2017-11-22 17:50:51 UTC

Created attachment 4130 [details]
test_7260.sh

Comment 8 Jair Gonzalez 2017-11-22 17:51:57 UTC

Saul, are you using a custom build?

During my tests, I found that Bluetooth was always enabled by default, so I disabled the bluetooth service at boot and left only connman running. However this caused the issue to NOT reproduce at all, even after more than 50 tries with different sequences.

But after enabling again the bluetooth and the connman service running together, a simple script like the attached 'test_7260.sh' always reproduced the error.

Comment 9 Saul Wold 2018-01-17 00:04:33 UTC

Still no joy on reproducing it, I will close this for now, if the issue re-appears, then this or a new bug can be opened.