Finally, after 10 kernels built, I've obtained the result. Here is the
output:
1fdb926974695d3dbc05a429bafa266fdd16510e is the first new commit
commit 1fdb926974695d3dbc05a429bafa266fdd16510e
Author: Hans de Goede <hdego...@redhat.com>
Date: Tue Feb 20 09:06:18 2018 +0100
Bluetooth: btusb: Use DMI matching for QCA reset_resume quirking
Commit 61f5acea8737 ("Bluetooth: btusb: Restore QCA Rome suspend/resume fix
with a "rewritten" version") applied the USB_QUIRK_RESET_RESUME to all QCA
USB Bluetooth modules. But it turns out that the resume problems are not
caused by the QCA Rome chipset, on most platforms it resumes fine. The
resume problems are actually a platform problem (likely the platform
cutting all power when suspended).
The USB_QUIRK_RESET_RESUME quirk also disables runtime suspend, so by
matching on usb-ids, we're causing all boards with these chips to use extra
power, to fix resume problems which only happen on some boards.
This commit fixes this by applying the quirk based on DMI matching instead
of on usb-ids, so that we match the platform and not the chipset.
Here is the /sys/kernel/debug/usb/devices for the Bluetooth module:
T: Bus=01 Lev=01 Prnt=01 Port=07 Cnt=04 Dev#= 5 Spd=12 MxCh= 0
D: Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0cf3 ProdID=e300 Rev= 0.01
C:* #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I:* If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=81(I) Atr=03(Int.) MxPS= 16 Ivl=1ms
E: Ad=82(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
I:* If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 0 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 0 Ivl=1ms
I: If#= 1 Alt= 1 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 9 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 9 Ivl=1ms
I: If#= 1 Alt= 2 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 17 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 17 Ivl=1ms
I: If#= 1 Alt= 3 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 25 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 25 Ivl=1ms
I: If#= 1 Alt= 4 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
BugLink: https://bugzilla.redhat.com/show_bug.cgi?id=1514836
Fixes: 61f5acea8737 ("Bluetooth: btusb: Restore QCA Rome suspend/resume..")
Cc: sta...@vger.kernel.org
Cc: Brian Norris <briannor...@chromium.org>
Cc: Kai-Heng Feng <kai.heng.f...@canonical.com>
Reported-and-tested-by: Kevin Fenzi <ke...@scrye.com>
Signed-off-by: Hans de Goede <hdego...@redhat.com>
Signed-off-by: Marcel Holtmann <mar...@holtmann.org>
:040000 040000 2930a43c59c0e767763843528fa8526d4e17b764
626944fe592accb35e33c69be141dbcee910910c M drivers
** Bug watch added: Red Hat Bugzilla #1514836
https://bugzilla.redhat.com/show_bug.cgi?id=1514836
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1757218
Title:
QCA9377 isn't being recognized sometimes
Status in linux package in Ubuntu:
Confirmed
Bug description:
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
xx:xx:xx:xx:xx:xx: -110
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
wireless card.
ProblemType: Bug
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
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: usuario 1364 F.... pulseaudio
/dev/snd/seq: usuario 1258 F.... timidity
CurrentDesktop: XFCE
Date: Tue Mar 20 14:43:42 2018
HibernationDevice: RESUME=UUID=9f36068f-c6d6-4fd6-87d5-46f1f5247563
InstallationDate: Installed on 2017-06-13 (279 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: LENOVO 80UG
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet
RelatedPackageVersions:
linux-restricted-modules-4.15.0-12-generic N/A
linux-backports-modules-4.15.0-12-generic N/A
linux-firmware 1.173
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2017-10-20 (151 days ago)
dmi.bios.date: 07/10/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: 0XCN43WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Toronto 4A2
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 310-14ISK
dmi.modalias:
dmi:bvnLENOVO:bvr0XCN43WW:bd07/10/2017:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80UG
dmi.product.version: Lenovo ideapad 310-14ISK
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757218/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
