<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [NVA5] Corruption in Plasma 5 on resume after changing screen configuration"
href="https://bugs.freedesktop.org/show_bug.cgi?id=92504#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [NVA5] Corruption in Plasma 5 on resume after changing screen configuration"
href="https://bugs.freedesktop.org/show_bug.cgi?id=92504">bug 92504</a>
from <span class="vcard"><a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> <span class="fn">Ilia Mirkin</span></a>
</span></b>
<pre>Actually the issue is most likely due to
[20351.450000] nouveau E[plasmashell[13570]] fail set_domain
[20351.450006] nouveau E[plasmashell[13570]] validating bo list
[20351.450015] nouveau E[plasmashell[13570]] validate: -22
Which is... odd. This happens when
uint32_t domains = valid_domains & nvbo->valid_domains &
(write_domains ? write_domains : read_domains);
if (!domains)
return -EINVAL;
Which means that unless nvbo->valid_domains had something funny in it, this is
all good. Hmmm....
nvbo->valid_domains = NOUVEAU_GEM_DOMAIN_VRAM |
NOUVEAU_GEM_DOMAIN_GART;
if (drm->device.info.family >= NV_DEVICE_INFO_V0_TESLA)
nvbo->valid_domains &= domain;
So if we ever supply a valid/read/write domains that's not the same as the
domain we created the bo with, then this will fail. However after some scouring
of the code, I don't where we'd be messing this up. And unfortunately nothing
that libdrm prints will help this. I'm also unsure of
If you can, could you patch
drivers/gpu/drm/nouveau/nouveau_gem.c:nouveau_gem_set_domain to have a print of
all 4 inputs to domains to see why it's coming out as 0?</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 the assignee for the bug.</li>
</ul>
</body>
</html>