Bug 1095147 - Atheros AR3012 bluetooth fails on kernel 4.4.132-53-default with Configuration file not found ar3k/ramps_0x00000200_0.dfu
Atheros AR3012 bluetooth fails on kernel 4.4.132-53-default with Configuratio...
Status: RESOLVED FIXED
Classification: openSUSE
Product: openSUSE Distribution
Classification: openSUSE
Component: Kernel
Leap 42.3
Other Other
: P5 - None : Normal (vote)
: ---
Assigned To: E-mail List
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-05-30 07:25 UTC by David Chewning
Modified: 2018-07-03 19:33 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Chewning 2018-05-30 07:25:14 UTC
Installing the latest kernel on Leap 42.3, 4.4.132-53-default makes bluetooth fail in my MSI GS40 laptop.

dmesg|grep -i blue
[   20.548957] Bluetooth: Core ver 2.21
[   20.548971] Bluetooth: HCI device and connection manager initialized
[   20.548974] Bluetooth: HCI socket layer initialized
[   20.548975] Bluetooth: L2CAP socket layer initialized
[   20.548980] Bluetooth: SCO socket layer initialized
[   20.560174] Bluetooth: Configuration file not found ar3k/ramps_0x00000200_0.dfu
[   20.560174] Bluetooth: Loading sysconfig file failed
[   54.478616] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   54.478617] Bluetooth: BNEP filters: protocol multicast
[   54.478621] Bluetooth: BNEP socket layer initialized


I checked to insure all these files are present:
/lib/firmware/ath3k-1.fw
/lib/firmware/ar3k/AthrBT_0x01020200.dfu
/lib/firmware/ar3k/ramps_0x01020200_26.dfu
/lib/firmware/ar3k/ramps_0x01020200_40.dfu

I also checked to insure these files were on the system, since as you will see below these are the ones the previous kernel used:
/lib/firmware/qca/rampatch_usb_00000200.bin
/lib/firmware/qca/nvm_usb_00000200.bin



According to this thread https://bbs.archlinux.org/viewtopic.php?id=201646

the _0.dfu part of the file means the clock value is being read incorrectly.

There also seems to be some issues around Qualcomm and Rome using the same chip ID. Which seems to be the issue here.

In 4.4.126-48-default bluetooth worked fine, and I hope this will help from the /var/log/boot.log file from when it worked:

May 22 09:16:06 kvm kernel: Bluetooth: Core ver 2.21
May 22 09:16:06 kvm kernel: Bluetooth: HCI device and connection manager initialized
May 22 09:16:06 kvm kernel: Bluetooth: HCI socket layer initialized
May 22 09:16:06 kvm kernel: Bluetooth: L2CAP socket layer initialized
May 22 09:16:06 kvm kernel: Bluetooth: SCO socket layer initialized
May 22 09:16:06 kvm kernel: Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00000200.bin
May 22 09:16:06 kvm kernel: Bluetooth: hci0: QCA: patch rome 0x200 build 0x299, firmware rome 0x200 build 0x111
May 22 09:16:07 kvm kernel: Bluetooth: hci0: using NVM file: qca/nvm_usb_00000200.bin
May 22 09:16:07 kvm systemd[1]: Starting Bluetooth service...
May 22 09:16:07 kvm bluetoothd[1599]: Bluetooth daemon 5.41
May 22 09:16:07 kvm bluetoothd[1599]: Starting SDP server
May 22 09:16:07 kvm systemd[1]: Started Bluetooth service.
May 22 09:16:07 kvm systemd[1]: Reached target Bluetooth.
May 22 09:16:07 kvm kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
May 22 09:16:07 kvm kernel: Bluetooth: BNEP filters: protocol multicast
May 22 09:16:07 kvm kernel: Bluetooth: BNEP socket layer initialized
May 22 09:16:07 kvm bluetoothd[1599]: Bluetooth management interface 1.10 initialized
May 22 09:16:07 kvm bluetoothd[1599]: Failed to obtain handles for "Service Changed" characteristic
May 22 09:16:07 kvm bluetoothd[1599]: Sap driver initialization failed.
May 22 09:16:07 kvm bluetoothd[1599]: sap-server: Operation not permitted (1)
May 22 09:16:41 kvm bluetoothd[1599]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSource
May 22 09:16:41 kvm bluetoothd[1599]: Endpoint registered: sender=:1.36 path=/MediaEndpoint/A2DPSink
May 22 09:16:41 kvm kernel: Bluetooth: RFCOMM TTY layer initialized
May 22 09:16:41 kvm kernel: Bluetooth: RFCOMM socket layer initialized
May 22 09:16:41 kvm kernel: Bluetooth: RFCOMM ver 1.11

