<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED --- - [HSW/BYT/BDW Bisected ]system sporadically boot fail" href="https://bugs.freedesktop.org/show_bug.cgi?id=81140#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED --- - [HSW/BYT/BDW Bisected ]system sporadically boot fail" href="https://bugs.freedesktop.org/show_bug.cgi?id=81140">bug 81140</a> from <a class="email" href="mailto:lei.a.liu@intel.com" title="liulei <lei.a.liu@intel.com>"> liulei</a> <pre>(In reply to <a href="show_bug.cgi?id=81140#c9">comment #9</a>) > Comment on <a href="attachment.cgi?id=102512" name="attach_102512" title="boot log">attachment 102512</a> <a href="attachment.cgi?id=102512&action=edit" title="boot log">[details]</a> > boot log > > Yeah I'm not seeing how this patch would affect non-BDW either. All the > structures it checks in the pre VLV check look like they ought to be > allocated and present. And the log doesn't have a crash in it... > > So either this is timing related or this is the wrong bisect result. As this bug title said this issue can't be reproduced 100%. Each time I run 5 times. If machine boot successfully with no crash in this round, I considered the commit I tested was good. Eventually bisect shown this commit was the first bad commit.And i tested its parent commit 5 five times , I didn't get crash. Since you both thought this bisect was wrong. I will try more times for a more credible bisect result.I will reply after my second bisect.</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>