[SOLVED] Suspend Skylake Fatal1ty z170 gaming-itx

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Strange, I think I solved the problem by going with BIOS 2.1 (with 1.8 I also got the black screen).

So you can suspend several times without problem now ?

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Jessie Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 22 Jun 2016 Status: Offline Points: 32	Post Options Post Reply Quote Jessie Report Post Thanks(0) Quote Reply Posted: 28 Jun 2016 at 4:37am
	Strange, I think I solved the problem by going with BIOS 2.1 (with 1.8 I also got the black screen). So you can suspend several times without problem now ?

def Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 27 Jun 2016 Status: Offline Points: 7	Post Options Post Reply Quote def Report Post Thanks(0) Quote Reply Posted: 29 Jun 2016 at 5:03am
	Yes, I can suspend as much as I want. But one problem remains and I tried out a few BIOS versions and none fixed it, the TSC keeps becoming unstable after suspend. I believe the BIOS is changing the TSC values in suspend/resume, which it should not do. Setting tsc to reliable just makes the clock run backwards... The exact error I get about TSC: Jun 28 22:49:23 al kernel: TSC synchronization [CPU#0 -> CPU#1]: Jun 28 22:49:23 al kernel: Measured 3072272461 cycles TSC warp between CPUs, turning off TSC clock. Jun 28 22:49:23 al kernel: tsc: Marking TSC unstable due to check_tsc_sync_source failed Jun 28 01:17:48 al kernel: clocksource: Switched to clocksource hpet Using HPET instead of TSC is not acceptable. Some applications that call gettimeofday() a lot slow down by a factor of 10 or more. Edited by def - 29 Jun 2016 at 5:04am

Jessie Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 22 Jun 2016 Status: Offline Points: 32	Post Options Post Reply Quote Jessie Report Post Thanks(0) Quote Reply Posted: 29 Jun 2016 at 5:41am
	Yes I also got that one after the first suspend: kernel: [ 47.547506] TSC synchronization [CPU#0 -> CPU#1]: kernel: [ 47.547507] Measured 4423217582 cycles TSC warp between CPUs, turning off TSC clock. kernel: [ 47.547509] tsc: Marking TSC unstable due to check_tsc_sync_source failed kernel: [ 48.678307] cache: parent cpu1 should not be sleeping kernel: [ 47.547688] CPU1 is up kernel: [ 47.547710] smpboot: Booting Node 0 Processor 2 APIC 0x1 kernel: [ 48.678948] cache: parent cpu2 should not be sleeping kernel: [ 47.548329] CPU2 is up kernel: [ 47.548350] smpboot: Booting Node 0 Processor 3 APIC 0x3 kernel: [ 48.679451] cache: parent cpu3 should not be sleeping kernel: [ 47.548830] CPU3 is up kernel: [ 0.020000] ACPI: Waking up from system sleep state S3 kernel: [ 48.697375] clocksource: Switched to clocksource hpet I wonder if this is causing instability (which my explain my hard reboot). I will confirm with the second board that I also have this issue.

Jessie Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 22 Jun 2016 Status: Offline Points: 32	Post Options Post Reply Quote Jessie Report Post Thanks(0) Quote Reply Posted: 30 Jun 2016 at 5:14pm
	Confirmed on the computer of my friend: he has the same TSC problem. I will contact Asrock. Thanks def for your help.

def Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 27 Jun 2016 Status: Offline Points: 7	Post Options Post Reply Quote def Report Post Thanks(0) Quote Reply Posted: 04 Jul 2016 at 3:58am
	Okay, actually resuming from suspend doesn't always work for me. When I do it in short intervals it seems to work fine, but after a few hours it sometimes fails.

Jessie Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 22 Jun 2016 Status: Offline Points: 32	Post Options Post Reply Quote Jessie Report Post Thanks(0) Quote Reply Posted: 04 Jul 2016 at 4:12am
	Ok. I have reinstalled Windows 10 in order to reproduce the problem with Windows 10 (otherwise Asrock will ignore me). Do you have any idea how to check for TSC/HPET synchronization issues on Windows 10 ? I have no idea how to look at the logs after resume.

def Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 27 Jun 2016 Status: Offline Points: 7	Post Options Post Reply Quote def Report Post Thanks(0) Quote Reply Posted: 09 Jul 2016 at 4:40pm
	No idea, I'm really not a Windows guy. But they sent me a new BIOS version that's supposed to fix the TSC issue, I just can't test it because nothing newser than 1.8 can resume from suspend for me.

Jessie Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 22 Jun 2016 Status: Offline Points: 32	Post Options Post Reply Quote Jessie Report Post Thanks(0) Quote Reply Posted: 09 Jul 2016 at 4:49pm
	Perhaps you can send it to me ? Or drop it somewhere where I can download it ? I can resume from suspend with a BIOS 2.1. Edited by Jessie - 09 Jul 2016 at 4:49pm

Brad Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 22 Jun 2016 Status: Offline Points: 19	Post Options Post Reply Quote Brad Report Post Thanks(0) Quote Reply Posted: 09 Jul 2016 at 10:45pm
	Jessie, On your original post you said you had problems resuming from suspend on Bios 2.1. Now you say you can resume from suspend on Bios 2.1. What has changed? Did the fresh install of Win 10 fix it?

Jessie Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 22 Jun 2016 Status: Offline Points: 32	Post Options Post Reply Quote Jessie Report Post Thanks(0) Quote Reply Posted: 10 Jul 2016 at 5:14am
	Hello Brad, Sorry for the misunderstanding. With BIOS 1.8 I cannot suspend/resume at all. With BIOS 2.1 I can suspend/resume but only one time. And even for this one time, I got the TSC/HPET problem. I will try the BIOS that def send me and report how it goes.