> I used to have them handy but having recently moved (from Lake County > to Vacaville) I can't find anything. When my broken back (compression > fracture of T12) heals, I might be able to try a brand new GeForce > GTX1080-Ti, but not for a while.
take are of yourself! > One more item... > > If I boot up and get an X session going, with xclock window running, and > then I Ctrl-Alt-F1 to go to "console" display, whenn I subsequenty go > back to X via Ctrl-Alt-F5 it takes 5- to 10-seconds before X becomes > responsive. Until then, no kb events, no mouse tracking, nada. Any > xterm output generated while viewing console is delayed until the above > delay expires, and xclock does a "catch-up" when the system becomes > ready, Note that the delay occurs even if I immediately switch back to > the F5 X window. > > It seems as though its getting confused on what it should be waiting > for, perhaps passing a garbage [fm]utex pointer into the kernel. (This > is just CONJECTURE on my part.) Sometimes the random value is sort-of > valid (even if wrong) while other times it is so far from reality that > some sort of fault occurs. > > And one more observation... > > Sometimes after the F1/F5 dance it doesn't recover, hanging instead. In > this case I can usually ssh in from my Windoze laptop and kill the main > firefox process; often but not always this unhangs the X window. when you get into this situation, can you run crash(8) and find out what things are hanging on? i just tested (on 1030T) and i was able to switch quickly to tty1 back to tty5 to tty1 to tty5 in about 3 seconds. about as fast as i'd expect... .mrg.
