[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

456.0. "P00>>> show device?" by QBUS::E_BURKHALTER () Fri Jan 31 1997 16:04

    
    A customer has a AlphaServer 4100 5/300 with SRM 3.0-10.
    
    The following commands work fine:
    P00>>>show fru 
    P00>>>show config
    
    This command doesn't show any data.
    P00>>>show device
    Doesn't show any devices or ewa0 address
    
    These commands were done after POST and before a boot.
    
    Any ideas why this doesn't work?
    
    Ed Burkhalter
    CSC Atlanta
T.RTitleUserPersonal
Name		DateLines
456.1show device hangs consoleCSC32::HUTMACHERFri Jan 31 1997 16:5520
    Hi Ed
    
    think this may be related to blitx in note 93.32 and i would
    follow those instructions. enven though it doesnt mention the
    show and set hanging i have heard of it doing this.
    When this problem occurs any console command like "set", "ls", "show"
    the console comes back with "string loo long" message at the screen
    followed by a console hang.
    
    so
    
      To erase the SRM's NVRAM, type the following at console:
    
          P00>>> d eerom:1800 -b -n 7ff 0
    
      Then cycle reset and reset any preferred environment variables.
    
    jim hutmacher mvhs colorado csc 800-354-9000 ext 25561
456.2P00>>> show device? CSC32::HUTMACHERFri Jan 31 1997 17:096
    opps Ed i did not read your problem description well enough.
    not sure anymore that this could cause >>>show device not 
    to report any devices and not hang console.
    
    jim hutmacher mvhs colorado csc
456.3Not a problem. Expected behavior.LANDO::CUMMINSFri Jan 31 1997 18:1136
    Re: .0
    
    This is not related to Blitz 93.32.
    
    My assumption is that the customer had run TEST or SET MODE DIAGNOSTIC
    prior to typing SHOW DEVICE.
    
    All console versions prior to V4.8 (soon to be available) leave the
    console in diagnostic mode following TEST command execution. V4.8
    console changes this behavior such that console is restored to normal
    mode following completion of the TEST command.
    
    SHOW DEVICE behaves differently when in diag mode versus normal mode.
    In diag mode, it only displays devices that have been config'd after a
    console (diag mode) CONFIG [-N] command. The CONFIG [-N] command says
    load and start device drivers specified and leave them running. SHOW
    DEVICE in normal mode starts up the device drivers and then shuts them
    down after use.
    
    The reason for this difference in behavior is that in normal mode (e.g.
    capable of booting an operating system), console runs with a reduced
    memory heap. In diagnostic mode, we more or less expand our memory heap
    so we can run all device drivers at once, have lots of devices open,
    run diagnostic with large DMA buffers, etc.
    
    Without getting into too much more detail, suffice it to say that if my
    assumption is correct about the customer doing SHOW DEVICE after TEST,
    then the firmware is behaving as expected (since TEST shuts down all
    drivers upon completion). V4.8-3 console will implement a change over
    past console behavior in that it will restore mode to normal mode. This
    will tell SHOW DEVICE to re-size the I/O buses and devices should be
    seen. In diagnostic mode, SHOW DEVICE only displays configured devices
    (i.e. via the CONFIG command).
    
    Hope this helps,
    BC