To clear up any confusion I want to correct some typos:
We originally had 7 GIGAbytes, not MEGAbytes. We added in 16 Gigabytes,
and removed 1 Gigabyte from the original set. Now the ES40 has 22
Gigabytes of memory. It also has 20 Gigs of swap space.
Sorry about my constant errors.
Kevin
> We are having serious problems here, so I'm asking for help. Almost two
> weeks ago, we planned to upgrade our ES40 (Tru64 4.0f) by adding 16
> megabytes of RAM and changing the single 500 Mhz CPU (EV6) to dual 667
> Mhz (EV67). After upgrading the firmware to 5.9 (from v.5.7) level
> which was included on CD with the CPUs, we discovered that our
> motherboard did not satisfy the minimum Revision E0* specified by the
> installation guide. Disappointed but not deterred, we finished by
>
> ...putting in the 16 Megs of memory. It originally had 7 megabytes of
> memory, and we arranged it by pulling out four 256M sticks and leaving
> in twelve 512M sticks, then adding in sixteen 1024M sticks for a total
> of 22 Gigabytes of memory (I hope that make sense, I can get the array
> arrangement if someone needs it).
>
> Well after that, we have had constant crash/reboots. Over five this
> weekend alone. uerf -R now seems like it's broken, it ends with "Error
> reading syserr file". I'm not even sure how to fix that now. The
> crash-dump file seems to report "Processor Machine Check" on the
> _Panic_string.
>
> I was told that one of the work jobs has a possible memory leak and is
> using up all 22 megs of memory, plus 20 Gigs swap space. But the
> machine even crashes on idle a couple of times.
>
> I don't want to attach the crash-dump file, and force everyone to read
> it. But if someone is willing to look, I'll send it.
>
> I'm not sure where to begin to isolate the problem. Could it be bad
> memory? I will run memx in a little bit. Could it be the firmware
> upgrade that we did? Could it be some user's process using up all the
> memory and crashing the machine? Is the unusual mix of 512Meg and 1G
> memory causing unstability? We are also fearing static electricity
> damage on some hardware.
>
> If I'm not providing enough information and someone is willing to help,
> I'll be happy to provide some answers.
--
Kevin Dea
UNIX System Administrator
Alpine Electronics Research of America
Received on Mon Jun 25 2001 - 20:10:37 NZST