[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

2010.0. "Window Manager keeps exiting..." by TOOK::C_PEREZ (The InFAMous Eight) Mon Jan 08 1990 11:14

  I didn't see any topics that related to my problem so here goes...

  My window manager keeps exiting with no given reason. All that
appears is the message "Window Manager exited." in DECterm 1. I'm
running SSB VMS V5.3 and DECwindows V2 that came with VMS.

 This problem appeared right after my VS2000 got a 12Mb memory board
put in.  Initially the problem happened the first time I logged in,
maybe 30 minutes. After looking a friends UAF parameters I bumped up
values, ran AUTOGEN and every was OK then a couple days later the
window manager exited. This has happened a few times now and I'm fed
up with it!! Is there something I can do, some value I can change?

  Some additional info: I have about 14 windows running, 3 DECterms,
Fileview, Calculator, [these are run from AutoStart menu], Banner
spawned from DECterm 1, AutoFocus also spawned from DECterm 1, and
several DECwindows applications running from our cluster. Except for
Banner [I use the Active Icons option], I ran with the same setup under
the 6Mb configuration [Yes, it was SLOW!!!] so I'm puzzled why this
happens now...
                      Any help appreciated...  Thanks,
                                                Craig
T.RTitleUserPersonal
Name		DateLines
2010.1How old is your memory board?AGBEAR::HORNERA.G.Bear, Old fashion teddy bearMon Jan 08 1990 12:4311
    Well, I wouldn't think that this would still be possible since it has
    now been six months since the problem was diagnosed and fixed, but have
    Field Service check the rev level of your 12MB board.  Depending on
    where, when, and how you got it, you might have one of the boards that
    crashes systems when the referenced physical address gets above 10MB.

    Barring that, the next most likely suspect is quotas/sysgen values.  I
    have almost exactly the same configuration that you mention, with a
    similiar load, and have no problems.

               Dave
2010.2exSTAR::CYPRYCHMon Jan 08 1990 13:565
    Is "Window Manager exited." the exact message?
    
    Assigning DECW$WINMGR_OUTPUT as a system logical
    pointing to a file will allow the window manager
    to log connection aborts.
2010.3What params to look at?TOOK::C_PEREZThe InFAMous EightMon Jan 08 1990 14:1419
RE: .1

   Hmmm... I don't think it's an old 12Mb board. The shipment came
recently and all the other people who got them haven't run into this
problem. I have also gotten memory usage close to 100%, plus I just
loaded DECwindows LSE V3.0 when I had 75% usage and everything is
still fine [this must have addressesd above 10Mb].

RE: .2

   Yes, "Window Manager exited." is the exact message. I will define
the logical and see what happens.


   Going back to Dave's second suggestion, could someone give me a
clue as to what quotas/sysgen params that I should be looking at...

                                      Thanks,
                                       Craig
2010.4GOSOX::RYANDECwindows MailTue Jan 09 1990 07:465
	I would also try running without AutoFocus - since it sort of
	treads in window manager territory, it's not hard to imagine
	some negative interaction there...

	Mike
2010.5AHHhh... It crashed!TOOK::C_PEREZThe InFAMous EightWed Jan 10 1990 13:25458
  Well my window manager just died again, only this time the whole
DECwindows server crashed. This happened to me once before but I
never realized the server crashed. I hope to get a window manger log
of when it just exits...

  I have enclosed the window manager log and server error log below.
I should also note I had a some problems with DECwindows applications
running on our cluster die on me, from looking at the log I think that
errors on my VS2000 may have caused the problem. It happend mostly with
DECW$MAIL when I clicked on 'Send', all the mail windows just went poof!

  BTW, could this the conditioned mention in .1 where an early rev 12Mb
board causes a crash? or did the crash involve the whole system?

   HELP... -Craig


This is window manager log I got by using DECW$WINMGR_OUPUT logical:
---------------------------------------------------------------------
 Digital Equipment Corporation VMS Window Manager 
X Toolkit Warning: Cannot allocate colormap entry for "Grey"
 FATAL X I/O error 
 Dpy: 1437688
---------------------------------------------------------------------
This is DECW$SERVER_0_ERROR.LOG
----------------------------------------------------------------------
 8-JAN-1990 10:47:29.6 Hello, this is the X server
Dixmain address=127b0
Now attach all known txport images
%DECW-I-ATTACHED, transport DECNET attached to its network
in SetFontPath
out SetFontPath
Monochrome Frame Buffer support loaded
mfb$InitOutput address=14c600
Connection Prefix: len == 36
 8-JAN-1990 10:48:47.5 Now I call scheduler/dispatcher
 8-JAN-1990 10:48:57.8 Connection 98d00 is closed by Txport
 8-JAN-1990 10:50:17.0 Connection 98d38 is closed by Txport
 8-JAN-1990 11:15:04.6 Connection 2bbd00 is closed by Txport(status = 20e4)
 8-JAN-1990 11:19:06.1 Connection 2be588 is closed by Txport(status = 20e4)
 8-JAN-1990 11:20:18.8 Using extra todo packet pool...
 8-JAN-1990 11:22:05.7 Connection 2be5c0 is closed by Txport
 8-JAN-1990 11:23:14.1 Connection 2be588 is closed by Txport(status = 20e4)
 8-JAN-1990 13:23:58.4 Connection 2be5c0 is closed by Txport(status = 20e4)
 8-JAN-1990 14:36:34.5 Connection 2be5c0 is closed by Txport
 8-JAN-1990 14:37:52.5 Connection 457800 is closed by Txport
 8-JAN-1990 14:38:05.7 Connection 2be588 is closed by Txport(status = 20e4)
 8-JAN-1990 14:38:06.3 Connection 2b98b0 is closed by Txport
 8-JAN-1990 14:38:07.0 Connection 26fa48 is closed by Txport
 8-JAN-1990 15:25:56.3 Connection 460708 is closed by Txport(status = 20e4)
 8-JAN-1990 17:27:34.9 Connection 457c70 is closed by Txport(status = 20e4)
 8-JAN-1990 19:28:04.4 Connection 457c70 is closed by Txport(status = 20e4)
 8-JAN-1990 21:30:01.4 Connection 457c70 is closed by Txport(status = 20e4)
 8-JAN-1990 23:31:39.9 Connection 457c70 is closed by Txport(status = 20e4)
 9-JAN-1990 01:32:09.0 Connection 457c70 is closed by Txport(status = 20e4)
 9-JAN-1990 03:34:05.8 Connection 457c70 is closed by Txport(status = 20e4)
 9-JAN-1990 05:35:44.7 Connection 457c70 is closed by Txport(status = 20e4)
 9-JAN-1990 07:36:13.7 Connection 457c70 is closed by Txport(status = 20e4)
 9-JAN-1990 09:38:11.3 DissociateDMH - bad ref count -1 for header 354b90
 9-JAN-1990 09:38:15.0 Connection 457c70 is closed by Txport(status = 20e4)
 9-JAN-1990 10:00:21.0 %SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=00010001, PC=0014DB1E, PSL=03C00008
Request opcode 53 is ignored due to internal runtime error c for client 1(#error = 1)
Exception Call stack dump follows: 
	8eec5
	14db1e
	14dc73
	202cf
	d60a
	10f5b
	10a91
	12a7f
********** marking the end of call stack dump **********
********************************************************
 9-JAN-1990 10:00:39.7 %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=FB1369C3, PC=0014DB0A, PSL=03C00008
Client 1 has made too many runtime errors(2), its connection is marked for termination
Exception Call stack dump follows: 
	8eec5
	14db0a
	14dc73
	202cf
	d60a
	10f5b
	10a91
	12a7f
********** marking the end of call stack dump **********
********************************************************
 9-JAN-1990 10:00:40.0 ..ddx layer returns bad status(17)
 9-JAN-1990 10:00:40.4 ..Dispatcher close down connection 1
 9-JAN-1990 10:00:44.3 %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000008, PC=00033BE5, PSL=03C00000
Request opcode 63 is ignored due to internal runtime error c for client 2(#error = 1)
Exception Call stack dump follows: 
	8eec5
	33be5
	33bcb
	a581
	132dc6
	1611c2
	2105b
	d60a
	10f5b
	10a91
	12a7f
********** marking the end of call stack dump **********
********************************************************
 9-JAN-1990 10:06:42.6 Connection 457838 is closed by Txport
 9-JAN-1990 10:06:44.1 %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000008, PC=00033BE5, PSL=03C00000
Client 2 has made too many runtime errors(2), its connection is marked for termination
Exception Call stack dump follows: 
	8eec5
	33be5
	33bcb
	a581
	132dc6
	1611c2
	2105b
	d60a
	10f5b
	10a91
	12a7f
********** marking the end of call stack dump **********
********************************************************
 9-JAN-1990 10:06:44.4 ..ddx layer returns bad status(17)
 9-JAN-1990 10:06:44.6 ..Dispatcher close down connection 2
 9-JAN-1990 10:30:20.9 Connection 45e2b8 is closed by Txport
 9-JAN-1990 10:31:37.7 Connection 457800 is closed by Txport
 9-JAN-1990 10:37:56.7 Connection 2be550 is closed by Txport(status = 20e4)
 9-JAN-1990 10:38:00.1 Connection 2bbd00 is closed by Txport(status = 20e4)
 9-JAN-1990 10:38:03.4 Connection 2b9878 is closed by Txport(status = 20e4)
 9-JAN-1990 10:38:07.8 Connection 220e90 is closed by Txport
 9-JAN-1990 10:38:19.4 Client 3 resets the server
  9-JAN-1990 10:38:21.9 mfb$CloseScreen - cannot destroy screen DMD - count 2
 9-JAN-1990 10:38:24.8 Monochrome Frame Buffer support loaded
mfb$InitOutput address=14c600
in logical_name_Value, bad status( 20 ) returned for Logical DECW$MONITOR_DENSITY
 9-JAN-1990 10:38:34.7 Now I call scheduler/dispatcher
 9-JAN-1990 10:38:43.3 Connection 459c70 is closed by Txport
 9-JAN-1990 10:39:03.1 Connection 459ca8 is closed by Txport
 9-JAN-1990 10:41:54.5 Connection 459d18 is closed by Txport
 9-JAN-1990 10:41:55.0 Connection 459ca8 is closed by Txport
 9-JAN-1990 10:41:56.4 Client 3 resets the server
  9-JAN-1990 10:42:00.4 Monochrome Frame Buffer support loaded
mfb$InitOutput address=14c600
in logical_name_Value, bad status( 20 ) returned for Logical DECW$MONITOR_DENSITY
 9-JAN-1990 10:42:06.3 Now I call scheduler/dispatcher
 9-JAN-1990 10:42:23.1 Connection 459c70 is closed by Txport
 9-JAN-1990 10:42:38.8 Connection 459ca8 is closed by Txport
 9-JAN-1990 10:51:04.1 Connection 2be768 is closed by Txport
 9-JAN-1990 10:53:43.2 Connection 2be4e0 is closed by Txport(status = 20e4)
 9-JAN-1990 10:56:08.5 Connection 2be4e0 is closed by Txport
 9-JAN-1990 11:08:26.1 MEMMGR/XREALLOC - zero amount is requested
 9-JAN-1990 11:08:28.0 MEMMGR/XREALLOC - zero amount is requested
 9-JAN-1990 11:08:28.7 MEMMGR/XREALLOC - zero amount is requested
 9-JAN-1990 11:08:41.0 MEMMGR/XREALLOC - zero amount is requested
 9-JAN-1990 11:08:42.1 MEMMGR/XREALLOC - zero amount is requested
 9-JAN-1990 11:08:43.0 MEMMGR/XREALLOC - zero amount is requested
 9-JAN-1990 11:09:02.5 %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=FB1369C3, PC=0014DB0A, PSL=03C00008
Request opcode 53 is ignored due to internal runtime error c for client 10(#error = 1)
Exception Call stack dump follows: 
	8eec5
	14db0a
	14dc73
	202cf
	d60a
	10f5b
	10a91
	12a7f
********** marking the end of call stack dump **********
********************************************************
 9-JAN-1990 11:09:03.1 %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=FB1369C3, PC=0014DD16, PSL=03C00008
Client 10 has made too many runtime errors(2), its connection is marked for termination
Exception Call stack dump follows: 
	8eec5
	14dd16
	14e5b8
	18ca0
	22321
	d60a
	10f5b
	10a91
	12a7f
********** marking the end of call stack dump **********
********************************************************
 9-JAN-1990 11:09:03.4 ..ddx layer returns bad status(17)
 9-JAN-1990 11:09:03.8 ..Dispatcher close down connection 10
 9-JAN-1990 11:11:28.2 %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=FB1369C3, PC=0014DD16, PSL=03C00008
Request opcode 72 is ignored due to internal runtime error c for client 10(#error = 1)
Exception Call stack dump follows: 
	8eec5
	14dd16
	14e589
	18ca0
	22879
	d60a
	10f5b
	10a91
	12a7f
********** marking the end of call stack dump **********
********************************************************
 9-JAN-1990 11:11:28.5 %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=FB1369C3, PC=0014DB0A, PSL=03C00008
Client 10 has made too many runtime errors(2), its connection is marked for termination
Exception Call stack dump follows: 
	8eec5
	14db0a
	14dc73
	202cf
	d60a
	10f5b
	10a91
	12a7f
********** marking the end of call stack dump **********
********************************************************
 9-JAN-1990 11:11:28.9 ..ddx layer returns bad status(17)
 9-JAN-1990 11:11:29.2 ..Dispatcher close down connection 10
 9-JAN-1990 12:40:12.3 %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=FB1369C3, PC=0014DB0A, PSL=03C00008
Request opcode 53 is ignored due to internal runtime error c for client 10(#error = 1)
Exception Call stack dump follows: 
	8eec5
	14db0a
	14dc73
	202cf
	d60a
	10f5b
	10a91
	12a7f
********** marking the end of call stack dump **********
********************************************************
 9-JAN-1990 12:40:12.6 %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=FB1369C3, PC=0014DD16, PSL=03C00008
Client 10 has made too many runtime errors(2), its connection is marked for termination
Exception Call stack dump follows: 
	8eec5
	14dd16
	14e5b8
	18ca0
	22321
	d60a
	10f5b
	10a91
	12a7f
********** marking the end of call stack dump **********
********************************************************
 9-JAN-1990 12:40:12.9 ..ddx layer returns bad status(17)
 9-JAN-1990 12:40:13.2 ..Dispatcher close down connection 10
 9-JAN-1990 12:54:16.9 Connection 2be748 is closed by Txport(status = 20e4)
 9-JAN-1990 13:08:31.5 MEMMGR/XREALLOC - zero amount is requested
 9-JAN-1990 13:08:32.6 MEMMGR/XREALLOC - zero amount is requested
 9-JAN-1990 13:08:33.8 MEMMGR/XREALLOC - zero amount is requested
 9-JAN-1990 13:08:37.7 Server internal runtime error threshold exceeded(code = c)
, server performance may be degraded.
%SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=FB1369C3, PC=0014DB0A, PSL=03C00008
Request opcode 72 is ignored due to internal runtime error c for client 10(#error = 1)
Exception Call stack dump follows: 
	8eec5
	14db0a
	158d9e
	229b7
	d60a
	10f5b
	10a91
	12a7f
********** marking the end of call stack dump **********
********************************************************
 9-JAN-1990 13:08:38.0 %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=FB1369C3, PC=0014DD16, PSL=03C00008
Client 10 has made too many runtime errors(2), its connection is marked for termination
Exception Call stack dump follows: 
	8eec5
	14dd16
	14e5b8
	18ca0
	22321
	d60a
	10f5b
	10a91
	12a7f
********** marking the end of call stack dump **********
********************************************************
 9-JAN-1990 13:08:38.3 ..ddx layer returns bad status(17)
 9-JAN-1990 13:08:38.6 ..Dispatcher close down connection 10
 9-JAN-1990 14:56:18.8 Connection 2be748 is closed by Txport(status = 20e4)
 9-JAN-1990 16:04:52.1 MEMMGR/XREALLOC - zero amount is requested
 9-JAN-1990 16:04:53.2 MEMMGR/XREALLOC - zero amount is requested
 9-JAN-1990 16:04:54.2 MEMMGR/XREALLOC - zero amount is requested
 9-JAN-1990 16:18:44.6 MEMMGR/XREALLOC - zero amount is requested
 9-JAN-1990 16:18:46.2 MEMMGR/XREALLOC - zero amount is requested
 9-JAN-1990 16:18:47.7 MEMMGR/XREALLOC - zero amount is requested
 9-JAN-1990 16:32:01.5 %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=FB1369C3, PC=0014DB0A, PSL=03C00008
Request opcode 53 is ignored due to internal runtime error c for client 1(#error = 1)
Exception Call stack dump follows: 
	8eec5
	14db0a
	14dc73
	202cf
	d60a
	10f5b
	10a91
	12a7f
********** marking the end of call stack dump **********
********************************************************
 9-JAN-1990 16:58:03.7 Connection 2be748 is closed by Txport(status = 20e4)
 9-JAN-1990 18:58:34.8 Connection 2be748 is closed by Txport(status = 20e4)
 9-JAN-1990 21:00:39.8 Connection 2be748 is closed by Txport(status = 20e4)
 9-JAN-1990 23:02:23.3 Connection 2be748 is closed by Txport(status = 20e4)
10-JAN-1990 01:02:53.9 Connection 2be748 is closed by Txport(status = 20e4)
10-JAN-1990 03:04:55.7 Connection 2be748 is closed by Txport(status = 20e4)
10-JAN-1990 05:06:39.4 Connection 2be748 is closed by Txport(status = 20e4)
10-JAN-1990 07:07:10.3 Connection 2be748 is closed by Txport(status = 20e4)
10-JAN-1990 09:09:06.0 Connection 2be748 is closed by Txport(status = 20e4)
10-JAN-1990 10:58:00.9 %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=FB1369C3, PC=0014DD16, PSL=03C00008
Request opcode 72 is ignored due to internal runtime error c for client 10(#error = 1)
Exception Call stack dump follows: 
	8eec5
	14dd16
	14e589
	18ca0
	22879
	d60a
	10f5b
	10a91
	12a7f
********** marking the end of call stack dump **********
********************************************************
10-JAN-1990 10:58:01.7 %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=FB1369C3, PC=0014DB0A, PSL=03C00008
Client 10 has made too many runtime errors(2), its connection is marked for termination
Exception Call stack dump follows: 
	8eec5
	14db0a
	14dc73
	202cf
	d60a
	10f5b
	10a91
	12a7f
********** marking the end of call stack dump **********
********************************************************
10-JAN-1990 10:58:01.9 ..ddx layer returns bad status(17)
10-JAN-1990 10:58:02.2 ..Dispatcher close down connection 10
10-JAN-1990 11:11:17.8 Connection 2be748 is closed by Txport(status = 20e4)
10-JAN-1990 11:35:07.6 Using extra todo packet pool...
10-JAN-1990 11:35:38.8 Connection 2be5c0 is closed by Txport(status = 20e4)
10-JAN-1990 12:40:58.0 %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=FB1369C3, PC=0014DB0A, PSL=03C00008
Request opcode 72 is ignored due to internal runtime error c for client 8(#error = 1)
Exception Call stack dump follows: 
	8eec5
	14db0a
	158d9e
	229b7
	d60a
	10f5b
	10a91
	12a7f
********** marking the end of call stack dump **********
********************************************************
10-JAN-1990 12:40:58.4 Server performance still degrading...
%SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=FB1369C3, PC=0014DD16, PSL=03C00008
Client 8 has made too many runtime errors(2), its connection is marked for termination
Exception Call stack dump follows: 
	8eec5
	14dd16
	14e5b8
	18ca0
	22321
	d60a
	10f5b
	10a91
	12a7f
********** marking the end of call stack dump **********
********************************************************
10-JAN-1990 12:40:58.9 ..ddx layer returns bad status(17)
10-JAN-1990 12:40:59.1 ..Dispatcher close down connection 8
10-JAN-1990 12:41:37.2 Connection 2be550 is closed by Txport(status = 20e4)
10-JAN-1990 12:41:37.5 Txport status = 20e4 ( copy and write) on client 8
10-JAN-1990 12:48:55.6 %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=FB1369C3, PC=0014DB0A, PSL=03C00008
Request opcode 72 is ignored due to internal runtime error c for client 8(#error = 1)
Exception Call stack dump follows: 
	8eec5
	14db0a
	158d9e
	229b7
	d60a
	10f5b
	10a91
	12a7f
********** marking the end of call stack dump **********
********************************************************
10-JAN-1990 12:48:56.9 %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=FB1369C3, PC=0014DD16, PSL=03C00008
Request opcode 72 is ignored due to internal runtime error c for client 12(#error = 1)
Exception Call stack dump follows: 
	8eec5
	14dd16
	14e589
	18ca0
	22879
	d60a
	10f5b
	10a91
	12a7f
********** marking the end of call stack dump **********
********************************************************
10-JAN-1990 12:48:57.2 %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=FB1369C3, PC=0014DB0A, PSL=03C00008
Client 12 has made too many runtime errors(2), its connection is marked for termination
Exception Call stack dump follows: 
	8eec5
	14db0a
	14dc73
	1e979
	24213
	d60a
	10f5b
	10a91
	12a7f
********** marking the end of call stack dump **********
********************************************************
10-JAN-1990 12:48:57.7 ..ddx layer returns bad status(17)
10-JAN-1990 12:48:58.0 ..Dispatcher close down connection 12
10-JAN-1990 12:49:26.7 %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=FB1369C3, PC=0014DB0A, PSL=03C00008

Unrecoverable server internal error(error code = 12) found, terminating all connections.
Exception Call stack dump follows: 
	8eec5
	14db0a
	14dc73
	202cf
	d60a
	10f5b
	10a91
	12a7f
********** marking the end of call stack dump **********
********************************************************
10-JAN-1990 12:49:36.3 Connection 2be588 is closed by Txport(status = 20e4)
10-JAN-1990 12:49:41.3 Server is doing reset or coldstart, new connection is rejected
10-JAN-1990 12:49:42.0 %DECW-I-REFUSED_BY_SERV, server refused connect request
10-JAN-1990 12:49:45.7 
Fatal server bug!
10-JAN-1990 12:49:46.4 Server runtime error limit exceeded - type @SYS$MANAGER:DECW$STARTUP server to restart, or see your system manager.10-JAN-1990 12:49:46.7 
%SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=00000000, PC=00011F25, PSL=03C00004

  Improperly handled condition, image exit forced.

	Signal arguments	      Stack contents

	Number = 00000005		 000089A4
	Name   = 0000000C		 0000000B
		 00000004		 00000000
		 00000000		 7FF972A4
		 00011F25		 00000000
		 03C00004		 200C0000
					 0004B964
					 7FF972B0
					 0002C217
					 00000001

	Register dump

	R0 = 00000000  R1 = 8026C080  R2 = 0002D088  R3 = 0004A5B0
	R4 = 0004DB64  R5 = 00009B3C  R6 = 00007C30  R7 = 0004A5B0
	R8 = 00008F14  R9 = 00009120  R10= 00000001  R11= 000089A4
	AP = 7FF9722C  FP = 7FF971EC  SP = 7FF97268  PC = 00011F25
	PSL= 03C00004
2010.6Please QAR thisSTAR::VATNEPeter Vatne, VMS DevelopmentWed Jan 10 1990 14:384
Anytime the server ACCVIOs, it is an automatic candidate for a QAR.
(This also goes for system crashers.)

Thank you.
2010.7abort STAR::CYPRYCHWed Jan 10 1990 16:184
    The fatal x i/o error in the window manager log
    is usually due to an abort request from the server,
    probably when it accviod.