Conference vaxaxp::vmsnotes

435.0. "XQPERR, Error detected by file system XQP" by FORAT::PONS () Tue Apr 08 1997 14:07

	Hy,

	One important customer in Spain have a serious problem 
	with two different systems:

	- Alphaserver 8400 EV56/440
	  OpenVMS 6.2-1H3  FRONT1	
	
	- 7000-720
	  OpenVMS V6.1     FACTU2

	Since yesterday every time that from any of two systems start a
	BACKUP,to tape or disk, the system crash with the next crash:

	FRONT1:

	Module:            F11BXQP
	Offset:            00001AB8
	Always the same but with different process and image.

	FACTU2:

	Module:            F11BXQP
	Offset:            00001AC8
	Always the same but with different process and image.

	The two systems are standalone systems, and two systems have the
	next ECO installed:

	FRONT1:

ALPCLIU01_062.RELEASE_NOTES;1           ALPF11X03_070.RELEASE_NOTES;1
ALPHA_UCX033.RELEASE_NOTES;1            ALPMANA01_062.RELEASE_NOTES;1
ALPMANA02_070.RELEASE_NOTES;1           ALPMOTF07_U3012.RELEASE_NOTES;1
ALPRMS02_062.RELEASE_NOTES;1            ALPSCSI02_070.RELEASE_NOTES;1
ALPSCSI03_062.RELEASE_NOTES;1           ALPSMUP01_070.RELEASE_NOTES;1
ALPSYS02_062.RELEASE_NOTES;1            ALPSYS08_070.RELEASE_NOTES;2
ALPVERI01_071.RELEASE_NOTES;1           AMDS062.RELEASE_NOTES;1
AXPSCSI01_062.RELEASE_NOTES;1           AXPVMSU1H3_062.RELEASE_NOTES;1
CC050.RELEASE_NOTES;1                   DCPS012.RELEASE_NOTES;1
DECNET_OSI-V6_3.RELEASE_NOTES;1         DECW$MOTIFU3012.RELEASE_NOTES;1
HSZTERM010.RELEASE_NOTES;1              OSCINT021.RELEASE_NOTES;1
OSIF$032.RELEASE_NOTES;1                PATROL030.RELEASE_NOTES;1
PSDC022.RELEASE_NOTES;1                 SNALU62022.RELEASE_NOTES;1
SNATE015.RELEASE_NOTES;1                SNS_ECO01022.RELEASE_NOTES;2
TNT010.RELEASE_NOTES;1                  UCX041.RELEASE_NOTES;1
UCXECO3-041.RELEASE_NOTES;1             UCXECO4-033.RELEASE_NOTES;2
UCXECO5-041.RELEASE_NOTES;1


	FACTU2:

ALPBACK01_061.RELEASE_NOTES;1           ALPCLIU01_062.RELEASE_NOTES;1
ALPF11X03_070.RELEASE_NOTES;1           ALPHA_UCX033.RELEASE_NOTES;1
ALPLAVC01_062.RELEASE_NOTES;1           ALPMANA01_070.RELEASE_NOTES;1
ALPMANA02_070.RELEASE_NOTES;2           ALPRMS03_061.RELEASE_NOTES;2
ALPSYS08_070.RELEASE_NOTES;1            ALPSYS11_061.RELEASE_NOTES;1
ALPVERI01_071.RELEASE_NOTES;1           CC052.RELEASE_NOTES;1
DCPS012.RELEASE_NOTES;1                 DECNET_OSI-V6_2.RELEASE_NOTES;1
LPS050.RELEASE_NOTES;1                  LPS051.RELEASE_NOTES;2
OSCINT021.RELEASE_NOTES;1               PATROL030.RELEASE_NOTES;1
PSDC022.RELEASE_NOTES;1                 SNS_ECO01022.RELEASE_NOTES;1
UCXECO4-033.RELEASE_NOTES;2

	The last ECO  about F11 was installed, I hope,

	I'm waiting for a SYSDUMP.DMP file to escalate the situation, but
	in the waiting time, any suggestion!!!!!!

	Thanks in advance

	Jordi
	MCS SPAIN
    
    
    	Crossposted  Alphanotes #78

    SDA>eva/con @r0
    %SYSTEM-W-ILLEGAL_SHADOW, illegal formed trap shadow, Imask=!XL,
    Fmask=!XL, summary=!XB, PC=!XL, PS=!XL
    
    The warning message user action said, Recompile the program to enable
    software completion, but the command that force a crash is a simple
    backup/ver/ignore=interlock disk:[000000...]
    disk:[bck]saveset_name.bck/save
    
    Thanks
    Jordi

    Best suggestion is to Raise a IMPT if you need formal help...

    OBTW, Looking at R0 for a XQPERR isn't likely to help much.  Try
    Canasta/...

   Get the CLUE output from the crashdump, (as mentioned previously)
   e-mail it to the CANASTA e-mail server (see 233.* for more details
   here), and if the CANASTA server does not return anything useful
   on the problem, get the IPMT started.