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: Wed, 17 Apr 2019 08:19:03 +0000 [thread overview]
Message-ID: <bug-104206-502-4ZPC8afHWf@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104206-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 3883 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104206
--- Comment #22 from Luya Tshimbalanga <luya@fedoraproject.org> ---
I also confirm a similar issue running on mobile Raven Ridge Ryzen 2500u from a
HP Envy x360 model. Kernel version: 5.0.7-300.fc30.x86_64
[drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from
Adapter Service for connector index:2! type 0 expected 3
[ 2.806093] fb0: switching to amdgpudrmfb from EFI VGA
[ 2.806194] amdgpu 0000:03:00.0: enabling device (0006 -> 0007)
[ 2.813008] amdgpu 0000:03:00.0: VRAM: 1024M 0x000000F400000000 -
0x000000F43FFFFFFF (1024M used)
[ 2.813009] amdgpu 0000:03:00.0: GART: 1024M 0x0000000000000000 -
0x000000003FFFFFFF
[ 2.813010] amdgpu 0000:03:00.0: AGP: 267419648M 0x000000F800000000 -
0x0000FFFFFFFFFFFF
[ 2.813139] [drm] amdgpu: 1024M of VRAM memory ready
[ 2.813141] [drm] amdgpu: 3072M of GTT memory ready.
[ 2.984250] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector
ObjectID from Adapter Service for connector index:2! type 0 expected 3
[ 3.022277] fbcon: amdgpudrmfb (fb0) is primary device
[ 3.022295] amdgpu 0000:03:00.0: fb0: amdgpudrmfb frame buffer device
[ 3.032310] amdgpu 0000:03:00.0: ring gfx uses VM inv eng 0 on hub 0
[ 3.032321] amdgpu 0000:03:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[ 3.032327] amdgpu 0000:03:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[ 3.032334] amdgpu 0000:03:00.0: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[ 3.032341] amdgpu 0000:03:00.0: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[ 3.032347] amdgpu 0000:03:00.0: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[ 3.032353] amdgpu 0000:03:00.0: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[ 3.032358] amdgpu 0000:03:00.0: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[ 3.032364] amdgpu 0000:03:00.0: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[ 3.032370] amdgpu 0000:03:00.0: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
[ 3.032376] amdgpu 0000:03:00.0: ring sdma0 uses VM inv eng 0 on hub 1
[ 3.032382] amdgpu 0000:03:00.0: ring vcn_dec uses VM inv eng 1 on hub 1
[ 3.032389] amdgpu 0000:03:00.0: ring vcn_enc0 uses VM inv eng 4 on hub 1
[ 3.032395] amdgpu 0000:03:00.0: ring vcn_enc1 uses VM inv eng 5 on hub 1
[ 3.032400] amdgpu 0000:03:00.0: ring vcn_jpeg uses VM inv eng 6 on hub 1
[ 3.058543] [drm] Initialized amdgpu 3.27.0 20150101 for 0000:03:00.0 on
minor 0
[ 364.360663] amdgpu: [powerplay] dpm has been enabled
[ 366.914619] amdgpu 0000:03:00.0: ring gfx uses VM inv eng 0 on hub 0
[ 366.914620] amdgpu 0000:03:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0
[ 366.914622] amdgpu 0000:03:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0
[ 366.914624] amdgpu 0000:03:00.0: ring comp_1.2.0 uses VM inv eng 5 on hub 0
[ 366.914625] amdgpu 0000:03:00.0: ring comp_1.3.0 uses VM inv eng 6 on hub 0
[ 366.914626] amdgpu 0000:03:00.0: ring comp_1.0.1 uses VM inv eng 7 on hub 0
[ 366.914628] amdgpu 0000:03:00.0: ring comp_1.1.1 uses VM inv eng 8 on hub 0
[ 366.914629] amdgpu 0000:03:00.0: ring comp_1.2.1 uses VM inv eng 9 on hub 0
[ 366.914630] amdgpu 0000:03:00.0: ring comp_1.3.1 uses VM inv eng 10 on hub 0
[ 366.914631] amdgpu 0000:03:00.0: ring kiq_2.1.0 uses VM inv eng 11 on hub 0
[ 366.914632] amdgpu 0000:03:00.0: ring sdma0 uses VM inv eng 0 on hub 1
[ 366.914633] amdgpu 0000:03:00.0: ring vcn_dec uses VM inv eng 1 on hub 1
[ 366.914634] amdgpu 0000:03:00.0: ring vcn_enc0 uses VM inv eng 4 on hub 1
[ 366.914635] amdgpu 0000:03:00.0: ring vcn_enc1 uses VM inv eng 5 on hub 1
[ 366.914636] amdgpu 0000:03:00.0: ring vcn_jpeg uses VM inv eng 6 on hub 1
[ 6158.513437] amdgpu: [powerplay] pp_dpm_switch_power_profile was not
implemented.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4808 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 prev parent reply other threads:[~2019-04-17 8:19 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
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 [this message]
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-4ZPC8afHWf@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).