[lkml]   [2005]   [Feb]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.6.11-rc3-mm1: softlockup and suspend/resume

* Rafael J. Wysocki <> wrote:

> > I've attached a patch for touch_softlockup_watchdog() below - but i think
> > what we really need is another mechanism. I'm wondering what the primary
> > reason for the lockup-detection is - did swsuspend stop the the softlockup
> > threads?
> If my understanding is correct, the time between suspend (ie the
> creation of the image) and resume (ie the resotration of the image) is
> considered as spent in the kernel, so it triggers softlockup as soon
> as its threads are woken up (is that correct, Pavel?).

ah, ok. Could you try my patch and add touch_softlockup_watchdog() to
the resume code (before interrupts are re-enabled)?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:10    [from the cache]
©2003-2014 Jasper Spaans. hosted at Digital Ocean