<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [BAT] igt@pm_rpm@basic-pci-d3-state - incomplete - timeout/system hang" href="https://bugs.freedesktop.org/show_bug.cgi?id=103339#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [BAT] igt@pm_rpm@basic-pci-d3-state - incomplete - timeout/system hang" href="https://bugs.freedesktop.org/show_bug.cgi?id=103339">bug 103339</a> from <a class="email" href="mailto:marta.lofstedt@intel.com" title="Marta Löfstedt <marta.lofstedt@intel.com>"> Marta Löfstedt</a> <pre>(In reply to Rodrigo Vivi from <a href="show_bug.cgi?id=103339#c2">comment #2</a>) > Was this one time thing randomly or is this happening always now? > It is random. Here is a description on how you can retrieve this information. So, you don't have to wait for a reply in the future. >From Intel GFX CI top page: <a href="https://intel-gfx-ci.01.org/">https://intel-gfx-ci.01.org/</a> The CNL machine is in farm1 running the IGT fastfeedback testslist. So, to get a visual overview of the current issues checkout DRM-Tip - Fast: issues: <a href="https://intel-gfx-ci.01.org/tree/drm-tip/">https://intel-gfx-ci.01.org/tree/drm-tip/</a> we are looking for fi-cnl-y, when I just check the last 5 run has been green so, yes this issue appear to be random. Now if you click the fi-cnl-y label, you will see a longer history of the result for fi-cnl-y. Here I see 5 purple spots indicating the incomplete test results. If you click those you'll get to the piglit generated result pages: <a href="https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3218/fi-cnl-y/igt@gem_ctx_switch@basic-default.html">https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3218/fi-cnl-y/igt@gem_ctx_switch@basic-default.html</a> <a href="https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3271/fi-cnl-y/igt@gem_exec_flush@basic-batch-kernel-default-uc.html">https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3271/fi-cnl-y/igt@gem_exec_flush@basic-batch-kernel-default-uc.html</a> <a href="https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3259/fi-cnl-y/igt@kms_pipe_crc_basic@read-crc-pipe-b-frame-sequence.html">https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3259/fi-cnl-y/igt@kms_pipe_crc_basic@read-crc-pipe-b-frame-sequence.html</a> <a href="https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3283/fi-cnl-y/igt@kms_pipe_crc_basic@read-crc-pipe-b.html">https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3283/fi-cnl-y/igt@kms_pipe_crc_basic@read-crc-pipe-b.html</a> <a href="https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3258/fi-cnl-y/igt@pm_rpm@basic-pci-d3-state.html">https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3258/fi-cnl-y/igt@pm_rpm@basic-pci-d3-state.html</a> The first 2 have pstore generated panic/oops logs. In this case a panic was generated from a BUG_ON, this issue issue is filed on <a class="bz_bug_link bz_status_NEW " title="NEW - [BAT][CI] kernel BUG at drivers/gpu/drm/i915/intel_lrc.c:880!" href="show_bug.cgi?id=102035">bug 102035</a> and not on this bug. The last 3 doesn't have any logs, so the machine ended up in a state that either none of our watchdog systems could trigger, i.e. system hang or the run was timed out externally by the Jenkins system. When I found these issues I file a new bug for each machine, and when I get a new occurrence in cibuglog I will open the bug and add the new information. However, in this case it looks like I have missed the <a href="https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3259/fi-cnl-y/igt@kms_pipe_crc_basic@read-crc-pipe-b-frame-sequence.html">https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3259/fi-cnl-y/igt@kms_pipe_crc_basic@read-crc-pipe-b-frame-sequence.html</a>. But, if we look at the dmesg from that run: <a href="https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3259/fi-cnl-y/dmesg0.log">https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3259/fi-cnl-y/dmesg0.log</a> the last message is: <2>[ 471.997559] watchdog: watchdog0: watchdog did not stop! This we believe is due to a flaw in our softdog deamon owatch, and is filed on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - [BAT][CI][ALL] igt@potentially all tests - watchdog: watchdog0: watchdog did not stop" href="show_bug.cgi?id=102332">bug 102332</a>. You can also got a lot of information from the cibuglog page: <a href="https://intel-gfx-ci.01.org/cibuglog/">https://intel-gfx-ci.01.org/cibuglog/</a> If you are interested in fi-cnl-y, find a link for it in the Affected machines column: <a href="https://intel-gfx-ci.01.org/cibuglog/index.html%3Faction_failures_history=-1&failures_machine=fi-cnl-y.html">https://intel-gfx-ci.01.org/cibuglog/index.html%3Faction_failures_history=-1&failures_machine=fi-cnl-y.html</a> and you will see all issues that has occurred since CI_DRM_3121. Note, once a failing test has been reported on a machine and bug. The following results from this test machine combination is suppressed from both affecting pre-merge results and new reporting to cibuglog, i.e. I will not see if for example an incomplete is reproduced or not. If you look at the entry of this bug in cibuglog, it currently say 2 / 23 runs (9 %) in the Failure rate column. In this case it is true, this issue has only happened twice, however if one of the reporeted test had failed instead of incomplete:ed there would ne 3 / 23 runs. Martin is currently fixing this so that the reason for fail on a test should matter. > I believe it is the same I'm starting to see with testdisplay with multiple > monitors connected. > > do you have more than 1 monitor plugged on this cnl? >From our top page there is a link to our hardware descrition page: <a href="https://intel-gfx-ci.01.org/tree/drm-tip/hardware.html">https://intel-gfx-ci.01.org/tree/drm-tip/hardware.html</a> fi-cnl-y Intel Cannonlake-Y RVP Cannonlake eDP, (DP, HDMI) So, this machine only has an eDP panel connected. Parentheses show non connected options. > > if this is always happening now, do we have a good day / a good bisect point? > > Thanks, > Rodrigo.</pre> </div> <hr> You are receiving this mail because: <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>