]> git.hungrycats.org Git - linux/commit
[CPUFREQ] avoid re-enabling of interrupts too early during resume
authorDave Jones <davej@redhat.com>
Wed, 11 Aug 2004 12:31:55 +0000 (13:31 +0100)
committerDave Jones <davej@delerium.codemonkey.org.uk>
Wed, 11 Aug 2004 12:31:55 +0000 (13:31 +0100)
commite6c343874d2bc351d6de9eb40f704d7eef007999
tree7c2325dcd17e528603a430d24795bd2be0165192
parent81cc0c4263b868327936366d7c5f8deaf29aaf6e
[CPUFREQ] avoid re-enabling of interrupts too early during resume

Avoid re-enabling the interrupts in "write_sequnlock_irq" in
cpufreq_timer_notifier() when it gets called in "CPUFREQ_RESUMECHANGE" state
-- that happens if the CPU frequency is detected to be different now from
what it was during suspension, and that's a resume call of a sys device, so
with interrupts off.

Without this patch, it can cause nasty oopses. IIRC resume is done on one
CPU only, so we don't need no lock anyways. Right?

Many thanks to Brian J. Murrell for debugging this issue.

Signed-off-by: Dominik Brodowski <linux@brodo.de>
Signed-off-by: Dave Jones <davej@redhat.com>
arch/i386/kernel/timers/timer_tsc.c