Page 1 of 1

V0.9.2 hung after 2nd wake up

Posted: Wed Oct 30, 2013 8:48 pm
by ckwong
The system hung from the 2nd wake up. The first was fine but the second could not complete the wake up. The screen was blank. No dump can be produced. Disk check reported no problem.

PrimoCache version: 0.9.2
OS: Windows 7 Ultimate x54
CPU: i950 12G memory
Motherboard: ASUS Sabertooth X58
SSD: OCZ Vertex 2 60G

A PrimoCache screen shot is attached.

Re: V0.9.2 hung after 2nd wake up

Posted: Wed Oct 30, 2013 9:04 pm
by Support
So this sleep/wake issue still exists in version 0.9.2. We have implememented a new mechanism for level-2 cache which may solve this issue. I'll keep you updated when it is ready. Thank you for the report!

Re: V0.9.2 hung after 2nd wake up

Posted: Wed Oct 30, 2013 9:18 pm
by Support
BTW, I'd like to know if you stoped the old cache task and created a new one after you updated the program to v0.9.2. If not, I'm afraid that the old cache contents stored in level-2 storage might be not correct and affect the results of testing.

Re: V0.9.2 hung after 2nd wake up

Posted: Mon Nov 04, 2013 11:48 am
by ckwong
I uninstalled the 0.9.1 and reformatted the SSD using the system utility and created new cache partition.

Re: V0.9.2 hung after 2nd wake up

Posted: Wed Nov 06, 2013 3:19 am
by Support
Thanks!

Re: V0.9.2 hung after 2nd wake up

Posted: Sun Nov 10, 2013 1:53 pm
by ckwong
The system is waken up when a batch job is scheduled to executed. These are data intensive and I/O intensive (network and disk) jobs. To avoid any critical race before the system is stabilized, I put a delay of 5 seconds to execute these jobs after the wake up. So far, no more hung or crash since last time.

Re: V0.9.2 hung after 2nd wake up

Posted: Mon Nov 11, 2013 4:07 pm
by Support
Thank you very much for the information!

PS. did you receive the updated version we sent to you by email?

Re: V0.9.2 hung after 2nd wake up

Posted: Mon Nov 11, 2013 5:07 pm
by ckwong
Yes. Thank you.

Re: V0.9.2 hung after 2nd wake up

Posted: Thu Apr 17, 2014 3:02 pm
by Support
This issue shall have been fixed in version 1.0.1. Thanks.