i can no longer reproduce this bug with kernel 2.6.38 to be sure that it's not due to some other change in testing, i did: -clean install of debian 6 (kernel 2.6.32-5), suspend, resume, kerneloops -add kernel 2.6.38-2 (from testing), suspend, resume, everything goes fine