Bug 204153 - iwlwifi: 8260: WARNING: wlwifi/mvm/scan.c:1874 iwl_mvm_rx_umac_scan_complete_notif
Summary: iwlwifi: 8260: WARNING: wlwifi/mvm/scan.c:1874 iwl_mvm_rx_umac_scan_complete_...
Status: CLOSED DUPLICATE of bug 204151
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: Intel Linux
: P1 high
Assignee: DO NOT USE - assign "network-wireless-intel" component instead
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-12 22:26 UTC by Chris Murphy
Modified: 2020-01-24 15:02 UTC (History)
7 users (show)

See Also:
Kernel Version: 5.3.0-0.rc6.git1.1.fc32.x86_64
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
dmesg (139.59 KB, text/plain)
2019-07-12 22:27 UTC, Chris Murphy
Details
lspci -vvnn (3.23 KB, text/plain)
2019-07-12 22:27 UTC, Chris Murphy
Details
dmesg (155.43 KB, text/plain)
2019-07-31 04:58 UTC, Chris Murphy
Details
dmesg2 (154.83 KB, text/plain)
2019-08-31 17:00 UTC, Chris Murphy
Details
dmesg3 (97.85 KB, text/plain)
2019-09-28 13:19 UTC, magiblot
Details

Description Chris Murphy 2019-07-12 22:26:29 UTC
This is on Fedora 30 with a Rawhide kernel. Changelog says Fri Jul 12 2019 5.3.0-0.rc0.git4.1 - Linux v5.2-7109-gd7d170a8e357

So that's probably linux-next git d7d170a8e357.

Hardware

6c:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a)

Product Name: HP Spectre Notebook
SKU Number: W2K28UA#ABA


This might be this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1728319
which I opened and then closed when referred to
https://bugzilla.kernel.org/show_bug.cgi?id=203315
as already being fixed.

The thing is I never ran into this with kernel 5.1.0, it first started in 5.2.0rc's rarely and quite a lot with release. And now with this linux-next kernel I'm getting a bigger splat with a bunch more stuff in dmesg including this scan.c backtrace.

Full dmesg attached.
Comment 1 Chris Murphy 2019-07-12 22:27:05 UTC
Created attachment 283659 [details]
dmesg
Comment 2 Chris Murphy 2019-07-12 22:27:43 UTC
Created attachment 283661 [details]
lspci -vvnn
Comment 3 Chris Murphy 2019-07-31 04:58:06 UTC
Created attachment 284049 [details]
dmesg

Update dmesg attachment. Slightly different output.

5.3.0-0.rc2.git1.1.fc31.x86_64 corresponds to git 2a11c76e5301
Comment 4 Luca Coelho 2019-08-22 05:35:41 UTC
The last dmesg shows that this is the same bug as 204151.  Marking this as a duplicate.  If the original bug in the previous dmesg comes back, please reopen.

*** This bug has been marked as a duplicate of bug 204151 ***
Comment 5 Chris Murphy 2019-08-31 16:58:46 UTC
The problem as originally reported never went away, it just so happens I also run into bug 204151.
Comment 6 Chris Murphy 2019-08-31 17:00:02 UTC
Created attachment 284725 [details]
dmesg2

Attaching latest dmesg using kernel 5.3.0-0.rc6.git1.1.fc32.x86_64, which is git 9e8312f5e160.
Comment 7 Chris Murphy 2019-08-31 17:08:31 UTC
I get this first, which is reported in the other bug
[   16.291560] iwlwifi 0000:6c:00.0: FW error in SYNC CMD GEO_TX_POWER_LIMIT

Then this happens, which is what I originally reported
[   16.292000] WARNING: CPU: 3 PID: 75 at drivers/net/wireless/intel/iwlwifi/mvm/scan.c:1874 iwl_mvm_rx_umac_scan_complete_notif.cold+0xc/0x13 [iwlmvm]
Comment 8 Chris Murphy 2019-09-01 18:23:19 UTC
5.3.0-0.rc6.git1.1.fc32.x86_64   ~2MB/sec transfers
5.2.11-200.fc30.x86_64+debug    ~16MB/sec transfers

(same AP, same laptop physical location, back to back tests, merely rebooting different kernel versions)
Comment 9 Chris Murphy 2019-09-01 18:27:07 UTC
Downstream bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1745766
Comment 10 magiblot 2019-09-28 13:19:07 UTC
Created attachment 285221 [details]
dmesg3

I'm suffering from the same issue. I'm attaching my dmesg output as well, and also adding linuxwifi@intel.com to the bug, as pointed out in https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging.
Comment 11 magiblot 2019-09-28 13:20:37 UTC
(In reply to magiblot from comment #10)

PS: My firmware version is 36.77d01142.0
Comment 12 Gil Adam 2019-10-15 08:20:08 UTC
All the logs show scan warning immediately following the GEO_TX_POWER_LIMIT FW error which was mentioned before (and resolved). Has anyone been able to reproduce this bug without the GEO error? if so please add the logs, otherwise this might a duplicate after all
Comment 13 Luca Coelho 2019-10-15 08:26:06 UTC
Thanks, Gil.  Setting to NEEDINFO.
Comment 14 magiblot 2019-10-19 16:49:38 UTC
I can't reproduce the issue anymore after a few updates. Currently using kernel 5.3.7-arch1-1-ARCH. Same firmware version as in comment #11. But I can't say the OP isn't suffering from a different issue.

Thank you very much.
Comment 15 Luca Coelho 2019-12-16 19:55:11 UTC
Marking this bug as duplicate again, since at least one of the reporters (thanks magiblot!) is not experiencing the bug anymore and the original reporter has not replied for a while.

*** This bug has been marked as a duplicate of bug 204151 ***
Comment 16 Mikhail Zabaluev 2020-01-24 15:02:28 UTC
The problem still occurs in kernel 5.4.10-200.fc31.x86_64: https://bugzilla.redhat.com/show_bug.cgi?id=1745766#c17

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