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

Conference mvblab::alphaserver_4100

Title:AlphaServer 4100
Moderator:MOVMON::DAVISS
Created:Tue Apr 16 1996
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:648
Total number of notes:3158

546.0. "V3.8 bug ???" by SWAM1::SUKOVICH_RO () Tue Mar 25 1997 19:54

    Hello;
    
    I just spoke briefly with an engineer who has experienced the
    following. Sorry for the lack of detail but only this much is
    available at present.
    
    AS4000 running Digital Unix 4.0A or 4.0B. Default console version
    from the 3.8 CD: The system panics.
    		     Memory Error/Invalid read error.
    
    Same machine running Unix 4.0A or 4.0B. Default console version
    form the 3.7 CD: Works fine.
    
    I will prod this fellow for all the details but I just wanted to see
    if anyone had seen anything similar. All I'm aware of on the 3.8 CD
    is the V8 CIXCD bug.
    
    Regards;
    
    Bob Sukovich
T.RTitleUserPersonal
Name
DateLines
546.1HARMNY::CUMMINSWed Mar 26 1997 10:1124
    Not sure what the CIXCD issue you're referring to is about (CIXCD is an
    XMI-CI adapter and only supported on the 7000 and 8200/8400 platforms.
    
    It sounds like the customer has run into a problem which has been
    described elsewhere in this notes conference in detail. That is, the
    MEMORY_TEST EV must be set to FULL until UNIX resolves an issue with
    partially-tested memory on 4100/4000. 
    
    Here's a snippet from the V3.8 CD's V3.0-10 SRM console readme file:
    
      Mark untested memory pages (memory_test=partial/none) as untested
      rather than good in bitmaps passed to Digital UNIX (and OpenVMS,
      even though not yet supported). Note: see UNIX release notes for
      list of UNIX versions and/or patches which support partial memory
      test.
    
    The above change as of V3.0-10 (per request of UNIX) exposed an as of
    yet unidentified bug in the UNIX VM code. The bug was only found after
    V3.0-10 shipped and occurs only on certain memory configurations. No
    version of UNIX today supports MEMORY_TEST < FULL.
    
    Let us know whether MEMORY_TEST was the problem on this machine.
    
    BC