[Pm-utils] System unstable after resume if not setting NEED_CLOCK_SYNC for pm-utils

[Robby Workman]

Victor,
I CC'd pm-utils list, but I'm not subscribed with this address.
If possible, can you whitelist this address on this list?
Either way, please approve the posting, and if necessary, I'll
send followups from the on-list address.

The "meat" of the message is below...

On Fri, 17 Apr 2009, Grissiom wrote:

> Hello rworkman,
>
> I have encountered that if not set NEED_CLOCK_SYNC=1 in
> /etc/pm/config.d/defaults, system will go unstable after resume from suspend
> to RAM. I see you write if anyone encounter this kind if problem, mail
> rworkman at slackware.com. So I do it ;)


Thanks!  I like people who read (and follow) the documentation  ;-)


> Full story can be found here:
>
> http://www.linuxquestions.org/questions/slackware-14/system-unstable-after-resume-from-suspend-719718/


Hrm... interesting.  That bit from dmesg is especially telling.
Victor, should this be CC'd to someone @kernel.org?


> And I upgrade pm-utils to 1.2.5 only with a version jump in SlackBuild.
> Nothing broken except for this case(which is also broken in 1.2.4). Is there
> any upgrade schedule in Slackware Official team?


I'll get to that in -current soon, I think.  The changes in 1.2.5 aren't
really needed for us yet though, but it can't hurt to upgrade.


> My laptop is DELL1501. If you want any information, feel free to ask me ;)


This is on the stock 2.6.27.7 kernel, correct?
Honestly, I'm not sure what else would be needed on the pm-utils end
of things; this seems more like a kernel bug.  You might consider 
building the latest in the 2.6.27.x series (.21 last I checked) to see
if it still happens there; this might have already been fixed upstream,
and I'd hate to waste someone's time with a bug report that's already
fixed.

-RW