<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTOURBUG - [IGT][SNB] intel_pstate: Turbo disabled by BIOS or unavailable on processor"
href="https://bugs.freedesktop.org/show_bug.cgi?id=104467">bug 104467</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>NOTOURBUG
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTOURBUG - [IGT][SNB] intel_pstate: Turbo disabled by BIOS or unavailable on processor"
href="https://bugs.freedesktop.org/show_bug.cgi?id=104467#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTOURBUG - [IGT][SNB] intel_pstate: Turbo disabled by BIOS or unavailable on processor"
href="https://bugs.freedesktop.org/show_bug.cgi?id=104467">bug 104467</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>