elm/hana: dmesg sometimes contains devfreq "Couldn't update frequency transition information. |
||||
Issue descriptionCHROMEOS_RELEASE_BUILDER_PATH=hana-release/R60-9523.0.0 (1) run webgl aquarium (2) inspect /var/log/messages Sometimes the log contains messages like: 2017-05-15T17:53:54.503485+08:00 ERR kernel: [ 2975.667432] devfreq 13000000.mfgsys-gpu: Couldn't update frequency transition information. 2017-05-15T17:53:54.855528+08:00 ERR kernel: [ 2976.019583] devfreq 13000000.mfgsys-gpu: Couldn't update frequency transition information. 2017-05-15T17:53:55.879375+08:00 ERR kernel: [ 2977.043419] devfreq 13000000.mfgsys-gpu: Couldn't update frequency transition information. 2017-05-15T17:53:56.183465+08:00 ERR kernel: [ 2977.347445] devfreq 13000000.mfgsys-gpu: Couldn't update frequency transition information. 2017-05-15T17:53:59.035471+08:00 ERR kernel: [ 2980.199398] devfreq 13000000.mfgsys-gpu: Couldn't update frequency transition information. 2017-05-15T17:53:59.367488+08:00 ERR kernel: [ 2980.531606] devfreq 13000000.mfgsys-gpu: Couldn't update frequency transition information.
,
May 31 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/74a4cd5b155421b6d137041241cbf07c30cbcc45 commit 74a4cd5b155421b6d137041241cbf07c30cbcc45 Author: Daniel Kurtz <djkurtz@chromium.org> Date: Wed May 31 09:15:26 2017 CHROMIUM: drm/img-rogue: Always convert defreq_target to OPP frequency The devfreq core expects a devfreq profile's target() callback to always return with freq set to the current frequency - even if the function does not actually change the frequency, it should still modify *freq to match the current un-set value. * @target: * Before returning, target function should set * freq at the current frequency. The devfeq core relies on the returned freq value being a correct OPP frequency to perform its state transition statistics. Signed-off-by: Daniel Kurtz <djkurtz@chromium.org> BUG= chromium:722329 TEST=http://webglsamples.org/aquarium/aquarium.html => dmesg does not contain "devfreq 13000000.mfgsys-gpu: Couldn't update frequency transition information." Change-Id: Ia42354cfc98edd303c40d3def31f06a097d9152d Reviewed-on: https://chromium-review.googlesource.com/505988 Commit-Ready: Daniel Kurtz <djkurtz@chromium.org> Tested-by: Daniel Kurtz <djkurtz@chromium.org> Reviewed-by: Frank Binns <frank.binns@imgtec.com> Reviewed-by: Nicolas Boichat <drinkcat@chromium.org> [modify] https://crrev.com/74a4cd5b155421b6d137041241cbf07c30cbcc45/drivers/gpu/drm/img-rogue/1.7/pvr_dvfs_device.c
,
May 31 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/74a4cd5b155421b6d137041241cbf07c30cbcc45 commit 74a4cd5b155421b6d137041241cbf07c30cbcc45 Author: Daniel Kurtz <djkurtz@chromium.org> Date: Wed May 31 09:15:26 2017 CHROMIUM: drm/img-rogue: Always convert defreq_target to OPP frequency The devfreq core expects a devfreq profile's target() callback to always return with freq set to the current frequency - even if the function does not actually change the frequency, it should still modify *freq to match the current un-set value. * @target: * Before returning, target function should set * freq at the current frequency. The devfeq core relies on the returned freq value being a correct OPP frequency to perform its state transition statistics. Signed-off-by: Daniel Kurtz <djkurtz@chromium.org> BUG= chromium:722329 TEST=http://webglsamples.org/aquarium/aquarium.html => dmesg does not contain "devfreq 13000000.mfgsys-gpu: Couldn't update frequency transition information." Change-Id: Ia42354cfc98edd303c40d3def31f06a097d9152d Reviewed-on: https://chromium-review.googlesource.com/505988 Commit-Ready: Daniel Kurtz <djkurtz@chromium.org> Tested-by: Daniel Kurtz <djkurtz@chromium.org> Reviewed-by: Frank Binns <frank.binns@imgtec.com> Reviewed-by: Nicolas Boichat <drinkcat@chromium.org> [modify] https://crrev.com/74a4cd5b155421b6d137041241cbf07c30cbcc45/drivers/gpu/drm/img-rogue/1.7/pvr_dvfs_device.c
,
May 31 2017
,
Jun 16 2017
not reproducible in Chrome OS 9656.0.0, 61.0.3132.0.
,
Jul 10 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/1cf4b393673c5eea49f8820c748894f4c810cc84 commit 1cf4b393673c5eea49f8820c748894f4c810cc84 Author: Daniel Kurtz <djkurtz@chromium.org> Date: Mon Jul 10 22:27:24 2017 CHROMIUM: drm/img-rogue: Always convert defreq_target to OPP frequency The devfreq core expects a devfreq profile's target() callback to always return with freq set to the current frequency - even if the function does not actually change the frequency, it should still modify *freq to match the current un-set value. * @target: * Before returning, target function should set * freq at the current frequency. The devfeq core relies on the returned freq value being a correct OPP frequency to perform its state transition statistics. Note: This change was previously applied to the 1.7 driver (CL:505988), but lost during the upgrade to 1.8. Signed-off-by: Daniel Kurtz <djkurtz@chromium.org> BUG= chromium:722329 TEST=http://webglsamples.org/aquarium/aquarium.html => dmesg does not contain "devfreq 13000000.mfgsys-gpu: Couldn't update frequency transition information." Change-Id: I824744615711c9afbfcbb8edc6b56a7526f258da Reviewed-on: https://chromium-review.googlesource.com/564877 Commit-Ready: Daniel Kurtz <djkurtz@chromium.org> Tested-by: Daniel Kurtz <djkurtz@chromium.org> Reviewed-by: Nicolas Boichat <drinkcat@chromium.org> [modify] https://crrev.com/1cf4b393673c5eea49f8820c748894f4c810cc84/drivers/gpu/drm/img-rogue/pvr_dvfs_device.c |
||||
►
Sign in to add a comment |
||||
Comment 1 by djkurtz@chromium.org
, May 15 2017