Re: RX2600 hangs (VMS 8.3) - VMS

This is a discussion on Re: RX2600 hangs (VMS 8.3) - VMS ; In article , Malcolm Dunnett writes: > > >I have an rx2600 (dual 1.4GHz/1.5MB CPUs) which has been happily running >VMS for several years. It's at 8.3 with VMS83I_UPDATE4 and VMS83I_SYS4 >(along with a few other) patches installed. It's running ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: Re: RX2600 hangs (VMS 8.3)

  1. Re: RX2600 hangs (VMS 8.3)

    In article <47583595$1@flight>, Malcolm Dunnett writes:
    >
    >
    >I have an rx2600 (dual 1.4GHz/1.5MB CPUs) which has been happily running
    >VMS for several years. It's at 8.3 with VMS83I_UPDATE4 and VMS83I_SYS4
    >(along with a few other) patches installed. It's running Oracle 10.2.0.2
    >server as its only application.
    >
    >This morning at around 4am it "stopped cold". No crash dump, no errors
    >in the system error log, nothing untoward in the OPERATOR log, no error
    >messages on the console. The other cluster nodes simply report losing
    >communication to it at that time.
    >
    >Unfortunately in the heat of the moment to get it going again this
    >morning I didn't get a chance to take a crash dump (I will if the
    >problem occurs again.) I did note the following errors in the BMC error
    >log that happened at the time of the hang:
    >
    >576 SFW 0 2 0x5680028500E02630 0000000000000000 MC_INITIALIZED_RSE
    > 06 Dec 2007 04:13:10
    >577 SFW *7 0xC1475776D6022650 003FA17000130300 Type-02 137001 1273857
    > 06 Dec 2007 04:13:10
    >578 SFW 0 *7 0xF680009800E02660 000000000000000B MC_INITIATED
    > 06 Dec 2007 04:13:10
    >579 SFW 0 2 0x568002A100E02680 08000000FFF61020 MC_PSP
    > 06 Dec 2007 04:13:11
    >580 SFW 0 2 0x5680010900E026A0 0000000000000000 PAL_CORRECTED_MC
    > 06 Dec 2007 04:13:11
    >581 SFW 0 2 0x568002B000E026C0 2007120600041313 MC_TIMESTAMP
    > 06 Dec 2007 04:13:11
    >582 SFW 0 2 0x568002A000E026E0 0000000000000000 MC_POST_PROCESS_PLAT
    > 06 Dec 2007 04:13:11
    >583 SFW 0 *7 0x7680011700E02700 0000000000000000
    >UNEXPECTED_RET_TO_SAL_CHECK
    > 06 Dec 2007 04:13:11
    >
    >do these provide any clue as to what the problem might be?
    >
    >ps I already have a call open through ITRC - but I have a feeling
    >there's folks in this group who know a lot more than ITRC does.


    Go to the CM menu and type RB ( this is the command to clear buffers).
    If this fills, I've found that my rx2600 seizes up too. My morning
    ritual is not to clear these buffers (CM=>RB) as well as the SL logs
    available from the main menu.

    Nothing like having a robust OS that can stay up and running years at
    a time to be taken down because of a console log filling.

    Not sure that this is *your* problem but it is one I have observed
    since having my box.

    --
    VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM

    "Well my son, life is like a beanstalk, isn't it?"

    http://tmesis.com/drat.html

  2. Re: RX2600 hangs (VMS 8.3)

    In article , VAXman- @SendSpamHere.ORG
    wrote:

    > In article <47583595$1@flight>, Malcolm Dunnett
    > writes:
    > >
    > >
    > >I have an rx2600 (dual 1.4GHz/1.5MB CPUs) which has been happily running
    > >VMS for several years. It's at 8.3 with VMS83I_UPDATE4 and VMS83I_SYS4
    > >(along with a few other) patches installed. It's running Oracle 10.2.0.2
    > >server as its only application.
    > >
    > >This morning at around 4am it "stopped cold". No crash dump, no errors
    > >in the system error log, nothing untoward in the OPERATOR log, no error
    > >messages on the console. The other cluster nodes simply report losing
    > >communication to it at that time.
    > >
    > >Unfortunately in the heat of the moment to get it going again this
    > >morning I didn't get a chance to take a crash dump (I will if the
    > >problem occurs again.) I did note the following errors in the BMC error
    > >log that happened at the time of the hang:
    > >
    > >576 SFW 0 2 0x5680028500E02630 0000000000000000 MC_INITIALIZED_RSE
    > > 06 Dec 2007 04:13:10
    > >577 SFW *7 0xC1475776D6022650 003FA17000130300 Type-02 137001 1273857
    > > 06 Dec 2007 04:13:10
    > >578 SFW 0 *7 0xF680009800E02660 000000000000000B MC_INITIATED
    > > 06 Dec 2007 04:13:10
    > >579 SFW 0 2 0x568002A100E02680 08000000FFF61020 MC_PSP
    > > 06 Dec 2007 04:13:11
    > >580 SFW 0 2 0x5680010900E026A0 0000000000000000 PAL_CORRECTED_MC
    > > 06 Dec 2007 04:13:11
    > >581 SFW 0 2 0x568002B000E026C0 2007120600041313 MC_TIMESTAMP
    > > 06 Dec 2007 04:13:11
    > >582 SFW 0 2 0x568002A000E026E0 0000000000000000 MC_POST_PROCESS_PLAT
    > > 06 Dec 2007 04:13:11
    > >583 SFW 0 *7 0x7680011700E02700 0000000000000000
    > >UNEXPECTED_RET_TO_SAL_CHECK
    > > 06 Dec 2007 04:13:11
    > >
    > >do these provide any clue as to what the problem might be?
    > >
    > >ps I already have a call open through ITRC - but I have a feeling
    > >there's folks in this group who know a lot more than ITRC does.

    >
    > Go to the CM menu and type RB ( this is the command to clear buffers).
    > If this fills, I've found that my rx2600 seizes up too. My morning
    > ritual is not to clear these buffers (CM=>RB) as well as the SL logs
    > available from the main menu.


    This isn't very good advice, at least in the present context.

    VMS won't stop working if the hardware error logs are full. The worst
    symptom I know of is a "stop boot" condition (which prevents autoboot,
    but not manual boot) if the SEL is full. VMS tries to prevent the SEL
    from filling up, if you don't go out of your way to stop it. We only
    see filled SELs occasionally, and usually on systems that are routinely
    crashed just after boot, so VMS doesn't have time to maintain the SEL.

    In this case, if Malcolm clears all the logs, the HP service folks are
    likely to have nothing to help them diagnose the problem. Then the only
    thing is to wait for it to happen again.

    > Nothing like having a robust OS that can stay up and running years at
    > a time to be taken down because of a console log filling.


    VMS isn't taken down by filled-up logs. Look for another explanation if
    you're having crashes.


    > Not sure that this is *your* problem but it is one I have observed
    > since having my box.


  3. Re: RX2600 hangs (VMS 8.3)

    In article , Robert Deininger writes:
    >
    >
    >In article , VAXman- @SendSpamHere.ORG
    >wrote:
    >
    >> In article <47583595$1@flight>, Malcolm Dunnett
    >> writes:
    >> >
    >> >
    >> >I have an rx2600 (dual 1.4GHz/1.5MB CPUs) which has been happily running
    >> >VMS for several years. It's at 8.3 with VMS83I_UPDATE4 and VMS83I_SYS4
    >> >(along with a few other) patches installed. It's running Oracle 10.2.0.2
    >> >server as its only application.
    >> >
    >> >This morning at around 4am it "stopped cold". No crash dump, no errors
    >> >in the system error log, nothing untoward in the OPERATOR log, no error
    >> >messages on the console. The other cluster nodes simply report losing
    >> >communication to it at that time.
    >> >
    >> >Unfortunately in the heat of the moment to get it going again this
    >> >morning I didn't get a chance to take a crash dump (I will if the
    >> >problem occurs again.) I did note the following errors in the BMC error
    >> >log that happened at the time of the hang:
    >> >
    >> >576 SFW 0 2 0x5680028500E02630 0000000000000000 MC_INITIALIZED_RSE
    >> > 06 Dec 2007 04:13:10
    >> >577 SFW *7 0xC1475776D6022650 003FA17000130300 Type-02 137001 1273857
    >> > 06 Dec 2007 04:13:10
    >> >578 SFW 0 *7 0xF680009800E02660 000000000000000B MC_INITIATED
    >> > 06 Dec 2007 04:13:10
    >> >579 SFW 0 2 0x568002A100E02680 08000000FFF61020 MC_PSP
    >> > 06 Dec 2007 04:13:11
    >> >580 SFW 0 2 0x5680010900E026A0 0000000000000000 PAL_CORRECTED_MC
    >> > 06 Dec 2007 04:13:11
    >> >581 SFW 0 2 0x568002B000E026C0 2007120600041313 MC_TIMESTAMP
    >> > 06 Dec 2007 04:13:11
    >> >582 SFW 0 2 0x568002A000E026E0 0000000000000000 MC_POST_PROCESS_PLAT
    >> > 06 Dec 2007 04:13:11
    >> >583 SFW 0 *7 0x7680011700E02700 0000000000000000
    >> >UNEXPECTED_RET_TO_SAL_CHECK
    >> > 06 Dec 2007 04:13:11
    >> >
    >> >do these provide any clue as to what the problem might be?
    >> >
    >> >ps I already have a call open through ITRC - but I have a feeling
    >> >there's folks in this group who know a lot more than ITRC does.

    >>
    >> Go to the CM menu and type RB ( this is the command to clear buffers).
    >> If this fills, I've found that my rx2600 seizes up too. My morning
    >> ritual is not to clear these buffers (CM=>RB) as well as the SL logs
    >> available from the main menu.

    >
    >This isn't very good advice, at least in the present context.
    >
    >VMS won't stop working if the hardware error logs are full. The worst
    >symptom I know of is a "stop boot" condition (which prevents autoboot,
    >but not manual boot) if the SEL is full. VMS tries to prevent the SEL
    >from filling up, if you don't go out of your way to stop it. We only
    >see filled SELs occasionally, and usually on systems that are routinely
    >crashed just after boot, so VMS doesn't have time to maintain the SEL.
    >
    >In this case, if Malcolm clears all the logs, the HP service folks are
    >likely to have nothing to help them diagnose the problem. Then the only
    >thing is to wait for it to happen again.
    >
    >> Nothing like having a robust OS that can stay up and running years at
    >> a time to be taken down because of a console log filling.

    >
    >VMS isn't taken down by filled-up logs. Look for another explanation if
    >you're having crashes.


    Well, I crash mine routinely when working on kernel code. I can get the
    bugger to reboot unless I clear out these logs.

    --
    VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)COM

    "Well my son, life is like a beanstalk, isn't it?"

    http://tmesis.com/drat.html

+ Reply to Thread