Edit: it’s possibly one plugin I forgot I installed.
When I restart the Vero (because it crashed), I can watch one or many movies, avi or mp4. Then I switch off the screen and the AV receiver. Vero keeps running. After a while, when I come back to it, it shows the red light and is unresponsive.
I started the logging, rebooted, had the Vero play a movie, and stopped the movie. As always, I turned off the screen and the AV receiver.
I extracted this part here: http://paste.osmc.tv/etisehequf which points to a python exception thrown while probably updating the library. I turned regular library updating on in the configuration.
Edit: ah, it’s not in the configuration, it’s a plugin I forgot I installed (library auto updater). I disabled the cleaning of the database now.
it’s like 5 hours now with the automatic clean-up (not: automatic update) of the library turned off, and the vero hasn’t crashed. It seems to be related with the automatic library clean-up.
Well, this was too early. I watched a movie, and sometime later, the vero showed me the red light. So I rebooted, and disabled the plugin completely.
It crashed again. So I rebooted, turned on logging, rebooted, watched a movie (or rather: had my empty chair watch a movie), came back later and: red light.
It still looks like a overheating which normally is tough to find. But we have seems Library updates possible sources. How do you have Library Updates configured now that you have watchdog disabled?
Ok, then need to dig in to find the culprit.
I would suggest to open two SSH connections (best in the ssh session start a screen session).
In one window have tail -f .kodi/temp/kodi.log running
In the other one have watch cat /sys/class/thermal/thermal_zone0/temp
Indeed, for whatever reason, the temperature seems to be lower when watching a movie. Afterwards it increased from 92 to 117, then at ~14:30 the connection broke down, vero crashed.
tail -f kodi.log
osmc@osmc:~/.kodi/temp$ tail -f kodi.log
2020-06-24 13:49:56.451 T:4068012032 NOTICE: Fallback resolution at 16 + 7 01080050.00000pstd
2020-06-24 13:49:56.451 T:4068012032 NOTICE: Found resolution 1920 x 1080 with 1920 x 1080i @ 60.000000 Hz
2020-06-24 13:49:56.451 T:4068012032 NOTICE: Fallback resolution at 16 + 8 01080060.00000istd
2020-06-24 13:49:56.451 T:4068012032 NOTICE: Found resolution 1920 x 1080 with 1920 x 1080i @ 59.940060 Hz
2020-06-24 13:49:56.451 T:4068012032 NOTICE: Found resolution 1920 x 1080 with 1920 x 1080 @ 60.000000 Hz
2020-06-24 13:49:56.451 T:4068012032 NOTICE: Current resolution setting found at 16 + 10
2020-06-24 13:49:56.451 T:4068012032 NOTICE: Found resolution 1920 x 1080 with 1920 x 1080 @ 59.940060 Hz
2020-06-24 13:49:56.451 T:4068012032 NOTICE: Found best resolution 0192001080060.00000pstd at 26, setting to RES_DESKTOP at 16
2020-06-24 13:49:56.714 T:4068012032 ERROR: GetString: error reading /sys/firmware/devicetree/base/buggymali
2020-06-24 13:49:56.890 T:4068012032 NOTICE: Updated resolutions and set desktop
Connection to vero closed by remote host.
Connection to vero closed.
In fact, I am using the default OSMC skin. (Is that the corresponding message in the log? 2020-06-24 10:57:24.540 T:4068012032 NOTICE: load skin from: /usr/share/kodi/addons/skin.osmc (version: 18.3.0?)I have been using that for a long time now. The requested debug log is attached in Vero 4k regular crashes in idle - #4 by jan.stuehler. Please let me know if you want another debug log.
Ah, understand. Enabled debug logging, restarted, ran a movie. Movie ended, temperature rose to 117, kodi switched off. Unfortunately, the ssh session ends then, and since I grabbed the output in screen, I cannot scroll up to get the remainder of the log. But anyway, the movie ended at 20:18.
Yeah that is the issue with screen. Actually if it is so easy to reproduce would not need screen just do a ssh session.
Anyhow we as we now know that it increased right after the movie and have the time stamp we can check the kod.log.old. Just upload that via grab-logs -X
But I am really suprized what could raise the temperature within 20 seconds so much.
Voilà: https://paste.osmc.tv/rejubuwiye
But let me add that it was 20:18 when the movie stopped and 20:54 when kodi gracefully shut down to prevent heat damage at 117°C. It’s just not seen in the logfile, because no further message was printed by kodi. So it is approximately 35 minutes between movie end and heat shut down.
That’s really strange.
After playing then movie was the Veron on a Menu where here was a srcolling text?
It would be really strange if Kodi eats all the CPU without anything in debug logging.
Suggest to open a 3 rd SSH session to check with htop if Kodi is really the main CPU user when the device overheats.
Did that. Vero gets back to the episode screen with scrolling text. In this phase, top reports that kodi eats up to 75% CPU. To compare, it’s 46% while playing the movie, and 44% in kodi’s start screen.
Is there anything I can do about that? Can the scrolling text be disabled, or can I use a screensaver which inhibits the scrolling text from eating up CPU? Or can kodi jump back to the season or series overview?
Or… can the scroll feature be programmed in a way that it does not eat up plus 30% (45 => 75) CPU?
Edit: just switched back to the season screen. 26% CPU.