I am happy to test as needed.
Comment 1 Takashi Iwai 2018-05-30 08:08:35 UTC
Yes, it's a known issue, and it was already addressed for Leap 15.0 / TW (bug 1082504).

There was a "fix" once in 4.4.x, but it was reverted later since it breaks other devices.

I'll try to build a test kernel with the backport of the latest fix patch for Leap 42.3.
Comment 2 Takashi Iwai 2018-05-30 08:36:56 UTC
A test kernel is being built in OBS home:tiwai:bsc1095147 repo.
It'll take some time until the build finishes (an hour or so), and after that, the package will appear at
  http://download.opensuse.org/repositories/home:/tiwai:/bsc1095147/standard/

Please give it a try later.
Comment 3 David Chewning 2018-05-30 10:51:56 UTC
I installed: kernel-default-4.4.132-1.1.gb7f7da0.x86_64.rpm
Turned off secure boot
Booted into the new kernel and bluetooth is working :)
Comment 4 Takashi Iwai 2018-05-30 11:26:34 UTC
Good to hear.  I'll queue the fix patch to Leap 42.3 branch.
It'll be included in the next update kernel.
Comment 5 Swamp Workflow Management 2018-06-21 16:16:40 UTC
SUSE-SU-2018:1772-1: An update that solves 6 vulnerabilities and has 47 fixes is now available.

Category: security (important)
Bug References: 1012382,1024718,1031717,1035432,1041740,1045330,1056415,1066223,1068032,1068054,1068951,1070404,1073311,1075428,1076049,1078583,1079152,1080542,1080656,1081500,1081514,1082153,1082504,1082979,1085185,1085308,1086400,1086716,1087036,1087086,1088871,1090435,1090534,1090734,1090955,1091594,1094532,1095042,1095147,1096037,1096140,1096214,1096242,1096281,1096751,1096982,1097234,1097356,1098009,1098012,971975,973378,978907
CVE References: CVE-2017-17741,CVE-2017-18241,CVE-2017-18249,CVE-2018-12233,CVE-2018-3665,CVE-2018-5848
Sources used:
SUSE Linux Enterprise Workstation Extension 12-SP3 (src):    kernel-default-4.4.138-94.39.1
SUSE Linux Enterprise Software Development Kit 12-SP3 (src):    kernel-docs-4.4.138-94.39.1, kernel-obs-build-4.4.138-94.39.1
SUSE Linux Enterprise Server 12-SP3 (src):    kernel-default-4.4.138-94.39.1, kernel-source-4.4.138-94.39.1, kernel-syms-4.4.138-94.39.1
SUSE Linux Enterprise Live Patching 12-SP3 (src):    kgraft-patch-SLE12-SP3_Update_14-1-4.5.1
SUSE Linux Enterprise High Availability 12-SP3 (src):    kernel-default-4.4.138-94.39.1
SUSE Linux Enterprise Desktop 12-SP3 (src):    kernel-default-4.4.138-94.39.1, kernel-source-4.4.138-94.39.1, kernel-syms-4.4.138-94.39.1
SUSE CaaS Platform ALL (src):    kernel-default-4.4.138-94.39.1
Comment 6 Swamp Workflow Management 2018-06-21 16:29:16 UTC
openSUSE-SU-2018:1773-1: An update that solves 11 vulnerabilities and has 66 fixes is now available.

