From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104206] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2!
Date: Thu, 21 Dec 2017 00:35:19 +0000 [thread overview]
Message-ID: <bug-104206-502-G5V9Uv5gqX@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104206-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1004 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104206
--- Comment #17 from Andrew <formisc@gmail.com> ---
Harry,
On rc2 i had this message , but i also saw terminals(init3)
On rc3 i didnt see this message, but i didnt see terminals either.
The new kernel version was the only change on the system.
On Dec 20, 2017 19:04, <bugzilla-daemon@freedesktop.org> wrote:
> *Comment # 16 <https://bugs.freedesktop.org/show_bug.cgi?id=104206#c16> on
> bug 104206 <https://bugs.freedesktop.org/show_bug.cgi?id=104206> from Harry
> Wentland <harry.wentland@amd.com> *
>
> Do I understand it correctly that the issue is resolved other than the error
> message on cold boot?
>
> That error message is logged erroneously. The fix for the wrong error log is in
> the pipeline and should land with 4.16.
>
> ------------------------------
> You are receiving this mail because:
>
> - You reported the bug.
>
>
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2943 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-12-21 0:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 3:15 [Bug 104206] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! bugzilla-daemon
2017-12-11 11:18 ` bugzilla-daemon
2017-12-11 11:24 ` bugzilla-daemon
2017-12-11 13:24 ` bugzilla-daemon
2017-12-11 15:32 ` bugzilla-daemon
2017-12-11 15:33 ` bugzilla-daemon
2017-12-11 15:48 ` bugzilla-daemon
2017-12-11 16:06 ` bugzilla-daemon
2017-12-11 16:09 ` bugzilla-daemon
2017-12-11 17:37 ` bugzilla-daemon
2017-12-14 20:11 ` bugzilla-daemon
2017-12-14 20:12 ` bugzilla-daemon
2017-12-14 20:14 ` bugzilla-daemon
2017-12-14 20:23 ` bugzilla-daemon
2017-12-14 20:33 ` bugzilla-daemon
2017-12-15 0:09 ` bugzilla-daemon
2017-12-15 8:39 ` bugzilla-daemon
2017-12-21 0:04 ` bugzilla-daemon
2017-12-21 0:35 ` bugzilla-daemon [this message]
2018-06-16 16:29 ` bugzilla-daemon
2018-08-11 16:56 ` bugzilla-daemon
2018-08-13 19:44 ` bugzilla-daemon
2019-01-01 21:20 ` bugzilla-daemon
2019-04-17 8:19 ` bugzilla-daemon
2019-04-17 8:21 ` bugzilla-daemon
2019-05-18 22:29 ` bugzilla-daemon
2019-09-03 16:34 ` bugzilla-daemon
2019-11-19 8:27 ` 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-104206-502-G5V9Uv5gqX@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).