Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1960564 - WIFI (ath11k) has stopped working since kernel 5.11.20 (Fedora 34) on a Dell XPS 15 9500 i9
Summary: WIFI (ath11k) has stopped working since kernel 5.11.20 (Fedora 34) on a Dell ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-14 09:00 UTC by Jerry Kiely
Modified: 2021-05-25 15:31 UTC (History)
26 users (show)

Fixed In Version: kernel-5.12.6-300.fc34 kernel-5.12.6-200.fc33
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-25 01:09:21 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
output of dmesg (deleted)
2021-05-14 09:00 UTC, Jerry Kiely 		no flags Details
output of journalctl (deleted)
2021-05-14 09:02 UTC, Jerry Kiely 		no flags Details
output of lsmod (deleted)
2021-05-14 09:03 UTC, Jerry Kiely 		no flags Details
output of lspci (deleted)
2021-05-14 09:03 UTC, Jerry Kiely 		no flags Details
output of dmesg for kernel 5.11.21 (deleted)
2021-05-17 12:07 UTC, Jerry Kiely 		no flags Details
output of journalctl for kernel 5.11.21 (deleted)
2021-05-17 12:08 UTC, Jerry Kiely 		no flags Details
output of lshw for kernel 5.11.21 (deleted)
2021-05-17 12:09 UTC, Jerry Kiely 		no flags Details
output of lsmod for kernel 5.11.21 (deleted)
2021-05-17 12:10 UTC, Jerry Kiely 		no flags Details
output of lspci for kernel 5.11.21 (deleted)
2021-05-17 12:10 UTC, Jerry Kiely 		no flags Details
Show Obsolete (4) View All

Description Jerry Kiely 2021-05-14 09:00:40 UTC 
Created attachment 1783129 [details]
output of dmesg

Created attachment 1783129 [details]
output of dmesg

Description of problem:

Since upgrading to Fedora 34 from Fedora 33 on my Dell XPS 15 9500 a couple of days ago wifi has stopped working. 




Version-Release number of selected component (if applicable):

kernel-5.11.20-300.fc34 / kernel-5.11.21-300.fc34
linux-firmware-20210511-120



How reproducible:

Always on boot.



Steps to Reproduce:
1. Boot laptop
2.
3.



Actual results:

wifi does not work



Expected results:

wifi should work



Additional info:

wifi works for kernels kernel-5.11.18-300.fc34 / kernel-5.11.19-300.fc34.
Comment 1 Jerry Kiely 2021-05-14 09:02:29 UTC 
Created attachment 1783130 [details]
output of journalctl
Comment 2 Jerry Kiely 2021-05-14 09:03:00 UTC 
Created attachment 1783131 [details]
output of lsmod
Comment 3 Jerry Kiely 2021-05-14 09:03:25 UTC 
Created attachment 1783132 [details]
output of lspci
Comment 4 Justin M. Forbes 2021-05-14 12:18:39 UTC 
Can you try the kernel from https://koji.fedoraproject.org/koji/buildinfo?buildID=1746705 and see if that helps things? We would be rebasing to 5.12 next week anyway.
Comment 5 Jerry Kiely 2021-05-14 13:58:45 UTC 
Actually, what I wrote above is incorrect - to summarize my issue:


kernel-5.11.20-300.fc34 + linux-firmware-20210511-120.fc34

no bluetooth + no wifi


kernel-5.11.19-300.fc34 + linux-firmware-20210315-119.fc34

no bluetooth + wifi works

kernel-5.11.18-300.fc34 + linux-firmware-20210315-119.fc34

no bluetooth + wifi works




Both bluetooth and wifi worked perfectly under Fedora 33 before I upgreded. Since upgrading bluetooth has not worked, and wifi stopped working with kernel-5.11.20-300.fc34

Unfortunately I don't have time to install the 5.12 kernel right now, but I will try to do it over the weekend, or early next week. Thanks for your feedback / suggestion.
Comment 6 Jerry Kiely 2021-05-17 08:30:39 UTC 
From journalcl:



