dmesg does not use a persistent journal on OSMC
you should run dmesg instead of looking at /var/log/dmesg.
It seems that people experiencing freezing are predominantly using the original Raspberry Pi. it would be great if you guys could test this build, which does not included @popcornmixās JPEG decoding on ARM patch. Just copy and paste the following commands via SSH.
wget https://www.dropbox.com/s/26veswfypwyglq2/rbp1-mediacenter-osmc.deb?dl=1 -O rbp1-mediacenter-osmc.deb
sudo dpkg -i rbp1-mediacenter-osmc.deb
rm rbp1-mediacenter-osmc.deb
sudo reboot
Iām installing it in my RPi1 B+ setup. Will report ASAP the results!
thanks sam, i did run dmesg but was looking for logs and noticed it was there.
Normally only managed to watch 1 thing then when going back to gui its all messed up and if go to play something else it hangs.
Just Increased the ram on my pi1b to 190mb and have watched 3 movies with no problem and using skip function, which also makes it hang, with no problems.
So might hold off with that version you just posted for now
Nope, it didnāt work.
I was scrolling fast through my movies list, and it was taking a bit of time when hopping between titles, without having the time to load the fanart properly. After 10-20 items scrolled, it stopped doing the GUI sound, and started scrolling faster. From that time on, Kodi wasnāt able to load any fanart at all, and the playback was impossible, as for this bug.
The kodi log reported this:
17:26:22 3993.046631 T:2669671408 ERROR: DoWork - Direct texture file loading failed for resource://resource.images.studios.white/
17:26:25 3996.121094 T:2608174064 ERROR: DoWork - Direct texture file loading failed for resource://resource.images.studios.white/Sky Cinema (IT).png
17:27:34 4065.364258 T:2840589296 NOTICE: script.tv.show.next.aired: ### TV Show - Next Aired starting GUI proc (6.0.15)
17:29:12 4163.192383 T:2686448624 NOTICE: ES: Client from 192.168.1.100 timed out
17:32:20 4350.672852 T:2797597680 ERROR: COMXCoreComponent::WaitForCommand OMX.broadcom.egl_render wait timeout event.eEvent 0x00000000 event.command 0x00000000 event.nData2 1
17:32:20 4350.673340 T:2797597680 ERROR: COMXCoreComponent::WaitForCommand - OMX.broadcom.egl_render failed with omx_err(0x80001011)
I hope this could help solving this issueā¦
It would be useful to confirm if reverting to the March or April image (and not updating) still has the issue.
After thinking i was running ok after being left for a while when i went to get some food I came back and the gui was froze again. Time was still showing from few hours before.which I think was 6.01pm
This time there is an error showing
here is dmesg output https://www.dropbox.com/s/ud1fa4ylxdvaa5m/dmesg.txt?dl=0
here is last part of journalctl https://www.dropbox.com/s/aw6s7949ythpkx5/journalctl.txt?dl=0
kodi log https://www.dropbox.com/s/83k5t4cco4udymz/kodi.log?dl=0
Iām running 2016.05-1 on rbp 3 b and I also have the freeze.
Iāve noticed it happens for me when I was streaming something from an addon and then pausing the player, getting back directly to 
āhomeā (without using previous menu but home button on OSMC remote control instead), browsing to another addon, and when itās trying to fetch thumbnails then the system freezes.
Okay, this is something new. Thatās a kernel panic in tcp_urg, and so not a kodi issue.
Be interesting if the same issue occurs again (for you or for others).
Can you reliably replicate this kernel panic? Does the program counter always hold tcp_urg()?
Dont know how to replicate other than leaving it idle.
Iām watching movies at the moment but will keep an eye out and let you know.
It did freeze this morning when I went to watch a movie, a few seconds in, but there wasnāt any errors in dmesg.
Some more changes to try.
@popcornmix has added a guard around vchiq again.
Please try the following for Pi 1
wget http://apt.osmc.tv/pool/main/r/rbp1-mediacenter-osmc/rbp1-mediacenter-osmc_16.1.0-7_armhf.deb -O pi1-mediacenter.deb
sudo dpkg -i pi1-mediacenter.deb
sudo reboot
And the following for Pi2/Pi3:
wget http://apt.osmc.tv/pool/main/r/rbp2-mediacenter-osmc/rbp2-mediacenter-osmc_16.1.0-7_armhf.deb -O pi2-mediacenter.deb
sudo dpkg -i pi2-mediacenter.deb
sudo reboot
Testing is very much appreciated,
Sam
Iāll test this ASAP.
Can you please post instruction for reverting to the March release too? I would like to test that too if this doesnāt work.
Just download the March image from the blog. Itās the easiest way
Updating to this version now, will let you know the outcome, thanks.
Will I lose all the settings?
no, I just did it and it updates it over the top as usual
I think @Jean was referring to installing the March Image and not the updates Sam suggested.
If you install march image all settings/data would be lost. You could use the Backup function in MyOSMC to at least save your Kodi settings. While it might be best to do a complete image of your current install so that you can fall back. Or install on second SD card.
1 Like
FWIW, mine has been shaky as well after the last update. It seems to hang when you try fast-forwarding when watching something from TVHeadend. I am extremely pressed for time at the moment so I do not have much time to test. Shall I take it that rbp1-mediacenter-osmc_16.1.0-7_armhf.deb is for testing and the fix will be in the next release? If so when? On the blog I see:
2016.05-1 9bd3206bdb4e112c8b4cbd1e24fd1e89
2016.04-1 20413abde6065ee7bf31caa7344118cb
2016.02-3 31e47e995a6c1671a1ae32bd84a13e59
Whish is the march one? Does not a new image overwrite all my settings?