Category: security (important)
Bug References: 1012382,1019695,1019699,1022604,1022607,1022743,1024718,1031492,1031717,1035432,1036215,1041740,1045330,1056415,1066223,1068032,1068054,1068951,1070404,1073311,1075428,1076049,1078583,1079152,1080542,1080656,1081500,1081514,1082153,1082504,1082979,1085308,1086400,1086716,1087007,1087012,1087036,1087082,1087086,1087095,1088871,1090435,1090534,1090734,1090955,1091594,1091815,1092552,1092813,1092903,1093533,1093904,1094177,1094268,1094353,1094356,1094405,1094466,1094532,1094823,1094840,1095042,1095147,1096037,1096140,1096214,1096242,1096281,1096751,1096982,1097234,1097356,1098009,1098012,971975,973378,978907
CVE References: CVE-2017-13305,CVE-2017-17741,CVE-2017-18241,CVE-2017-18249,CVE-2018-1092,CVE-2018-1093,CVE-2018-1094,CVE-2018-12233,CVE-2018-3639,CVE-2018-3665,CVE-2018-5848
Sources used:
openSUSE Leap 42.3 (src):    kernel-debug-4.4.138-59.1, kernel-default-4.4.138-59.1, kernel-docs-4.4.138-59.1, kernel-obs-build-4.4.138-59.1, kernel-obs-qa-4.4.138-59.1, kernel-source-4.4.138-59.1, kernel-syms-4.4.138-59.1, kernel-vanilla-4.4.138-59.1
Comment 9 Swamp Workflow Management 2018-06-26 16:28:48 UTC
SUSE-SU-2018:1816-1: An update that solves 17 vulnerabilities and has 109 fixes is now available.

Category: security (important)
Bug References: 1009062,1012382,1019695,1019699,1022604,1022607,1022743,1024718,1031717,1035432,1036215,1041740,1043598,1044596,1045330,1056415,1056427,1060799,1066223,1068032,1068054,1068951,1070404,1073059,1073311,1075087,1075428,1076049,1076263,1076805,1078583,1079152,1080157,1080542,1080656,1081500,1081514,1081599,1082153,1082299,1082485,1082504,1082962,1082979,1083635,1083650,1083900,1084721,1085185,1085308,1086400,1086716,1087007,1087012,1087036,1087082,1087086,1087095,1088810,1088871,1089023,1089115,1089393,1089895,1090225,1090435,1090534,1090643,1090658,1090663,1090708,1090718,1090734,1090953,1090955,1091041,1091325,1091594,1091728,1091960,1092289,1092497,1092552,1092566,1092772,1092813,1092888,1092904,1092975,1093008,1093035,1093144,1093215,1093533,1093904,1093990,1094019,1094033,1094059,1094177,1094268,1094353,1094356,1094405,1094466,1094532,1094823,1094840,1095042,1095147,1096037,1096140,1096214,1096242,1096281,1096751,1096982,1097234,1097356,1098009,1098012,919144,971975,973378,978907,993388
CVE References: CVE-2017-13305,CVE-2017-17741,CVE-2017-18241,CVE-2017-18249,CVE-2018-1000199,CVE-2018-1065,CVE-2018-1092,CVE-2018-1093,CVE-2018-1094,CVE-2018-1130,CVE-2018-12233,CVE-2018-3639,CVE-2018-3665,CVE-2018-5803,CVE-2018-5848,CVE-2018-7492,CVE-2018-8781
Sources used:
SUSE Linux Enterprise Real Time Extension 12-SP3 (src):    kernel-rt-4.4.138-3.14.1, kernel-rt_debug-4.4.138-3.14.1, kernel-source-rt-4.4.138-3.14.1, kernel-syms-rt-4.4.138-3.14.1
Comment 10 David Chewning 2018-06-27 13:35:49 UTC
Sorry for being slow to respond. However, I do want to thank you and tell you this kernel update did resolve the issue.