S3 Suspend and Sage Sleep

[DFA]

Hi:

I must be the only one having this problem so might be system specific.

If I suspend and resume the HTPC while Sage is open, there are no problems. If Sage has been open and it is put in sleep before suspending it is also OK.

BUT if the system is resumed with Sage asleep in the tray and Sage not opened at least once before going back to suspend, Sage will crash at the time of the suspend event (date/time stamp from Sage error log).

Can anyone else duplicate this? More importantly, anyone have a fix (yea, I know, open Sage once before suspending again!). I experience this w/ 2.2.2 and 2.2.3

I have been round and round with power save. Everything else HW and SW seems to work fine through S3 suspend and resume cycles. Just Sage which will not go through a suspend / resume cycle if left asleep in the tray through the cycle.

EDIT: I am not using the Sage Service.

DFA

[jphhughes]

I tried using the SageTV built in Power management but could never get it to go back into suspend mode automatically. I have reverted back to SageWage which is a solid program and works the as advertised. One of the benefits of the current verison of SageTV is that it does restart the 350 card whihc I am using. Prior to the current version I had to you a program called Devcon along with sagewage to get SageTv to go into standby comeout of standby and then go back into standy.

[DFA]

For me, 2.2.2 and 2.2.3 will re-suspend the system after a scheduled recording provided nothing "moves" while the system is up for the recording; not even a mouse movement.

I have tried SageWake as well but that does not help me. The result is the same no matter how, what or who suspends / resumes the system: if Sage stays asleep in the tray through a cycle, it will crash at the time of suspend.

DFA

[DFA]

I have FINALLY isolated what the problem is with Sage crashing after a S3 suspend cycle while remaining asleep in the tray:

The culprit is the "uu_irsage.dll" plugin.

I had never given up on finding the source of the problem but was running out of ideas. I finally hit on the idea that perhaps the "uu_irsage.dll" plugin could be the source of difficulty. This evening, I manually removed the "uu_irsage.dll" plugin from the "prop" file and voila, no more Sage crashes after six S3 suspend cycles. Of course, I had no channel control of the STB during the test.

After editing the return of the "uu_irsage.dll" plugin to the "prop" file, the S3 suspend crashing problem as described in the first post of this thread immediately resurfaced.

I had long ago reported the S3 suspend crashing as a bug to Frey, but I'm sure they were unable to duplicate since probably not having the uu_irsage.dll in use. I will update them to what the cause appears to be and drop a post with Jon Rhees in the USB-UIRT forum.

Now to see about getting a fix. I am using version 1.0.0.1 of uu_irsage.dll and not aware of anything later than that. Is there?

DFA

[DFA]

The S3 suspend issue with uu_irsage.dll is now resolved. This may have been fixed at version 2.2.6RC but I did not install that release so can't say. It is definitly corrected in 2.2.7.

Thanks very very much Frey! Case closed.

DFA