Created attachment 1271004 [details] dmesg Description of problem: Set up hotspot in Fedora, mobile phone connected to that hotspot may stop working and ABRT start complaining Please note that ABRT keep complaining when trying to report --- Running report_uReport --- Server responded with an error: 'uReport data is invalid.' reporter-ureport failed with exit code 1 ('report_uReport' exited with 1) Other times it reports kernel has been tainted (flags:GW) which is not as I do not add Nvidia drivers or something else that mess with kernel... So this bug report is added manually and retrace has been uploaded here (I think since I cannot access it)... https://retrace.fedoraproject.org/faf/dumpdirs/new/oops-2017-04-12-03:04:49-873-0.tar.gz
Created attachment 1271638 [details] dmesg2
I got same error here.
Created attachment 1271781 [details] dmesg-microcode-sw-error Here I added an additional dmesg where there's a time that causes microcode software error... Causes is unknown and the usage is fairly normal (connecting to a Wifi Hotspot and hosting a Hotspot) without messing all sorts of configuration files...
I am experiencing the exact same issue with Ubuntu Zesty Zapus kernel linux-image-extra-4.10.0-19-generic (also in iwlwifi/mvm/tx.c:507). Does it mean this should be reported to the kernel team instead? It only happens once at boot when hostapd is starting, which also means it is 100% reproductible. The device still seem to be working properly after the stack trace. Up until yesterday I was still using linux-image-extra-4.8.0-46-generic and never encountered such error. Let me know if you would like me to attach some logs and/or do some testing.
It seems that with current kernel updates the error has slightly changed WARNING: CPU: 3 PID: 537 at drivers/net/wireless/intel/iwlwifi/mvm/tx.c:1360 iwl_mvm_rx_tx_cmd+0x88b/0x980 [iwlmvm] Details of the bug is in the 2nd attachment: https://bugzilla.redhat.com/show_bug.cgi?id=1491370 Btw, I think I found a workaround and it does stop abrt from spamming when hotspot is on/off-ing... I want to mention specifically that I have Intel Single-Band Wireless-N 7260 and therefore only rx/tx using 2.4GHz In nm-connection-editor and edit the hotspot settings, I see there's the Band section It has Auto, A (5GHz) and B/G (2.4GHz). The default is Auto. I set to 2.4GHz, saved the settings, clear out all the rests of abrt and reboot. Those nagging abrt no longer appeared. Seems like the driver module auto settings doesn't work properly.
Scratch that comment 5, I realise I am running on rawhide kernel 4.14 and that workaround may not apply to 4.12. The good news is that the nagging problem don't occur on 4.14 anymore, not sure 4.13
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.