1. This forum section is a read-only archive which contains old newsgroup posts. If you wish to post a query, please do so in one of our main forum sections (here). This way you will get a faster, better response from the members on Motherboard Point.

SunFire 280R issue

Discussion in 'Sun Hardware' started by Yannick ROGER, Sep 18, 2007.

  1. After updating OBP to 4.16.4, i'm facing the following issue:

    Sun Fire 280R (2 X UltraSPARC-III+) , No Keyboard
    Copyright 1998-2004 Sun Microsystems, Inc. All rights reserved.
    OpenBoot 4.16.4, 8192 MB memory installed, Serial #53288557.
    Ethernet address 0:3:ba:2d:1e:6d, Host ID: 832d1e6d.

    Boot device: disk File and args:
    SunOS Release 5.10 Version Generic_125100-10 64-bit
    Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    Hostname: recette-chu
    SUNW,eri0 : 100 Mbps half duplex link up
    checking ufs filesystems
    /dev/md/rdsk/d37: is logging.

    recette-chu console login: Sep 18 13:54:54 recette-chu eri: SUNW,eri0 : No
    response from Ethernet network : Link down -- cable problem?
    Sep 18 13:54:59 recette-chu eri: SUNW,eri0 : 100 Mbps full duplex link up
    Fatal Error reported by: (PCI-PBM)

    Any idea?


    Yannick ROGER, Sep 18, 2007
    1. Advertisements

  2. Yannick ROGER

    Trinean Guest

    I doubt the new firmware broke you, but may be better at catching problems
    undetected by the old firmware.
    Do you have access to a system you can connect via NULL modem to TTYA on the
    Sun Fire 280R
    or do you use the RSC for this already?

    If so then try setting diag-level to max and turn the machine off via the
    Then turn it back on with the key in the diag-position.

    You may get lucky and have something called out like a CPU.

    Otherwise you may need to remove CPU1 and run diags with just CPU0
    If it fails remove CPU0 and install CPU1 in the CPU0 slot and try again.

    If it doesn't fail, then CPU1 was probably bad, but still swap it in for
    CPU0 just to see if it then fails.

    Should it fail with either CPU by itself in the CPU0 position, then the
    system board could be the problem afterall.
    Or you could get lucky and just reseating the CPUs and torqueing them
    correctly could make the problem vanish.

    Good luck!
    Trinean, Sep 18, 2007
    1. Advertisements

  3. Yannick ROGER

    Guest Guest

    No, I haven't access anymore to the system.
    It cycle on:
    Fatal Error reported by: (PCI-PBM)

    I try putting off some componements (as you suggest CPU but RAM too...)

    Thanks for your reply,


    Guest, Sep 18, 2007
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.