[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | laser | 
|  | 
| Moderator: | PROXY::ALLEN | 
|  | 
| Created: | Thu Jul 16 1992 | 
| Last Modified: | Wed May 28 1997 | 
| Last Successful Update: | Fri Jun 06 1997 | 
| Number of topics: | 1267 | 
| Total number of notes: | 4891 | 
1265.0. "DUMP can't be taken/VAX7620/V5.52" by TKTVFS::HAMADA_T (Tsuyoshi Hamada, TECM/CSC/MCS in Japan) Thu May 15 1997 03:57
We have experienced the crash twice in a month with ASYNCWRTER/SYSLOA+0000A3F3 
in VAX7620/VMS V5.52.
However, crash dump CAN'T BE TAKEN. Forced crash dump can be taken normally.
When VAX7620/V5.52 crashed with MACHINECHK or ASYNCWRTER(ECC err in B-CACHE),
why can't crash dump be tabken ?  
Any suggestion will be highly appreciated.
Best regards and thanks,
Tsuyoshi.
Flow:	[1] INT 60 : LMERR-> 00000180 	B-CACHE DATA SINGLE BIT ERROR
					B-CACHE DATA DOUBLE BIT ERROR
	[2] ASYNCWRTER BUGCHECK
	    PC: SYSLOA + 0000A3F3 ( From ERROR LOG )
ENVIRONMENT:
	VAX7620/VMS V5.52	 
	SYSLOA Image is listed below.(VAXSYSL18_U2055)
        Image Identification Information
                image name: "SYSLOA1701"
                image file identification: "X-35"
                link date/time: 11-OCT-1994 19:24:35.84
                linker identification: "05-13"
	Error writing 127 block(s), starting at VBN 971524 - status = 00001D48
		:                                                     ^^^^^^^^
		:
	**** Error reporting suppressed, memory dump continuing...
	**** Memory dump written, although 608 ERROR(S)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|