<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [bisected] Fury fails to boot on drm-next-4.9"
href="https://bugs.freedesktop.org/show_bug.cgi?id=98016#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [bisected] Fury fails to boot on drm-next-4.9"
href="https://bugs.freedesktop.org/show_bug.cgi?id=98016">bug 98016</a>
from <span class="vcard"><a class="email" href="mailto:adf.lists@gmail.com" title="Andy Furniss <adf.lists@gmail.com>"> <span class="fn">Andy Furniss</span></a>
</span></b>
<pre>(In reply to Ernst Sjöstrand from <a href="show_bug.cgi?id=98016#c3">comment #3</a>)
<span class="quote">> This seems to be very hard to reproduce. Perhaps it's related to the kernel
> I'm rebooting from or some complex combination.
> Pretty hard to debug when the computer simply stops responding without any
> text etc.</span >
Yea, it's tricky sometimes.
For my (I guess different) tonga start up issue I had to power down "properly"
between bisect steps. By properly I mean shutdown/halt then cut the power to
the PSU and wait a couple of minutes before powering up again.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>