Jump to content
  • Hard Crashes using Raven Ridge


    reey
    • Closed

    Hi,

     

    I'm running unRAID 6.5.1 RC3 on my AMD 2400G with a Asus Prime X370 Pro Motherboard.

    I disabled the C6 States in my go file and this has been working with my AMD 1700X.

    I've then switched to the 2400G and with that the system hard crashes after a few minutes..

    I've been trying Ubuntu with kernel 4.15 and newer and had no such problems..

    I'm not sure if this has anything to do with the kernel version, but would it be possible to bump the unraid kernel to 4.15 or newer?

     

    I will try to attach a log tomorrow as described here:

     

    I've tried it multiple times, but I'm not getting any stacktrace or error message with the method from the link above..

    If the output is needed I can send it per PM, since it contains IP adresses and URLs I don't want to publish.

     

    Regards

    Reey




    User Feedback

    Recommended Comments

    There was talk of moving to 4.16?

     

    Due to filesystem improvements.

     

    Maybe one of the devs can chime in if unRaid 6.6 will be on kernel 4.16 :)

    • Like 1
    Link to comment
    On 4/2/2018 at 6:11 PM, Dazog said:

    There was talk of moving to 4.16?

     

    Planning to do this in unRAID 6.6 release.

    Closing this issue because this is not prerelease-specific.  Please post in General Support.

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.

×
×
  • Create New...