[x86-64] Unregistered exception handler message when booting

    Greetings. New user on the forum.

    I had an old version of libreelec installed on a USB, with the data folder on the computer disk in an ext4 partition. It worked without problems

    In the last few weeks, after updating to v12, via the same UI, only sometimes, when I want to start libreelec, right after the boot menu, I get this message: "Unregistered exception handler".

    After several attempts, I can start Libreelec and used normally. But it's annoying to have to keep trying to log in.But it's annoying having to keep trying to log in this way.

    Any ideas on how to track down the underlying problem and fix it?


    Note: That computer is otherwise working fine, as I can boot Windows (which is also installed) without any difficulties.

    Please provide a full debug log.

    How to post a log (wiki)

    1. Enable debugging in Settings>System Settings>Logging
    2. Restart Kodi
    3. Replicate the problem
    4. Generate a log URL (do not post/upload logs to the forum)

    use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link

    Usage of banned add-ons means no support. Clean your system, and try again.

    Thread

    Forum Rules

    General Conduct

    • Be polite and respectful to forum staff and other users
    • Be polite and respectful towards this project and other projects
    • Be patient, user and staff are spread all over the world, an answer may take time
    Posting

    • One topic per thread
    • Posts should be written in English (add text in your native language if needed)
    • Be as descriptive and detailed as possible. We are not mind readers!
    • Do not cross-post or double-post
    • Do not post or promote external URL links to products, a name description is
    …
    newphreak
    March 15, 2016 at 1:02 AM

    Forgive me if I'm wrong, but it would seem that the log does not include the problem discussed.

    During the log creation, I tried to access my system without success from 12:05 to 12:15. The log starts from 12:15.

    I think it's a RAM / cache size error, maybe triggered by large Google Drive cache:

    Code
    2024-09-08 12:15:40.746 T:998     debug <general>: CGLContextEGL::SwapBuffers: sync check blocking
2024-09-08 12:15:40.758 T:998     debug <general>: CGLContextEGL::SwapBuffers: sync sleep: 11686
    • try LE Generic (non-Legacy, just copy the image into /storage/.update, and reboot)
    • remove those cache settings from advancedsettings.xml:
    Code
    <cache>
	<buffermode>2</buffermode>
	<freememorycachepercent>5</freememorycachepercent>
	<memorysize>99145600</memorysize>
	<readfactor>30.0</readfactor>
</cache>

    Thank you.

    I have just tried both options, but the problem persists.

    I'm not sure if the problem is recorded in the log, or if in any case it is in the last recorded and uploaded log or in some other previous one (given the number of times I have to try to access LE).

    Any other ideas?

    I think you're right, and the boot error isn't in the log. I thought I could find something in the log, but I guess what I found is not the real problem.

    So when LE boots, then the log with the boot error is at kodi.old.log. Post that one.

    Workflow for kodi.old.log:

    • install LE 12.0.1 Generic
    • replicate the issue
    • restart until LE boots successfully
    • login by SSH
    • cd .kodi/temp
    • cat kodi.old.log | pastebinit
    • post the resulting URL
    Quote from marialovesmatcha

    Is there any way to capture a manual log? Or does the fact that no log is created mean that LE doesn't even manage to start...

    kodi.old.log shows a successful boot sequence, so it's not helpful. Maybe a broken hardware part, which can't be initialized at boot sometimes. Hardware boot sequences are complex, so random results are possible.

    You can search for dead hardware parts after successful boot (internal WiFi, Bluetooth etc.). I don't think it's an LE problem.

    It must be an error in the Linux kernel, before LE starts logging.

    The kodi.old.log has this part, which isn't at kodi.log:

    Code
    2024-09-14 07:15:26.343 T:975     debug <general>: libva info: VA-API version 1.20.0
2024-09-14 07:15:26.343 T:975     debug <general>: libva info: Trying to open /usr/lib/dri/iHD_drv_video.so
2024-09-14 07:15:26.343 T:975     debug <general>: libva info: Found init function __vaDriverInit_1_20
2024-09-14 07:15:26.343 T:975     error <general>: libva error: /usr/lib/dri/iHD_drv_video.so init failed
2024-09-14 07:15:26.343 T:975     debug <general>: libva info: va_openDriver() returns 1

    After that the correct driver gets loaded in both logs:

    Code
    2024-09-14 07:15:26.343 T:975     debug <general>: libva info: Trying to open /usr/lib/dri/i965_drv_video.so
2024-09-14 07:15:26.343 T:975     debug <general>: libva info: Found init function __vaDriverInit_1_20
2024-09-14 07:15:26.344 T:975     debug <general>: libva info: va_openDriver() returns 0

    Maybe it's worth to blacklist the iHD driver.