PDA

View Full Version : Boom Restart with SuperDateTime?



androidtopp
2008-12-04, 06:45
This may not be the right place to post, but I'll give it a shot. Ever since I installed SuperDateTime and SaverSwitcher (for use on my Boom) I am getting odd power-on behavior.

I usually flip the Boom on at night to listen to something as I'm falling asleep. So it's now roughly 10pm, and the Boom has been off and unused since it woke me up this morning at about 4:40am. When I press power, I get a quick flash (a second or two) of a little SlimDevices/Logitech logo, and then the screen goes dark for a few seconds. Then it turns itself off and goes back to displaying the standard clock. If I press power again, it boots right up, no problems, ready to go. If I turn it off and turn it back on, there are no issues.

So, it seems like after a certain amount of time, the first time I try to turn on the Boom, it chokes on something and shuts back off. Subsequent attempts within whatever this timeout window is work fine - no automatic power off. Also of note, every time I see this power off behavior, I get the following entry in my server.log:

[08-12-03 22:28:15.6543] Slim::Hardware::IR::executeButton (1088) Error: Subroutine for irCode: [voldown_front.hold] mode: [] does not exist!

I am running SC 7.2.1 on Server 2003 x86, and the active plugins that seem to have triggered the issue are SuperDateTime in combination with SaverSwitcher. I get 10 seconds of weather followed by 20 seconds of clock. Not sure if this is relevant, but it feels like the problem is related to one or both of these plugins.

Has anyone seen this issue before with these plugins? It's not a big deal...just annoying.

Thanks,
Andrew

MeSue
2008-12-04, 07:46
I only use SDT--not Saverswitcher--and I have not had anything like that happening running 7.3 under Windows Home Server.

peterw
2008-12-08, 13:52
TAlso of note, every time I see this power off behavior, I get the following entry in my server.log:

[08-12-03 22:28:15.6543] Slim::Hardware::IR::executeButton (1088) Error: Subroutine for irCode: [voldown_front.hold] mode: [] does not exist!

I am running SC 7.2.1 on Server 2003 x86, and the active plugins that seem to have triggered the issue are SuperDateTime in combination with SaverSwitcher. I get 10 seconds of weather followed by 20 seconds of clock. Not sure if this is relevant, but it feels like the problem is related to one or both of these plugins.


Is that the only weird log message you see???

Two thoughts:

1) SaverSwitcher does handle/wrap IR events, and Boom button presses are treated by SC7 as IR events, but I don't think that's the problem here. If you don't use a remote with numbered buttons, you might as well set the SaverSwitcher button control to disabled to minimize the likelihood that it's SS' IR code.

2) There's likely a "mode stack" problem. See comments #22 and following on http://forums.slimdevices.com/showthread.php?t=35650&page=3. With your setup, the client's mode stack is growing by 4 items every minute, and even though SDT is very efficient, there's likely to be some lag when you power on as the mode stack is torn down. The mode stack would be almost 4000 items long after that 4:40-22:00 stretch. Last year I tried modifying SaverSwitcher so that it would do some mode stack cleanup as it ran, but hit some nasty problems (my fault, I'm sure: http://forums.slimdevices.com/showthread.php?t=35650&page=4), and so I abandoned that route. I've learned a bit more about SC7's screensaver code, and there've been some important changes since 7.0.1 (and improvements in SaverSwitcher), so maybe I should revisit that approach.

-Peter

peterw
2008-12-08, 19:54
Andrew, if you want to give it a try, I just posted a lightly tested version of SaverSwitcher with code that keeps the client mode stack more trim as it changes savers -- version 7a20. I'd love to hear if this makes a difference for you. It's in my TESTING area:
http://www.tux.org/~peterw/slim/slim7/TESTING/SaverSwitcher/

-Peter

androidtopp
2008-12-30, 12:18
Peter,

Whew - sorry for the long delay, and thanks for all your help! I will give this a shot tonight and see what happens.

Thanks,
Andrew

peterw
2008-12-30, 12:40
Whew - sorry for the long delay, and thanks for all your help! I will give this a shot tonight and see what happens.


Great. FYI, the latest production release of SaverSwitcher now has the stack-trimming logic, so
you don't need to use my testing version/repo.

-Peter

androidtopp
2008-12-30, 13:01
Peter,

I just noticed that your repository (using SC 7.3.1) shows version 7a26...does this include the fix you placed in the 7a20 version you referred to?

Edit: NM - I should refresh and read newer posts before I reply to myself!

Thanks,
Andrew

androidtopp
2009-01-03, 10:10
After several nights, it works perfectly. I've been off this week, so it actually has been sitting off about 24 hours - between when I go to bed one night and the same time the next night.

Thanks, Peter!

peterw
2009-01-03, 14:25
After several nights, it works perfectly. I've been off this week, so it actually has been sitting off about 24 hours - between when I go to bed one night and the same time the next night.

Thanks, Peter!

Thanks for the update. I'm very glad we got that solved!

-Peter