Bug 197373 - iwlwifi: 7265: BAD COMMAND after connection loss
Summary: iwlwifi: 7265: BAD COMMAND after connection loss
Status: CLOSED DUPLICATE of bug 197279
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: Intel Linux
: P1 low
Assignee: DO NOT USE - assign "network-wireless-intel" component instead
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-24 18:31 UTC by Dan Aloni
Modified: 2017-11-17 09:21 UTC (History)
2 users (show)

See Also:
Kernel Version: 4.13.5-200.fc26.x86_64
Subsystem:
Regression: No
Bisected commit-id:

Attachments
dmesg (187.92 KB, text/plain)
2017-10-24 18:31 UTC, Dan Aloni 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Dan Aloni 2017-10-24 18:31:19 UTC 
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.
Comment 1 Luca Coelho 2017-11-17 08:15:30 UTC 
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
Comment 2 Luca Coelho 2017-11-17 09:20:16 UTC 
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 ***
Note You need to log in before you can comment on or make changes to this bug.