Bug 110734 - [drm:hsw_enable_pc8 [i915]] *ERROR* Switching to FCLK failed
Summary: [drm:hsw_enable_pc8 [i915]] *ERROR* Switching to FCLK failed
Status: RESOLVED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: Triaged
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-23 03:09 UTC by zhang rui
Modified: 2019-07-02 06:41 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
sleepgraph output with the error (526.67 KB, text/html)
2019-05-23 03:10 UTC, zhang rui 		no flags Details
[PATCH] drm/i915: Increase HSW/BDW FCLK<->LCPLL switch timeout (1.92 KB, patch)
2019-05-23 14:07 UTC, Ville Syrjala 		no flags Details | Splinter Review
View All

Description zhang rui 2019-05-23 03:09:26 UTC 
[drm:hsw_enable_pc8 [i915]] *ERROR* Switching to FCLK failed

this error message is shown during suspend on a Lenovo broadwell laptop.

and it appears 416 times out of 2000 s2idle cycles. s2mem is broken on this laptop.
Comment 1 zhang rui 2019-05-23 03:10:12 UTC 
Created attachment 144327 [details]
sleepgraph output with the error
Comment 2 Ville Syrjala 2019-05-23 14:07:10 UTC 
Created attachment 144331 [details] [review]
[PATCH] drm/i915: Increase HSW/BDW FCLK<->LCPLL switch timeout

Might just be the hw is just a bit slow in responding. Increasing the timeout could avoid the error.
Comment 3 Lakshmi 2019-05-24 13:34:51 UTC 
Zhang, Can you verify the issue with the attached patch?
Comment 4 Lakshmi 2019-05-31 08:04:29 UTC 
Zhang, any updates here?
Comment 5 Lakshmi 2019-07-02 06:41:32 UTC 
No feedback for more than a month. Closing this bug as WORKSFORME. 

If the issue persists with the attached patch, please reopen the issue. Remember to attach dmesg from boot with kernel parameters drm.debug=0x1e log_buf_len=4M

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.