Ok, seems to be a problem of Kodi. The same behavier happens on raspberry OS and Kodi. I think we can close this thread here. I will start a threat on kodi forum.
Thanks for your help!
Ok, seems to be a problem of Kodi. The same behavier happens on raspberry OS and Kodi. I think we can close this thread here. I will start a threat on kodi forum.
Thanks for your help!
Perhaps the SDcard is having hiccups/problems? If your RPi4's firmware is already up-to-date, then you can also boot from a USB stick, or even an SSD connected via USB/SATA. Use a different image writer, Rufus in Windows usually works for me.
I don't think so. When I plug the network cable off if works.
Anyway I installed it new on a USB-Stick.
It reboots immediatly but this time it doesn't even show kodi BUT I do get a logfile:
Some warnings but nothing serious... It just keeps rebooting...
I also tried another raspberry pi 4 but the same happens. I updated the VIA USB firmware and the raspberry firmware to the newest version.
Any ideas? (This time it reboots but nothing has been set up, so it might not be related to the NFS problem...).
Frank
I did not install any addons.
It's a plain installation (2 days old) with only added NFS-Shares. The same happened with new Beta... The mediafolders are configured to use only local database for movies and tv shows.
Ok, as soon as I got a logfile, I'm gonna post it at pastebin.
But for now it seems I don't get any logfiles because it crashes before it writes anything.
I activated debug logfiles with networking off.
As soon as I have network on again (cable in) I don't get any logs.
[hommesf@stark temp]$ ls -la
total 5
drwxr-xr-x 5 root root 1024 Apr 11 2019 .
drwxr-xr-x 7 root root 1024 Apr 11 2019 ..
drwxr-xr-x 2 root root 1024 Apr 11 2019 archive_cache
-rw-r--r-- 1 root root 0 Apr 11 2019 kodi.log
-rw-r--r-- 1 root root 0 Apr 11 2019 kodi.old.log
drwxr-xr-x 3 root root 1024 Mar 27 14:20 scrapers
drwxr-xr-x 2 root root 1024 Apr 11 2019 temp
The Kodi log start from the very beginning of the application, and there is also the Linux kernel's journal for background/OS processes.
Logfiles are empty. How can I get logfiles about booting or where do I find them? I can't check dmesg or anything because it crashes within milliseconds.
Best regards
Frank
Hey,
I just got a new raspberry 4 and installed libreelec on it. I set it up to scan the files on my network share but after some time it crashed. Everytime I restart to raspberry it immediately crashes again. I see the CEC info and then reboot.
When I disconnect the network cable it boots and I can set up stuff. This is how I set up debug logging but I'm not sure if it already logs after booting!
The last lines are:
2021-04-08 18:34:58.060 T:3011495248 DEBUG: CloseBundle - Closed bundle
2021-04-08 18:34:58.098 T:3011495248 DEBUG: CDRMUtils::DrmFbDestroyCallback - removing framebuffer: 58
2021-04-08 18:34:58.103 T:3011495248 DEBUG: CDRMUtils::DrmFbDestroyCallback - removing framebuffer: 67
2021-04-08 18:34:58.104 T:3011495248 DEBUG: CWinSystemGbmEGLContext::DestroyWindow - deinitialized GBM
2021-04-08 18:34:58.105 T:3011495248 NOTICE: unload sections
2021-04-08 18:34:58.111 T:3011495248 DEBUG: LogindUPowerSyscall - delay lock sleep released
2021-04-08 18:34:58.112 T:2766459760 DEBUG: Thread Timer 2766459760 terminating
2021-04-08 18:34:58.113 T:3011495248 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x1f52fc8 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
2021-04-08 18:34:58.113 T:3011495248 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x1fac008 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
2021-04-08 18:34:58.113 T:3011495248 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x20753d0 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
2021-04-08 18:34:58.114 T:3011495248 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x1f1a450 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
2021-04-08 18:34:58.114 T:3011495248 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x1fb66d8 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
2021-04-08 18:34:58.114 T:3011495248 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x20740e8 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
2021-04-08 18:34:58.114 T:3011495248 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x2073368 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
2021-04-08 18:34:58.114 T:3011495248 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x2072da8 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
2021-04-08 18:34:58.114 T:3011495248 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x1f38d68 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
2021-04-08 18:34:58.114 T:3011495248 INFO: ADDON: cpluff: 'An unreleased information object was encountered at address 0x1f9d2b8 with reference count 1 when destroying the associated plug-in context. Not releasing the object.'
2021-04-08 18:34:58.115 T:3011495248 DEBUG: object 0 --> 0 instances
2021-04-08 18:34:58.115 T:3011495248 DEBUG: object 1 --> 0 instances
2021-04-08 18:34:58.115 T:3011495248 DEBUG: object 2 --> 0 instances
2021-04-08 18:34:58.115 T:3011495248 DEBUG: object 3 --> 0 instances
2021-04-08 18:34:58.115 T:3011495248 DEBUG: object 4 --> 0 instances
2021-04-08 18:34:58.115 T:3011495248 DEBUG: object 5 --> 0 instances
2021-04-08 18:34:58.115 T:3011495248 DEBUG: object 6 --> 0 instances
2021-04-08 18:34:58.115 T:3011495248 DEBUG: object 7 --> 0 instances
2021-04-08 18:34:58.115 T:3011495248 DEBUG: object 8 --> 0 instances
2021-04-08 18:34:58.115 T:3011495248 DEBUG: object 9 --> 0 instances
2021-04-08 18:34:58.158 T:3011495248 DEBUG: CWinSystemGbm::DestroyWindowSystem - deinitialized DRM
2021-04-08 18:34:58.237 T:3001021296 DEBUG: Thread libinput 3001021296 terminating
2021-04-08 18:34:58.238 T:2933912432 DEBUG: Thread Lirc 2933912432 terminating
2021-04-08 18:34:58.253 T:3011495248 DEBUG: CDRMUtils::RestoreOriginalMode - set original crtc mode
2021-04-08 18:34:58.280 T:3011482480 DEBUG: Thread Announce 3011482480 terminating
2021-04-08 18:34:58.282 T:3011495248 NOTICE: XBApplicationEx: application stopped!
############### END LOG FILE ################
############ END kodi CRASH LOG #############
Display More
Is there a possibility to get more information about the crash?
I believe it's some kind of preview jpg generation on the network file share mount which blows the system up.
I already tried the new beta but there is the same problem...
Any ideas or help?
Best regards
Frank