Comment # 11 on bug 1004933 from John H.

(In reply to Luis Rodriguez from comment #10)
> (In reply to John H. from comment #9)
> > although this maybe due to gdm switching to wayland.
> 
> Perhaps but how? The issue I saw with this code path which seemed rather
> racy path with getting EDID info on bootup/suspend.

yes, i guess a race problem, too. wayland may simply be slower (or later or
loading wayland-lib takes longer) then X when requesting information on
screens.

> To this end I have had
> some changes I've made to firmware_class which I'd like you to test. Is it
> possible for you to test random kernel trees ?
> 
> If so can you test this branch ?
> 
> https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux-next.git/log/
> ?h=20170329-driver-data-v2-try2

havn't build a kernel in a while, but i'll try.

> > just had this while trying to access a tty
> > from X.
> 
> How exactly did this happen. You booted up, and after a while you switch to
> a tty from X ? No suspend / resume at all ?

no suspend / resume. i just wanted to switch to another runlevel so i pressed
ctrl + alt + f1 from X and then all rendering stopped because of the above bug.
i sshd into the machine and saw i had to reboot...