On Tue, Feb 28, 2017 at 03:34:53PM +0100, Pavel Machek wrote: > Hi! > > mplayer stopped working after a while. Dmesg says: > > [ 3000.266533] cdc_ether 2-1.2:1.0 usb0: register 'cdc_ether' at > usb-0000:00:1d.0-1.2, CDC Ethernet Device, 22:1b:e4:4e:56:f5 > [ 3190.767227] [drm] GPU HANG: ecode 6:0:0xbb409fff, in chromium > [4597], reason: Hang on render ring, action: reset > [ 3190.767311] [drm] GPU hangs can indicate a bug anywhere in the > entire gfx stack, including userspace. > [ 3190.767313] [drm] Please file a _new_ bug report on > bugs.freedesktop.org against DRI -> DRM/Intel > [ 3190.767315] [drm] drm/i915 developers can then reassign to the > right component if it's not a kernel issue. > [ 3190.767317] [drm] The gpu crash dump is required to analyze gpu > hangs, so please always attach it. > [ 3190.767320] [drm] GPU crash dump saved to > /sys/class/drm/card0/error > [ 3190.767427] drm/i915: Resetting chip after gpu hang > [ 3228.329384] cdc_ether 2-1.2:1.0 usb0: kevent 12 may have been > dropped > [ 3228.329604] cdc_ether 2-1.2:1.0 usb0: kevent 12 may have been > dropped > [ 3877.246261] perf: interrupt took too long (3142 > 3133), lowering > kernel.perf_event_max_sample_rate to 63500 > [ 4802.784478] drm/i915: Resetting chip after gpu hang > [ 4810.784851] drm/i915: Resetting chip after gpu hang > [ 4829.829795] drm/i915: Resetting chip after gpu hang > [ 4837.826154] drm/i915: Resetting chip after gpu hang > [ 5125.026814] [drm:intel_pipe_update_end] *ERROR* Atomic update > failure on pipe A (start=308257 end=308258) time 203 us, min 763, max > 767, scanline start 761, end 771 > [ 5125.192602] [drm:intel_pipe_update_end] *ERROR* Atomic update > failure on pipe B (start=307385 end=307386) time 204 us, min 1073, max > 1079, scanline start 1071, end 1086 > [ 5125.309992] [drm:intel_pipe_update_end] *ERROR* Atomic update > failure on pipe A (start=308274 end=308275) time 203 us, min 763, max > 767, scanline start 758, end 768 > [ 5125.460013] [drm:intel_pipe_update_end] *ERROR* Atomic update > failure on pipe A (start=308283 end=308284) time 204 us, min 763, max > 767, scanline start 761, end 771 > [ 5125.493340] [drm:intel_pipe_update_end] *ERROR* Atomic update > failure on pipe A (start=308285 end=308286) time 202 us, min 763, max > 767, scanline start 761, end 771 > [ 5125.526684] [drm:intel_pipe_update_end] *ERROR* Atomic update > failure on pipe A (start=308287 end=308288) time 204 us, min 763, max > 767, scanline start 762, end 772 > [ 5125.593245] [drm:intel_pipe_update_end] *ERROR* Atomic update > failure on pipe A (start=308291 end=308292) time 203 us, min 763, max > 767, scanline start 758, end 768 > [ 5125.676636] [drm:intel_pipe_update_end] *ERROR* Atomic update > failure on pipe A (start=308296 end=308297) time 202 us, min 763, max > 767, scanline start 762, end 772 > [ 5125.709960] [drm:intel_pipe_update_end] *ERROR* Atomic update > failure on pipe A (start=308298 end=308299) time 203 us, min 763, max > 767, scanline start 762, end 772 > [ 5126.093109] [drm:intel_pipe_update_end] *ERROR* Atomic update > failure on pipe A (start=308321 end=308322) time 204 us, min 763, max > 767, scanline start 759, end 770 > [ 5647.879171] drm/i915: Resetting chip after gpu hang > [ 5655.879507] drm/i915: Resetting chip after gpu hang > [ 5850.864464] drm/i915: Resetting chip after gpu hang > [ 5858.864853] drm/i915: Resetting chip after gpu hang > [ 5904.850879] drm/i915: Resetting chip after gpu hang > [ 5912.851252] drm/i915: Resetting chip after gpu hang > [ 5949.876973] drm/i915: Resetting chip after gpu hang > [ 5957.877460] drm/i915: Resetting chip after gpu hang > [ 6018.872153] drm/i915: Resetting chip after gpu hang > [ 6030.872646] drm/i915: Resetting chip after gpu hang > [ 7108.362610] perf: interrupt took too long (3935 > 3927), lowering > kernel.perf_event_max_sample_rate to 50750 > [ 9670.047072] drm/i915: Resetting chip after gpu hang > [ 9678.047415] drm/i915: Resetting chip after gpu hang > [10408.064806] drm/i915: Resetting chip after gpu hang > [10416.097168] drm/i915: Resetting chip after gpu hang > [10416.097181] [drm:i915_reset] *ERROR* GPU recovery failed > pavel@duo:/data/film$ > > Umm. Dmesg wants me to attach card0/error, but it looks like it > contains quite a lot of data. If it contains actual framebuffer > content, it may not be wise to post to mailing list.... It contains command and register states. No pixel data unless userspace got particularly creative with its memory corruption. -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
