ath10k_pci (QCA9377) firmware crashes when charger plugged

[Eduardo P. Gomez]

This issue only occurs when charger is plugged. My network adapter is built-in in my laptop (it's not an usb).
I'm also connected in a 5ghz network, so i suggest using it.

=== How to reproduce ==
* shutdown your laptop (do not use reboot option);
* connect charger to laptop and turn it on; (the firmware should start and connect to the 5ghz network)
* If no error is thrown, continue using your laptop and your wlan device. It took me about 5 minutes to get a "firmware crash" error with code "-11".
* If the firmware crashed, reboot (using shutdown command) your laptop with charger plugged in.
You might similar error: "device descriptor read/64, error -71"
* Temporary fix: Unplug the charger and reboot using shutdown command (two times as it might not work for the first)

=== Device Info: ===
# uname -a && lsb_release -a:
Linux eduapps 6.2.0-33-generic #33-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 5 14:49:19 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 23.04
Release: 23.04
Codename: lunar

# apt-cache policy linux-firmware:
linux-firmware:
  Instalado: 20230323.gitbcdcfbcf-0ubuntu1.6
  Candidato: 20230323.gitbcdcfbcf-0ubuntu1.6
  Tabela de versão:
 *** 20230323.gitbcdcfbcf-0ubuntu1.6 500
        500 http://br.archive.ubuntu.com/ubuntu lunar-updates/main amd64 Packages
        500 http://br.archive.ubuntu.com/ubuntu lunar-updates/main i386 Packages
        100 /var/lib/dpkg/status
     20230323.gitbcdcfbcf-0ubuntu1.2 500
        500 http://br.archive.ubuntu.com/ubuntu lunar-security/main amd64 Packages
        500 http://br.archive.ubuntu.com/ubuntu lunar-security/main i386 Packages
     20230323.gitbcdcfbcf-0ubuntu1 500
        500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
        500 http://br.archive.ubuntu.com/ubuntu lunar/main i386 Packages

# cat /var/log/dmesg.0:
[...]
[ 9.852826] kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device
[ 9.964095] kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC256: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[ 9.964109] kernel: snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 9.964112] kernel: snd_hda_codec_realtek hdaudioC0D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0)
[ 9.964115] kernel: snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0
[ 9.964117] kernel: snd_hda_codec_realtek hdaudioC0D0: inputs:
[ 9.964120] kernel: snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19
[ 9.964122] kernel: snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x1b
[ 9.964124] kernel: snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x13
[ 10.037952] kernel: input: HDA Intel PCH Headphone as /devices/pci0000:00/0000:00:0e.0/sound/card0/input13
[ 10.038029] kernel: input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:0e.0/sound/card0/input14
[ 10.038091] kernel: input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:0e.0/sound/card0/input15
[ 10.038153] kernel: input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:0e.0/sound/card0/input16
[ 13.658522] kernel: kauditd_printk_skb: 73 callbacks suppressed
[ 13.658528] kernel: audit: type=1400 audit(1695260291.507:85): apparmor="DENIED" operation="capable" class="cap" profile="/snap/snapd/20092/usr/lib/snapd/snap-confine" pid=835 comm="snap-confine" capability=12 capname="net_admin"
[ 13.659312] kernel: audit: type=1400 audit(1695260291.507:86): apparmor="DENIED" operation="capable" class="cap" profile="/snap/snapd/20092/usr/lib/snapd/snap-confine" pid=835 comm="snap-confine" capability=38 capname="perfmon"
[ 13.703536] kernel: loop22: detected capacity change from 0 to 8
[ 14.776596] kernel: usb 1-1: new full-speed USB device number 8 using xhci_hcd
[ 14.905067] kernel: usb 1-1: device descriptor read/64, error -71
[ 15.148740] kernel: usb 1-1: device descriptor read/64, error -71
[ 15.392606] kernel: usb 1-1: new full-speed USB device number 9 using xhci_hcd
[ 15.524631] kernel: usb 1-1: device descriptor read/64, error -71
---
ProblemType: Bug
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: eduardo 1647 F.... wireplumber
 /dev/snd/seq: eduardo 1641 F.... pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Dependencies: firmware-sof-signed 2.2.4-1
