<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][SHARDS] Random tests - incomplete - empty stdout/stderr/dmesg - watchdog0: watchdog did not stop!"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110246#c32">Comment # 32</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [CI][SHARDS] Random tests - incomplete - empty stdout/stderr/dmesg - watchdog0: watchdog did not stop!"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110246">bug 110246</a>
from <span class="vcard"><a class="email" href="mailto:arkadiusz.hiler@intel.com" title="Arek Hiler <arkadiusz.hiler@intel.com>"> <span class="fn">Arek Hiler</span></a>
</span></b>
<pre>But still seems to be present. Assessment stays true.
<7>[ 26.796741] [IGT] kms_universal_plane: exiting, ret=0
<NOTHIGN FROM IGT>
<2>[ 27.667078] watchdog: watchdog0: watchdog did not stop!
That's 1s in which we do nothing, and then just die, which looks suspicious.
Jenkin's side log end sooner, I guess this did not get enough time to sync over
network.
Few ideas that may help:
1. make ioctls/writes to watchdog more robust (retry on EAGAIN or EINTR)
2. log if we decrease watchdog timeout
3. log watchdog related messages to the dmesg too (this makes them recoverable
from pstores/dmesg logs)</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 on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>