aboutsummaryrefslogtreecommitdiffstats
path: root/kernel/printk.c
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2007-03-16 19:25:52 -0400
committerLinus Torvalds <torvalds@woody.linux-foundation.org>2007-03-16 22:35:25 -0400
commitcd05a1f818073a623455a58e756c5b419fc98db9 (patch)
tree4e148e96f00fe07b0c53a379e812344733e8484a /kernel/printk.c
parent24c4ac070adffe4a21f3a8daf4aee7c98fa6c4f9 (diff)
[PATCH] clockevents: Fix suspend/resume to disk hangs
I finally found a dual core box, which survives suspend/resume without crashing in the middle of nowhere. Sigh, I never figured out from the code and the bug reports what's going on. The observed hangs are caused by a stale state transition of the clock event devices, which keeps the RCU synchronization away from completion, when the non boot CPU is brought back up. The suspend/resume in oneshot mode needs the similar care as the periodic mode during suspend to RAM. My assumption that the state transitions during the different shutdown/bringups of s2disk would go through the periodic boot phase and then switch over to highres resp. nohz mode were simply wrong. Add the appropriate suspend / resume handling for the non periodic modes. Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'kernel/printk.c')
0 files changed, 0 insertions, 0 deletions