SUMMARY: CDE problem

Thomas Wong (
Wed, 18 Feb 1998 15:44:16 -0800 (PST)

Thank you to the following for their replies:
Joel Lee <> (Lee Fedor-User)
Greg Obremski <>
"Kevin P. Inscoe" <>


Original question:

We have a strange problem with one of our machines. The machine is a Sparc5
running Solaris 2.5.1. The user would login and use CDE for the desktop. Every
once in awhile, CDE would suddenly die and logs him off whether he's using the
machine or sitting idle.

Checking his .dt's errorlog file, it reads:

02/13/98 00:13:18 (/usr/dt/bin/dtexec) /usr/dt/bin/dtscreen

X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 25 (X_SendEvent)
Resource id in failed request: 0x2800063
Serial number of failed request: 9
Current serial number in output stream: 10

Fri Feb 13 00:13:28 1998
Workspace Manager: I/O error on display:: :0.0

The above error occured after he'd left the machine for the night in lockscreen.
Only to come back the next day to find that he was logoff. Not sure why it
would die. And he may have left some programs on the desktop but nothing was
active so don't know what was running. He have had this occured while he was
reading his email (hence only thing running was dtmail).

I've re-jumpstarted his machine in thinking that Solaris is corrupted somewhere
somehow. Still the same thing. Any ideas? Thanks.

------------------------------------------------------------------------------ (Lee Fedor-User) suggested that it could be the cache on the
motherboard. They had a similar problem and it took months for the error to
become severe enough to produce error messages. Our maintenance contract won't
allow a motherboard swap unless I can prove there's a problem so I guess I will
have to wait till errors show up, if we have the same problem.


Greg Obremski <> suggested that we could be running low on
RAM/swap, but we have a number of systems with the same config (all jumpstart)
and some of the other machines are used much more heavily than this machine with
no problem. And we do have plenty of RAM/swap on our machines... I think.


"Kevin P. Inscoe" <> also suggests that it could be the swap.
But I have almost as much swap as he does so maybe not.


Joel Lee <> suggested that I remove the user's .dt directory and
see if this fixes things. Since this is the easiest thing to try, I've done
this first. So far so good (one day so far) but we've had a couple of good days
straight before so I will wait and see.

I'm hoping this is the solution. If not, I'll have to try the other
suggestions. Thanks you once again for the replies.