Isssues with resume from suspend

Hi,
When I use the suspend mode for the Vero 4K+ (activated with CEC when the TV is shut down) while an screensaver is active (picture slideshow), the Vero hangs when I turn it on again. When the screensaver isn’t active, this doesn’t happen.

I have this issue for a long time already, but just thought why not ask if a solution for this issue is available?

If needed I can sent log files? But not sure if this is possible because the Vero hangs at that moment.

Please post some debug logs (via SSH if possible) so we can see what the issue is

Thanks

Sam

Hi, currently I have the issue with one of the Vero’s while log file creation was on. I am logged in with SSH, but no idea how to sent the log file. Can you please give me the needed instruction for this purpose?

Found the right command: grab-logs -A

Log file is available with: https://paste.osmc.tv/eresituxux

CPU load according to Kodi is 166,87%?

So as the picture is showing the GUI are you saying it is frozen at that picture?
Because in the first post you wrote

Which I assumed the screensaver is active after you return.

Yes this is the screen in which it is frozen.
So it is active for a split second I think, but then freezes.

The Vero is put into sleep when the screen saver is active.

Looking at the log it seems at 11:16 the wake worked:

2020-08-04 11:16:34.050 T:3802133216    INFO: Toggle standby state is waking
2020-08-04 11:16:34.051 T:3802133216    INFO: CApplication::ToggleStandby -- Toggle TMDS clock to 1
2020-08-04 11:16:34.165 T:3802133216    INFO: CApplication::ToggleStandby -- Toggle LED brightness to 1
2020-08-04 11:16:34.167 T:3802133216    INFO: CApplication::ToggleStandby -- governor will now be ondemand
2020-08-04 11:16:34.172 T:3802133216    INFO: CApplication::ToggleStandby -- HPD locking will now be hpd_lock0
2020-08-04 11:16:34.172 T:3802133216  NOTICE: CApplication::ToggleStandby -- checking for existence of /home/osmc/.kodi/userdata/wake.py
2020-08-04 11:16:34.458 T:4066377728   DEBUG: using python screensaver add-on screensaver.picture.slideshow
2020-08-04 11:16:34.459 T:4066377728   DEBUG: CPythonInvoker(8, /home/osmc/.kodi/addons/screensaver.picture.slideshow/default.py): trigger Monitor abort request
2020-08-04 11:16:34.938 T:3802133216   DEBUG: started alarm with name: sssssscreensaver
2020-08-04 11:16:35.908 T:3665818336   DEBUG: screensaver.picture.slideshow: script stopped
2020-08-04 11:16:35.908 T:3665818336    INFO: CPythonInvoker(8, /home/osmc/.kodi/addons/screensaver.picture.slideshow/default.py): script successfully run
2020-08-04 11:16:35.908 T:3665818336   DEBUG: onExecutionDone(8, /home/osmc/.kodi/addons/screensaver.picture.slideshow/default.py)
2020-08-04 11:16:35.921 T:3665818336 WARNING: CPythonInvoker(8, /home/osmc/.kodi/addons/screensaver.picture.slideshow/default.py): the python script "/home/osmc/.kodi/addons/screensaver.picture.slideshow/default.py" has left several classes in memory that we couldn't clean up. The classes include: N14PythonBindings42XBMCAddon_xbmcgui_WindowXMLDialog_DirectorE,N9XBMCAddon7xbmcgui6WindowE,N14PythonBindings31XBMCAddon_xbmc_Monitor_DirectorE,N14PythonBindings31XBMCAddon_xbmc_Monitor_DirectorE
2020-08-04 11:16:35.922 T:3665818336    INFO: Python interpreter interrupted by user
2020-08-04 11:16:35.922 T:4066377728   DEBUG: CPythonInvoker(8, /home/osmc/.kodi/addons/screensaver.picture.slideshow/default.py): script termination took 1463ms

But at it seems it is not terminating on time as it just started loading a picture from the server. Maybe that “killing” is then stalling something

