Bug 197373
Summary: | iwlwifi: 7265: BAD COMMAND after connection loss | ||
---|---|---|---|
Product: | Drivers | Reporter: | Dan Aloni (alonid) |
Component: | network-wireless | Assignee: | DO NOT USE - assign "network-wireless-intel" component instead (linuxwifi) |
Status: | CLOSED DUPLICATE | ||
Severity: | low | CC: | alonid, luca |
Priority: | P1 | ||
Hardware: | Intel | ||
OS: | Linux | ||
Kernel Version: | 4.13.5-200.fc26.x86_64 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: | dmesg |
I don't think the issue is related with suspend resume, since it happened almost one minute after resuming. It seems to have happened immediately after a connection loss. I can't really see what happened here and the command that is being reported as bad, 0x1C, is TX_CMD, which is used everywhere. Does it still reproduce? If yes, could you try to capture trace-cmd logs, as explained here? https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging Actually this is a duplicate of 197279, but with a different device. I'll set this as duplicate and make sure the fix (when it's ready) will also be applied to this NIC's firmware. *** This bug has been marked as a duplicate of bug 197279 *** |
Created attachment 260373 [details] dmesg The issue did not disrupt my workflow - I noticed it accidentally when looking at dmesg. I don't have steps to reproduce the issue. I think it was caused when I returned from suspend. The hardware is a Levono Carbon X Gen 3 laptop.