Jump to content

mechmess

Members
 View Profile  See their activity

  • Posts

    16

  • Joined

  • Last visited

 Content Type 

Report Comments posted by mechmess

    [6.9.x - 6.11.x] intel i915 module causing system hangs with no report in syslog (not alder lake)

    in Prereleases

    Posted

    9 minutes ago, ich777 said:

    Why? Please update to 6.11.5

     

    Did you also change the path to /mnt/cache/... instead of /mnt/user/... in the template?

    I honestly somehow missed that there we were all the way to 6.11.5. Updating now. 

     

    Just changed the path. 

     

    I'll report back with my experience in a couple of days. Thanks for the help - my apologies for not getting totally caught up on the current best-practices. 

    [6.9.x - 6.11.x] intel i915 module causing system hangs with no report in syslog (not alder lake)

    in Prereleases

    Posted · Edited by mechmess

    EDIT: I'll try switching to ipvlan to see if that helps anything.... 


    This has been a continuous issue for me for a long time now (I first posted in this thread back in April/May), and my only solution has been to move my Plex container/transcoding to a second system running Unraid 6.8.3. The 6.8.3 system has been solid. 

     

    With hardware transcoding enabled, I get at most about a day and a half before a crash. Without, I'm rock solid. There are never any related/similar system logs at the time of crash (mirroring to flash and to a remote syslog server), and my system automatically restarts after the crash. 

     

    • i9-9900k
    • 6.11.1
    • Dummy Plug
    • GPU Top with nothing in the Go file
    • Official PlexInc container
    • Ran Memtest for 24 hours with no errors
    • Appdata on Cache:Prefer, with plenty of available space.
    • Transcoding on the Cache Drive (not in RAM) - thought this might have been the issue so I switched away from RAM

     

     

    tower-diagnostics-20230209-0719.zip

    • Like 1

    [6.9.x - 6.11.x] intel i915 module causing system hangs with no report in syslog (not alder lake)

    in Prereleases

    Posted

    3 hours ago, ich777 said:

    You don't have to use Intel GPU TOP anymore because the iGPU is actiavated on boot by Unraid itself, however you have to use it if you want to use it with the GPU Statistics plugin, otherwise GPU Statistics won't work.

    If I dont have GPU TOP installed, I do not get /dev/dri to populate. Is there something else I need to change? I have GPU TOP installed, so maybe that is causing some sort of issue vs just letting it roll default. 

    [6.9.x - 6.11.x] intel i915 module causing system hangs with no report in syslog (not alder lake)

    in Prereleases

    Posted · Edited by mechmess

    On 5/6/2022 at 2:24 PM, ich777 said:

    Please post your Diagnostics.

    Wanted to wait for another crash before sending. 

     

    Last crash was ~23:00 on May 9th. Plex transcoding was happening at the time of crash.

     

    I have a remote syslog server set up and included the log from that. The last few lines before the crash are:

     

    May  9 03:07:54 Tower CA Backup/Restore: Backup / Restore Completed
    May  9 08:02:33 Tower webGUI: Successful login user root from 192.168.7.153
    May  9 08:04:52 Tower kernel: mdcmd (36): check 
    May  9 08:04:52 Tower kernel: md: recovery thread: check P ...
    May  9 08:05:05 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
    May  9 13:13:07 Tower flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
    May  9 15:51:27 Tower kernel: curl[26998]: segfault at d ip 0000151904658751 sp 00007ffd2fb6afc0 error 4 in ld-2.31.so[15190464e000+23000]
    May  9 15:51:27 Tower kernel: Code: 68 4c 8b 6c 24 70 49 89 c0 48 8b ac 24 d0 00 00 00 4c 8b a4 24 e8 00 00 00 4c 8b 5c 24 78 0f 1f 00 48 83 bc 24 f8 00 00 00 00 <0f> 84 61 01 00 00 41 0f b6 40 05 83 e0 03 83 e8 01 83 f8 01 0f 86

    tower-diagnostics-20220510-0902.zip syslog-192.168.7.224.log

    Unraid OS version 6.9.0-rc2 available

    in Prereleases

    Posted

    I think there's a bug in the drive temperature monitor thresholds - I am unable to set individual warning or critical temps for drives in my array or the cache. When I click apply, they simply go back to the global setting. This happens with my array both started and stopped, and following a fresh reboot. 

     

    Changing the temps through the global setting does persist. 

×
×
  • Create New...