Messages in this thread | | | Date | Sat, 5 Feb 2005 20:07:00 +0100 | From | Ingo Molnar <> | Subject | Re: 2.6.11-rc3-mm1: softlockup and suspend/resume |
| |
* Rafael J. Wysocki <rjw@sisk.pl> 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)?
Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |