All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 107817] New: NV50 : Nvidia NVS295 - Printing out EDID errors about not connected monitor ports
Date: Mon, 03 Sep 2018 16:12:43 +0000	[thread overview]
Message-ID: <bug-107817-8800@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 3408 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=107817

            Bug ID: 107817
           Summary: NV50 : Nvidia NVS295 - Printing out EDID errors about
                    not connected monitor ports
           Product: xorg
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: minor
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: cezdhzez-GK+4nHxFadIswetKESUqMA@public.gmane.org
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org

Card: Nvidia NVS295 with 2 DisplayPort connectors.

Problem: nouveau is spamming the kernel message, that it cant find the EDID of
not connected ports. Of course it cant, because there is no monitor connected
to that port.

When i connect the monitor to DisplayPort number 1, it writes, that it cant
find EDID on DisplayPort number 2. When i connect it to DisplayPort 2, it
writes that it cant find EDID of Display Port 1.

Linux kernel version: Kernel 4.19RC2 (its also there on older kernels)

Output when connected to DisplayPort 2 on kernel 4.19RC2 :

[    1.929715] fb: switching to nouveaufb from EFI VGA
[    1.930182] nouveau 0000:01:00.0: NVIDIA G98 (298e80a2)
[    2.064262] nouveau 0000:01:00.0: bios: version 62.98.75.00.08
[    2.086423] nouveau 0000:01:00.0: fb: 256 MiB GDDR3
[    2.155387] nouveau 0000:01:00.0: DRM: VRAM: 256 MiB
[    2.155388] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[    2.155393] nouveau 0000:01:00.0: DRM: TMDS table version 2.0
[    2.155394] nouveau 0000:01:00.0: DRM: DCB version 4.0
[    2.155397] nouveau 0000:01:00.0: DRM: DCB outp 00: 02000386 0f200010
[    2.155399] nouveau 0000:01:00.0: DRM: DCB outp 01: 02000332 00020010
[    2.155401] nouveau 0000:01:00.0: DRM: DCB outp 02: 040113a6 0f200010
[    2.155402] nouveau 0000:01:00.0: DRM: DCB outp 03: 04011342 00020010
[    2.155404] nouveau 0000:01:00.0: DRM: DCB conn 00: 00005046
[    2.155405] nouveau 0000:01:00.0: DRM: DCB conn 01: 0000a146
[    2.164991] nouveau 0000:01:00.0: DRM: MM: using M2MF for buffer copies
[    2.291693] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for DP-1
[    2.299041] nouveau 0000:01:00.0: DRM: allocated 1920x1080 fb: 0x50000, bo
(____ptrval____)
[    2.299785] fbcon: nouveaufb (fb0) is primary device
[    2.423693] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for DP-1
[    2.607694] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for DP-1
[    2.616508] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device
[    2.631694] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on
minor 1
[    3.283698] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for DP-1
[   38.267703] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for DP-1
[   38.403699] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for DP-1
[   50.075703] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for DP-1
[   50.207697] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for DP-1
[   53.323704] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for DP-1
[   53.455714] nouveau 0000:01:00.0: DRM: DDC responded, but no EDID for DP-1

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4713 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2018-09-03 16:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-03 16:12 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-107817-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2018-09-05  0:17   ` [Bug 107817] NV50 : Nvidia NVS295 - Printing out EDID errors about not connected monitor ports bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-107817-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.