Qualcomm QCA6174 [168c:003e] (rev 32) on Ubuntu Bionic fresh install has flakey wifi and no BT Bluetooth

Bug #1777258 reported by josh
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

On fresh install on Yoga920 of Bionic Beaver 18, wifi and bluetooth work. Then they degrade with BT not working withing a day or five, and wifi is consistently inconsistent. On the bluetooth gui, user is unable to turn bt on or off and the CLI shows no blocking on bt but it doesn't work.

I think this has to do with the Qualcomm QCA6174 [168c:003e] (rev 32) on Ubuntu Bionic and the ath10k_pci driver but Qualcomm nor Lenovo have answers.

https://paste.ubuntu.com/p/XC5PWRFywp/

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.19
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun 16 08:57:46 2018
InstallationDate: Installed on 2018-06-09 (6 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: phelix 1834 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=0690300c-b74d-4b47-925d-49298e311243
InstallationDate: Installed on 2018-06-16 (7 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc.
 Bus 001 Device 002: ID 04f2:b5da Chicony Electronics Co., Ltd
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80Y7
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-23-generic N/A
 linux-backports-modules-4.15.0-23-generic N/A
 linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 02/22/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 5NCN38WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo YOGA 920-13IKB
dmi.modalias: dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB:
dmi.product.family: YOGA 920-13IKB
dmi.product.name: 80Y7
dmi.product.version: Lenovo YOGA 920-13IKB
dmi.sys.vendor: LENOVO
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-06-16 (7 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Tags: bionic
Uname: Linux 4.18.0-041800rc1-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

Revision history for this message
josh (freedman-joshua) wrote :
affects: ubuntu-release-upgrader (Ubuntu) → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1777258

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc1

Revision history for this message
josh (freedman-joshua) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
josh (freedman-joshua) wrote : CRDA.txt

apport information

Revision history for this message
josh (freedman-joshua) wrote : CurrentDmesg.txt

apport information

Revision history for this message
josh (freedman-joshua) wrote : IwConfig.txt

apport information

Revision history for this message
josh (freedman-joshua) wrote : Lspci.txt

apport information

Revision history for this message
josh (freedman-joshua) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
josh (freedman-joshua) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
josh (freedman-joshua) wrote : ProcInterrupts.txt

apport information

Revision history for this message
josh (freedman-joshua) wrote : ProcModules.txt

apport information

Revision history for this message
josh (freedman-joshua) wrote : PulseList.txt

apport information

Revision history for this message
josh (freedman-joshua) wrote : RfKill.txt

apport information

Revision history for this message
josh (freedman-joshua) wrote : UdevDb.txt

apport information

Revision history for this message
josh (freedman-joshua) wrote : WifiSyslog.txt

apport information

Revision history for this message
josh (freedman-joshua) wrote :

After BT stopped working last time, I did a fresh install a week ago. BT worked fine. 5 mins ago it stopped working again.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
josh (freedman-joshua) wrote :

Linux darkle90210 4.18.0-041800rc1-generic #201806162031 SMP Sun Jun 17 00:34:22 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

I have updated to 4.18 and the problem persists.

description: updated
Revision history for this message
josh (freedman-joshua) wrote : ProcCpuinfoMinimal.txt

apport information

tags: added: kernel-bug-exists-upstream
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Can you attach dmesg when BT failed to work?

Revision history for this message
josh (freedman-joshua) wrote :

Anything specific I should be looking for? When I dmesg its a pretty long list.

Revision history for this message
josh (freedman-joshua) wrote :
Download full text (111.2 KiB)

[ 0.000000] Linux version 4.18.0-041800rc1-generic (kernel@tangerine) (gcc version 7.3.0 (Ubuntu 7.3.0-21ubuntu1)) #201806162031 SMP Sun Jun 17 00:34:22 UTC 2018
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.18.0-041800rc1-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
[ 0.000000] x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64
[ 0.000000] x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64
[ 0.000000] x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000059000-0x000000000009dfff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009e000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000027498fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000027499000-0x0000000027499fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x000000002749a000-0x000000002749afff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000002749b000-0x0000000028827fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000028828000-0x0000000029127fff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000029128000-0x000000002ed3dfff] usable
[ 0.000000] BIOS-e820: [mem 0x000000002ed3e000-0x000000002ef3dfff] type 20
[ 0.000000] BIOS-e820: [mem 0x000000002ef3e000-0x000000002f72dfff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000002f72e000-0x000000002ff7dfff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x000000002ff7e000-0x000000002fffdfff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x000000002fffe000-0x000000002fffefff] usable
[ 0.000000] BIOS-e820: [mem 0x000000002ffff000-0x000000003cffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fd000000-0x00000000fe7fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed84000-0x00000000fed84fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ffa00000-0x00000000ffffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x00000004c1ffffff] usable
[ 0.000000] NX (Execute Disable) protection: acti...

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

I guess you warm booted instead of cold booted your system?

Please power off the system, and boot with v4.18-rc1 again.

Revision history for this message
josh (freedman-joshua) wrote : Re: [Bug 1777258] Re: Qualcomm QCA6174 [168c:003e] (rev 32) on Ubuntu Bionic fresh install has flakey wifi and no BT Bluetooth
Download full text (102.9 KiB)

[ 0.000000] Linux version 4.18.0-041800rc1-generic (kernel@tangerine)
(gcc version 7.3.0 (Ubuntu 7.3.0-21ubuntu1)) #201806162031 SMP Sun Jun 17
00:34:22 UTC 2018
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.18.0-041800rc1-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point
registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds
registers'
[ 0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
[ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
[ 0.000000] x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64
[ 0.000000] x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64
[ 0.000000] x86/fpu: Enabled xstate features 0x1f, context size is 960
bytes, using 'compacted' format.
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff]
reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000059000-0x000000000009dfff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009e000-0x00000000000fffff]
reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000027498fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000027499000-0x0000000027499fff] ACPI
NVS
[ 0.000000] BIOS-e820: [mem 0x000000002749a000-0x000000002749afff]
reserved
[ 0.000000] BIOS-e820: [mem 0x000000002749b000-0x0000000028827fff] usable
[ 0.000000] BIOS-e820: [mem 0x0000000028828000-0x0000000029127fff]
reserved
[ 0.000000] BIOS-e820: [mem 0x0000000029128000-0x000000002ed3dfff] usable
[ 0.000000] BIOS-e820: [mem 0x000000002ed3e000-0x000000002ef3dfff] type
20
[ 0.000000] BIOS-e820: [mem 0x000000002ef3e000-0x000000002f72dfff]
reserved
[ 0.000000] BIOS-e820: [mem 0x000000002f72e000-0x000000002ff7dfff] ACPI
NVS
[ 0.000000] BIOS-e820: [mem 0x000000002ff7e000-0x000000002fffdfff] ACPI
data
[ 0.000000] BIOS-e820: [mem 0x000000002fffe000-0x000000002fffefff] usable
[ 0.000000] BIOS-e820: [mem 0x000000002ffff000-0x000000003cffffff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fd000000-0x00000000fe7fffff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed10000-0x00000000fed19fff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed84000-0x00000000fed84fff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ffa00000-0x00000000ffffffff]
reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x00000004c1ffffff] usable
[ 0.000000] NX (Execute Disable) protection: acti...

