Killer Wireless 1525 firmware crashes on suspend

Bug #1827879 reported by Sander Los
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Ubuntu
Expired
Undecided
Unassigned
linux (Ubuntu)
Expired
Undecided
Unassigned
network-manager (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Problem:
Ubuntu running on Alienware 17 R2 system hangs on suspend. The Keyboard LED's stay on and FAN keeps running. Strangely this does not happen in Fedora 29 (Kernel 4.18 & same board firmware)

System:
Ubuntu 19.04
Kernel 5.0.0-13-generic
Wireless chipset Killer Wireless 1525 (Atheros QCA6174, hw2.1)
Wireless info:
       description: Wireless interface
       product: QCA6174 802.11ac Wireless Network Adapter
       vendor: Qualcomm Atheros
       physical id: 0
       bus info: pci@0000:03:00.0
       logical name: wlp3s0
       version: 20
       serial: 40:b8:9a:ca:2b:99
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.0-13-generic firmware=SW_RM.1.1.1-00157-QCARMSWPZ-1 ip=192.168.55.161 latency=0 link=yes multicast=yes wireless=IEEE 802.11
       resources: irq:32 memory:f6800000-f69fffff

My attempts:
1. Tried other kernels:
5.0.12, 4.20.17, 4.19.7, 4.18.16, 4.18.0, 4.16.0, 4.14.114

2. Tried several distro's based on ubuntu -> all have the same issue

3. Checked firmware from Fedora 29 (md5sum was equal) and updated firmware (not available, using latest)

4. Created systemd scripts for disabling & enabling the driver, this causes the same crashes in /var/log/syslog
See: https://forum.manjaro.org/t/solved-qca6174-freez-after-suspend/66232/11

5. Physically replaced Killer 1525 with Intel 8260 --> problem is gone, standby works perfectly

Of course i want to be able to use the 1525, so please help me solve the issue.
Happy to perform additional debugging if required.
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: sander 1527 F.... pulseaudio
 /dev/snd/controlC0: sander 1527 F.... pulseaudio
CurrentDesktop: KDE
DistroRelease: Ubuntu 19.04
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 192.168.55.1 dev wlp3s0 proto dhcp metric 600
 169.254.0.0/16 dev wlp3s0 scope link metric 1000
 192.168.55.0/24 dev wlp3s0 proto kernel scope link src 192.168.55.58 metric 600
MachineType: Alienware Alienware 17 R2
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
NonfreeKernelModules: nvidia_modeset nvidia
Package: network-manager 1.16.0-0ubuntu2
PackageArchitecture: amd64
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=9f06fd28-fdb2-4ada-986f-1e7eb1b87882 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-15-generic N/A
 linux-backports-modules-5.0.0-15-generic N/A
 linux-firmware 1.178.1
Tags: disco
Uname: Linux 5.0.0-15-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/31/2017
dmi.bios.vendor: Alienware
dmi.bios.version: A08
dmi.board.name: Alienware 17 R2
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Alienware
dmi.chassis.version: A08
dmi.modalias: dmi:bvnAlienware:bvrA08:bd03/31/2017:svnAlienware:pnAlienware17R2:pvrA08:rvnAlienware:rnAlienware17R2:rvrA00:cvnAlienware:ct8:cvrA08:
dmi.product.family: Alienware 17 R2
dmi.product.name: Alienware 17 R2
dmi.product.sku: Alienware 15
dmi.product.version: A08
dmi.sys.vendor: Alienware
nmcli-nm:
 RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
 running 1.16.0 connected started full enabled enabled enabled enabled enabled

Revision history for this message
Sander Los (sander-6) wrote :
Download full text (3.7 KiB)

The Crashlog:
May 2 12:20:17 AW17 kernel: [ 33.622257] ath10k_pci 0000:03:00.0: firmware crashed! (guid a4d786d4-4867-4145-a4d6-3a0e2fa1b406)
May 2 12:20:17 AW17 kernel: [ 33.622265] ath10k_pci 0000:03:00.0: qca6174 hw2.1 target 0x05010000 chip_id 0x003405ff sub 1a56:1525
May 2 12:20:17 AW17 kernel: [ 33.622267] ath10k_pci 0000:03:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
May 2 12:20:17 AW17 kernel: [ 33.622651] ath10k_pci 0000:03:00.0: firmware ver SW_RM.1.1.1-00157-QCARMSWPZ-1 api 5 features ignore-otp,no-4addr-pad crc32 10bf8e08
May 2 12:20:17 AW17 kernel: [ 33.622830] ath10k_pci 0000:03:00.0: board_file api 2 bmi_id N/A crc32 ae2e275a
May 2 12:20:17 AW17 kernel: [ 33.622833] ath10k_pci 0000:03:00.0: htt-ver 3.1 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
May 2 12:20:17 AW17 kernel: [ 33.624871] ath10k_pci 0000:03:00.0: firmware register dump:
May 2 12:20:17 AW17 kernel: [ 33.624876] ath10k_pci 0000:03:00.0: [00]: 0x05010000 0x00000000 0x0092E4DC 0x6C9F52F4
May 2 12:20:17 AW17 kernel: [ 33.624879] ath10k_pci 0000:03:00.0: [04]: 0x0092E4DC 0x00060130 0x00000018 0x0041A760
May 2 12:20:17 AW17 kernel: [ 33.624882] ath10k_pci 0000:03:00.0: [08]: 0x6C9F52E0 0x00400000 0x00000000 0x000A5C88
May 2 12:20:17 AW17 kernel: [ 33.624885] ath10k_pci 0000:03:00.0: [12]: 0x0000000D 0x00000000 0x0096C09C 0x0096C0A7
May 2 12:20:17 AW17 kernel: [ 33.624888] ath10k_pci 0000:03:00.0: [16]: 0x00000004 0x0040A090 0x0000FFFF 0x00000001
May 2 12:20:17 AW17 kernel: [ 33.624891] ath10k_pci 0000:03:00.0: [20]: 0x80996343 0x0041A7D0 0x0044FD68 0x0040D400
May 2 12:20:17 AW17 kernel: [ 33.624894] ath10k_pci 0000:03:00.0: [24]: 0x80942BC4 0x0041A790 0x6C9F52E0 0x00400000
May 2 12:20:17 AW17 kernel: [ 33.624896] ath10k_pci 0000:03:00.0: [28]: 0x0041A7B0 0x0041A790 0x00000024 0x00000000
May 2 12:20:17 AW17 kernel: [ 33.624899] ath10k_pci 0000:03:00.0: [32]: 0x80947BA7 0x0041A7B0 0x00404D88 0x0040E074
May 2 12:20:17 AW17 kernel: [ 33.624902] ath10k_pci 0000:03:00.0: [36]: 0x6C9F52C0 0x00000000 0x00000000 0x00000001
May 2 12:20:17 AW17 kernel: [ 33.624905] ath10k_pci 0000:03:00.0: [40]: 0x809BDECC 0x0041A7D0 0x00404D88 0x0040E074
May 2 12:20:17 AW17 kernel: [ 33.624907] ath10k_pci 0000:03:00.0: [44]: 0x004124C4 0x00404DB4 0x0000FFFF 0x00000001
May 2 12:20:17 AW17 kernel: [ 33.624910] ath10k_pci 0000:03:00.0: [48]: 0x8099638C 0x0041A7F0 0x00404D88 0x00000000
May 2 12:20:17 AW17 kernel: [ 33.624913] ath10k_pci 0000:03:00.0: [52]: 0x00000000 0x004124C4 0x00404DAC 0x00000005
May 2 12:20:17 AW17 kernel: [ 33.624916] ath10k_pci 0000:03:00.0: [56]: 0x80992076 0x0041A810 0x0044FD68 0x0046FFE8
May 2 12:20:17 AW17 kernel: [ 33.624918] ath10k_pci 0000:03:00.0: Copy Engine register dump:
May 2 12:20:17 AW17 kernel: [ 33.624937] ath10k_pci 0000:03:00.0: [00]: 0x00034400 1 1 3 3
May 2 12:20:17 AW17 kernel: [ 33.624952] ath10k_pci 0000:03:00.0: [01]: 0x00034800 22 22 217 218
May 2 12:20:17 AW17 kernel: [ 33.624966] ath10k_pci 0000:03:00.0: [02]: 0x00034c00 7 7 70 71
May 2 12:20:17 AW17 kernel: [ 33.624979] ath10k_pci 0000:03:00.0: [03]: 0x00035000 19 19 20 19
May ...

Read more...

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1827879/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Sander Los (sander-6) wrote :

Some additional information: It looks like NetworkManager is part of the problem / solution.
--> Linked to networkmanager <--
If wifi is disabled (nmcli radio wifi off) the suspend works as expected.
Unfortunately, when scripting this into a systemctl script hooking to suspend.target, networkmanager is killed before the script is executed, thus networkmanager cannot respond anymore to the command.

Example of this systemctl script included here:

[Unit]
Description=Network suspend service
Before=sleep.target
StopWhenUnneeded=yes

[Service]
User=root
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/bin/sudo -u $USER /bin/bash -lc 'nmcli radio wifi off'
ExecStart=/usr/bin/sleep 5

[Install]
WantedBy=sleep.target

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 1827879

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
tags: added: disco
Revision history for this message
Sander Los (sander-6) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Sander Los (sander-6) wrote : CRDA.txt

apport information

Revision history for this message
Sander Los (sander-6) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Sander Los (sander-6) wrote : Dependencies.txt

apport information

Revision history for this message
Sander Los (sander-6) wrote : IpAddr.txt

apport information

Revision history for this message
Sander Los (sander-6) wrote : IwConfig.txt

apport information

Revision history for this message
Sander Los (sander-6) wrote : Lspci.txt

apport information

Revision history for this message
Sander Los (sander-6) wrote : Lsusb.txt

apport information

Revision history for this message
Sander Los (sander-6) wrote : NetDevice.enp2s0.txt

apport information

Revision history for this message
Sander Los (sander-6) wrote : NetDevice.lo.txt

apport information

Revision history for this message
Sander Los (sander-6) wrote : NetDevice.wlp3s0.txt

apport information

Revision history for this message
Sander Los (sander-6) wrote : NetworkManager.conf.txt

apport information

Revision history for this message
Sander Los (sander-6) wrote : PciNetwork.txt

apport information

Revision history for this message
Sander Los (sander-6) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Sander Los (sander-6) wrote : ProcEnviron.txt

apport information

Revision history for this message
Sander Los (sander-6) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Sander Los (sander-6) wrote : ProcModules.txt

apport information

Revision history for this message
Sander Los (sander-6) wrote : PulseList.txt

apport information

Revision history for this message
Sander Los (sander-6) wrote : RfKill.txt

apport information

Revision history for this message
Sander Los (sander-6) wrote : UdevDb.txt

apport information

Revision history for this message
Sander Los (sander-6) wrote : WifiSyslog.txt

apport information

Revision history for this message
Sander Los (sander-6) wrote : nmcli-con.txt

apport information

Revision history for this message
Sander Los (sander-6) wrote : nmcli-dev.txt

apport information

Revision history for this message
Sander Los (sander-6) wrote :

Please note that the killer wireless card is replaced by intel when running apport-collect.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Does the issue still happen?

Revision history for this message
Sander Los (sander-6) wrote :

Yes, nothing changed as far as i know, so the issue remains

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

Please run `sudo modprobe -r btusb` before suspend and see if it helps.

Changed in network-manager (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Ubuntu because there has been no activity for 60 days.]

Changed in ubuntu:
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in network-manager (Ubuntu):
status: Incomplete → Expired
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.