| Title: | VAX and Alpha VMS |
| Notice: | This is a new VMSnotes, please read note 2.1 |
| Moderator: | VAXAXP::BERNARDO |
| Created: | Wed Jan 22 1997 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 703 |
| Total number of notes: | 3722 |
Hi all, i have recently began to analyze a problem with a A1000 with 64 MB and running vms v6.2; the machine crashed lots of times a day and according to the "Machine Check Decoder" program there was a problem with the cpu daughter card. The daughter card was replaced and also the power supply due to some electrical problems, but the problem persisted. Then the motherboard was replaced and still the problem continued to happen. On the next day the motherboard was replaced again, because the problem was different from the first one; also with the memory SIMMs. After these replacements the machine seemed ok. It worked for 2 to 3 days without giving any problems. During the weekend the machine crashed again with a similar error than the first one reported. I tried to analyze it again through the machinecheck decoder and noticed that this program is stating that the machine has 128Mb of memory althought it has only 64 Mb. According to the registers on DECevent the Bank 0 and Bank 1 return the same code althought the bank0 is the only one with simms: coma_base0 6d8d0000 coma_base1 6d8d0000 coma_base2 6d8d0000 coma_base3 80000000 coma_cnfg0 6d8d0049 coma_cnfg1 6d8d0049 coma_cnfg2 47ff0000 coma_cnfg3 80000000 The result of the machinecheck decoder is to replace the daughter card, but i think that this problem can influence this result. Thanks, NElsonR.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 560.1 | AlphaServer 1000 Notes Conference: WRKSYS::MIKASA | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Mon May 05 1997 10:09 | 12 |
"A1000"? I'll assume that's an AlphaServer 1000, also known as a "Mikasa" system. Check the PALcode version, making sure that it is up to date for the OpenVMS Alpha release. Check for any previous reports of any similar problems in the WRKSYS::MIKASA notes conference -- there are a numbner of various machine checks and machine check codes. Check for a correct configuration of SIMMs in the memory slots and for valid SIMM types and known/tested manufacturers. Then check for any weird device drivers or site-specific kernel code -- kernel code can also cause machine checks. And then report this through formal channels via an IPMT. | |||||
| 560.2 | AUSS::GARSON | DECcharity Program Office | Mon May 05 1997 19:54 | 12 | |
re .0
>noticed that this program is stating that the machine has 128Mb of memory
>althought it has only 64 Mb.
Maybe the machine is trying to tell you something. (-: Even the poxy PC on
my desk has 48MB.
But seriously, verify that the memory has been installed correctly and
that the rules regarding combination of SIMMS have been followed. The
machine specific conference would be a better place to find out what
those rules are if you don't have the manual that came with the machine.
| |||||