[twobob]

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

Spoiler:

[root@kindle root]# ps.procps -A
PID TTY TIME CMD
1 ? 00:00:01 init.sysvinit
2 ? 00:00:00 kthreadd
3 ? 00:00:00 posixcputmr/0
4 ? 00:00:00 sirq-high/0
5 ? 00:00:00 sirq-timer/0
6 ? 00:00:00 sirq-net-tx/0
7 ? 00:00:00 sirq-net-rx/0
8 ? 00:00:00 sirq-block/0
9 ? 00:00:00 sirq-tasklet/0
10 ? 00:00:00 sirq-sched/0
11 ? 00:00:00 sirq-hrtimer/0
12 ? 00:00:00 sirq-rcu/0
13 ? 00:00:05 desched/0
14 ? 00:00:05 events/0
15 ? 00:00:00 khelper
67 ? 00:00:00 kblockd/0
72 ? 00:00:00 mxc_spi.0
75 ? 00:00:00 mxc_spi.1
94 ? 00:00:00 kmmcd
102 ? 00:00:00 pmic_spi/0
174 ? 00:00:00 pdflush
175 ? 00:00:00 pdflush
176 ? 00:00:00 kswapd0
177 ? 00:00:00 aio/0
178 ? 00:00:00 nfsiod
214 ? 00:00:00 kondemand/0
225 ? 00:00:31 mmcqd
256 ? 00:00:00 rpciod/0
271 ? 00:00:00 kjournald
373 ? 00:00:01 udevd
652 ? 00:00:00 kjournald
887 ? 00:08:20 eink_fb_bt
889 ? 00:00:26 eink_fb_pt
965 ? 00:00:18 syslog-ng
1373 ? 00:00:06 loop0
1409 ? 00:16:23 fsp
1502 ? 00:00:00 launchpad
1572 ? 00:00:00 lifeguard
1634 ? 00:00:00 lifeguard
2060 ? 00:00:00 recEvent
2062 ? 00:00:30 AR6K Async
2085 ? 00:00:34 ksdiorqd
2115 ? 00:00:01 wpa_supplicant
2318 ? 00:00:26 dbus-daemon
2396 ? 00:00:00 usb-watchdog
2469 ? 00:00:00 dbus-monitor
2471 ? 00:00:00 usb-watchdog-he
2582 ? 00:00:00 pmond
2632 ? 00:00:08 powerd
2769 ? 00:01:19 cmd
2789 ? 00:03:16 wifid
2835 ? 00:00:05 wand
2903 ? 00:00:00 phd
2997 ? 00:00:00 mcsd
3043 ? 00:00:00 volumd
3242 ? 00:00:00 ttsd
3396 ? 00:00:00 tmd
3397 ? 00:00:00 lipc-daemon
3398 ? 00:00:00 crond
3490 ? 00:00:01 webreader
3531 ? 00:00:00 browserd
3596 ? 00:00:00 exe
3628 ? 00:00:01 start.sh
3882 ttymxc/0 00:00:00 getty
3918 ? 00:00:00 sh <defunct>
4669 ? 00:00:01 myts
4674 pts/0 00:00:00 sh
4740 ? 00:00:00 busybox
4747 ? 00:00:00 sshd
4759 ? 00:01:23 kaffeine
4760 ? 00:00:00 dbus-sigd
10209 ? 00:00:00 start.sh
10210 ? 00:00:00 exe
10216 ? 00:08:33 cvm
14536 ? 00:00:00 pppd
14602 ? 00:00:01 sshd
14607 pts/1 00:00:00 sh
15323 ? 00:00:00 audioServer
20069 ? 00:00:00 ksuspend_usbd
20071 ? 00:00:00 khubd
21093 pts/1 00:00:00 ps.procps

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.