<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:vanshidhar.r.konda@intel.com" title="Vanshidhar Konda <vanshidhar.r.konda@intel.com>"> <span class="fn">Vanshidhar Konda</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][SHARDS] igt@gem_eio@kms - dmesg-warn - NMI backtrace for cpu 1 skipped: idling at intel_idle+0x7b/0x120"
href="https://bugs.freedesktop.org/show_bug.cgi?id=112000">bug 112000</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;">Priority</td>
<td>not set
</td>
<td>medium
</td>
</tr>
<tr>
<td style="text-align:right;">Severity</td>
<td>not set
</td>
<td>minor
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][SHARDS] igt@gem_eio@kms - dmesg-warn - NMI backtrace for cpu 1 skipped: idling at intel_idle+0x7b/0x120"
href="https://bugs.freedesktop.org/show_bug.cgi?id=112000#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][SHARDS] igt@gem_eio@kms - dmesg-warn - NMI backtrace for cpu 1 skipped: idling at intel_idle+0x7b/0x120"
href="https://bugs.freedesktop.org/show_bug.cgi?id=112000">bug 112000</a>
from <span class="vcard"><a class="email" href="mailto:vanshidhar.r.konda@intel.com" title="Vanshidhar Konda <vanshidhar.r.konda@intel.com>"> <span class="fn">Vanshidhar Konda</span></a>
</span></b>
<pre>This issue seems to be related to:
<a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][SHARDS]igt@gem_eio@kms - dmesg-warn - watchdog: BUG: soft lockup - CPU#2 stuck for 255s! [swapper/2:0]"
href="show_bug.cgi?id=112001">https://bugs.freedesktop.org/show_bug.cgi?id=112001</a>
In both these issues, the kernel has detected that the TSC is skewed on one of
the CPUs and it switches from TSC as the clocksource to HPET. In both cases the
issues occur on SNB platform and started occuring 3 weeks, 3 days ago. The
issue noted in this bug occurs once almost everyday. The two issues may be a
manifestation of the same error.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>