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

Conference turris::digital_unix

Title:DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:Welcome to the Digital UNIX Conference
Moderator:SMURF::DENHAM
Created:Thu Mar 16 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:10068
Total number of notes:35879

9827.0. "DU 3.2D crash: invalid memory write " by MAIL2::YATES () Thu May 15 1997 07:01

	My customer has a 2100 running Digital UNIX 3.2d.

	When they try to bring up thier application (SAP) the system
	crashes.  The database (ORACLE) comes up ok, but the application
	crashes the system.  It was fine yesterday.

	The error they are getting is 

	trap: invalid memory write access from kernal mode
	Faulting virtual address: 0x00000000000000000

	can someone give me a clue whats going on here?


	- a side note that i just learned is that they have 2 fddi
	  controllers configured in the kernal but only 1 fddi card
	  in the 2100.	The second card has been out for a while
	  (what ever that is).
T.RTitleUserPersonal
Name
DateLines
9827.1advfs patchesMAIL2::YATESThu May 15 1997 10:558
    
    	i am told that we need to apply 2 advfs patches by support.
    
    	we are in the process of pulling the patches down now
    
    	ill let you know.
    
    	tom
9827.2pls use CANASTA Mail ServerHAN::HALLEVolker Halle MCS @HAO DTN 863-5216Fri May 16 1997 02:4215
    Tom,
    
    could you please send the crash-data file to the CANASTA Mail Server.
    Please use the following mail command (this will point anyone with the
    SAME CRASH FOOTPRINT to this note, if they use CANASTA):
    
    # Mail -s "DIAGNOSE CASE=DUNIX_9827 Customer=notes_on_turris" 
    		[email protected] < crash-data.n
    
    Please also specify the installed patches and whether they solved your
    customer's problem as a reply to this note.
    
    Volker.
    
    PS: regarding CANASTA, please read note 8919
9827.3did we hit a high water mark?MAIL2::YATESWed May 21 1997 12:1211
    
    
    	My customer has asked me why this happened now.
    
    	They have been running this operating system for months
    	and never saw this problem.
    
    	Did we hit some high water mark?
    
    
    	tom