Bug 106285 - Multiple Xorg restarts leads to `Surface: can not attach plane_state` (raven ridge)
Summary: Multiple Xorg restarts leads to `Surface: can not attach plane_state` (raven ...
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/AMDgpu (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-27 17:36 UTC by ojab
Modified: 2019-11-19 08:36 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description ojab 2018-04-27 17:36:26 UTC
Raven ridge APU (2400g), no external GPU, linux-4.17-rc2, libdrm-2.4.91, mesa-18.1.0-rc1, xorg-server-1.19.6, xf86-video-amdgpu-18.0.1.

So I've tried to reproduce https://bugs.freedesktop.org/show_bug.cgi?id=106276 using simple script:
```
#!/bin/sh
set -ex
while true; do
    set -x
    X&
    XPID=$!
    sleep 1
    kill ${XPID}
    sleep 1
done
```

and ended up with screen showing nothing (i. e. backlight enabled, but all image is black) in both console & X. dmesg is full of
[Fri Apr 27 16:17:33 2018] [drm:dc_add_plane_to_context [amdgpu]] *ERROR* Surface: can not attach plane_state 00000000a97ad24a! Maximum is: 4
[Fri Apr 27 16:17:33 2018] [drm:dc_add_plane_to_context [amdgpu]] *ERROR* Surface: can not attach plane_state 00000000d38d9362! Maximum is: 4
[Fri Apr 27 16:17:33 2018] [drm:dc_add_plane_to_context [amdgpu]] *ERROR* Surface: can not attach plane_state 00000000d38d9362! Maximum is: 4
[Fri Apr 27 16:17:33 2018] [drm:dc_add_plane_to_context [amdgpu]] *ERROR* Surface: can not attach plane_state 00000000d38d9362! Maximum is: 4
[Fri Apr 27 16:18:01 2018] [drm:dc_add_plane_to_context [amdgpu]] *ERROR* Surface: can not attach plane_state 00000000b7ff318d! Maximum is: 4
[Fri Apr 27 16:18:04 2018] [drm:dc_add_plane_to_context [amdgpu]] *ERROR* Surface: can not attach plane_state 00000000b7ff318d! Maximum is: 4
Comment 1 ojab 2018-04-30 14:34:23 UTC
```
#!/bin/sh
set -ex
while true; do
    set -x
    X&
    sleep 1
    XPID=$!
    kill -9 ${XPID}
    sleep 0.1
done
```
reliably triggers this error in a minute or so.
Comment 2 Martin Peres 2019-11-19 08:36:24 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/357.


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.