Revision history for this message
josh (freedman-joshua) wrote :
Download full text (90.0 KiB)

I can see BT stuff when cold booting. Unable to test right now, but the
ability to see devices was not available before, so I think it probably
works. It must be a resume and warm boot issue?

On Tue, Jun 26, 2018 at 9:37 PM Joshua Freedman <email address hidden>
wrote:

> [ 0.000000] Linux version 4.18.0-041800rc1-generic (kernel@tangerine)
> (gcc version 7.3.0 (Ubuntu 7.3.0-21ubuntu1)) #201806162031 SMP Sun Jun 17
> 00:34:22 UTC 2018
> [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.18.0-041800rc1-generic
> root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
> [ 0.000000] KERNEL supported cpus:
> [ 0.000000] Intel GenuineIntel
> [ 0.000000] AMD AuthenticAMD
> [ 0.000000] Centaur CentaurHauls
> [ 0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating
> point registers'
> [ 0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
> [ 0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
> [ 0.000000] x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds
> registers'
> [ 0.000000] x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
> [ 0.000000] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
> [ 0.000000] x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64
> [ 0.000000] x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64
> [ 0.000000] x86/fpu: Enabled xstate features 0x1f, context size is 960
> bytes, using 'compacted' format.
> [ 0.000000] BIOS-provided physical RAM map:
> [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff]
> usable
> [ 0.000000] BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff]
> reserved
> [ 0.000000] BIOS-e820: [mem 0x0000000000059000-0x000000000009dfff]
> usable
> [ 0.000000] BIOS-e820: [mem 0x000000000009e000-0x00000000000fffff]
> reserved
> [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x0000000027498fff]
> usable
> [ 0.000000] BIOS-e820: [mem 0x0000000027499000-0x0000000027499fff] ACPI
> NVS
> [ 0.000000] BIOS-e820: [mem 0x000000002749a000-0x000000002749afff]
> reserved
> [ 0.000000] BIOS-e820: [mem 0x000000002749b000-0x0000000028827fff]
> usable
> [ 0.000000] BIOS-e820: [mem 0x0000000028828000-0x0000000029127fff]
> reserved
> [ 0.000000] BIOS-e820: [mem 0x0000000029128000-0x000000002ed3dfff]
> usable
> [ 0.000000] BIOS-e820: [mem 0x000000002ed3e000-0x000000002ef3dfff] type
> 20
> [ 0.000000] BIOS-e820: [mem 0x000000002ef3e000-0x000000002f72dfff]
> reserved
> [ 0.000000] BIOS-e820: [mem 0x000000002f72e000-0x000000002ff7dfff] ACPI
> NVS
> [ 0.000000] BIOS-e820: [mem 0x000000002ff7e000-0x000000002fffdfff] ACPI
> data
> [ 0.000000] BIOS-e820: [mem 0x000000002fffe000-0x000000002fffefff]
> usable
> [ 0.000000] BIOS-e820: [mem 0x000000002ffff000-0x000000003cffffff]
> reserved
> [ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff]
> reserved
> [ 0.000000] BIOS-e820: [mem 0x00000000fd000000-0x00000000fe7fffff]
> reserved
> [ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff]
> reserved
> [ 0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed00fff]
> reserved
> [ 0.000000] BIOS-e820: [mem 0x0000000...

Revision history for this message
josh (freedman-joshua) wrote :

The bt works on a cold boot.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

The BT issue is pretty similar to LP: #1757218.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.