DistroRelease: Ubuntu 23.04
InstallationDate: Installed on 2023-06-24 (88 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
 Bus 001 Device 003: ID 13d3:5a11 IMC Networks USB2.0 VGA UVC WebCam
 Bus 001 Device 002: ID 04ca:301c Lite-On Technology Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. VivoBook 15_ASUS Laptop X540MA_X540MA
Package: linux-firmware 20230323.gitbcdcfbcf-0ubuntu1.6
PackageArchitecture: all
ProcEnviron:
 LANG=pt_BR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=a454b9cb-2da2-47bf-bae2-7ffe871f895b ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-6.2.0-33-generic N/A
 linux-backports-modules-6.2.0-33-generic N/A
 linux-firmware 20230323.gitbcdcfbcf-0ubuntu1.6
Tags: lunar
Uname: Linux 6.2.0-33-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 01/12/2021
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X540MA.319
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X540MA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX540MA.319:bd01/12/2021:br5.13:svnASUSTeKCOMPUTERINC.:pnVivoBook15_ASUSLaptopX540MA_X540MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: VivoBook
dmi.product.name: VivoBook 15_ASUS Laptop X540MA_X540MA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

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 2036862

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.

[Eduardo P. Gomez (eduapps)]

apport information

[Eduardo P. Gomez (eduapps)]

apport information

[Eduardo P. Gomez (eduapps)]

apport information

[Eduardo P. Gomez (eduapps)]

apport information

[Eduardo P. Gomez (eduapps)]

apport information

[Eduardo P. Gomez (eduapps)]

apport information

[Eduardo P. Gomez (eduapps)]

apport information

[Eduardo P. Gomez (eduapps)]

apport information

[Eduardo P. Gomez (eduapps)]

apport information

[Eduardo P. Gomez (eduapps)]

apport information

[Eduardo P. Gomez (eduapps)]

apport information

[Eduardo P. Gomez (eduapps)]

apport information

[Eduardo P. Gomez (eduapps)]

apport information

[Eduardo P. Gomez (eduapps)]

apport information

[Eduardo P. Gomez (eduapps)]

apport information

[Juerg Haefliger (juergh)]

I'm not seeing any problems in the provided dmesg log. Please attach full logs that show the problems. You can use 'journalctl -b X' to show logs from previous boots.

$ sudo journalctl -b 0 # current boot
$ sudo journalctl -b -1 # previous boot

and so on.

Show all available boot logs:
$ journalctl --list-boots

[Eduardo P. Gomez (eduapps)]

Indeed, these logs are from the current boot. When I get home I will
reproduce this bug.

Em sex., 22 de set. de 2023 03:10, Juerg Haefliger <
<email address hidden>> escreveu:

> I'm not seeing any problems in the provided dmesg log. Please attach
> full logs that show the problems. You can use 'journalctl -b X' to show
> logs from previous boots.
>
> $ sudo journalctl -b 0 # current boot
> $ sudo journalctl -b -1 # previous boot
>
> and so on.
>
> Show all available boot logs:
> $ journalctl --list-boots
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2036862
>
> Title:
> ath10k_pci (QCA9377) firmware crashes when charger plugged
>
> Status in linux package in Ubuntu:
> Incomplete
> Status in linux-firmware package in Ubuntu:
> New
>
> Bug description:
> This issue only occurs when charger is plugged. My network adapter is
> built-in in my laptop (it's not an usb).
> I'm also connected in a 5ghz network, so i suggest using it.
>
> === How to reproduce ==
> * shutdown your laptop (do not use reboot option);
> * connect charger to laptop and turn it on; (the firmware should start
> and connect to the 5ghz network)
> * If no error is thrown, continue using your laptop and your wlan
> device. It took me about 5 minutes to get a "firmware crash" error with
> code "-11".
> * If the firmware crashed, reboot (using shutdown command) your laptop
> with charger plugged in.
> You might similar error: "device descriptor read/64, error -71"
> * Temporary fix: Unplug the charger and reboot using shutdown command
> (two times as it might not work for the first)
>
> === Device Info: ===
> # uname -a && lsb_release -a:
> Linux eduapps 6.2.0-33-generic #33-Ubuntu SMP PREEMPT_DYNAMIC Tue Sep 5
> 14:49:19 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description: Ubuntu 23.04
> Release: 23.04
> Codename: lunar
>
> # apt-cache policy linux-firmware:
> linux-firmware:
> Instalado: 20230323.gitbcdcfbcf-0ubuntu1.6
> Candidato: 20230323.gitbcdcfbcf-0ubuntu1.6
> Tabela de versão:
> *** 20230323.gitbcdcfbcf-0ubuntu1.6 500
> 500 http://br.archive.ubuntu.com/ubuntu lunar-updates/main
> amd64 Packages
> 500 http://br.archive.ubuntu.com/ubuntu lunar-updates/main i386
> Packages
> 100 /var/lib/dpkg/status
> 20230323.gitbcdcfbcf-0ubuntu1.2 500
> 500 http://br.archive.ubuntu.com/ubuntu lunar-security/main
> amd64 Packages
> 500 http://br.archive.ubuntu.com/ubuntu lunar-security/main
> i386 Packages
> 20230323.gitbcdcfbcf-0ubuntu1 500
> 500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64
> Packages
> 500 http://br.archive.ubuntu.com/ubuntu lunar/main i386 Packages
>
> # cat /var/log/dmesg.0:
> [...]
> [ 9.852826] kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame
> buffer device
> [ 9.964095] kernel: snd_hda_codec_realtek hdaudioC0D0: autoconfig for
> ALC256: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
> [ 9.964109] kernel: snd_hda_codec_realtek hdau...

[Eduardo P. Gomez (eduapps)]

Indeed, these logs were from the current boot. When I get home I will reproduce this bug.

[Eduardo P. Gomez (eduapps)]

That's the dmesg output from first boot (after wifi breaks). I could include the logs from the time it broke, but it may be contamined by other actions (my laptop has been suspended, and its known for causing troubles).

I think it should be enough proof that there's some truth behind my infos. I did almost the same step by step from before. Almost, except the fact my laptop was charging while suspended and I'm in a different Wi-Fi network (also 5Ghz).

I did opened the lid switch and wifi was already gone. I turned off the laptop without the charger and the result was this log. Restarted again and went back to normal.

[Eduardo P. Gomez (eduapps)]

Here it is, the firmware crash it at "7119.478819" There's also interesting data in the end of the file.
It happened when i did plug the charger when my laptop was at 4%.

Given the fact that it's related with the charger, and sometimes it also happens during the suspension. I suspect it's caused by the powersave mode.

[Eduardo P. Gomez (eduapps)]

Journalctl file from the firmware crash

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Eduardo P. Gomez (eduapps)]

Deleted unimportant attachments. This will save us precious time.

Also, i'm unfamiliar with LaunchPad, if i were going to check the code to see what's going on, where i'm supposed to go?

[Juerg Haefliger (juergh)]

https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/lunar/tree/?h=Ubuntu-6.2.0-33.33