All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 207901] Nouveau: In a 4 monitor setup, 1-2 displays remains black after boot
Date: Thu, 02 Jul 2020 19:03:49 +0000	[thread overview]
Message-ID: <bug-207901-2300-EAZlplY29q@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207901-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=207901

--- Comment #22 from Lyude Paul (lyude@redhat.com) ---
Hi! Sorry this took me a little bit to reply to. So-it looks like we did indeed
fix the i2c timeout issue that I was seeing on your board, so the next
suspicious thing in your log seems to be the fact one of your DP ports (DP-7 in
particular) appears to think it's being continuously hotplugged:

[   90.996867] nouveau 0000:01:00.0: DRM: unplugged DP-7
[   91.191704] [drm:drm_add_display_info [drm]] non_desktop set to 0
[   91.191711] [drm:drm_add_display_info [drm]] HDMI: DVI dual 0, max TMDS
clock 300000 kHz
[   91.297638] [drm:drm_dp_dpcd_access [drm_kms_helper]] Too many retries,
giving up. First error: -110
[   91.297642] [drm:drm_helper_hpd_irq_event [drm_kms_helper]]
[CONNECTOR:73:DP-4] status updated from connected to connected
[   91.493173] [drm:drm_add_display_info [drm]] non_desktop set to 0
[   91.493179] [drm:drm_add_display_info [drm]] HDMI: DVI dual 0, max TMDS
clock 300000 kHz
[   91.599120] [drm:drm_dp_dpcd_access [drm_kms_helper]] Too many retries,
giving up. First error: -110
[   91.599123] [drm:drm_helper_hpd_irq_event [drm_kms_helper]]
[CONNECTOR:76:DP-5] status updated from connected to connected
[   91.599335] nouveau 0000:01:00.0: DRM: display: 4x540000 dpcd 0x12
[   91.599336] nouveau 0000:01:00.0: DRM: encoder: 4x810000
[   91.599336] nouveau 0000:01:00.0: DRM: maximum: 4x540000
[   91.605980] [drm:drm_add_display_info [drm]] non_desktop set to 0
[   91.605986] [drm:drm_add_display_info [drm]] HDMI: DVI dual 0, max TMDS
clock 0 kHz
[   91.606300] [drm:drm_helper_hpd_irq_event [drm_kms_helper]]
[CONNECTOR:79:DP-6] status updated from connected to connected
[   91.606518] nouveau 0000:01:00.0: DRM: display: 4x540000 dpcd 0x12
[   91.606519] nouveau 0000:01:00.0: DRM: encoder: 4x810000
[   91.606519] nouveau 0000:01:00.0: DRM: maximum: 4x540000
[   91.613389] [drm:drm_add_display_info [drm]] non_desktop set to 0
[   91.613394] [drm:drm_add_display_info [drm]] HDMI: DVI dual 0, max TMDS
clock 0 kHz
[   91.613722] [drm:drm_helper_hpd_irq_event [drm_kms_helper]]
[CONNECTOR:82:DP-7] status updated from connected to connected
[   91.614016] nouveau 0000:01:00.0: DRM: plugged DP-7

What kind of setup do you have your monitors hooked up through? Are they on any
laptop docks/standalone MST hubs, do they go through any video adaptors, what
models/brands and what kind of connectors do they use, etc.

As well, do you think you can grab another log from your system but using:

log_buf_len=50M drm.debug=0x116 nouveau.debug=disp=trace

(include the full log from your boot if you can and don't trim it, since it's
likely going to be a big log)

I have a feeling one of your MST devices is doing some weird out-of-spec
behavior that we might need to teach nouveau to handle

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-07-02 19:03 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 19:17 [Bug 207901] New: Nouveau: In a 4 monitor setup, 1-2 displays remains black after boot bugzilla-daemon
2020-05-26 19:19 ` [Bug 207901] " bugzilla-daemon
2020-05-26 19:20 ` bugzilla-daemon
2020-05-26 19:20 ` bugzilla-daemon
2020-05-26 19:21 ` bugzilla-daemon
2020-05-26 19:26 ` bugzilla-daemon
2020-05-26 19:28 ` bugzilla-daemon
2020-05-27 15:37 ` bugzilla-daemon
2020-05-27 15:38 ` bugzilla-daemon
2020-05-27 15:38 ` bugzilla-daemon
2020-05-27 16:36 ` bugzilla-daemon
2020-05-27 19:35 ` bugzilla-daemon
2020-05-27 19:35 ` bugzilla-daemon
2020-05-27 19:37 ` bugzilla-daemon
2020-06-10 22:28 ` bugzilla-daemon
2020-06-10 23:49 ` bugzilla-daemon
2020-06-11 17:31 ` bugzilla-daemon
2020-06-18 15:14 ` bugzilla-daemon
2020-06-18 15:30 ` bugzilla-daemon
2020-06-23 16:49 ` bugzilla-daemon
2020-06-25 15:27 ` bugzilla-daemon
2020-06-25 15:28 ` bugzilla-daemon
2020-07-02 19:03 ` bugzilla-daemon [this message]
2020-07-13 14:51 ` bugzilla-daemon
2020-07-13 14:52 ` bugzilla-daemon
2020-07-20 21:44 ` bugzilla-daemon
2020-07-27 15:32 ` bugzilla-daemon
2020-07-27 15:37 ` bugzilla-daemon
2020-07-31 21:23 ` bugzilla-daemon
2020-08-10 15:32 ` bugzilla-daemon
2020-09-21 18:54 ` bugzilla-daemon
2020-11-02 15:48 ` bugzilla-daemon

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-207901-2300-EAZlplY29q@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.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.