May 17 09:01:22 ponocrates kernel: Oops: 0003 [#1] SMP NOPTI
May 17 09:01:22 ponocrates kernel: CPU: 13 PID: 251 Comm: kworker/u33:0 Tainted: P           OE     5.11.18-300.fc34.x86_64 #1
May 17 09:01:22 ponocrates kernel: Hardware name: Dell Inc. XPS 15 9500/0HH6JF, BIOS 1.7.1 03/29/2021
May 17 09:01:22 ponocrates kernel: Workqueue: hci0 hci_power_on [bluetooth]
May 17 09:01:22 ponocrates kernel: RIP: 0010:qca_download_firmware+0x231/0x490 [btqca]
May 17 09:01:22 ponocrates kernel: Code: 1b 75 04 80 48 0c 01 0f b7 c1 8d 54 02 0c 41 39 d7 0f 8e 99 fe ff ff 48 63 c2 4c 01 e8 0f b7 30 0f b7 48 02 66 83 fe 11 75 d3 <80> 48 0c 80 41 83 fc 03 7e 6f 44 88 70 0d eb cd 41 0f b6 45 0e 48
May 17 09:01:22 ponocrates kernel: RSP: 0018:ffffb3f000adbc60 EFLAGS: 00010246
May 17 09:01:22 ponocrates kernel: RAX: ffffb3f00044d03b RBX: 0000000000000005 RCX: 0000000000000006
May 17 09:01:22 ponocrates kernel: RDX: 0000000000000037 RSI: 0000000000000011 RDI: ffff8e604e884860
May 17 09:01:22 ponocrates kernel: RBP: ffff8e6040e3e000 R08: ffff8e605e2a52c0 R09: ffff8e604e884860
May 17 09:01:22 ponocrates kernel: R10: 00000000001236c1 R11: 0000000000000000 R12: 0000000000000005
May 17 09:01:22 ponocrates kernel: R13: ffffb3f00044d004 R14: 000000000000000e R15: 00000000000016a9
May 17 09:01:22 ponocrates kernel: FS:  0000000000000000(0000) GS:ffff8e67ad740000(0000) knlGS:0000000000000000
May 17 09:01:22 ponocrates kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 17 09:01:22 ponocrates kernel: CR2: ffffb3f00044d047 CR3: 0000000311a10005 CR4: 00000000007706e0
May 17 09:01:22 ponocrates kernel: PKRU: 55555554
May 17 09:01:22 ponocrates kernel: Call Trace:
May 17 09:01:22 ponocrates kernel:  qca_uart_setup+0x277/0x5a0 [btqca]
May 17 09:01:22 ponocrates kernel:  ? qca_read_soc_version+0x136/0x220 [btqca]
May 17 09:01:22 ponocrates kernel:  qca_setup+0x52e/0xb40 [hci_uart]
May 17 09:01:22 ponocrates kernel:  hci_dev_do_open+0x1d0/0x740 [bluetooth]
May 17 09:01:22 ponocrates kernel:  ? try_to_wake_up+0x1c1/0x4f0
May 17 09:01:22 ponocrates kernel:  hci_power_on+0x3f/0x200 [bluetooth]
May 17 09:01:22 ponocrates kernel:  process_one_work+0x1ec/0x380
May 17 09:01:22 ponocrates kernel:  worker_thread+0x53/0x3e0
May 17 09:01:22 ponocrates kernel:  ? process_one_work+0x380/0x380
May 17 09:01:22 ponocrates kernel:  kthread+0x11b/0x140
May 17 09:01:22 ponocrates kernel:  ? kthread_associate_blkcg+0xa0/0xa0
May 17 09:01:22 ponocrates kernel:  ret_from_fork+0x1f/0x30
May 17 09:01:22 ponocrates kernel: Modules linked in: acpi_cpufreq(-) qrtr_mhi snd_sof_pci snd_sof_intel_hda_common snd_hda_codec_hdmi snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_soc_skl snd_hda_codec_realtek snd_soc_h>
May 17 09:01:22 ponocrates kernel:  videobuf2_common pcspkr dell_wmi_sysman(+) wmi_bmof intel_wmi_thunderbolt dell_wmi_descriptor i2c_i801 thunderbolt hci_uart soundcore i2c_smbus mhi videodev btqca hid_sensor_als libarc4 btrtl hid_sensor_trigger btbcm proces>
May 17 09:01:22 ponocrates kernel: CR2: ffffb3f00044d047
May 17 09:01:22 ponocrates kernel: ---[ end trace b912c5558b19bdb3 ]---
May 17 09:01:22 ponocrates kernel: RIP: 0010:qca_download_firmware+0x231/0x490 [btqca]
May 17 09:01:22 ponocrates kernel: Code: 1b 75 04 80 48 0c 01 0f b7 c1 8d 54 02 0c 41 39 d7 0f 8e 99 fe ff ff 48 63 c2 4c 01 e8 0f b7 30 0f b7 48 02 66 83 fe 11 75 d3 <80> 48 0c 80 41 83 fc 03 7e 6f 44 88 70 0d eb cd 41 0f b6 45 0e 48
May 17 09:01:22 ponocrates kernel: RSP: 0018:ffffb3f000adbc60 EFLAGS: 00010246
May 17 09:01:22 ponocrates kernel: RAX: ffffb3f00044d03b RBX: 0000000000000005 RCX: 0000000000000006
May 17 09:01:22 ponocrates kernel: RDX: 0000000000000037 RSI: 0000000000000011 RDI: ffff8e604e884860
May 17 09:01:22 ponocrates kernel: RBP: ffff8e6040e3e000 R08: ffff8e605e2a52c0 R09: ffff8e604e884860
May 17 09:01:22 ponocrates kernel: R10: 00000000001236c1 R11: 0000000000000000 R12: 0000000000000005
May 17 09:01:22 ponocrates kernel: R13: ffffb3f00044d004 R14: 000000000000000e R15: 00000000000016a9
May 17 09:01:22 ponocrates kernel: FS:  0000000000000000(0000) GS:ffff8e67ad740000(0000) knlGS:0000000000000000
May 17 09:01:22 ponocrates kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
May 17 09:01:22 ponocrates kernel: CR2: ffffb3f00044d047 CR3: 0000000311a10005 CR4: 00000000007706e0
May 17 09:01:22 ponocrates kernel: PKRU: 55555554
Comment 7 Jerry Kiely 2021-05-17 08:36:55 UTC 
lspci 



6c:00.0 Network controller [0280]: Qualcomm QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] [17cb:1101] (rev 01)
        Subsystem: Rivet Networks Device [1a56:a501]
        Kernel driver in use: ath11k_pci
        Kernel modules: ath11k_pci
