[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

7258.0. "System hang - "pmap_begin_shared_region timeout"" by HGOVC::SIUKEUNGLEE () Mon Sep 30 1996 13:34

T.RTitleUserPersonal
Name
DateLines
7258.1Re: System hang - "pmap_begin_shared_region timeout"QUABBI::"[email protected]"Shashi MangalatThu Oct 03 1996 11:4415
7258.2Can we skip the shared memory alignment tuning?NETRIX::"[email protected]"Feynman LoFri Oct 04 1996 03:1322
7258.3same panic on 4100/Dunix 4.0A/SybasePRMS00::COLEMon Jan 27 1997 09:5917
    I have the same crash on a 4100 system running DUnix 4.0A.
    (_pmap_begin_shared_region timeout)
    
    System has 1.0 GB memory and 2 CPU's and is running Sybase 11.
    
    
    Crash dump has been sent to support.
    
    Any progress on this ??
    
    thanks,
    
    	
    larry cole
    Email:	[email protected]    or   [email protected]
    
    
7258.4SMURF::MANGALATTue Jan 28 1997 16:399
>Any progress on this ??

If you are asking about the problem in the previous notes, it looked like a
hardware problem.  It didn't look like it had anything to do with shared
memory.

Without seeing the crash dump, it is hard to say what caused your crash.

--shashi
7258.5no indication of any hardware errorsPRMS00::COLEWed Jan 29 1997 15:4416
    Wes Trainer ([email protected]) at the Atlanta CSC has the
    crash dump.
    
    No crashes since this one (Jan 10), but customer is complaining
    about corrupted data in Sybase.  No hardware errors found in
    system error log.
    
    We will shut system down to console mode and run memory/processor
    diagnostics.  Any other suggestions ?  Would it make sense to
    disable one of the CPUs ?
    
    Thanks,
    
    larry cole
    [email protected]