[Nouveau] [Bug 92504] [NVA5] Corruption in Plasma 5 on resume after changing screen configuration

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=92504

--- Comment #11 from Ilia Mirkin <imirkin at alum.mit.edu> ---
(In reply to Alexander Schlarb from comment #9)
> I now have also noted that the first "fail set_domain" messages already
> appear during the first suspend (including the plasmashell nouveau dump and
> even some of the corruption). How could I have not noticed this? :-/
> 
> Anyway, here we go:
> 
> I patched Linux 4.3.0-rc5-next-20151016+ (cd685d8558) with these lines:
> 
>     diff --git a/drivers/gpu/drm/nouveau/nouveau_gem.c
> b/drivers/gpu/drm/nouveau/nouveau_gem.c
>     index 2c99815..caff0e0 100644
>     --- a/drivers/gpu/drm/nouveau/nouveau_gem.c
>     +++ b/drivers/gpu/drm/nouveau/nouveau_gem.c
>     @@ -291,7 +291,10 @@ nouveau_gem_set_domain(struct drm_gem_object *gem,
> uint32_t read_domains,
>             uint32_t domains = valid_domains & nvbo->valid_domains &
>                     (write_domains ? write_domains : read_domains);
>             uint32_t pref_flags = 0, valid_flags = 0;
>     -
>     +       printk("nouveau_gem_set_domain - drm_gem_object: 0x%08p\n", gem);
>     +       printk("nouveau_gem_set_domain - read_domains:   0x%08x\n",
> read_domains);
>     +       printk("nouveau_gem_set_domain - write_domains:  0x%08x\n",
> write_domains);                                                             
> 
>     +       printk("nouveau_gem_set_domain - valid_domains:  0x%08x\n",
> valid_domains);                                                             
> 
>             if (!domains)                                                   
> 
>                     return -EINVAL;

I should have been more explicit. You need to move that into if (!domains), and
also print nvbo->valid_domains. So e.g.

if (!domains) {
  printk("bo valid domains: %x\n", nvbo->valid_domains);
  printk("valid domains: %x\n", valid_domains);
  printk("read domains: %x\n", read_domains);
  printk("write domains: %x\n", write_domains);
  return -EINVAL;
}

This should provide with the relevant info for the failing gem object.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20151017/15e6b256/attachment.html>