Comment 8 Jerry Kiely 2021-05-17 08:38:16 UTC 
lsusb



Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:5510 Realtek Semiconductor Corp. Integrated_Webcam_HD
Bus 001 Device 002: ID 27c6:533c Shenzhen Goodix Technology Co.,Ltd. FingerPrint
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Comment 9 Jerry Kiely 2021-05-17 08:39:51 UTC 
hciconfig 



hci0:   Type: Primary  Bus: UART
        BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
        DOWN INIT RUNNING 
        RX bytes:30 acl:0 sco:0 events:3 errors:0
        TX bytes:201094 acl:0 sco:0 commands:810 errors:0
Comment 10 Jerry Kiely 2021-05-17 08:41:41 UTC 
bluetoothctl show



No default controller available
Comment 11 Jerry Kiely 2021-05-17 09:19:29 UTC 
Please note that the last few comments relate to a (maybe unrelated) firmware compression issue affecting bluetooth, but the wifi not working with kernel 5.11.20 still stands. 

I apologize - I accidentally posted details relevant to a different issue in this bug report.
Comment 12 Jerry Kiely 2021-05-17 10:10:52 UTC 
journalctl -b -2 | grep 'ath11k\|version 5.11'



May 17 11:07:09 ponocrates kernel: Linux version 5.11.20-300.fc34.x86_64 (mockbuild.fedoraproject.org) (gcc (GCC) 11.1.1 20210428 (Red Hat 11.1.1-1), GNU ld version 2.35.1-41.fc34) #1 SMP Wed May 12 12:45:10 UTC 2021
May 17 10:07:12 ponocrates kernel: ath11k_pci 0000:6c:00.0: WARNING: ath11k PCI support is experimental!
May 17 10:07:12 ponocrates kernel: ath11k_pci 0000:6c:00.0: BAR 0: assigned [mem 0xb4200000-0xb42fffff 64bit]
May 17 10:07:12 ponocrates kernel: ath11k_pci 0000:6c:00.0: enabling device (0000 -> 0002)





journalctl -b -1 | grep 'ath11k\|version 5.11' 



