• [6.11.1] Unexpected DP dual mode adapter


    kaiguy
    • Minor

    I suspect this may be a related issue to the recent fix 'silence EDID "block all zeros" and "has corrupt header" notices'

     

    The following errors started showing up in the syslog about 6 hours after upgrading to 6.11.1 and continue to show up about every 15 minutes.

     

    Oct  7 03:33:08 titan kernel: i915 0000:00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 01
    Oct  7 03:47:00 titan kernel: i915 0000:00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 07
    Oct  7 03:49:15 titan kernel: i915 0000:00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 03
    Oct  7 03:55:59 titan kernel: i915 0000:00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 01
    Oct  7 03:57:06 titan kernel: i915 0000:00:02.0: [drm] *ERROR* Unexpected DP dual mode adaptor ID 03

     

    Running headless with no dummy plug. Diagnostics attached.

    titan-diagnostics-20221007-0707.zip




    User Feedback

    Recommended Comments

    I see your post is over 6 months old with no replies posted.  I have been getting these same error messages.  I'm a Linux / Unraid newbie and have little clue what is causing and/or how to stop the error messages.  I posted a similar message and received no replies   Did you ever get any guidance or figure out how to stop the error messages?   

    Link to comment

    IIRC the ones I've seen so far are all using Asrock boards, suggesting some BIOS/board issue, anyone here using a different brand?

    Link to comment
    On 8/10/2023 at 3:04 AM, JorgeB said:

    IIRC the ones I've seen so far are all using Asrock boards, suggesting some BIOS/board issue, anyone here using a different brand?

    I'm using a supermicro board with the same issue

    Link to comment
    On 8/15/2023 at 9:49 AM, JorgeB said:

    Anyone see this error using a board (any brand) that has an iGPU output and it's connected to a monitor?

    Yes, I am having this issue with:

    Motherboard: AsRock N100DC-ITX

    CPU: Intel N100 (onboard)

    RAM: Kingston Fury 16GB

    PSU: 19V 65W Barrel jack

    HDD: 2x 2TB WD Red

     

    Note: The server also crashes and reboots after a few minutes after I start the array

    I am still trying to get some kind of logs somewhere

    Link to comment

    I have the same error i am running

     

    Micro-Star International Co., Ltd. Z590-A PRO (MS-7D09) , Version 1.0
    American Megatrends International, LLC., Version 1.80
    BIOS dated: Thu 29 Sep 2022 12:00:00 AM BST
    Is there any update on the issue please  ?

    Link to comment

    I did some research. This is not an issue with UnRAID but instead the Linux kernel version it uses that does not have support for this CPU/iGPU.

     

    We have to wait for a Linux kernel version 6.2+ to have it working correctly with frequency scaling and video hardware acceleration. This is most probably a UnRAID version 1.13.x.

     

    In the meantime, as a workaround, one can create a virtual machine with an operative system running a Linux kernel 6.2+ and passthrough the iGPU to make use of hardware acceleration.

     

    Ref:

     

    Edited by GPereira
    Link to comment

    I am also getting this error a lot. So going by GPereira's post, I suppose there's no real harm? I can just leave it and wait for the next Unraid version to (likely) fix this?

     

    edit: I blacklisted the 915 iGPU using this command:

    That seems to have gotten rid of the error. I am not using the iGPU anyway.

    Edited by Aemstel
    Link to comment

    Same Problem here:

    Asrock N100DC-ITX. 32GB RAM, 2TB Samsung Evo Plus NVME + 4 TB Samsung Evo 870 + 2 TB Samsung Evo 870. A Monitor is connected via HDMI but switched off.

     

    What is interesting:

    - it happened on the day I booted the last time and flooded my log for approx. 8h with messages. Then it stopped and until today no further message (as no reboot since).

     

    Screenshots:

    Start of flood (Server was started 11:27 o'clock):

    1476562154_Bildschirmfoto2023-10-22um20_30_22.thumb.png.2a605091678f56a0d881a771d16eb171.png


    End of Flood:

    810750216_Bildschirmfoto2023-10-22um20_30_34.thumb.png.fdc5543172b2b605c2f9503c673c7268.png

     

    PS: I just checked the Power Consumption Logs of the server for the time of the problem. There was no remarkable additional Power Consumption visible. The min. Idle value was around 7,7W like always. 

    Edited by MPC561
    Link to comment
    56 minutes ago, MPC561 said:

    Same Problem here:

    Asrock N100DC-ITX. 32GB RAM, 2TB Samsung Evo Plus NVME + 4 TB Samsung Evo 870 + 2 TB Samsung Evo 870. A Monitor is connected via HDMI but switched off.

     

    What is interesting:

    - it happened on the day I booted the last time and flooded my log for approx. 8h with messages. Then it stopped and until today no further message (as no reboot since).

     

    Screenshots:

    Start of flood (Server was started 11:27 o'clock):

    1476562154_Bildschirmfoto2023-10-22um20_30_22.thumb.png.2a605091678f56a0d881a771d16eb171.png


    End of Flood:

    810750216_Bildschirmfoto2023-10-22um20_30_34.thumb.png.fdc5543172b2b605c2f9503c673c7268.png

     

    PS: I just checked the Power Consumption Logs of the server for the time of the problem. There was no remarkable additional Power Consumption visible. The min. Idle value was around 7,7W like always

    I get those errors when I trigger graphics related tasks like playing a video on Plex

    Link to comment
    1 minute ago, GPereira said:

    I get those errors when I trigger graphics related tasks like playing a video on Plex

    I will try it with Jellyfin and transcode something. At least I know that transcode in general works. This I tested already after I switched to this mainboard and had at least 4 transcode streams in parallel running. But I will try again now.

    Link to comment

    In Jellyfin I tested today only 4 parallel streams (1x4k to 1080p, 2x1080p to 720p/8/4 and 1x720 to 480p/3). No tone mapping activated.

     

    The load on the cores was high (maybe subtitle stuff?) but also the iGPU is very active:

    1131084600_Bildschirmfoto2023-10-22um22_03_43.thumb.png.06ceab0c639ff0fc8bbe4e04eaf30e3d.png

     

    In the log is no new entry with the i915 message.

     

    Link to comment

    Does your CPU Change frequencies dynamically? Mine is stuck at one specific frequency. I can set the boot frequency in BIOS, the frequency that the CPU is set before OS handoff but then UnRAID does not change it. If I set to high performance it stays at a fixed high frequency, if I set to low power it stays at a low frequency. Has this happened to you?

    Link to comment

    We should not go away from the maintopic, But yes, with corefreq I see that my system clocks up to high frequencies if there is load (I use powersave govenor btw.)

    2092698110_Bildschirmfoto2023-10-23um11_09_35.thumb.png.1893fcabf13dbd6842c00caaf41ff67f.png

    Link to comment

    I have been getting this message for several months.
    I have installed the plugin intel_gpu_top.
    When I shortly run "intel_gpu_top" in a terminal the messages in the log stop until the next reboot

     

    ASRock B360M-HDV with i7-8700K

    • Like 1
    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.