From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 105880] [dc][kabini] Cannot find any crtc or sizes Date: Thu, 12 Apr 2018 01:19:32 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1074954719==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 9BD896E3C7 for ; Thu, 12 Apr 2018 01:19:32 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1074954719== Content-Type: multipart/alternative; boundary="15234959720.bDD78.24167" Content-Transfer-Encoding: 7bit --15234959720.bDD78.24167 Date: Thu, 12 Apr 2018 01:19:32 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D105880 David Henningsson changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |diwic@ubuntu.com --- Comment #8 from David Henningsson --- Hi, I'm getting the same or similar error: * Black screen, no plymouth * "Cannot find any crtc or sizes" error in dmesg * amdgpu.dc=3D0 works around the issue ...and I might have a lead on it. The regression is between 4.15rc2 and 4.1= 5rc3 (found by downloading kernels from http://kernel.ubuntu.com/~kernel-ppa/mainline/).=20 The only one commit I could see being relevant between 4.15rc2 and 4.15rc3 = is this one: commit a703c55004e1c5076d57e43771b3e11117796ea0 Author: Daniel Vetter Date: Mon Dec 4 21:48:18 2017 +0100 drm: safely free connectors from connector_iter ...it seems relevant because the error I get is "Cannot find any crtc or sizes", and the code emitting this error message (in drivers/gpu/drm/drm_fb_helper.c) deals with connectors. So could this commit cause connectors to be freed where the previous code d= id not? It seems like this could be the case, but only if (obj->free_cb =3D=3D= NULL) - drm_connector_put checks for a obj->free_cb being null whereas drm_connector_put_safe decrements a refcount regardless of whether a free_c= b is present or not. Does all this make sense, or am I out on deep water here? --=20 You are receiving this mail because: You are the assignee for the bug.= --15234959720.bDD78.24167 Date: Thu, 12 Apr 2018 01:19:32 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated David Henningsson changed bug 10588= 0
What Removed Added
CC   diwic@ubuntu.com

Commen= t # 8 on bug 10588= 0 from David Henningsson
Hi,

I'm getting the same or similar error:
 * Black screen, no plymouth
 * "Cannot find any crtc or sizes" error in dmesg
 * amdgpu.dc=3D0 works around the issue

...and I might have a lead on it. The regression is between 4.15rc2 and 4.1=
5rc3
(found by downloading kernels from
http://kernel.ub=
untu.com/~kernel-ppa/mainline/).=20

The only one commit I could see being relevant between 4.15rc2 and 4.15rc3 =
is
this one:

commit a703c55004e1c5076d57e43771b3e11117796ea0
Author: Daniel Vetter <dan=
iel.vetter@ffwll.ch>
Date: Mon Dec 4 21:48:18 2017 +0100

    drm: safely free connectors from connector_iter

...it seems relevant because the error I get is "Cannot find any crtc =
or
sizes", and the code emitting this error message (in
drivers/gpu/drm/drm_fb_helper.c) deals with connectors.

So could this commit cause connectors to be freed where the previous code d=
id
not? It seems like this could be the case, but only if (obj->free_cb =3D=
=3D NULL) -
drm_connector_put checks for a obj->free_cb being null whereas
drm_connector_put_safe decrements a refcount regardless of whether a free_c=
b is
present or not.

Does all this make sense, or am I out on deep water here?


You are receiving this mail because:
  • You are the assignee for the bug.
= --15234959720.bDD78.24167-- --===============1074954719== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1074954719==--