Can you attach dmesg with "btusb.enable_autosuspend=0", and another
dmesg without the parameter?
I am guessing that ath10k and btusb can't get probed at the same time.
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
QCA9377 isn't being recognized sometimes
Status in linux package in Ubuntu:
Sometimes, the Wireless Network Card QCA9377 is not recognized on
boot. This caused, on prior versions, a kernel panic at boot. With
Bionic, the system boots but is unable to use wireless network. On
dmesg there are messages like:
[ 2.680590] usb 1-7: new full-speed USB device number 7 using xhci_hcd
[ 2.808640] usb 1-7: device descriptor read/64, error -71
[ 3.044337] usb 1-7: device descriptor read/64, error -71
[ 3.280064] usb 1-7: new full-speed USB device number 8 using xhci_hcd
[ 3.408245] usb 1-7: device descriptor read/64, error -71
[ 3.644244] usb 1-7: device descriptor read/64, error -71
[ 3.752193] usb usb1-port7: attempt power cycle
[ 4.404591] usb 1-7: new full-speed USB device number 9 using xhci_hcd
[ 4.404904] usb 1-7: Device not responding to setup address.
[ 4.612478] usb 1-7: Device not responding to setup address.
[ 4.820588] usb 1-7: device not accepting address 9, error -71
[ 4.948591] usb 1-7: new full-speed USB device number 10 using xhci_hcd
[ 4.949109] usb 1-7: Device not responding to setup address.
[ 5.156893] usb 1-7: Device not responding to setup address.
[ 5.364589] usb 1-7: device not accepting address 10, error -71
[ 5.364655] usb usb1-port7: unable to enumerate USB device
And lspci and lsusb don't show the wireless network card. The
alternative is to turn the system off. Reboot don't work and reboot to
Windows 10 also don't. The system must be powered off to restore
functionality. Then, on the next boot, it works properly.
However, after the system is turned off, it may cause the issue again.
This is not 100% consistent, but mostly it cycles between powering off
and powering on the notebook as:
Work -> Don't work -> Work -> Don't work
On Windows 10 this doesn't happen but when happens on Ubuntu, it's
possible to reboot and see the status on Windows 10 too: on Device
Manager it's shown a unidentified USB device at 1-7. Sometimes, on
Windows 10's Network Devices it's shown, instead of the QCA9377, from
four to six different devices with generic names and Bluetooth and/or
Wireless don't work.
When turning Ubuntu off, there are messages that appears a few
instants before the system is turned off:
Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403388]
ath10k_pci 0000:02:00.0: failed to install key for vdev 0 peer
Mar 18 18:27:26 usuario-Lenovo-ideapad-310-14ISK kernel: [14146.403399]
wlp2s0: failed to remove key (0, xx:xx:xx:xx:xx:xx) from hardware (-110)
Generally, only the second message appears (but both are recorded on
kern.log). The MAC adress is the one from the router, not from the
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-12-generic 4.15.0-12.13
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
USER PID ACCESS COMMAND
/dev/snd/controlC0: usuario 1364 F.... pulseaudio
/dev/snd/seq: usuario 1258 F.... timidity
Date: Tue Mar 20 14:43:42 2018
InstallationDate: Installed on 2017-06-13 (279 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: LENOVO 80UG
ProcFB: 0 inteldrmfb
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Toronto 4A2
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.version: Lenovo ideapad 310-14ISK
dmi.product.version: Lenovo ideapad 310-14ISK
To manage notifications about this bug go to:
Mailing list: https://launchpad.net/~kernel-packages
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp