Bug 151711 - [AR9285] WiFi LED stops working after suspend/hibernate cycle
Summary: [AR9285] WiFi LED stops working after suspend/hibernate cycle
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: drivers_network-wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-08-08 08:12 UTC by Coacher
Modified: 2016-09-25 11:30 UTC (History)
2 users (show)

See Also:
Kernel Version: 4.7.0
Subsystem:
Regression: Yes
Bisected commit-id:

Attachments
lspci (23.88 KB, text/plain)
2016-08-08 08:12 UTC, Coacher 		Details
config.gz (21.29 KB, application/gzip)
2016-08-08 08:14 UTC, Coacher 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Coacher 2016-08-08 08:12:40 UTC 
Created attachment 227911 [details]
lspci

Hello.

After kernel upgrade from 4.6.4 to 4.7.0 WiFi LED stops working after 
suspend/hibernate cycle. LED works properly right after (re)boot. LED worked 
properly after suspend/hibernate cycle with 4.6.4, thus it's a regression.

My hardware is "Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) 
[168c:002b] (rev 01)", my OS is Gentoo amd64, my ath9k modprobe configuration 
is "options ath9k blink=0 btcoex_enable=1 bt_ant_diversity=1 ps_enable=1".
I've attached my kernel configuration and "lspci -vvv -nn -k" output.
Please let me know if you need more info.

Steps to reproduce:
1. Boot computer and connect to WiFi network.
2. Suspend/hibernate computer.
3. Resume/thaw computer.
4. Connect to WiFi network again.

Actual results:
WiFi LED is off.

Expected results:
WiFi LED is on.

Please fix.

-- 
Best regards.
Ilya Tumaykin.

P.S. This is a copy-paste from my e-mail I've sent about a week ago to QCA ath9k Development <ath9k-devel@qca.qualcomm.com>, CC'ing linux-wireless@vger.kernel.org, ath9k-devel@lists.ath9k.org.
I can't see it at https://lists.ath9k.org/pipermail/ath9k-devel/ still.
Comment 1 Coacher 2016-08-08 08:14:12 UTC 
Created attachment 227921 [details]
config.gz
Comment 2 Giedrius Statkevičius 2016-09-02 09:47:26 UTC 
Can you try https://lkml.org/lkml/2016/9/1/702 this patch and see if it helps you? Also, if it helps you can I add a tested-by tag to it?
Comment 3 mswindows2003 2016-09-06 05:06:48 UTC 
(In reply to Giedrius Statkevičius from comment #2)
> Can you try https://lkml.org/lkml/2016/9/1/702 this patch and see if it
> helps you? Also, if it helps you can I add a tested-by tag to it?

I've tried this patch. It works. Thank you very much!
Comment 4 Coacher 2016-09-11 10:48:23 UTC 
(In reply to Giedrius Statkevičius from comment #2)
> Can you try https://lkml.org/lkml/2016/9/1/702 this patch and see if it
> helps you? Also, if it helps you can I add a tested-by tag to it?
I can confirm that this patch applied on top of 4.7.3 fixes the problem for me.
Thank you. Feel free to add tested-by tag if you'd like.
Comment 5 Giedrius Statkevičius 2016-09-15 22:10:17 UTC 
The patch that fixes this issue was accepted into 4.8 and should at some time be in the 4.7.x tree as well. Please close the bug. Thanks.
Comment 6 Coacher 2016-09-25 11:30:22 UTC 
Fixed in the recently released 4.7.5. Thank you. Closing.
Note You need to log in before you can comment on or make changes to this bug.