Machine Check Logout Frame Error Code
If you mix 16 and 64 MB kits, you have to put the big ones in first. - Hide quoted text -- Show quoted text -> -- > Robert Deininger You're also getting the address of the stack frame, so you could look at the whole thing if you feel brave enough. Once again, I wish someone could take a peek in the service manual and tell us what's going on here. -- Robert Deininger Top dec 3000 300 crashing Quote:> I conclude that the model 300 does not correctly implement whatever LLSC is trying to check. http://threadspodcast.com/machine-check/machine-check-error.html
The POST is real smart > If I'm wrong, beat me with a bent floppy. (got scars from being wrong) Top dec 3000 300 crashing by Paul Repachol » Sun, 14 Jan 2001 13:32:07 TEST MEM ? West Australia 6076 Raw, Cooked or Well-done, it's all half baked. https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.1.0/com.ibm.zos.v2r1.ifc2000/prtmcha.htm
If the machine survives long enough, they are later written to ERRLOG.SYS by ERRFMT. It will come tonight, as I have no access to my network at the moment.IIRC, the log told about machinechecks codes 630 and 660, last is a bugcheck entry. The table is too long to type. -- Robert Deininger Top dec 3000 300 crashing by Paul Repachol » Wed, 17 Jan 2001 01:37:42 > > test mem
Maybe it's wiggled a bit loose? SYMPTOM:System fails with power related symptoms. If you change DIAG_SECTION to 2, you get still more extensive tests, and a little more information. I didn't have a way to log the console on this machine, so I just jotted down some of the errors: stl_c bcache miss with victim at ...
Quote:> test mem addr > STS-MEM-OK > test mem ecc > T_ERR_MEM - ldl_l bcache miss no victim ad Addr: 00200264 > Uncorrected error count = 1 > Quote:> Maybe the problem is not the memory, but rather some external memory circuit. > From the hardware reference guide: > Memory subtests are > test mem cell detecs The T MEM LLSC test always fails! http://community.hpe.com/hpeb/attachments/hpeb/itrc-292/115/1/41528.txt Provide feedback Please rate the information on this page to help us improve our content.
For a workstation, this will need a SET CONSOLE SERIAL and some kind of console mgmt software, which records all output to the console port, to allow you to look at or a VLC, or a 3100, or a PC? IIRC.) - Hide quoted text -- Show quoted text -Quote:> So 800 is supposed to mean SIMM 0 is sick. Quote:> As far as I know, only the DEC 3000 300 family used this memory.
IIRC.) So 800 is supposed to mean SIMM 0 is sick. this page Top dec 3000 300 crashing by Antony Wardl » Mon, 15 Jan 2001 04:13:20 You are probably right. It only had 48 MB of RAM, so we obtained an extra 64 MB. I think in your first post, you said your machine had tried to boot.
Ldl_l/stl_c atomic (can read my writing) at ... this contact form We just bought the last set from clearpoint (used) at work, but Jeff Sullivan said he thinks he can get more. Quote:> any more help? Please see message in below."ERROR_ROUTINGES_1605**MACHINECHECK 660**CPU=0?"After that it show message system dump and reboot machine again.
I believe the operation of the MOP software interferes with the LLSC function. -- Robert Deininger 2. SYMPTOM:Output has been reduced for better readability.Cause CAUSE:Errorlog contains multiple environmental machine check related entries like: (Output has been reduced for better readability) . . The machine passes the power-up tests fine. http://threadspodcast.com/machine-check/machine-check-error-asus.html Jan Top dec 3000 300 crashing by Robert Deining » Sun, 14 Jan 2001 15:51:18 Quote:> Well, I have managed to keep my alpha, but i can't get
shows you how to set the starting and ending address of a memory test. There should be commands like MEMTEST and MEM_EXER (or similar).It may be preferable to run tests at the lowest possible level, if hardware problems are to be troubleshooted.Volker. 0 Kudos Willem See below for a comparison between the event as analyzed by DECevent and then by SEA.
The machine may be able to run without it (at > certainly severly reduced performance).
Quote:> Test mem > T-STS-MEM - LLSC Test : Addr 00200000 FWD Wr 0000000 > MCHK ID: 14 Logout Frame address: 00108060 > exc_addr: 000ED784 bui_stat: 00000050 bui_addr: 001081A0 > fill_addr: Some of these circuits maybe on the CPU board, some on the main board. System configuration did fulfill the power redundancy rules.Answer/Solution FIX:Requested user to check their power environment. Thank you!
The "victim" is the data in cache that's about to be replaced, it should be written back out to main memory. Quote:> test mem init > T_STS_MEM ok > test mem cell > T-STS-MEM ok > test mem bctp > T-ERR-MEM - TNF BCTP Again, this seems to indicate something with the It isn't too hard to find used if you aren't in a hurry. Check This Out The point is it worked well for weeks and more or less, all of a sudden, the problem appeared.I need to do some hardware maintenance shortly so clening would be a
Could you use SDA> CLUE ERRLOG to extract the errlog information from the dump ? It has a couple of rz26's and an rrd43. VMS wasn't even started, and if PALCode is not available, how to write a dump....Willem Willem GrootersOpenVMS Developer & System Manager 0 Kudos Willem Grooters Honored Contributor [Founder] Options Mark as Quote:> > Test mem > > T-STS-MEM - LLSC Test : Addr 00200000 FWD Wr 0000000 > > MCHK ID: 14 Logout Frame address: 00108060 > > exc_addr: 000ED784 bui_stat: 00000050
I'll see whether I have some old tool to evaluate AlphaStation 600 machine checks.Volker. 0 Kudos Willem Grooters Honored Contributor [Founder] Options Mark as New Bookmark Subscribe Subscribe to RSS Feed The figure implies this is a 64-bit quantity, but the tabulated values would seem to fit in a byte. What happens when you type something silly like "t mem silly"? Since you have an rrd43, are you booting from a CD?
I don't know if the cache data has parity, ECC, or what. Its been interesting. Mchk_Error_Code x0000 0206 Machine Check Logout Frame Error Code Value[31:0] x206 Environmental Fatal or Non-Fatal ES4X_Logout_Frame_System_Section Environ_QW_1_ES40 x0000 0000 0000 0000 TIG SMIR Register Environ_QW_2_ES40 x0000 0000 0000 0000 TIG CPUIR I found that the case just over the memory was very hot indeed.I let it go for a while, but one day it didn't even boot anymore - it gave errors
atari.st.tech 3. If it fails a test, it should at least tell you which part is sick. (Though that requires the secret decoder ring in some cases.) -- Robert Deininger Was the information on this page helpful? Do a TEST MEM CELL, and I'll bet it finds an error at a high memory address.