Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • mesa mesa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2,870
    • Issues 2,870
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 893
    • Merge requests 893
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Mesa
  • mesamesa
  • Issues
  • #1610

Closed
Open
Created Sep 25, 2019 by Bugzilla Migration User@bugzilla-migration

[SKL]GPU HANG: ecode 9:0:0x8fd87fff, in mpv/vo [2462], reason: Hang on render ring, action: reset

Submitted by Rik

Assigned to Intel 3D Bugs Mailing List

Link to original bug (#101729)

Description

Created attachment 132571 /sys/class/drm/card0/error

Got a new gpu hang on Skylake CPU during mpv playback.

%dmesg [drm] GPU HANG: ecode 9:0:0x8fd87fff, in mpv/vo [2462], reason: Hang on render ring, action: reset [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [drm] Please file a new bug report on bugs.freedesktop.org against DRI -> DRM/Intel [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [drm] GPU crash dump saved to /sys/class/drm/card0/error drm/i915: Resetting chip after gpu hang [drm] RC6 on

System info

System: Kernel: 4.11.9-1-stable x86_64 (64 bit) Desktop: Xfce 4.12.4 Distro: Arch Linux Machine: Device: desktop Mobo: ASRock model: Z170M Extreme4 serial: M80-68001700529 UEFI [Legacy]: American Megatrends v: P7.20 date: 12/13/2016 CPU: Dual core Intel Core i3-6100 (-HT-MCP-) cache: 3072 KB clock speeds: max: 3700 MHz 1: 799 MHz 2: 799 MHz 3: 799 MHz 4: 799 MHz Memory: Used/Total: 1045.4/6978.3MB Array-1 capacity: 64 GB devices: 4 EC: None Device-1: ChannelA-DIMM0 size: No Module Installed type: N/A Device-2: ChannelA-DIMM1 size: 8 GB speed: 2400 MT/s type: DDR4 Device-3: ChannelB-DIMM0 size: No Module Installed type: N/A Device-4: ChannelB-DIMM1 size: No Module Installed type: N/A Graphics: Card: Intel HD Graphics 530 Display Server: X.Org 1.19.3 drivers: intel (unloaded: modesetting) Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 530 (Skylake GT2) version: 4.5 Mesa 17.1.4

%cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-linux-stable root=UUID=4e2f3394-d315-4384-b975-05e33af1ab06 rw intremap=no_x2apic_optout acpi_backlight=none intel_iommu=on i915.enable_gvt=1 quiet loglevel=3 rd.systemd.show_status=false rd.udev.log-priority=3 systemd.log_level=err resume=UUID=25e25554-34e4-4d4a-a7f5-81ef2415db94 printk.time=0 splash

Attachment 132571, "/sys/class/drm/card0/error":
dump-gpu-crash-09072017.bz2

Version: 17.1

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking