• [6.7.0] call trace then ethernet interface down

    apotek

    By apotek

      • Solved Annoyance

    Try to upgrade from 6.6.7.  Once rebooted after upgrade to 6.7.0, the server has no active ethernet port. Logs show a call trace then constant resetting of adapter (Intel i211.) It happens if booted in safe mode with no plugins + GUI and when booted normally. If restored to 6.6.7, all issues disappear and the server has normal network access. I have tried install 6.7.1-rc2 and same results: call trace and network eth0 is down.

    Any ideas?

    Thanks

    unraidtoo-diagnostics-20190614-0413.zip unraidtoo-diagnostics-20190615-0023.zip unraidtoo-diagnostics-20190614-2148.zip

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    apotek

    I fixed this issue by editing the syslinux.cfg to include "iommu=pt":

     

    append initrd=/bzroot iommu=pt

     

    It also worked with "iommu=soft".   Now the server is updated to 6.7.0 with no issues. There are no call traces occurring and the network adapter works like it should with full access to the server from Windows 10 and the server has internet access for plugin and docker updates.

    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.