the solution *might* involve removing kernel modules which are giving you a problem because they do not fully or correctly support power management, suspend, hibernate, resume or whatever. Basically they cause headaches like you describe.
Or, if this is a laptop, maybe the ACPI subsystem is sketchy and is giving troubles...
However, before we can say any of this conclusively (or speculate some more) you will need to do some debugging. Examining the kernel log or syslog on your system after the suspend operation might give clues about what went wrong after resume. So, let's say it's 5:00p.m., you suspend the machine and then resume it; please look at /var/log/kernel or /var/log/syslog (maybe a different name, you'll have to check) and see what it contains from 5:00p.m. onwards; perhaps post it for us to look at.
SuSE has some sort of s2ram package, doesn't it? Are you using that, and/or how exactly do you suspend the machine? (I don't use *SuSE so am not familiar with what it offers in this department.)
You should read this other ongoing thread also; though it's involving Slackware, the troubleshooting routine for you is the same (step 1: check logs, proceed from there.):
Also, maybe important: is it a laptop machine, or what? What make & model is it, even if it is a desktop?
EDIT #2: which version of OpenSuSE is it? That might end up helping too.
Kind regards, keep us posted.