dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gabriel Feceoru <gabriel.feceoru@intel.com>
To: airlied@redhat.com, daniel.vetter@ffwll.ch
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	dri-devel@lists.freedesktop.org
Subject: [REGRESSION] *ERROR* Cannot create /sys/kernel/debug/dri/0
Date: Thu, 5 May 2016 20:10:53 +0300	[thread overview]
Message-ID: <572B7E9D.5060105@intel.com> (raw)

Hi Dave, Daniel,


This is a regression causing many failures in intel-gfx CI.


[  295.164523] [drm:drm_debugfs_init] *ERROR* Cannot create 
/sys/kernel/debug/dri/0
[  295.164531] [drm:drm_minor_register] *ERROR* DRM: Failed to 
initialize /sys/kernel/debug/dri.
[  295.167544] i915: probe of 0000:00:02.0 failed with error -1


After bisect:

commit d2307dea14a4f14a4b5db01b6d40a30fa6117e6c
Author: Dave Airlie <airlied@redhat.com>
Date:   Wed Apr 27 11:27:39 2016 +1000

     drm/atomic: use connector references (v3)

     Take a reference when setting a crtc on a connecter,
     also take one when duplicating if a crtc is set,
     and drop one on destroy if a crtc is set.

     v2: take Daniel Stone's advice and simplify the
     ref/unref dances, also take care of NULL as connector
     to state reset.

     v3: remove need for connector NULL check.

     Reviewed-by: Daniel Stone <daniels@collabora.com>
     Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
     Signed-off-by: Dave Airlie <airlied@redhat.com>

Regards,
Gabriel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

                 reply	other threads:[~2016-05-05 17:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=572B7E9D.5060105@intel.com \
    --to=gabriel.feceoru@intel.com \
    --cc=airlied@redhat.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox