Hi!
> > > It looks like softlockup is not happy with suspend/resume:
> >
> > Does it happen while writing out state to disk?
>
> No, it occurs during resume, right after the image has been restored (sorry,
> I should have said this before).
>
> > 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?).
I do not know how exactly softlockup works, but yes, that seems
reasonable.
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
