On Thu, 20 Dec 2007 08:38:03 -0500 Miles Lane <miles.lane@xxxxxxxxx> wrote: > On further investigation, "cat /proc/iomem" does not trigger the stack > trace until after a suspend-to-disk/resume cycle has occurred. I still can't reproduce this. Could you please try this? - cat /proc/iomem - suspend/resume - do while read i do echo $i sleep 1 done < /proc/iomem then, with luck, we'll be able to work out which /proc/iomem record immediately precedes the corrupted one. _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
