From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 109881] Screens reorganise, failed to enable link training errors in dmesg about 60s after plugging in dock
Date: Wed, 06 Mar 2019 07:59:06 +0000 [thread overview]
Message-ID: <bug-109881-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1166 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=109881
Bug ID: 109881
Summary: Screens reorganise, failed to enable link training
errors in dmesg about 60s after plugging in dock
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: All
Status: NEW
Keywords: have-backtrace
Severity: normal
Priority: medium
Component: General
Assignee: dri-devel@lists.freedesktop.org
Reporter: shifachishti65@gmail.com
CC: terrence.xu@intel.com, wahajakm1234@gmail.com,
zeeadeel9@gmail.com
Depends on: 109873
+++ This bug was initially created as a clone of Bug #109873 +++
Screens reorganise, failed to enable link training errors in dmesg about 60s
after plugging in dock
Referenced Bugs:
https://bugs.freedesktop.org/show_bug.cgi?id=109873
[Bug 109873] Screens reorganise, failed to enable link training errors in dmesg
about 60s after plugging in dock
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3294 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-03-06 7:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 7:59 bugzilla-daemon [this message]
2019-10-14 13:29 ` [Bug 109881] Screens reorganise, failed to enable link training errors in dmesg about 60s after plugging in dock bugzilla-daemon
2019-11-29 16: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-109881-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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.