<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [REGRESSION] KMS having issues after kernel upgrade (4.5.1-1 to 4.6.4-1)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97620#c20">Comment # 20</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [REGRESSION] KMS having issues after kernel upgrade (4.5.1-1 to 4.6.4-1)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=97620">bug 97620</a>
from <span class="vcard"><a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> <span class="fn">Ilia Mirkin</span></a>
</span></b>
<pre>(In reply to Luke Tidd from <a href="show_bug.cgi?id=97620#c18">comment #18</a>)
<span class="quote">> <a href="https://bugs.freedesktop.org/attachment.cgi?id=126609">https://bugs.freedesktop.org/attachment.cgi?id=126609</a>
> I don't see "bios: running init tables" but here is the entire dmesg.</span >
Indeed. So the "working" state is to not run the VBIOS. Something in there is
upsetting matters (normally running the VBIOS a second time doesn't hurt
anything, it's just pointless work and can cause a flicker). Assuming that
disabling vesafb doesn't help (the way those legacy interfaces are implemented
can be pretty brittle), please include
(a) /sys/kernel/debug/dri/0/vbios.rom (from any boot)
(b) nouveau.debug=debug,bios=trace output from a *broken* kernel boot
Ideally that should provide some further things to look at.</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>