Comment 57 for bug 681083

Hm, that stack trace looks a bit like that task somehow got starved off on its way into suspend. There has been regression reports (unfortunately after testing in proposed) on real hardware which was tracked to

commit f0cf1db8f15e8f95f5085f191313694cb623a558
Author: Thomas Gleixner <email address hidden>
Date: Fri Dec 2 16:02:45 2011 +0100

    clockevents: Set noop handler in clockevents_exchange_device()
    BugLink: http://bugs.launchpad.net/bugs/902317
    commit de28f25e8244c7353abed8de0c7792f5f883588c upstream.

That has been reverted now upstream and it will come down via stable. Luiz, does that happen to you all the time or at least often enough to verify with a kernel that has that patch reverted (which I would provide)?