Comment 4 for bug 1292627

Hi,

After a few tests with the latest kernel (3.14.0-031400rc6-generic #201403100035 SMP Mon Mar 10 04:36:54 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux) it is far better, but not enough!

Basically, the resume work, but a kernel thread (kworker) is eating 100% of 1 CPU core.
Time to time, it stop working for, something like less than 1s. I was able to launch htop under an X terminal, to see that.
The time this worker thread work, is not constant, something between 10s to 2min. During this time X freeze completely, and all others programs with it. During the clean reboot ('sudo reboot" in my X terminal), it happend too. The events are still monitored during that time. Even if the screen was frozen, I could type on the keybord or move the mouse. Just have to wait the worker thread to let others programs to work a little.

I tried to look at the logs, but I didn't found any evidence which may permit me to better know what was going on.
The only error in /var/log/pm-suspend.log is:

Running hook /usr/lib/pm-utils/sleep.d/60_wpa_supplicant resume suspend:
Failed to connect to non-global ctrl_ifname: (null) error: No such file or directory
/usr/lib/pm-utils/sleep.d/60_wpa_supplicant resume suspend: success.

I don't know if it is related.

You may notice that I have an another bug on this laptop. I can't use the proprietary WiFi driver (which is installed by default). This driver (firmware ? crashed with an "invalid instruction" error. It seems to not be compatible with an "AMD Athlon(tm) 64 X2 Dual-Core Processor TK-55" (on GNU/Linux only, I tried Win8.1 on this laptop, the driver worked fine). That is why, I only use the ethernet connexion,with the FOSS driver. Again, I don't know if this information can help too.

I will retry with the stock kernel, maybe it's the same, I just didn't wait 2min before performing a halt/boot. There is no hardware reset on laptops :-(

Thank you.