May 17 11:07:53 ponocrates kernel: Linux version 5.11.19-300.fc34.x86_64 (mockbuild.fedoraproject.org) (gcc (GCC) 11.1.1 20210428 (Red Hat 11.1.1-1), GNU ld version 2.35.1-41.fc34) #1 SMP Fri May 7 14:17:15 UTC 2021
May 17 10:07:55 ponocrates kernel: ath11k_pci 0000:6c:00.0: WARNING: ath11k PCI support is experimental!
May 17 10:07:55 ponocrates kernel: ath11k_pci 0000:6c:00.0: BAR 0: assigned [mem 0xb4200000-0xb42fffff 64bit]
May 17 10:07:55 ponocrates kernel: ath11k_pci 0000:6c:00.0: enabling device (0000 -> 0002)
May 17 10:07:56 ponocrates kernel: ath11k_pci 0000:6c:00.0: chip_id 0x0 chip_family 0xb board_id 0xff soc_id 0xffffffff
May 17 10:07:56 ponocrates kernel: ath11k_pci 0000:6c:00.0: fw_version 0x101c06cc fw_build_timestamp 2020-06-24 19:50 fw_build_id 
May 17 10:07:56 ponocrates kernel: ath11k_pci 0000:6c:00.0 wlp108s0: renamed from wlan0
May 17 10:08:00 ponocrates NetworkManager[2874]: <info>  [1621242480.1556] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.5/0000:6c:00.0/ieee80211/phy0/rfkill1) (driver ath11k_pci)





journalctl -b | grep 'ath11k\|version 5.11' 



May 17 11:10:54 ponocrates kernel: Linux version 5.11.18-300.fc34.x86_64 (mockbuild.fedoraproject.org) (gcc (GCC) 11.1.1 20210428 (Red Hat 11.1.1-1), GNU ld version 2.35.1-41.fc34) #1 SMP Mon May 3 15:10:32 UTC 2021
May 17 10:10:57 ponocrates kernel: ath11k_pci 0000:6c:00.0: WARNING: ath11k PCI support is experimental!
May 17 10:10:57 ponocrates kernel: ath11k_pci 0000:6c:00.0: BAR 0: assigned [mem 0xb4200000-0xb42fffff 64bit]
May 17 10:10:57 ponocrates kernel: ath11k_pci 0000:6c:00.0: enabling device (0000 -> 0002)
May 17 10:10:57 ponocrates kernel: ath11k_pci 0000:6c:00.0: chip_id 0x0 chip_family 0xb board_id 0xff soc_id 0xffffffff
May 17 10:10:57 ponocrates kernel: ath11k_pci 0000:6c:00.0: fw_version 0x101c06cc fw_build_timestamp 2020-06-24 19:50 fw_build_id 
May 17 10:10:57 ponocrates kernel: ath11k_pci 0000:6c:00.0 wlp108s0: renamed from wlan0
May 17 10:11:00 ponocrates NetworkManager[2914]: <info>  [1621242660.9346] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.5/0000:6c:00.0/ieee80211/phy0/rfkill1) (driver ath11k_pci)
Comment 13 Jerry Kiely 2021-05-17 10:31:08 UTC 
Can confirm same issue for 5.11.21





journalctl -b -1 | grep 'ath11k\|version 5.11'



May 17 12:25:06 ponocrates kernel: Linux version 5.11.21-300.fc34.x86_64 (mockbuild.fedoraproject.org) (gcc (GCC) 11.1.1 20210428 (Red Hat 11.1.1-1), GNU ld version 2.35.1-41.fc34) #1 SMP Fri May 14 17:43:38 UTC 2021
May 17 11:25:09 ponocrates kernel: ath11k_pci 0000:6c:00.0: WARNING: ath11k PCI support is experimental!
May 17 11:25:09 ponocrates kernel: ath11k_pci 0000:6c:00.0: BAR 0: assigned [mem 0xb4200000-0xb42fffff 64bit]
May 17 11:25:09 ponocrates kernel: ath11k_pci 0000:6c:00.0: enabling device (0000 -> 0002)
Comment 14 Jerry Kiely 2021-05-17 11:48:15 UTC 
After reading the below bug reports:

https://bugzilla.redhat.com/show_bug.cgi?id=1954465
https://bugzilla.redhat.com/show_bug.cgi?id=1957598

and uncompressing the required firmware, bluetooth works OK. But problem with ath11k_pci persists. So the bluetooth is unrelated. Apologies for muddying the water.

