[Bug 99345] [KBL] [drm:skl_set_cdclk] *ERROR* failed to inform PCU about cdclk change
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Tue Jan 17 09:26:25 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=99345
--- Comment #6 from Andrey <ryabinin.a.a at gmail.com> ---
(In reply to Imre Deak from comment #5)
> (In reply to Andrey from comment #4)
> Ok, please let me know if you see the 'failed to inform PCU' error with this
> patch after longer use. Would be also good to know the maximum poll duration
> you see based on the timestamp diff of the lines like the following two:
>
> [ 65.704858] [drm:skl_pcode_request] PCODE timeout, retrying with
> preemption disabled
> [ 65.707102] [drm:intel_update_cdclk] Current CD clock rate: 337500 kHz,
> VCO: 8100000 kHz, ref: 24000 kHz
>
> In your first dmesg it was ~10ms in the second ~4ms.
>
I've been running suspend-resume display script for couple hours and haven't
seen any 'failed to inform PCU' errors.
There were 46 PCODE timeouts. The maximum timestamp diff was 34ms:
[ 6689.473863] [drm:skl_pcode_request] PCODE timeout, retrying with preemption
disabled
[ 6689.508758] [drm:intel_update_cdclk] Current CD clock rate: 337500 kHz, VCO:
8100000 kHz, ref: 24000 kHz
There was also one 15ms. All other timeouts >=4ms.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170117/4aa5ee31/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list