Summary: | [KBL][drm:fw_domains_get [i915]] *ERROR* blitter: timed out waiting for forcewake ack request. | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Matwey V. Kornilov <matwey.kornilov> | ||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Status: | CLOSED WORKSFORME | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Severity: | normal | ||||||
Priority: | medium | CC: | intel-gfx-bugs | ||||
Version: | DRI git | ||||||
Hardware: | x86-64 (AMD64) | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | KBL | i915 features: | GPU hang | ||||
Attachments: |
|
Description
Matwey V. Kornilov
2017-08-05 16:23:13 UTC
Created attachment 133258 [details]
Full log
After half an our the rest of messages appears.
This scenario reproduces every time. Hello Matwey, Could you please attach error state from hang, also could you replicate with drm.debug=0x1e log_bug_len=2M on grub and attach log. After it goes blank is there any way to recovery besides power off? (In reply to Elizabeth from comment #3) > Hello Matwey, > Could you please attach error state from hang, also could you replicate with > drm.debug=0x1e log_bug_len=2M on grub and attach log. After it goes blank is > there any way to recovery besides power off? Hello Matwey, any look reproducing with debug info? Thank you. Mika suspected that commit 7130630323c562597191653560963e61c5bd0f57 Author: Mika Kuoppala <mika.kuoppala@linux.intel.com> Date: Thu Nov 2 11:48:36 2017 +0200 drm/i915: Use fallback forcewake if primary ack missing There is a possibility on gen9 hardware to miss the forcewake ack message. The recommended workaround is to use another free bit and toggle it until original bit is successfully acknowledged. Some future gen9 revs might or might not fix the underlying issue but using fallback forcewake bit dance can be considered as harmless: without the ack timeout we never reach the fallback bit forcewake. Thus as of now we adopt a blanket approach for all gen9 and leave the bypassing the fallback bit approach for future patches if corresponding hw revisions do appear. Commit 83e3337204b2 ("drm/i915: Increase maximum polling time to 50ms for forcewake request/clear ack") did increase the forcewake timeout. If the issue was a delayed ack, future work could include finding a suitable timeout value both for primary ack and reserve toggle to reduce the worst case latency. v2: use bit 15, naming, comment (Chris), only wait fallback ack v3: fix return on fallback, backoff after fallback write (Chris) v4: udelay on first pass, grammar (Chris) v4: s/reserve/fallback References: HSDES #1604254524 References: https://bugs.freedesktop.org/show_bug.cgi?id=102051 Cc: Chris Wilson <chris@chris-wilson.co.uk> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Cc: Sagar Arun Kamble <sagar.a.kamble@intel.com> Signed-off-by: Mika Kuoppala <mika.kuoppala@linux.intel.com> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> Link: https://patchwork.freedesktop.org/patch/msgid/20171102094836.2506-1-mika.kuoppala@linux.intel.com may help, but live_uncore is deliberately unfriendly to the hw... Test is now disabled by default; and perchance the w/a was relevant. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.