<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - [CI][BAT] igt* incomplete - /dev/kmsg buffer overrun, some messages lost - pstore cleanout broken" href="https://bugs.freedesktop.org/show_bug.cgi?id=103706#c36">Comment # 36</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - [CI][BAT] igt* incomplete - /dev/kmsg buffer overrun, some messages lost - pstore cleanout broken" href="https://bugs.freedesktop.org/show_bug.cgi?id=103706">bug 103706</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 Marta Löfstedt from <a href="show_bug.cgi?id=103706#c35">comment #35</a>) > <a href="https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3445/shard-hsw3/">https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3445/shard-hsw3/</a> > igt@<a href="mailto:kms_flip@vblank-vs-dpms-suspend-interruptible.html">kms_flip@vblank-vs-dpms-suspend-interruptible.html</a> > > none of the pstores match dmesg and are clearly from unrelated runs, since > this run is first after reboot. Took out the HSW3 from the lab, there was no issue cleaning out pstore logs with pstore kernel. There was no issue cleaning out pstore logs that was force generated on drm kernel with pstore kernel. There was no issue cleaning out pstore gereated on drm kernel with drm kernel. So, maybe there is something wrong with the algorith that rename the pstore logs or there was something wrong with pstore clean out early on 4.15 which has now been fixed.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>