[Bug 233259] multimedia/libva-intel-driver with HYBRID enabled causes system freezes on Sandy Bridge

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233259

            Bug ID: 233259
           Summary: multimedia/libva-intel-driver with HYBRID enabled
                    causes system freezes on Sandy Bridge
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: madpilot at FreeBSD.org
          Reporter: rkoberman at gmail.com
             Flags: maintainer-feedback?(madpilot at FreeBSD.org)
          Assignee: madpilot at FreeBSD.org

With the default configuration of multimedia/libva-intel-driver, the HYBRID
option is enabled. On my amd64 Sandy Bridge system this results in periodic
system deadlocks. These were on the order of daily events from the time I
installed the hybrid driver. None had occurred prior to the the hybrid driver
was added and non has occurred since I disabled this option.

I might also mention that I was seeing something similar about 8 months ago and
reported it in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226495. It
disappeared after updates to mesa and moving to drm-stable-kmod.

Here are the event logs of the events of 9-Nov, 10-Nov, and 11-Nov.:
Nov  9 13:09:11 rogue kernel: [drm:fw_domain_wait_ack] render: timed out
waiting for forcewake ack request.
Nov  9 13:09:11 rogue kernel: [drm:__gen6_gt_wait_for_thread_c0] GT thread
status wait timed out
Nov  9 13:09:13 rogue kernel: [drm:fw_domain_wait_ack] render: timed out
waiting for forcewake ack request.
Nov  9 13:09:13 rogue kernel: [drm:__gen6_gt_wait_for_thread_c0] GT thread
status wait timed out
Nov  9 13:09:15 rogue kernel: [drm:fw_domain_wait_ack] render: timed out
waiting for forcewake ack request.
Nov  9 13:09:15 rogue kernel: [drm:__gen6_gt_wait_for_thread_c0] GT thread
status wait timed out
Nov  9 13:09:18 rogue kernel: [drm:fw_domain_wait_ack] render: timed out
waiting for forcewake ack request.
Nov  9 13:09:18 rogue kernel: [drm:__gen6_gt_wait_for_thread_c0] GT thread
status wait timed out
Nov  9 13:09:18 rogue kernel: [drm:fw_domain_wait_ack] render: timed out
waiting for forcewake ack request.
Nov  9 13:09:18 rogue kernel: [drm:__gen6_gt_wait_for_thread_c0] GT thread
status wait timed out
Nov  9 13:09:18 rogue kernel: [drm] GPU HANG: ecode 6:0:0x00000000, in Xorg
[1454], reason: Hang on render ring, action: reset
Nov  9 13:09:18 rogue kernel: [drm] GPU hangs can indicate a bug anywhere in
the entire gfx stack, including userspace.
Nov  9 13:09:18 rogue kernel: [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
Nov  9 13:09:18 rogue kernel: [drm] drm/i915 developers can then reassign to
the right component if it's not a kernel issue.
Nov  9 13:09:18 rogue kernel: [drm] The gpu crash dump is required to analyze
gpu hangs, so please always attach it.
Nov  9 13:09:18 rogue kernel: [drm] GPU crash dump saved to
/sys/class/drm/card0/error
Nov  9 13:09:18 rogue kernel: [drm:fw_domain_wait_ack] render: timed out
waiting for forcewake ack request.
Nov  9 13:09:18 rogue kernel: [drm:__gen6_gt_wait_for_thread_c0] GT thread
status wait timed out
Nov  9 13:09:18 rogue kernel: drm/i915: Resetting chip after gpu hang
Nov  9 13:09:18 rogue kernel: [drm:fw_domain_wait_ack] render: timed out
waiting for forcewake ack request.
Nov  9 13:09:18 rogue kernel: [drm:__gen6_gt_wait_for_thread_c0] GT thread
status wait timed out


Nov 10 13:25:57 rogue kernel: [drm:fw_domain_wait_ack] render: timed out
waiting for forcewake ack request.
Nov 10 13:25:57 rogue kernel: [drm:__gen6_gt_wait_for_thread_c0] GT thread
status wait timed out
Nov 10 13:25:57 rogue kernel: [drm:fw_domain_wait_ack] render: timed out
waiting for forcewake ack request.
Nov 10 13:25:57 rogue kernel: [drm:__gen6_gt_wait_for_thread_c0] GT thread
status wait timed out
Nov 10 13:26:00 rogue kernel: [drm:fw_domain_wait_ack] render: timed out
waiting for forcewake ack request.
Nov 10 13:26:00 rogue kernel: [drm:__gen6_gt_wait_for_thread_c0] GT thread
status wait timed out
Nov 10 13:26:02 rogue kernel: [drm:fw_domain_wait_ack] render: timed out
waiting for forcewake ack request.
Nov 10 13:26:02 rogue kernel: [drm:__gen6_gt_wait_for_thread_c0] GT thread
status wait timed out
Nov 10 13:26:02 rogue kernel: [drm:fw_domain_wait_ack] render: timed out
waiting for forcewake ack request.
Nov 10 13:26:02 rogue kernel: [drm:__gen6_gt_wait_for_thread_c0] GT thread
status wait timed out
Nov 10 13:26:02 rogue kernel: [drm:fw_domain_wait_ack] render: timed out
waiting for forcewake ack request.
Nov 10 13:26:02 rogue kernel: [drm:__gen6_gt_wait_for_thread_c0] GT thread
status wait timed out
Nov 10 13:26:02 rogue kernel: [drm] GPU HANG: ecode 6:0:0x00000000, in Xorg
[1419], reason: Hang on render ring, action: reset
Nov 10 13:26:02 rogue kernel: [drm] GPU hangs can indicate a bug anywhere in
the entire gfx stack, including userspace.
Nov 10 13:26:02 rogue kernel: [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
Nov 10 13:26:02 rogue kernel: [drm] drm/i915 developers can then reassign to
the right component if it's not a kernel issue.
Nov 10 13:26:02 rogue kernel: [drm] The gpu crash dump is required to analyze
gpu hangs, so please always attach it.
Nov 10 13:26:02 rogue kernel: [drm] GPU crash dump saved to
/sys/class/drm/card0/error
Nov 10 13:26:02 rogue kernel: [drm:fw_domain_wait_ack] render: timed out
waiting for forcewake ack request.
Nov 10 13:26:02 rogue kernel: [drm:__gen6_gt_wait_for_thread_c0] GT thread
status wait timed out
Nov 10 13:26:02 rogue kernel: drm/i915: Resetting chip after gpu hang
Nov 10 13:26:02 rogue kernel: [drm:fw_domain_wait_ack] render: timed out
waiting for forcewake ack request.
Nov 10 13:26:02 rogue kernel: [drm:__gen6_gt_wait_for_thread_c0] GT thread
status wait timed out


Nov 11 22:46:21 rogue kernel: [drm] GPU HANG: ecode 6:0:0xf4e9fffe, in Xorg
[1355], reason: Hang on blitter ring, action: reset
Nov 11 22:46:21 rogue kernel: [drm] GPU hangs can indicate a bug anywhere in
the entire gfx stack, including userspace.
Nov 11 22:46:21 rogue kernel: [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
Nov 11 22:46:21 rogue kernel: [drm] drm/i915 developers can then reassign to
the right component if it's not a kernel issue.
Nov 11 22:46:21 rogue kernel: [drm] The gpu crash dump is required to analyze
gpu hangs, so please always attach it.
Nov 11 22:46:21 rogue kernel: [drm] GPU crash dump saved to
/sys/class/drm/card0/error
Nov 11 22:46:21 rogue kernel: drm/i915: Resetting chip after gpu hang

-- 
You are receiving this mail because:
You are the assignee for the bug.