<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [SNB] GPU hang after over temperature" href="https://bugs.freedesktop.org/show_bug.cgi?id=99611#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [SNB] GPU hang after over temperature" href="https://bugs.freedesktop.org/show_bug.cgi?id=99611">bug 99611</a> from <a class="email" href="mailto:elizabethx.de.la.torre.mena@intel.com" title="Elizabeth <elizabethx.de.la.torre.mena@intel.com>"> Elizabeth</a> <pre>(In reply to Chris Tillman from <a href="show_bug.cgi?id=99611#c5">comment #5</a>) > ... available measurements from coretemp were not being heeded. The > logs show that an overtemperature is reported only for a cycle until it > sets back, saying for example > > "[57849.613938] CPU1: Core temperature above threshold, cpu clock throttled > (total events = 12172)" > and then almost immediately (12 microseconds) after, > "[57849.614950] CPU1: Core temperature/speed normal" > > It appears from the logs that the only response to monitoring is an > immediate reset of the sensor, and that protection of the machine is not > occurring. > Hello Chris, Although this is in fact a problem, it seems to be more related to the CPU and the coretemp program than to the GPU and DRM, if that's the case there is no much to do for us here. Could you please take some time to check on the community forums for some orientation on what product/component could be causing the problem and change the bug information? That would be helpful to find a solution on this case: <a href="https://01.org/linuxgraphics/community">https://01.org/linuxgraphics/community</a> Thank you.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>