[Bug 104467] New: [IGT][SNB] intel_pstate: Turbo disabled by BIOS or unavailable on processor

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Jan 2 23:23:52 UTC 2018


https://bugs.freedesktop.org/show_bug.cgi?id=104467

            Bug ID: 104467
           Summary: [IGT][SNB] intel_pstate: Turbo disabled by BIOS or
                    unavailable on processor
           Product: DRI
           Version: DRI git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: major
          Priority: medium
         Component: DRM/Intel
          Assignee: intel-gfx-bugs at lists.freedesktop.org
          Reporter: elizabethx.de.la.torre.mena at intel.com
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
                CC: intel-gfx-bugs at lists.freedesktop.org

Created attachment 136513
  --> https://bugs.freedesktop.org/attachment.cgi?id=136513&action=edit
kern_log_snb_ff

We keep getting this messages on dmesg while running IGT:

[  224.416285] Setting dangerous option reset - tainting kernel
[  229.012298] intel_pstate: Turbo disabled by BIOS or unavailable on processor

CPU is Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz (family: 0x6, model: 0x2a,
stepping: 0x7).
I already confirmed that the Turbo boost option is enable on BIOS, also enable
CONFIG_INTEL_TURBO_MAX_3=y on kernel config, since I found this parameter on a
CI config shared on other bug, and the warn keeps appearing.

SUCCESS tests with the warn from today's commit:
IGT-Version: 1.20-gd86d53b (x86_64) (Linux:
4.15.0-rc5-drm-tip-config-intel-turbo-ww1-commit-16432d3+ x86_64)

igt at gem_exec_nop@basic-series
igt at gem_exec_flush@basic-wb-rw-before-default
igt at gem_exec_flush@basic-wb-ro-default

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180102/1b9500b6/attachment.html>


More information about the intel-gfx-bugs mailing list