Bug 104467 - [SNB] intel_pstate: Turbo disabled by BIOS or unavailable on processor
Summary: [SNB] intel_pstate: Turbo disabled by BIOS or unavailable on processor
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: medium major
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
Whiteboard: ReadyForDev
Depends on:
Reported: 2018-01-02 23:23 UTC by Elizabeth
Modified: 2018-01-04 21:48 UTC (History)
1 user (show)

See Also:
i915 platform: SNB
i915 features:

kern_log_snb_ff (14.24 MB, text/plain)
2018-01-02 23:23 UTC, Elizabeth
no flags Details

Description Elizabeth 2018-01-02 23:23:52 UTC
Created attachment 136513 [details]

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)

Comment 1 Elizabeth 2018-01-03 22:27:49 UTC
+ igt@gem_exec_flush@basic-wb-rw-default commit-cb4a985+
Comment 2 Elizabeth 2018-01-04 21:29:48 UTC
igt@gem_exec_flush@basic-wb-set-default, commit-eb3dae3+
igt@gem_exec_nop@basic-series, commit-eb3dae3+
Comment 3 Chris Wilson 2018-01-04 21:41:56 UTC
This is not a bug, drivers/cpufreq/intel_pstate.c is loudly reporting that it has no "turbo" (marginal overclock) frequencies. It is not even igt that is writing to /sys/devices/system/cpu/intel_pstate/no_turbo that triggers the warning. Look carefully at your own system; and file a bug against intel_pstate if you find the warning obnoxious, after all it is triggered by userspace and an error is reported already.
Comment 4 Elizabeth 2018-01-04 21:48:13 UTC
On it, thanks for the clarification.

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.