When I had the server setup with my Gigabyte board, coming out of suspend would take about 9-11 secs.

 

I have changed over to a Biostar board and now when I come out of suspend, the system hangs for about a minute and a half before becoming responsive (see last lines in syslog).

 

Would someone be kind enough to go through my attached syslog and see what could be causing the problem? It would be greatly appreciated..

 

 

Edit: After setting the Sata mode in the bios the system no longer comes out of suspend. I can see the lights light up but no ones home..

syslog1.txt

Do you have the latest BIOS for the mb?

 

Isn't there some S3 scan/debug tool that will tell you what troublesome devices you might have?

 

All I see is the following with nothing happening for aprox 1.5 minutes. I dont know if the other lines I highlighted are normal or not.

 

Sep 4 23:58:55 futurama kernel: sd 1:0:0:0: [sda] Starting disk

Sep 4 23:58:55 futurama kernel: Hangcheck: hangcheck value past margin!

Sep 4 23:58:55 futurama kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Sep 4 23:58:55 futurama kernel: ata3.00: link online but device misclassifed

Sep 4 23:58:55 futurama kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)

Sep 4 23:58:55 futurama kernel: ata4.00: configured for UDMA/133

Sep 4 23:58:55 futurama kernel: ata2: softreset failed (device not ready)

Sep 4 23:58:55 futurama kernel: ata1: softreset failed (device not ready)

Sep 4 23:58:55 futurama kernel: ata3.00: qc timeout (cmd 0xec)

Sep 4 23:58:55 futurama kernel: ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)

Sep 4 23:58:55 futurama kernel: ata3.00: revalidation failed (errno=-5)

Sep 4 23:58:55 futurama kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Sep 4 23:58:55 futurama kernel: ata2.00: configured for UDMA/133

Sep 4 23:58:55 futurama kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Sep 4 23:58:55 futurama kernel: ata1.00: configured for UDMA/133

Sep 4 23:58:55 futurama kernel: sd 2:0:0:0: [sdb] Starting disk

Sep 4 23:58:55 futurama kernel: sd 3:0:0:0: [sdc] Starting disk

Sep 4 23:58:55 futurama kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Sep 4 23:58:55 futurama kernel: ata3.00: configured for UDMA/133

Sep 4 23:58:55 futurama kernel: sd 4:0:0:0: [sdd] Starting disk

Sep 5 00:00:19 futurama kernel: Restarting tasks ... done.

I have the latest bios also I have followed the Wiki and made the necessary changes in he bios for the sata port ( Set to ahci ) as per Raj's suggestion. The orange lines you highlighted ar no longer there which is a good thing. These changes however prevents the system from coming out of an S3 sleep which is what I need.

 

I suspect users of Biostar boards don't put their system to sleep else we would definitely have seen a thread about it.

 

I'll try to post up a new syslog file shortly.

 

 

 

 

Are you using

 

s2ram 

 

or

 

echo -n "MEM" > /sys/power/state

 

to put your system to sleep?

Neither. I use

 

echo 3 > /proc/acpi/sleep

 

I'll try what you posted bubbaq and get back with the results..

Ok I have tried all three methods, however I noticed that when the system goes to sleep today the network card also goes to sleep. Very different from last night where the card remained awake. Manual resume does not bring it out of the comatose state. I am thinking maybe hardware problem, so tomorrow I am going to have it returned and get another board.

 

Hopefully they have something different than Biostar.

I use Biostar for my main unRAID server, and Gigabyte and Asus for my bench systems... all of them suspend and resume fine with unRAID.