[Bug 105811] kernel 4.15.x boot fails at kms

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=105811

--- Comment #22 from Alec Habig <ahabig at umn.edu> ---
sshing in let me continue to work on shell in the ssh session, after the
console hung upon exiting.  dmesg reports continued "flip timeout" errors as
kms flails.

"shutdown -r now" at this point, although booting the ssh session promptly as
expected, takes a few minutes to complete, seems to be waiting for the kms
errors to complete.  This clean boot did allow me to get a journalctl log of
the whole process (will attach that).

I understand that optimus is a nasty mess.  But, frustratingly, things work
just fine with the fedora 4.14.* series, and just fine with your debugging tree
kernel.  As a user I suppose I can always go back to the bad old days of hand
installing kernels rather than just loading them from the yum repository.  Last
time I did that regularly was going on 20 years ago :)

The fact that the errors happen with either fedora's 4.15.* tree or their 4.16
devel tree is telling us that something in the deltas they apply to their
kernel build is the source of the problem.  I suppose at this point, I go back
to the original fedora bugzilla and put the ball back in their court? 
bisecting their configs and patches sounds like the next (tedious) step.

Before I go, though: what are these "flip timeout" errors?  If I had to guess,
any number of things horribly wrong in there could make the i915 module get
into a funny state that eventually throws this error: but any insight as I move
forward would be appreciated.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180427/24e5f915/attachment-0001.html>