<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [CI][DRMTIP] igt@kms_atomic_transition@plane-all-modeset-transition* - fail - Last errno: 28, No space left on device"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109225#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [CI][DRMTIP] igt@kms_atomic_transition@plane-all-modeset-transition* - fail - Last errno: 28, No space left on device"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109225">bug 109225</a>
from <span class="vcard"><a class="email" href="mailto:stanislav.lisovskiy@intel.com" title="Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>"> <span class="fn">Stanislav Lisovskiy</span></a>
</span></b>
<pre>The actual reason for the "No space left on device" issue is in the IGT itself.
I've noticed there are "EDID invalid" messaged in attached dmesg, always when
issue happens:
915 0000:00:02.0: DP-2: EDID is invalid:
<4>[ 46.742040] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
<4>[ 46.742041] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
<4>[ 46.742043] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
<4>[ 46.742044] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
<4>[ 46.742045] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
<4>[ 46.742046] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
<4>[ 46.742047] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
<4>[ 46.742049] [00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
<7>[ 46.742399] [drm:drm_helper_probe_single_connector_modes]
[CONNECTOR:107:DP-2] probed modes :
<7>[ 46.742403] [drm:drm_mode_debug_printmodeline] Modeline 165:"1024x768" 60
65000 1024 1048 1184 1344 768 771 777 806 0x40 0xa
This causes drm to fallback to fixed mode 1024x768, is it could not read
displat EDID(see intel_dp.c and drm_edid.c). This resolution is lower than
typical resolution used in the test case. Then there is a problem that
run_transition_test case doesn't clean up plane size property which it sets,
during the test run. In next test case we create a framebuffer which is of size
of current output mode->hdisplay, mode->vdisplay. Usually it is of same size,
however due to this EDID it happens to be smaller(1024x768) which causes that
everytime proper cleanup wasn't done after previous run_transition_test call,
we are then attempting to set plane size bigger than the framebuffer size,
which causes -ENOSPC to be returned from drm_atomic_plane_check.
To fix that we need to cleanup all the plane properties associated to this
output before we proceed with the next test case, otherwise IGT seems to commit
those in the first commit when we associate output with pipe. I've simulated
this by either making drm intentionally return wrong EDID, so that fixed mode
is used or by simply decreasing mode->hdisplay/vdisplay second time the
function is called => this always results in ENOSPC. Simple cure is just add
igt_plane_set_size in the cleanup, so that plane size is reduced to 0 or
disabled.
So this issue is actually an IGT issue. Another problem is "Invalid EDID" being
read from display, however drm seems to act here as expected.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>