Bug 1961697

Summary: Qualcomm ath10k driver crash
Product: [Fedora] Fedora Reporter: David <kitt997>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 35CC: acaringi, adscvr, airlied, alciregi, bskeggs, emaster987, hdegoede, jarodwilson, jeremy, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, steved
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-12-13 15:23:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Kernel log, as per form request
none
Log of kernel when Qualcomm driver crashed and the system got frozen
none
dmesg output
none
dmesg output none

Description David 2021-05-18 14:02:20 UTC 
Created attachment 1784457 [details]
Kernel log, as per form request

1. Please describe the problem:
My WiFi adapter keeps crashing, and it's been years now.

2. What is the Version-Release number of the kernel:
5.11.20-300.fc34.x86_64

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
No. It basically never worked reliably, varying in MTTF from version to version.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Simply connect to an AP. After some hours of use (when lucky, sometimes after 10') driver crashes. When it gets bad, it completely freezes my system and I have to hard reset the machine. 
This is BAD.

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
Tried a live rawhide image, happened as well.

6. Are you running any modules that not shipped with directly Fedora's kernel?:
No.

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.
Logs added as attachment.

Please note people from linux-firmware suggested it is a kernel driver regression.
Comment 1 Emanuele Spirito 2021-05-31 07:04:05 UTC 
Created attachment 1788152 [details]
Log of kernel when Qualcomm driver crashed and the system got frozen

I can confirm I have the same bug with my Qualcomm driver ath10. I made the log after rebooting using the command
journalctl -k -b > dmesg.txt
This time even plasmashell and input from touchpad crashed.
Comment 2 Ben Cotton 2022-05-12 15:44:32 UTC 
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
Comment 3 Ben Cotton 2022-06-07 22:35:36 UTC 
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 4 David 2022-07-02 21:02:31 UTC 
Bug still persists today, and with kernel 5.18 started worsening (if possible). After bootup, 2 out of 4 times the chip is already gone and when it's not, after some 30-50' it crashes anyway.
Comment 5 David 2022-07-02 21:49:16 UTC 
Created attachment 1894162 [details]
dmesg output
Comment 6 David 2022-07-03 09:36:20 UTC 
Created attachment 1894218 [details]
dmesg output
Comment 7 Ben Cotton 2022-11-29 16:57:29 UTC 
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
Comment 8 Ben Cotton 2022-12-13 15:23:30 UTC 
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.