Leann correctly marked my bug (141339) as a duplicate of this one.
On my system, running "/etc/init.d/powernowd restart" reliably fixes the problem. I created a script in /etc/acpi/resume.d with these contents:
#!/bin/sh
/etc/init.d/powernowd restart
This is automatically run when the system resumes, and should work if you're using acpid. Be sure to chmod a+x the file.
I was surprised that this works, as powernowd is disabled on my system (I'm using the ondemand governor), so the command doesn't actually cause the daemon to start up. However, /etc/init.d/powernowd sets CPU frequencies via proc/ and reloads kernel modules even when powernowd isn't being used. That's probably enough to get the kernel space governors to behave properly.
Leann correctly marked my bug (141339) as a duplicate of this one.
On my system, running "/etc/init. d/powernowd restart" reliably fixes the problem. I created a script in /etc/acpi/resume.d with these contents:
#!/bin/sh d/powernowd restart
/etc/init.
This is automatically run when the system resumes, and should work if you're using acpid. Be sure to chmod a+x the file.
I was surprised that this works, as powernowd is disabled on my system (I'm using the ondemand governor), so the command doesn't actually cause the daemon to start up. However, /etc/init. d/powernowd sets CPU frequencies via proc/ and reloads kernel modules even when powernowd isn't being used. That's probably enough to get the kernel space governors to behave properly.