Bug 202965 - iwlwifi: 9260: Read index for DMA queue txq id (0), index 5 is out of range
Summary: iwlwifi: 9260: Read index for DMA queue txq id (0), index 5 is out of range
Status: CLOSED INVALID
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: Intel Linux
: P1 blocking
Assignee: DO NOT USE - assign "network-wireless-intel" component instead
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-18 16:38 UTC by brorhieigho
Modified: 2019-04-05 21:29 UTC (History)
0 users

See Also:
Kernel Version: 4.20.14-200.fc29.x86_64
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg.log (147.06 KB, text/plain)
2019-03-18 16:38 UTC, brorhieigho
Details
dmesg1.log (76.10 KB, text/plain)
2019-03-19 22:10 UTC, brorhieigho
Details
Network Manager log (821 bytes, text/plain)
2019-03-21 19:14 UTC, brorhieigho
Details

Description brorhieigho 2019-03-18 16:38:23 UTC
Created attachment 281893 [details]
dmesg.log

$ ethtool -i wlp2s0 | grep firmware
firmware-version: 41.fc1a7aea.0

Duplicate of:
https://ask.fedoraproject.org/en/question/133877/wlp2s0-is-selecting-ent0/

Bluetooth does work, but the wifi does not seem to work.
Comment 1 Emmanuel Grumbach 2019-03-19 06:40:39 UTC
Can you try the latest firmware? -43.ucode?
Comment 2 brorhieigho 2019-03-19 17:16:23 UTC
Yes, I am currently using the current iwlwifi-9260-th-b0-jf-b0-34.ucode
Comment 3 brorhieigho 2019-03-19 17:19:10 UTC
Oops, sorry about the number mixup. Where can I find the most current ucode? The link bellow is where I found -34.ucode

https://www.intel.com/content/www/us/en/support/articles/000005511/network-and-i-o/wireless-networking.html
Comment 5 brorhieigho 2019-03-19 18:55:48 UTC
Thank you for the link Emmanuel. I have copied it over to /lib/firmware/ and restarted the system. I did not seen a difference in the functionality.
Comment 6 Emmanuel Grumbach 2019-03-19 19:37:48 UTC
Can you please attach the dmesg output with the new firmware?

Thanks
Comment 7 brorhieigho 2019-03-19 22:10:03 UTC
Created attachment 281913 [details]
dmesg1.log
Comment 8 Emmanuel Grumbach 2019-03-20 18:36:42 UTC
Do you see any interface?

what does:

iw dev

return?

THanks.
Comment 9 brorhieigho 2019-03-20 20:24:42 UTC
$ iw dev
phy#0
	Interface wlp2s0
		ifindex 3
		wdev 0x1
		addr 66:03:27:43:9b:ce
		type managed
		txpower 0.00 dBm
Comment 10 Emmanuel Grumbach 2019-03-20 20:47:58 UTC
Ok, so the interface is set up.

What doesn't work then?
Comment 11 brorhieigho 2019-03-20 20:57:26 UTC
Not yet. When I open the wifi settings, I do not see any wireless network around me. Is it weird that the MAC address in '$ iw dev' does not match '$ dmesg | grep wifi'?
Comment 12 brorhieigho 2019-03-21 19:14:29 UTC
Created attachment 281957 [details]
Network Manager log

Attached is an excerpt from NetworkManager.service log regarding wlp2s0
Comment 13 Emmanuel Grumbach 2019-03-21 19:23:33 UTC
What is your system brand / model?

can you please record tracing while enabling Wifi?

1) disable Wifi
2) start tracing
3) enable Wifi
4) stop tracing

you can find info on how to record tracing here:
https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging#tracing

sudo trace-cmd record -e iwlwifi

thanks.
Comment 14 brorhieigho 2019-03-22 18:44:46 UTC
# trace-cmd record -e iwlwifi
trace-cmd: No such file or directory
  No events enabled with iwlwifi
Comment 15 brorhieigho 2019-03-26 21:18:57 UTC
The device is an HP 15-ay, but I have replaced the wireless network card with Intel 9260NGW from Newegg.

https://support.hp.com/us-en/product/hp-15-ay000-notebook-pc-series-touch/10862302/model/11830175/product-info?sku=X0H86UA
Comment 16 Emmanuel Grumbach 2019-03-27 06:57:08 UTC
Then we can't do much.

The device needs to be correctly integrated with the platform / OEM.
There may be electrical issues because you swapped the devices.
Comment 17 brorhieigho 2019-03-29 12:20:48 UTC
I don't think that is the case. The system dual boots Windows 10. When I first installed it was a bit buggy but now it works.
Comment 18 brorhieigho 2019-03-29 12:26:03 UTC
But only for windows 10 and not Fedora 29. I was able to scan for wifi on Fedora 29 using:
$ sudo iwlist wlp2s0 scan
The scan only works with Sudo.
Comment 19 Emmanuel Grumbach 2019-03-29 13:03:46 UTC
(In reply to brorhieigho from comment #18)
> $ sudo iwlist wlp2s0 scan
> The scan only works with Sudo.

This is expected...
Comment 20 brorhieigho 2019-03-29 13:57:23 UTC
Since I am able to scan networks with the command above, it looks like more of a software issue with NetworkManager and/or it's dependencies. I have reinstalled NetworkManager:
$ sudo dnf reinstall NetworkManager
So far, I have not seen any changes. I will dig more into how NetworkManager works to find root cause.
Comment 21 Emmanuel Grumbach 2019-03-30 19:19:23 UTC
You can't see any networks in NetworkManager?
Comment 22 brorhieigho 2019-03-31 23:13:29 UTC
No, I have talked with people in the NetworkManager IRC(https://webchat.freenode.net/?channels=#nm). fgiudici said it is an issue with the wpa_supplicant. So, I messed around with it and learned that it only worked with root permissions. I am asking around on the IRC mentioned above if this is normal behaviour for the wpa_supplicant program.
Comment 23 brorhieigho 2019-04-05 21:29:25 UTC
After submitting a bug to Network Manager, I was able to resolve the problem.

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/149

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