Right I think I can field this one now then.
a) the stack dump. not sure what PID 3518 is at that moment.
But raising the log level to something higher would possibly help determine that.
also running this:
ps.procps -A > /mnt/us/Documents/WhatWasRunningBefore.txt; dbus-send --system /default com.lab126.powerd.resuming int32:1
just before you suspend would give you a better clue for what the PIDS were
So that would give you something to give us
Looking at why it MIGHT be a few seconds slower anyway
Your log rotate stuff happens after the crash and it takes a while.
That would explain probably why mine takes a few seconds less: The size of the logs.
Mine are hacked to be 0 size, so they just wipe, whereas you are making genuine tar.gz's or w/e of your activity. That would take a little bit more time I would imagine also.
Well, hope that helps.