What is worrying is that I am not seeing any relevant logs - not in dmesg or journalctl (see above). No stack trace relating to ath11k at all.
Comment 15 Jerry Kiely 2021-05-17 12:07:57 UTC 
Created attachment 1784031 [details]
output of dmesg for kernel 5.11.21
Comment 16 Jerry Kiely 2021-05-17 12:08:38 UTC 
Created attachment 1784032 [details]
output of journalctl for kernel 5.11.21
Comment 17 Jerry Kiely 2021-05-17 12:09:30 UTC 
Created attachment 1784033 [details]
output of lshw for kernel 5.11.21
Comment 18 Jerry Kiely 2021-05-17 12:10:08 UTC 
Created attachment 1784034 [details]
output of lsmod for kernel 5.11.21
Comment 19 Jerry Kiely 2021-05-17 12:10:40 UTC 
Created attachment 1784035 [details]
output of lspci for kernel 5.11.21
Comment 20 Ahmed El-Rayess 2021-05-18 00:27:45 UTC 
I have the same exact issue, used to work with 5.11.18, 5.11.19, but not with 5.11.20

dmesg ath11k messages stops at
[    4.901406] ath11k_pci 0000:05:00.0: WARNING: ath11k PCI support is experimental!
[    4.901460] ath11k_pci 0000:05:00.0: BAR 0: assigned [mem 0xd2100000-0xd21fffff 64bit]
[    4.901486] ath11k_pci 0000:05:00.0: enabling device (0000 -> 0002)
Comment 21 jan p. springer 2021-05-18 22:14:31 UTC 
same here, fresh install of an xps 13 9310 works with 5.11.12-300 (install kernel), after software update (to 5.11.20) wifi and bluetooth are not working anymore.
Comment 22 Eduard 2021-05-21 00:47:26 UTC 
Note! I have important information: 

The same problem occurred also in the 5.12.3 update of the kernel.
See related the posts here:

On the official kernel bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=213055

On Arch Linux:
https://bugs.archlinux.org/task/70849

The exact commit here has already been identified for 5.12.3. See these posts for the details.

