Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!oberon!cit-vax!elroy!ames!pasteur!cory.Berkeley.EDU!dheller From: dheller@cory.Berkeley.EDU (Dan Heller) Newsgroups: comp.windows.x Subject: Xerver bug (Waitforsomething(): errno=22) Message-ID: <3577@pasteur.Berkeley.Edu> Date: 21 May 88 03:26:41 GMT Sender: news@pasteur.Berkeley.Edu Reply-To: dheller@cory.Berkeley.EDU (Dan Heller) Organization: University of California, Berkeley Lines: 27 /* I posted this once, but it didn't seem to make it */ Ever since I installed X11 on my sun3-110, I've had this symptom: The screen "blinks" (goes black and then returns immediately) and an error message appears in my console window: waitforsomething(), errno=22 Normally, I get about 5 or 6 of them and then it goes away. This doesn't bother me, but the last time it happened, the screen remained blank and I couldn't do anything. I logged in from a remote machine and did all the appropriate ps's and pstats and so on looking for something unusual, but I couldn't find anything. I tried to run some commands (such as xrefresh), but nothing happened. I had even run a couple programs which access the brame buffer directly with no avail. Curious as to how badly the hardware was munged, I did the ever-useful L1-A sequence on the console (with the intent to enter "c" should it have worked), but that didn't even take. I didn't even lose my connection from the remote host. Nothing was happening... So, I started to play with signals... I sent sigcont, sighup and finally sigterm to the server, but nothing happened. Finally, I sent the KILL signal and my system crashed. Suggestions as to what {sh,c}ould I have done? Dan Heller