Posts by mhoogenbosch


    This is the reason for your hang:

    Code
    [29641.033009] BUG: unable to handle kernel paging request at ffffea0008fc7168
    [29641.033126] IP: [<ffffffff810a327c>] list_del+0x7/0x2a
    [29641.033212] PGD 21f5f7067 PUD 21f5f6067 PMD 0
    [29641.033272] Oops: 0002 [#1] SMP
    [29641.033312] Modules linked in: 8021q iwlmvm mac80211 iwlwifi wl(PO) intel_powerclamp intel_rapl iosf_mbi snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi btusb btrtl btbcm btintel bluetooth cfg80211 snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep ir_xmp_decoder ir_lirc_codec lirc_dev ir_mce_kbd_decoder ir_sharp_decoder ir_sanyo_decoder ir_sony_decoder ir_jvc_decoder ir_rc6_decoder ir_rc5_decoder ir_nec_decoder rc_rc6_mce nuvoton_cir rc_core dw_dmac dw_dmac_core snd_soc_rt5640 snd_soc_rl6231 snd_soc_sst_acpi
    [29641.034026] CPU: 0 PID: 29280 Comm: DVDPlayerVideo Tainted: P O 4.4.7 #1

    Looks like this is caused by DVDPlayerVideo, which is odd no matter what addons you have installed. I have had the same NUC model as you for a couple years and never had a kernel crash like this. Hard to say what's the root cause here, could be either HW or SW.

    Mmm.. thanks for your answer, could it be BIOS releated? I'm using BIOS 41 (latest) from Intel. Or maybe I should install from scratch, i'm using this install for a pretty long time, with constant upgrades and updates.


    what klojum wants to say is, that it would be best to have a clean kodi. That means no repos addons beside the officials should be installed.

    You are right, there seems not to be a banned repo installed, but also those other repos or addons might cause an issue probably. So you could rename your .kodi folder to something like "kodi-bak" and reboot. That's like a factory reset. All addons and settings are 'gone', but backuped in the "kodi-bak" folder. So it's easy to restore them after testing.

    If the issue is gone after renaming the .kodi folder, one of the repos/addons might be the issue. So install them one after another and see, after which addon causes Kodi to hang.

    If the issue still persists, please get us a new (clean) logfile.

    Okay, I see what you mean. The problem is, this happens only once in a while. It's not reproducable. I do have deleted some of the Repro's, which weren't in use anymore, but removing all of them would result in a discussion with the wife. I'll try and find out what she hates more. A few weeks without the addons, or the incidental power cycle.


    Some of your added repos are questionable 3rd party repositories. Addons from those repos can contain functionality beyone our control. A test with a clean setup (a bootable usb stick with LibreELEC, and no added repos) should clarify things.

    Which dmesg error are you referring to?

    The Call trace is not normal behavior i believe.

    What repro's are you talking about, I've removed all banned repro's I believe, all other repro's are legit and contain normal addons.

    Sometimes my system just hangs. This happens every two weeks or so. Most of the time i'm not at home and my wife reboots the device which leads to loss of logs.

    Now I was home.

    dmesg:
    VeCi

    kodi.log:
    KJPD

    I think the dmesg displays the error, but I don't know for sure.

    I'm using a Intel NUC (D54250WYK)

    Why would you use settings designed for "Intel VAAPI howto with Krypton v17 based on Ubuntu 16.04 server" on a Pi?

    We are in control of all the defaults and they will be set to give the best behaviour for the majority or users.
    If there were a setting that was universally better, then we would change the default.

    As such, don't change default settings without a good reason.

    Fair enough.

    The reason for these settings in there are because I also have a IntelNUC based on Intel Haswell, I just copied these settings thinking it would be a good idea. But apperently it was not, atleast not for this version of Kodi. On the 'old' OpenElec (6.0.3) I used the same advancedsettings.xml and did not have these kind of problems.

    Never the less, your explaination sure makes sens. Thanks for your help!

    After removing the settings and changing the log to 0 I didn't reboot. Obiously this is needed (foolish me), but I think we have made progress. This morning I didn't notice the stutters. Will check tonight more. I'll let you know.

    the settings in Advancedsettings.xml aren't needed anymore? The refreshrate change?

    Okay, tonight, or tormorrow night i'll try a few settings

    1. remove superrepro (don't even know which addons are from that repro)
    2. change log to 0
    3. remove settings in advancedsettings.xml

    4. change player

    Tnx! and will report back!

    BTW, it is good to know there is not a known issue and then it should be resolvable.

    Edit:

    1. Removing the repro's don't help.
    2. Didn't help...
    3. Didn't help... coming close to the 'not so wanted solution'.

    Ofcourse I could try and remove some repro's, but I don't see why this would help. I will try nevertheless, but I've always used these addons, and am using them on my NUC where I don't have these problems. I'm not aware of any 'banned' addons i'm using. I don't watch streamed media, other than youtube and trailers from Apple trailers.

    I was always using OpenElec 6.03, recently I updated to the latest OpenElec build (6.95.3), that update introduced a strange stutter on my Pi2. So i tought i would upgrade to LibreElec 7.0.0, but the stutter remains.

    It happens during Live TV, but also during MKV playback. It runs stable for about 30 seconds to a minute and than a stutter (i see lot's of dropped frames and skips). Just like the Pi2 can't handle it. But with the previous version i never had such problems.

    Logfiles:
    LibreELEC (official) Version: 7.0.0
    raspberrpi:~ # dmesg | pastebinit
    XDEK
    raspberrpi:~ # journalctl -a | pastebinit
    BEdH
    raspberrpi:~ # cat /storage/.kodi/temp/kodi.log | pastebinit
    FfIR

    I've read somewhere you should set the buffermode to 1 instead of the default 0, i've tried that but that didn't help, didn't need it on the previous build but hey.. it was worth a shot.

    Can anybody help? Of does anyone have an idea where to start looking?