I believe that the same issue somehow has been ported to kernel update 5.11.20 as well, at least on Fedora.
Comment 23 Jerry Kiely 2021-05-21 08:14:58 UTC 
problem persists with kernel-5.12.5-300.fc34
Comment 24 TJ Barber 2021-05-21 14:26:14 UTC 
Confirmed that this is still broken in kernel 5.11.21-300.fc34.
Comment 25 Eduard 2021-05-23 13:38:31 UTC 
Bug has been fixed upstream in 5.12.6, but Fedora did not wait for it and first updates to 5.12.5 right now, in which the problem still persists.
Comment 26 Fedora Update System 2021-05-23 15:21:25 UTC 
FEDORA-2021-af98aa2f3c has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-af98aa2f3c
Comment 27 Fedora Update System 2021-05-23 15:21:27 UTC 
FEDORA-2021-181c975561 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-181c975561
Comment 28 Fedora Update System 2021-05-24 01:05:10 UTC 
FEDORA-2021-181c975561 has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-181c975561`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-181c975561

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 29 Fedora Update System 2021-05-24 01:47:28 UTC 
FEDORA-2021-af98aa2f3c has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-af98aa2f3c`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-af98aa2f3c

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 30 Fedora Update System 2021-05-25 01:09:21 UTC 
FEDORA-2021-af98aa2f3c has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 31 Fedora Update System 2021-05-25 01:09:59 UTC 
FEDORA-2021-181c975561 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 32 jan p. springer 2021-05-25 04:24:09 UTC 
unfortunately, kernel-5.12.6-300.fc34 does not solve the problem. ath11k is reported in the kernel log but network device is created. closing the bug seems premature.
Comment 33 jan p. springer 2021-05-25 04:25:35 UTC 
(In reply to jan p. springer from comment #32)
> unfortunately, kernel-5.12.6-300.fc34 does not solve the problem. ath11k is
> reported in the kernel log but network device is created. closing the bug
                                ^ NO
> seems premature.
Comment 34 Jerry Kiely 2021-05-25 07:58:10 UTC 
Problem resolved for me with kernel-5.12.6-300.fc34. Thanks.
Comment 35 Félix Bellanger 2021-05-25 10:12:16 UTC 
(In reply to jan p. springer from comment #33)
> (In reply to jan p. springer from comment #32)
> > unfortunately, kernel-5.12.6-300.fc34 does not solve the problem. ath11k is
> > reported in the kernel log but network device is created. closing the bug
>                                 ^ NO
> > seems premature.

I have the exact same issue, updated my kernel using the `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-af98aa2f3c` but to no avail, the network device isn't created.
Comment 36 Jerry Kiely 2021-05-25 10:24:14 UTC 
Is it possible that you both could have accidentally booted into an earlier kernel (such as 5.11.19) after the kernel upgrade? 

Here is the output of a journalctl query for you to compare:



> journalctl -b | grep 'ath11k\|version 5.1' 
May 25 09:36:13 ponocrates kernel: Linux version 5.12.6-300.fc34.x86_64 (mockbuild.fedoraproject.org) (gcc (GCC) 11.1.1 20210428 (Red Hat 11.1.1-1), GNU ld version 2.35.1-41.fc34) #1 SMP Sat May 22 20:42:55 UTC 2021
May 25 08:36:15 ponocrates kernel: ath11k_pci 0000:6c:00.0: BAR 0: assigned [mem 0xb4200000-0xb42fffff 64bit]
May 25 08:36:15 ponocrates kernel: ath11k_pci 0000:6c:00.0: enabling device (0000 -> 0002)
May 25 08:36:16 ponocrates kernel: ath11k_pci 0000:6c:00.0: chip_id 0x0 chip_family 0xb board_id 0xff soc_id 0xffffffff
May 25 08:36:16 ponocrates kernel: ath11k_pci 0000:6c:00.0: fw_version 0x101c06cc fw_build_timestamp 2020-06-24 19:50 fw_build_id 
May 25 08:36:16 ponocrates kernel: ath11k_pci 0000:6c:00.0 wlp108s0: renamed from wlan0
May 25 08:36:20 ponocrates NetworkManager[2924]: <info>  [1621928180.0728] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.5/0000:6c:00.0/ieee80211/phy0/rfkill1) (driver ath11k_pci)



Thanks again to everyone for their swift response on this issue.
Comment 37 Félix Bellanger 2021-05-25 10:32:13 UTC 
Here's the output :

> journalctl -b | grep 'ath11k\|version 5.1'
May 25 12:22:31 fedora kernel: Linux version 5.12.6-300.fc34.x86_64 (mockbuild.fedoraproject.org) (gcc (GCC) 11.1.1 20210428 (Red Hat 11.1.1-1), GNU ld version 2.35.1-41.fc34) #1 SMP Sat May 22 20:42:55 UTC 2021
May 25 12:22:46 fedora kernel: ath11k_pci 0000:6c:00.0: BAR 0: assigned [mem 0xb4200000-0xb42fffff 64bit]
May 25 12:22:46 fedora kernel: ath11k_pci 0000:6c:00.0: enabling device (0000 -> 0002)
Comment 38 Jerry Kiely 2021-05-25 10:43:32 UTC 
Strange. Some more outputs.


> rfkill list  
0: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no


> lspci -nnk | grep -i -A2 net
6c:00.0 Network controller [0280]: Qualcomm QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] [17cb:1101] (rev 01)
        Subsystem: Rivet Networks Device [1a56:a501]
        Kernel driver in use: ath11k_pci
        Kernel modules: ath11k_pci


Let me know if I can post anything else that might help - to figure out what the difference is.
Comment 39 Félix Bellanger 2021-05-25 10:49:19 UTC 
Here's those outputs :

> rfkill list
0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

> lspci -nnk | grep -i -A2 net
6c:00.0 Network controller [0280]: Qualcomm QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] [17cb:1101] (rev 01)
	Subsystem: Rivet Networks Device [1a56:a501]
	Kernel driver in use: ath11k_pci
	Kernel modules: ath11k_pci

Event tried to downgrade linux-firmware out of curiosity to no avail knowing it shouldn't make a difference anyways.
Comment 40 Félix Bellanger 2021-05-25 11:00:18 UTC 
Okay nevermind, turned off the laptop, unplugged power and any adapters for a minute and now it works.
Comment 41 Jerry Kiely 2021-05-25 11:20:03 UTC 
That was actually the next thing I was going to recommend. Whenever there are wifi or bluetooth issues one of the first things I do is shutdown the laptop and unplug from the power supply, and sometimes I even disable / enable the devices in the BIOS. This I have found helps for both network and bluetooth devices. Good to hear it's back working. Very strange laptop indeed :-D
Comment 42 jan p. springer 2021-05-25 15:31:20 UTC 
wow, rebooting != poweroff + poweron. just did that and the xps 13 9310 has wifi. thank you.
Note You need to log in before you can comment on or make changes to this bug.