So this is a "suspend/hibernate/whatever" bug.
The default kernel comes with a ton of drivers. Many of these will be as removable modules and not baked in. (And for many devices having a driver active means they will be powered on.)
You could induce the 100% cpu condition and then lsmod to see what modules there are and then try removing (rmmod) those one by one to see if you can find the culprit that way. If you do, then add the offending module back (modprobe) and see if the condition persists or not. If not, then you could modify the "suspend/hibernate/whatever" scripts to do the module un/loading for you.
