Dear coreboot folks,
the issue is still not solved, so here is an update.
First of all, my thanks go to Kyösti for helping me debug this issue in
#coreboot on <irc.freenode.net>.
According to Kyösti there is fairly strong evidence of RAM / stack
corruption during S3 resume.
Memtest 5.00b5 successfully passed twice run from GRUB 2 on hard disk
with coreboot and SeaBIOS payload. I’ll still have to test resume from
S3 with other memory modules.
Kyösti pushed a AMD K8/Fam 10h CAR rewrite to Gerrit . Additionally
he provided the attached diff  to capture a stacktrace. Please find
my logs with `PRINT_IN_CAR` set to 0 and 1 attached.
Testing from other owners of the Asus M2V-MX SE would be very helpful as
resume from suspend to RAM was supposedly working in the past for them.
(Use `sp++` instead of `sp += 4`.)