Date: Tue, 11 Apr 2017 07:33:33 +0200 From: Andre Albsmeier <mail@fbsd.e4m.org> To: freebsd-x11@freebsd.org Cc: mail@fbsd.e4m.org Subject: Re: drm:pid959:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake to ack request Message-ID: <20170411053333.GA63970@gate>
next in thread | raw e-mail | index | archive | help
Commenting my own message in case anyone is interested: "Fixed" it here by changing FORCEWAKE_ACK_TIMEOUT_MS from 2 to 10 in sys/dev/drm2/i915/intel_pm.c. 5 improved things (messages appeared more infrequently) but with 10 they are gone entirely. -Andre ----- Forwarded message from Andre Albsmeier ----- From: Andre Albsmeier <mail@fbsd.e4m.org> Date: Wed, 5 Apr 2017 19:32:46 +0200 Subject: [drm:pid959:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake to ack request I am seeing error: [drm:pid959:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake to ack request. on several boxes with i7-3770K and i5-4590 cpus. This is with the latest drm, mesa, xorg, driver ... ports but happened also with all versions since January (didn't try earlier stuff). Sometimes there are 1-2 minutes between these messages and sometimes it takes up to 1 hour. It almost never happens under normal desktop work (fvwm2 with a lot of xterms) but as soon as xlockmore with its GL stuff kicks in the messages appear. I didn't find a lot about it on the web -- just some linux posts where the problem appears to be fixed. Anyone else seeing this? -Andre
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170411053333.GA63970>