From owner-freebsd-ports-bugs@freebsd.org Fri Nov 16 19:21:34 2018 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 63945110295C for ; Fri, 16 Nov 2018 19:21:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C6CAA8C053 for ; Fri, 16 Nov 2018 19:21:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 8A8711102958; Fri, 16 Nov 2018 19:21:33 +0000 (UTC) Delivered-To: ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 687341102957 for ; Fri, 16 Nov 2018 19:21:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C75BC8C04C for ; Fri, 16 Nov 2018 19:21:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 199E4B70A for ; Fri, 16 Nov 2018 19:21:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id wAGJLVko077393 for ; Fri, 16 Nov 2018 19:21:31 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id wAGJLVtd077392 for ports-bugs@FreeBSD.org; Fri, 16 Nov 2018 19:21:31 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 233259] multimedia/libva-intel-driver with HYBRID enabled causes system freezes on Sandy Bridge Date: Fri, 16 Nov 2018 19:21:31 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rkoberman@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: madpilot@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter flagtypes.name Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-Rspamd-Queue-Id: C6CAA8C053 X-Spamd-Result: default: False [-105.92 / 15.00]; FORGED_RECIPIENTS_FORWARDING(0.00)[]; ALLOW_DOMAIN_WHITELIST(-100.00)[freebsd.org]; FORWARDED(0.00)[ports-bugs@mailman.ysv.freebsd.org]; SPF_FAIL_FORWARDING(0.00)[]; TO_DN_NONE(0.00)[]; HAS_XAW(0.00)[]; R_SPF_SOFTFAIL(0.00)[~all]; XAW_SERVICE_ACCT(1.00)[]; RCVD_IN_DNSWL_MED(-0.20)[5.0.0.0.0.5.0.0.0.0.0.0.0.0.0.0.a.6.0.2.4.5.2.2.0.0.9.1.1.0.0.2.list.dnswl.org : 127.0.9.2]; MX_GOOD(-0.01)[cached: mx66.freebsd.org]; NEURAL_HAM_SHORT(-1.00)[-1.000,0]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; IP_SCORE(-3.71)[ip: (-9.87), ipnet: 2001:1900:2254::/48(-4.82), asn: 10310(-3.76), country: US(-0.10)]; ASN(0.00)[asn:10310, ipnet:2001:1900:2254::/48, country:US]; FORGED_RECIPIENTS(0.00)[ports-bugs@FreeBSD.org,freebsd-ports-bugs@freebsd.org]; TO_DOM_EQ_FROM_DOM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; FROM_NO_DN(0.00)[]; RCVD_COUNT_SEVEN(0.00)[7] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Nov 2018 19:21:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D233259 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@FreeBSD.org Reporter: rkoberman@gmail.com Flags: maintainer-feedback?(madpilot@FreeBSD.org) Assignee: madpilot@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 driv= er 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=3D226495. = 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 analy= ze 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 analy= ze 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 analy= ze 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 --=20 You are receiving this mail because: You are the assignee for the bug.=