Bug 197279
| Summary: | iwlwifi: 7265/8260: sporadic BAD COMMAND after connection loss - WIFI-5909 | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Dan Aloni (alonid) |
| Component: | network-wireless | Assignee: | DO NOT USE - assign "network-wireless-intel" component instead (linuxwifi) |
| Status: | CLOSED CODE_FIX | ||
| Severity: | normal | CC: | alonid, christopher, josh.fryman, kernel, luca, rstachowiak, weber.aulendorf |
| Priority: | P1 | ||
| Hardware: | Intel | ||
| OS: | Linux | ||
| See Also: |
https://bugzilla.kernel.org/show_bug.cgi?id=197281 https://bugzilla.kernel.org/show_bug.cgi?id=198017 |
||
| Kernel Version: | 4.13.5-100.fc25.x86_64 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
dmesg
dmesg with kernel 4.13.5-100.fc25.x86_64 and firmware 31.532993.0 8260 firmware with debug enabled Firmware dump 1 dmesg related to fimware dump 1 |
||
|
Description
Dan Aloni
2017-10-14 11:21:12 UTC
Created attachment 258823 [details]
dmesg
If you need more info, I've read
https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging
and may be able to supply it.
*** Bug 197277 has been marked as a duplicate of this bug. *** Please move to 4.13 and use -31.ucode. Created attachment 258829 [details]
dmesg with kernel 4.13.5-100.fc25.x86_64 and firmware 31.532993.0
Thanks for the quick response. I've upgraded the system a few hours ago and the problem reproduced with the new versions - I think those are the requested ones. See the attached dmesg. This error is very surprising and not related to the previous one. Easy to reproduce? If yes, I'll send you a debug firmware tomorrow. Yes, it happens every few hours. Sure, send over a debug firmware, I'll get it running. Created attachment 258831 [details] 8260 firmware with debug enabled Hi, Here is the firmware for 8260. Please copy it to /lib/firmware (I assume your distro takes it from there), you can backup the existing one before you overriding it. The instructions on how to collect the data are here: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging#firmware_debugging Please take the time to read the privacy notice: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging#privacy_aspects In your case, it'd be nice to get tracing as well. Created attachment 258849 [details]
Firmware dump 1
Created attachment 258851 [details]
dmesg related to fimware dump 1
Here's a firmware dump, hope it helps for the meanwhile. I'll try to get tracing too. Weird. This log teaches me that we get this after we send command 0x28. Thing is that when I look at the Tx FIFO I can see the command that you send, looks fine. Right format. Then, I can see a command that comes immediately afterwards in the Tx FIFO and that command is bad. Not sure how the HW put that there. I doubt the driver sent that. So, I really need tracing and a firmware dump of the same run. Thanks. A few more minutes on the dump taught me that the driver hasn't sent any new command. This is clearly a firmware bug. routing this bug to the right person. No more data needed at this stage. *** Bug 197729 has been marked as a duplicate of this bug. *** *** Bug 197281 has been marked as a duplicate of this bug. *** Just as an update, this issue is currently being handled by our firmware team. I'll report back when we have more news. *** Bug 197373 has been marked as a duplicate of this bug. *** *** Bug 198017 has been marked as a duplicate of this bug. *** We have a fix in the firmware which we will release soon. |