Created attachment 283627 [details]
Full journalctl output for full context
Laptop Model: Dell Latitude 7490
Wifi Card: Intel 8265
Distribution: Fedora 30
Problem: A kernel bug appears to be randomly triggered after AP association, which in turn causes the laptop to misbehave and ultimately requires a shutdown by holding the power button down.
e.g. The laptop does not fully shutdown without physical intervention and random applications are totally hung and cannot be killed.
See journalctl.txt for the full context of the error.
Let me know if you need any additional information.
Created attachment 283629 [details]
lspci -vvv output
Thanks for reporting. I have created an internal ticket to track this and will have someone look into this issue ASAP.
This was also discussed in this thread:
I am unsure if this is relevant, but in my case at least, this has so far occurred only on a network using WPA2-EAP.
There is also a bug report in redhat bugzilla:
With a look at the source code, I think there is a modification of the list without a lock:
The change was introduced here:
iwlwifi: mvm: support mac80211 TXQs model
In the patch, there is one list_del_init (the one which causes the oops) in iwl_mvm_add_new_dqa_stream_wk(), and one list_add_tail() in iwl_mvm_mac_wake_tx_queue().
They do not share the same lock. There is a mutex in iwl_mvm_add_new_dqa_stream_wk(), but nothing in iwl_mvm_mac_wake_tx_queue(). Maybe it would help to use the mutex here or - if this is too expensive - introduce a spin lock for this list?
I am just guessing, but the list_add_tail() looks like the only thing not guarded by the mutex.
Let me know if there is any additional information/logs needed, or if there are patches you'd like us to test.