| Summary: | [hsw/bdw] *ERROR* Timed out waiting for forcewake old ack to clear. | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Chris Wilson <chris> |
| Component: | DRM/Intel | Assignee: | Ben Widawsky <ben> |
| Status: | CLOSED WORKSFORME | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: | normal | ||
| Priority: | medium | CC: | ben, huax.lu, przanoni |
| Version: | XOrg git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Chris Wilson
2013-08-26 14:16:26 UTC
(In reply to comment #0) > There is a low probabilty of this timeout ocurring, especially noticeable if > polling the rings for GPU busyness. So essentially it's broken, only pampered over by us not using forcewake too often? Do consistency checks of the forcewake register turn up anything? Iirc I've heard some noise that this register sometimes drops writes or wreaks other havoc ... Is this something we can try to reproduce with an IGT test? "drm/i915: use the correct force_wake function at the PC8 code" solves the bug I could reproduce. The way to reproduce it was through our sysfs i915_forcewake_user file, so this is probably not the bug Chris was mentioning... Chris, close? If you want to file a HSD... :-p Do we see the problem for extraordinarily high values of FORCEWAKE_ACK_TIMEOUT_MS? *** Bug 72773 has been marked as a duplicate of this bug. *** Chris, do we see this with extremely high FORCEWAKE_ACK_TIMEOUT_MS too? Just tried to reproduce this on crw without much luck. I might try again on the original hsw that showed the issue later on. I vote let's close it for now, and you can reopen when you see it? Jani, would you be able to come up with a list of potential commits? Crap, modified wrong bug. Sorry. Chris does this still occur? With the fixes from Mika, it appears to be gone on GEN8 at least. No, I can no longer easily trigger this. |
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.