ROSA Linux Bugzilla – Bug 3602
ath5k broken after suspend-to-ram
Last modified: 2015-04-27 01:10:30 MSD
Created attachment 2515 [details]
Description of problem:
After suspend-to-ram, Wifi isn't working anymore, only way to have it back is reboot
Tried workaround with SUSPEND_MODULES="iwlwifi" or SUSPEND_MODULES="ath5k" in /etc/pm/config.d/ but ineffective
journalctl give this error :
janv. 12 23:47:51 marc kernel: ath5k 0000:06:00.0: Refused to change power state, currently in D3
On another Desktop with ROSA LXDE 32 bits, the same Wifi card resumes correctly from suspend-to-ram
I attach journalctl and inxi -F results
Created attachment 2516 [details]
You need try change powersaving mode in BIOS first.
(In reply to comment #2)
> You need try change powersaving mode in BIOS first.
Hi Aleksandr, this was done as you can see in french subject below
Switch to S1 : it works on resume but the system isn't fully stopped
Switch to S3 : problem with ath5k on resume
Does reloading of ath5k module help? I mean,
# modprobe -r ath5k && modprobe ath5k
Besides that, could you please check if the problem persists in 3.12 kernel? You can install that kernel version from this repository:
If the problem is in the kernel and it is fixed there, we could try to identify and backport the fix to 3.10 as well.
Well, with the command "modprobe -r ath5k && modprobe ath5k"
Before suspend-to-ram, one can see Wifi goes down and then goes up
After suspend-to-ram, it cause a kernel panic
Same behavior with kernel 3.12 :/
With ROSA Marathon LiveCD session, suspend and resume works fine on this desktop
(In reply to comment #5)
> Well, with the command "modprobe -r ath5k && modprobe ath5k"
> Before suspend-to-ram, one can see Wifi goes down and then goes up
> After suspend-to-ram, it cause a kernel panic
Could you obtain the system log (dmesg) after the crash or at least take a photo of the screen with the info about that kernel panic and post it here?
Please attach also the output of 'lcpci -vnn' here.
(In reply to comment #7)
> Please attach also the output of 'lcpci -vnn' here.
Here the result of 'lcpci -vnn'
Here the result of dmesg
I have reported the problem to the maintainers of ath5k. Let's see what they say.
A similar problems occurred in the past (e.g. https://email@example.com/msg04964.html) but I have found no suitable solutions in these reports so far.
By the way, could you try 'modprobe -r ath5k && modprobe ath5k' once again and if kernel crash occurs, just take a photo of the screen with the crash info and post it here? The system log (dmesg) does not contain crash info unfortunately.
Also, could you try live images of recent Fedora or Ubuntu releases and check if the problem shows up?
Thanks for you patience.
Well, the maintainer of ath5k replied but it is not all that helpful.
He suggests to perform a bisection to identify which kernel change (if any) has caused this problem.
Not a silver bullet, but if you can help, this is doable.
What is needed is to try the kernels I'll be building and reporting if the bug shows up there. This may take time but, with a bit of luck, we may identify the cause of the problem as a result.
I have prepared the versions of kernel 3.10 and 3.2 without most of ROSA/Mandriva-specific patches. Could you check if the problem shows up there?
Here are the rpms:
Please attach the output of dmesg for these, no matter whether the bug is there or not.
You may also need to temporarily run your system with the opensource video driver (radeon) rather than fglrx to avoid potential problems with the latter.
Unfortunately the user on the french forum who had this problem no longer provides new.
We wait a bit but if he's gone, we will not be able to progress :/
It looks like we had no chance to test this deeply. Let's optimistically close this as "worksforme". Feel free to reopen if you have a reproducer for modern Fresh R5.