Skip to content

S3 is a cruel mistress

Well, I suppose I have no one to blame up myself. You may recall my triumphant declaration that S3 suspend was working on my desktop machine without any quirks. Naturally, that couldn’t last. Yesterday, something happened to the machine such that it will no longer resume from S3 – and it seems to be a very low level problem – I can’t resume successfully in windows anymore, either. I tried using a custom stripped down kernel but to no avail – I get identical symptoms in all cases. When I power it back on, basiclaly nothing happens. The drives power up and the disk activity light comes on solid for a while and then goes out – nothing else happens. Looking at the kernel logs, it seems control is never returned to the OS – and that would explain the failure on windows too.

I tried out S1 and I’ve confirmed that that still works, but something has broken S3 and I can’t for the life of me say what it is. I even wiped the BIOS configuration and recreated it, wondering if something bad had ended up in the nvram – but I’m not seeing any changes.

If anyone out there has any suggestions, I’m eager to hear them – but I’m feeling very pessimistic right now.

{ 2 } Comments

  1. Sebastian | 25th August 2007 at 12:37 | Permalink

    hi,

    try to remove the power chord for some time, maybe this helps.

    My Dell sometimes refuses to start until I do this…

    BR
    Sebastian (via N800)

  2. Philip Langdale | 26th August 2007 at 10:03 | Permalink

    I have tried that – and clearing the CMOS – and pulling all the hardware out I can, and disabling all the devices in the BIOS that I can – all to no avail.

    I can still use S1 (online standby) and S4 (hibernate) but it just won’t resume from S3. I’m pretty sure something has failed on the motherboard – it’s the only explaination I can think of. *sigh*

Post a Comment

Your email is never published nor shared. Required fields are marked *