Error* Cannot Create /sys/kernel/debug/dri
message: [Intel-gfx] kms_panel_fitting Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] 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 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 Reviewed-by: Daniel Vetter Signed-off-by: Dave Airlie Regards, Gabriel Previous message: [Intel-gfx] [PATCH v2] x86: Silence 32bit compiler warning in intel_graphics_stolen() Next message: [Intel-gfx] kms_panel_fitting Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the Intel-gfx mailing list
Thu, 5 May 2016 20:10:53 +0300 Cc: "intel-gfx@xxxxxxxxxxxxxxxxxxxxx" , dri-devel@xxxxxxxxxxxxxxxxxxxxx User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 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 Date: Wed https://lists.freedesktop.org/archives/intel-gfx/2016-May/095093.html 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 http://www.spinics.net/lists/dri-devel/msg106692.html 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 Reviewed-by: Daniel Vetter Signed-off-by: Dave Airlie Regards, Gabriel _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel Prev by Date: Re: Regression of v4.6-rc vs. v4.5 bisected: a98ee79317b4 "drm/i915/fbc: enable FBC by default on HSW and BDW" Next by Date: Re: Regression of v4.6-rc vs. v4.5 bisected: a98ee79317b4 "drm/i915/fbc: enable FBC by default on HSW and BDW" Previous by thread: [PATCH] drm: sun4i: fix probe error handling Next by thread: [PATCH] drm/hisilicon: Use drm_connector_register_all Index(es): Date Thread [IndexofArchives] [LinuxDRIUsers] [LinuxIntelGraphics] [LinuxUSBDevel] [VideoforLinux] [LinuxAudioUsers] [YosemiteNews] [LinuxKernel] [LinuxSCSI] [XFree86] [Linu
Documentation EPEL Infrastructure Internationalization Localization Marketing Magazine Package Maintainers Quality Assurance Websites All projects Search Tools What links here Related changes Special https://fedoraproject.org/wiki/How_to_debug_Xorg_problems pages Printable version Permanent link How to debug Xorg problems From FedoraProject Jump to: navigation, search Foreword If you are experiencing a problem with Xorg, please see the common bugs document before filing a bug. Some easy configuration tweaks that fix a wide range of issues are listed there. If the problem you are seeing is error* cannot not listed there or none of the workarounds seem to help, please consider filing a bug to help us make Fedora run better on your hardware. Be prepared to include some information (logs) about your system as well. These should be complete (no snippets please), not in an archive, uncompressed, with MIME type set as text/plain. error* cannot create Contents 1 Identifying your problem area 1.1 What driver am I using? 1.2 What area might the problem be in? 2 Information to include in your report 2.1 All bug reports 2.2 Rendering problems (unreadable text, corrupted display...) 2.2.1 Intel-specific 2.3 3D acceleration issues 3 Creating a xorg.conf 4 Input devices 5 Stack traces Identifying your problem area What driver am I using? If you do not know already, try to find out what video driver you are using. Examine the output of journalctl -e _COMM=gdm-x-session (Fedora 22+), journalctl -e _COMM=Xorg.bin (Fedora 21) or journalctl -e _COMM=Xorg (Fedora 20 and earlier). Quite early on, you will see some lines like this: (II) VESA(0): initializing int10 (II) VESA(0): Bad V_BIOS checksum The word in capital letters after (II) is the name of the driver in use (so, in this case, the word is VESA, indicating the vesa driver is in use). Drivers are packaged with the name xorg-x11-drv-(name), so the vesa driver is in the package