Bug 104206

Summary:

[drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2!

Product:

DRI

Reporter:

Andrew <formisc>

Component:

DRM/AMDgpu

Assignee:

Default DRI bug account <dri-devel>

Status:

RESOLVED MOVED

QA Contact:

Severity:

major

Priority:

medium

CC:

alex.bradatan85, bwalker, harry.wentland, jordan.lazare, jvdelisle, leonard

Version:

XOrg git

Hardware:

x86-64 (AMD64)

OS:

Linux (All)

Whiteboard:

i915 platform:

i915 features:

Attachments:

Description	Flags
attachment-32472-0.html	none
Xlog	none
messages.log	none
x log with "Aceel" turned off	none
attachment-30913-0.html	none
journalctl from a boot with a cold laptop archlinux	none
lspci -vv {Probook 455 G3 carrizo a10-8700p rev c5)	none
kernel parameters set for 4.15-rc3	none
journalctl of a boot of my archlinux notebook totally cold	none
attachment-28034-0.html	none
dmesg output showing the drm error	none
More recent dmesg with the error.	none
Journal boot from hp envy x360 cp0xxx	none
dmesg from vivobook x505za	none

Description Andrew 2017-12-11 03:15:29 UTC

Hello,
 i've got :
```
Dec 10 16:54:18 hp kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2!
Dec 10 16:54:19 hp kernel: [drm:hwss_wait_for_blank_complete [amdgpu]] *ERROR* DC: failed to blank crtc!  lete [amdgpu]] *ERROR* DC: failed to blank crtc!
```
during the boot after i upgraded from latest fedora kernel to 4.15.0-0.rc2.git2.2

the great part about this kernel that amd Carruzo finally (almost) working. I still don't get to boot into X. but at least i have terminals on init3 now.

X - https://paste.fedoraproject.org/paste/9VAWjgZgfELNKisxYSXEpw
boot - https://paste.fedoraproject.org/paste/8A4R4fYX09Rke~5UZcTqZQ

i used Kelly's kernel config (https://bugs.freedesktop.org/show_bug.cgi?id=95306#c74):
```
CONFIG_DRM_AMD_DC=y
CONFIG_DRM_AMD_DC_PRE_VEGA=y
# CONFIG_DRM_AMD_DC_FBC is not set
CONFIG_DRM_AMD_DC_DCN1_0=y
# CONFIG_DEBUG_KERNEL_DC is not set
```

Comment 1 Michel Dänzer 2017-12-11 11:18:53 UTC

Please attach files here directly instead of

Comment 2 Michel Dänzer 2017-12-11 11:24:38 UTC

... instead of referencing external sites, especially pastebins.

Looks like there's a Mesa installation / configuration issue which prevents hardware acceleration from working, and the xf86-video-amdgpu driver can't handle this and crashes.

Comment 3 Andrew 2017-12-11 13:24:10 UTC

Created attachment 136080 [details]
attachment-32472-0.html

Michael,
 Thank you for your reply.

Why pastebin is not good? ( Thought fedora's one is blessed/approved)

The rawhide mesa rpms versions are the same as in f27. Should i
recompile/reconfigure them somehow?


On Dec 11, 2017 6:25 AM, <bugzilla-daemon@freedesktop.org> wrote:

> *Comment # 2 <https://bugs.freedesktop.org/show_bug.cgi?id=104206#c2> on
> bug 104206 <https://bugs.freedesktop.org/show_bug.cgi?id=104206> from
> Michel Dänzer <michel@daenzer.net> *
>
> ... instead of referencing external sites, especially pastebins.
>
> Looks like there's a Mesa installation / configuration issue which prevents
> hardware acceleration from working, and the xf86-video-amdgpu driver can't
> handle this and crashes.
>
> ------------------------------
> You are receiving this mail because:
>
>    - You reported the bug.
>
>

Comment 4 Andrew 2017-12-11 15:32:50 UTC

Created attachment 136081 [details]
Xlog

Comment 5 Andrew 2017-12-11 15:33:59 UTC

Created attachment 136082 [details]
messages.log

Comment 6 Andrew 2017-12-11 15:48:41 UTC

Created attachment 136083 [details]
x log with "Aceel" turned off

the X doesn't hard crash when i turn an acceleration off. X still doesn't work - just exists back to the terminal.

i used the following config in this case:
[code]
Section "Device"
        Identifier "Carrizo"
        Driver "amdgpu"
        Option "AccelMethod" "none"
#       Option "Accel" "on"
#       Option "DRI" "3"
        Option "TearFree" "on"
EndSection
[/code]

Comment 7 Michel Dänzer 2017-12-11 16:09:39 UTC

(In reply to Andrew from comment #6)
> the X doesn't hard crash when i turn an acceleration off.

Normally you'd want Option "Accel" "off" to disable accleration, not "AccelMethod" "none".


> X still doesn't work - just exists back to the terminal.

The Xorg log doesn't show any problem anymore, so it sounds like that's an X client session issue now. How exactly are you trying to start X?

Comment 8 Andrew 2017-12-11 17:37:38 UTC

Created attachment 136089 [details]
attachment-30913-0.html

Correct you are about _not_ disabling the "accel". I was trying to figure
out what is breaking X this time around (i have a long thread on forums
trying to get amdgpu to work on this laptop).

I run on init3. And use "startx" when logged in as root. (Usually im on
init 5, but on all prior kernels to  4.15rc2 i didnt even got to see
terminals , just a black screen).


On Dec 11, 2017 11:10, <bugzilla-daemon@freedesktop.org> wrote:

> *Comment # 7 <https://bugs.freedesktop.org/show_bug.cgi?id=104206#c7> on
> bug 104206 <https://bugs.freedesktop.org/show_bug.cgi?id=104206> from
> Michel Dänzer <michel@daenzer.net> *
>
> (In reply to Andrew from comment #6 <https://bugs.freedesktop.org/show_bug.cgi?id=104206#c6>)> the X doesn't hard crash when i turn an acceleration off.
>
> Normally you'd want Option "Accel" "off" to disable accleration, not
> "AccelMethod" "none".
>
> > X still doesn't work - just exists back to the terminal.
>
> The Xorg log doesn't show any problem anymore, so it sounds like that's an X
> client session issue now. How exactly are you trying to start X?
>
> ------------------------------
> You are receiving this mail because:
>
>    - You reported the bug.
>
>

Comment 9 Charly 2017-12-14 20:11:27 UTC

Created attachment 136179 [details]
journalctl from a boot with a cold laptop archlinux

Comment 10 Charly 2017-12-14 20:12:53 UTC

Created attachment 136180 [details]
lspci -vv {Probook 455 G3 carrizo a10-8700p rev c5)

Comment 11 Charly 2017-12-14 20:14:11 UTC

Created attachment 136181 [details]
kernel parameters set for 4.15-rc3

Comment 12 Charly 2017-12-14 20:23:18 UTC

hi team

By installing kerenl 4.15-rc3 the blamk screen related on bug 95306 seems to be fixed, and I'm very happy for that !

the message :

[drm:hwss_wait_for_blank_complete [amdgpu]] *ERROR* DC: failed to blank crtc!

only appers when the laptop is cold (not a reboot, but a boot after it was powered off until it is cold)

The APU is a carrizo A10-8700p rev c5.

Absolutely no issue with X: I can start (xfce4) manually. I guess the error appears during mode setting. Before we got blamk screen... and now we have this message ...

Comment 13 Charly 2017-12-14 20:33:53 UTC

Created attachment 136182 [details]
journalctl of a boot of my archlinux notebook totally cold

Comment 14 Andrew 2017-12-15 00:09:28 UTC

Charly,
 Does X work all the time or only after reboot?

Comment 15 Charly 2017-12-15 08:39:07 UTC

Hi Andrew. X works all the time.

Comment 16 Harry Wentland 2017-12-21 00:04:21 UTC

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.

Comment 17 Andrew 2017-12-21 00:35:19 UTC

Created attachment 136337 [details]
attachment-28034-0.html

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.
>
>

Comment 18 Brad Walker 2018-06-16 16:29:24 UTC

Created attachment 140180 [details]
dmesg output showing the drm error

I continue to have this problem. The system is an HP 17-g121wm with a A10-8700P processor. This system contains an AMD Radeon R6 gpu.

I am testing Fedora 28 running the Linux 4.17 kernel.
https://fedoraproject.org/wiki/Test_Day:2018-06-12_Kernel_4.17_Test_Day

This error leaves causes my window system to crash, sometimes rotate its orientation in the wrong way, and leaves a black screen.

I understand there has been some progress on this. It would be really helpful to get this fixed.

Comment 19 Brad Walker 2018-08-11 16:56:22 UTC

I updated to the latest version of Fedora 28 and still this problem..

FYI...

Comment 20 Jordan L 2018-08-13 19:44:41 UTC

Hi Brad,

Would you happen to have a *full* dmesg and Xorg.0 log of the latest? Generally that error message shouldn't cause a hang, just that one connector the bios is reporting isn't mapped/supported properly.

Comment 21 JerryD 2019-01-01 21:20:43 UTC

Created attachment 142936 [details]
More recent dmesg with the error.

There are a number of other issues with this machine still, but it appears to be running stable. Providing this as a datapoint if you need it.

Comment 22 Luya Tshimbalanga 2019-04-17 08:19:03 UTC

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.

Comment 23 Luya Tshimbalanga 2019-04-17 08:21:14 UTC

Created attachment 144009 [details]
Journal boot from hp envy x360 cp0xxx

Comment 24 alex.bradatan85 2019-05-18 22:29:10 UTC

Created attachment 144298 [details]
dmesg from vivobook x505za

Added the dmesg from boot of a Asus Vivobook X505ZA with a Ryzen 2500U with Vega 8 mobile graphics running Arch Linux kernel version 5.1.2.

Comment 25 Paul 2019-09-03 16:34:59 UTC

Also seeing this on an HP255G7 Ryzen3 

paul@HP255G7:~> journalctl -b | grep -i "drm:construct"
Sep 03 17:21:39 HP255G7 kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3
Sep 03 17:21:39 HP255G7 kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3

paul@HP255G7:~> inxi -GxxSz
System:    Host: HP255G7 Kernel: 4.12.14-lp151.28.13-default x86_64 bits: 64 gcc: 7.4.0
           Desktop: KDE Plasma 5.12.8 (Qt 5.9.7) dm: sddm,sddm Distro: openSUSE Leap 15.1
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Radeon Vega 8 Mobile bus-ID: 04:00.0 chip-ID: 1002:15dd
           Display Server: x11 (X.Org 1.20.3 ) drivers: ati,amdgpu (unloaded: modesetting,fbdev,vesa)
           Resolution: 1920x1080@60.01hz
           OpenGL: renderer: AMD RAVEN (DRM 3.27.0, 4.12.14-lp151.28.13-default, LLVM 7.0.1)
           version: 4.5 Mesa 18.3.2 Direct Render: Yes

paul@HP255G7:~> /sbin/lspci -nnk | egrep -A3 "VGA|Display|3D"
04:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Radeon Vega 8 Mobile [1002:15dd] (rev c5)
        Subsystem: Hewlett-Packard Company Device [103c:84ae]
        Kernel driver in use: amdgpu
        Kernel modules: amdgpu


paul@HP255G7:~> journalctl -b | grep -i amdgpu
Sep 03 17:21:38 HP255G7 kernel: [drm] amdgpu kernel modesetting enabled.
Sep 03 17:21:38 HP255G7 kernel: fb: switching to amdgpudrmfb from EFI VGA
Sep 03 17:21:38 HP255G7 kernel: amdgpu 0000:04:00.0: VRAM: 256M 0x000000F400000000 - 0x000000F40FFFFFFF (256M used)
Sep 03 17:21:38 HP255G7 kernel: amdgpu 0000:04:00.0: GART: 1024M 0x000000F500000000 - 0x000000F53FFFFFFF
Sep 03 17:21:38 HP255G7 kernel: [drm] amdgpu: 256M of VRAM memory ready
Sep 03 17:21:38 HP255G7 kernel: [drm] amdgpu: 3072M of GTT memory ready.
Sep 03 17:21:39 HP255G7 kernel: amdgpu: [powerplay] dpm has been enabled
Sep 03 17:21:39 HP255G7 kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:2! type 0 expected 3
Sep 03 17:21:39 HP255G7 kernel: [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3
Sep 03 17:21:39 HP255G7 kernel: fbcon: amdgpudrmfb (fb0) is primary device
Sep 03 17:21:39 HP255G7 kernel: amdgpu 0000:04:00.0: fb0: amdgpudrmfb frame buffer device
Sep 03 17:21:39 HP255G7 kernel: amdgpu 0000:04:00.0: ring 0(gfx) uses VM inv eng 4 on hub 0
Sep 03 17:21:39 HP255G7 kernel: amdgpu 0000:04:00.0: ring 1(comp_1.0.0) uses VM inv eng 5 on hub 0
Sep 03 17:21:39 HP255G7 kernel: amdgpu 0000:04:00.0: ring 2(comp_1.1.0) uses VM inv eng 6 on hub 0
Sep 03 17:21:39 HP255G7 kernel: amdgpu 0000:04:00.0: ring 3(comp_1.2.0) uses VM inv eng 7 on hub 0
Sep 03 17:21:39 HP255G7 kernel: amdgpu 0000:04:00.0: ring 4(comp_1.3.0) uses VM inv eng 8 on hub 0
Sep 03 17:21:39 HP255G7 kernel: amdgpu 0000:04:00.0: ring 5(comp_1.0.1) uses VM inv eng 9 on hub 0
Sep 03 17:21:39 HP255G7 kernel: amdgpu 0000:04:00.0: ring 6(comp_1.1.1) uses VM inv eng 10 on hub 0
Sep 03 17:21:39 HP255G7 kernel: amdgpu 0000:04:00.0: ring 7(comp_1.2.1) uses VM inv eng 11 on hub 0
Sep 03 17:21:39 HP255G7 kernel: amdgpu 0000:04:00.0: ring 8(comp_1.3.1) uses VM inv eng 12 on hub 0
Sep 03 17:21:39 HP255G7 kernel: amdgpu 0000:04:00.0: ring 9(kiq_2.1.0) uses VM inv eng 13 on hub 0
Sep 03 17:21:39 HP255G7 kernel: amdgpu 0000:04:00.0: ring 10(sdma0) uses VM inv eng 4 on hub 1
Sep 03 17:21:39 HP255G7 kernel: amdgpu 0000:04:00.0: ring 11(vcn_dec) uses VM inv eng 5 on hub 1
Sep 03 17:21:39 HP255G7 kernel: amdgpu 0000:04:00.0: ring 12(vcn_enc0) uses VM inv eng 6 on hub 1
Sep 03 17:21:39 HP255G7 kernel: amdgpu 0000:04:00.0: ring 13(vcn_enc1) uses VM inv eng 7 on hub 1
Sep 03 17:21:39 HP255G7 kernel: amdgpu 0000:04:00.0: ring 14(vcn_jpeg) uses VM inv eng 8 on hub 1
Sep 03 17:21:39 HP255G7 kernel: [drm] Initialized amdgpu 3.27.0 20150101 for 0000:04:00.0 on minor 0
Sep 03 17:21:40 HP255G7 systemd[1]: Starting Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0...
Sep 03 17:21:40 HP255G7 systemd[1]: Started Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0.
Sep 03 17:22:31 HP255G7 org_kde_powerdevil[1557]: powerdevil: Udev device changed "/sys/devices/pci0000:00/0000:00:08.1/0000:04:00.0/backlight/amdgpu_bl0" "/sys/devices/pci0000:00/0000:00:08.1/0000:04:00.0/backlight/amdgpu_bl0"


Regards, Paul.

Comment 26 Martin Peres 2019-11-19 08:27:16 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/271.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.