https://bugzilla.novell.com/show_bug.cgi?id=579932
https://bugzilla.novell.com/show_bug.cgi?id=579932#c122
--- Comment #122 from Rafael Wysocki
Rafael, what's the upstream fix? Isn't processor.max_cstate=1 just a workaround?
The issue is an upstream problem and I'm not aware of any fixes other than limiting the set of C-states the CPUidle driver can use. The problem here is that the CPU cannot be woken up from deeper idle states by the clock event device we're using (HPET in this particular case if I'm not mistaken), but I'm not aware of any way to figure out which clock event device should be used instead (and, moreover, I'm not aware of any way to learn in advance that HPET will not work). Anyway, this problem should be reported upstream, so that we can involve more developers with expertise in this particular area in the discussion. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.