Bug 2034244 - Wifi driver will crash, forcing a reboot or a logout
Summary: Wifi driver will crash, forcing a reboot or a logout
Keywords:
Status: CLOSED DUPLICATE of bug 1846802
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 35
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-20 13:37 UTC by Ben Bromley
Modified: 2021-12-20 13:45 UTC (History)
18 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-12-20 13:45:52 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ben Bromley 2021-12-20 13:37:19 UTC
1. Please describe the problem:

Wifi driver will crash, forcing a reboot or a logout.


2. What is the Version-Release number of the kernel: 5.15.8-200.fc35.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 : It has been this way for multiple versions, it also happens on Ubuntu.


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below: I am unable to force it to happen, and sometimes will go days without it happening.


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``: I have not yet tested, but it has been in many previous kernel versions.


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.
[  380.223016] ath10k_pci 0000:02:00.0: timed out waiting peer stats info
[  380.990016] ath10k_pci 0000:02:00.0: firmware crashed! (guid 3bb9190f-90a2-458a-98a5-97c68acaef33)
[  380.990031] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:143a
[  380.990040] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
[  380.991806] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1-00157-QCARMSWPZ-1 api 6 features wowlan,ignore-otp,mfp crc32 90eebefb
[  380.993363] ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 318825bf
[  380.993370] ath10k_pci 0000:02:00.0: htt-ver 3.60 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[  381.003964] ath10k_pci 0000:02:00.0: failed to get memcpy hi address for firmware address 4: -16
[  381.003968] ath10k_pci 0000:02:00.0: failed to read firmware dump area: -16
[  381.003969] ath10k_pci 0000:02:00.0: Copy Engine register dump:
[  381.003977] ath10k_pci 0000:02:00.0: [00]: 0x00034400  11  11   3   3
[  381.003985] ath10k_pci 0000:02:00.0: [01]: 0x00034800   8   7 436 437
[  381.003993] ath10k_pci 0000:02:00.0: [02]: 0x00034c00  16  15  14  15
[  381.004001] ath10k_pci 0000:02:00.0: [03]: 0x00035000  22  21  22  20
[  381.004008] ath10k_pci 0000:02:00.0: [04]: 0x00035400 1643 1595  94  30
[  381.004015] ath10k_pci 0000:02:00.0: [05]: 0x00035800   0   0  64   0
[  381.004023] ath10k_pci 0000:02:00.0: [06]: 0x00035c00  10   8   1  31
[  381.004030] ath10k_pci 0000:02:00.0: [07]: 0x00036000   0   1   0   1
[  381.009948] ath10k_pci 0000:02:00.0: failed to read hi_board_data address: -28
[  381.069075] ieee80211 phy0: Hardware restart was requested
[  381.334622] ath10k_pci 0000:02:00.0: device successfully recovered

Comment 1 Ben Bromley 2021-12-20 13:45:52 UTC

*** This bug has been marked as a duplicate of bug 1846802 ***


Note You need to log in before you can comment on or make changes to this bug.