Summary: | [BSW]Ogles1conform sporadically causes system hang and *ERROR* Timed out: waiting for media to ack | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | lu hua <huax.lu> | ||||||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||
Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||
Severity: | critical | ||||||||||
Priority: | high | CC: | intel-gfx-bugs | ||||||||
Version: | unspecified | ||||||||||
Hardware: | All | ||||||||||
OS: | Linux (All) | ||||||||||
Whiteboard: | |||||||||||
i915 platform: | i915 features: | ||||||||||
Attachments: |
|
Description
lu hua
2014-12-17 06:49:27 UTC
This much more likely a kernel bug. Assigning back to INTEL GFX. This test wouldn't be using media, and the dmesg shows nothing to indicate mesa is at fault. by the log it seems it was from times where chv were reusing vlv reg force wake range. It change a lot lately. Please retry with latest nightly. I believe it is fixed already. It's sporadically issue. I will double check it. So update will be late. Created attachment 112826 [details]
dmesg
Test on the latest -nightly kernel and Mesa.
It still causes system hang. But I am not meet the error. Attached the demsg.
Is there any i915_error_state after hang? Could you please increase buf_log_len or paste a cleaner log? Created attachment 112867 [details] full dmesg (In reply to Rodrigo Vivi from comment #5) > Is there any i915_error_state after hang? > The system hang fast, I can't catch i915_error_state. If you have any suggestion, it's welcome. > Could you please increase buf_log_len or paste a cleaner log? Attach the full dmesg. There are no hangs nor timeouts on forcewake acks on the latest dmesg. Please verify that the original issue with media acks is resolved. Test 10 cycles on the latest -nightly kernel. I don't meet the hang ang error. Close it. Verified.Fixed. Closing old verified. |
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.