2020-08-04 12:30:38.184 T:3802133216    INFO: Toggle standby state is waking
2020-08-04 12:30:38.185 T:3802133216    INFO: CApplication::ToggleStandby -- Toggle TMDS clock to 1
2020-08-04 12:30:38.305 T:3802133216    INFO: CApplication::ToggleStandby -- Toggle LED brightness to 1
2020-08-04 12:30:38.307 T:3802133216    INFO: CApplication::ToggleStandby -- governor will now be ondemand
2020-08-04 12:30:38.312 T:3802133216    INFO: CApplication::ToggleStandby -- HPD locking will now be hpd_lock0
2020-08-04 12:30:38.312 T:3802133216  NOTICE: CApplication::ToggleStandby -- checking for existence of /home/osmc/.kodi/userdata/wake.py
2020-08-04 12:30:38.361 T:3467637472   DEBUG: CSMBFile::Open - opened smb://USERNAME:PASSWORD@192.168.0.11/Public/Pictures/2005/20050300 Wintersport Les2Alpez/20050310 Wintersport Les2Alpez-259.jpg, fd=10002
2020-08-04 12:30:38.671 T:4066377728   DEBUG: using python screensaver add-on screensaver.picture.slideshow
2020-08-04 12:30:38.671 T:4066377728   DEBUG: CPythonInvoker(39, /home/osmc/.kodi/addons/screensaver.picture.slideshow/default.py): trigger Monitor abort request
2020-08-04 12:30:38.966 T:3467637472   DEBUG: CSMBFile::Close closing fd 10002
2020-08-04 12:30:38.968 T:3467637472   DEBUG: DoWork - took 665 ms to load smb://192.168.0.11/Public/Pictures/2005/20050300 Wintersport Les2Alpez/20050310 Wintersport Les2Alpez-259.jpg
2020-08-04 12:30:40.212 T:3802133216   DEBUG: PushCecKeypress - received key d8 duration 0
2020-08-04 12:30:40.484 T:3802133216   DEBUG: PushCecKeypress - received key d8 duration 273
2020-08-04 12:30:43.683 T:4066377728   ERROR: CPythonInvoker(39, /home/osmc/.kodi/addons/screensaver.picture.slideshow/default.py): script didn't stop in 5 seconds - let's kill it
2020-08-04 12:30:44.160 T:3802133216   DEBUG: started alarm with name: sssssscreensaver

Can you try to sent a action via ssh (kodi-send) or via the webinterface to see if the GUI is frozen or just don’t accept keyboard input.

I have tried to reboot from SSH, but this didn’t work. Had to pull the power to get it working again.
The log messages are also frozen, so no update on the screen anymore.

In the log several toggle standby’s are present, because it doesn’t go wrong everytime.
The issue happened in the toggle standby ad 12.30

That’s really odd especially as Kodi seemed to be running fine at the moment you upload the logs.

I did the upload with remote SSH. Not sure if I use Kodi at that moment?
But I will try again when the freeze issue happens again.

No but it looked like Kodi still had log messages till 13:33 which was 1 hour after the wake

Yes I see this in log to. How strange, the screen has been locked into the status as shown in the picture all that time. I will try to reboot from SSH when it happens again.

If I look into differences I see a kill message for the screensaver because it doesn’t respond. I don’t see this messages with the other stanby toggles.

2020-08-04 12:30:38.671 T:4066377728 DEBUG: CPythonInvoker(39, /home/osmc/.kodi/addons/screensaver.picture.slideshow/default.py): trigger Monitor abort request
2020-08-04 12:30:38.966 T:3467637472 DEBUG: CSMBFile::Close closing fd 10002
2020-08-04 12:30:38.968 T:3467637472 DEBUG: DoWork - took 665 ms to load smb://192.168.0.11/Public/Pictures/2005/20050300 Wintersport Les2Alpez/20050310 Wintersport Les2Alpez-259.jpg
2020-08-04 12:30:40.212 T:3802133216 DEBUG: PushCecKeypress - received key d8 duration 0
2020-08-04 12:30:40.484 T:3802133216 DEBUG: PushCecKeypress - received key d8 duration 273
2020-08-04 12:30:43.683 T:4066377728 ERROR: CPythonInvoker(39, /home/osmc/.kodi/addons/screensaver.picture.slideshow/default.py): script didn’t stop in 5 seconds - let’s kill it
2020-08-04 12:30:44.160 T:3802133216 DEBUG: started alarm with name: sssssscreensaver
2020-08-04 12:31:08.307 T:3665818336 DEBUG: Thread JobWorker 3665818336 terminating (autodelete)
2020-08-04 12:31:08.969 T:3467637472 DEBUG: Thread JobWorker 3467637472 terminating (autodelete)

Yeah as I wrote, it might be a race condition as the screensaver just started to load a picture from the server in the second the wake is happening. But still not sure why it would crash.