Announcement

Collapse
No announcement yet.

memtest86 test3 causes the mainboard to break down

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • memtest86 test3 causes the mainboard to break down

    Hi,
    When I used memtest86 to test Test 3, the motherboard would break down on PHYTIUM FT-2000/64 platform(ARM v. The memory used for the test is Micron DDR4-3200 (Samsung particle), May I ask what causes the motherboard to break down?


    Click image for larger version

Name:	image.png
Views:	233
Size:	441.2 KB
ID:	56024

  • #2
    Can you try V10.6
    https://www.memtest86.com/whats-new.html

    Also, what exactly do you mean by "break down". I can see it didn't detect the CPU model name, is that what you mean?

    Comment


    • #3
      Originally posted by David (PassMark) View Post
      Can you try V10.6
      https://www.memtest86.com/whats-new.html

      Also, what exactly do you mean by "break down". I can see it didn't detect the CPU model name, is that what you mean?
      "break down" is when the motherboard doesn't work, when the motherboard dies in test3.

      Comment


      • #4
        V10.6 version is the same, test to the following interface, the motherboard will not work

        Click image for larger version

Name:	image.png
Views:	188
Size:	156.7 KB
ID:	56029

        Comment


        • #5
          The following rules are found in the experiment:As long as you run the test options 3/4/5 and 7, the motherboard will automatically crash!But when running other option tests, such as test0/1/2/6/8... The motherboard works normally without any exceptions or errors.

          Click image for larger version

Name:	image.png
Views:	180
Size:	334.7 KB
ID:	56031

          Comment


          • #6
            My guess is that it would be a UEFI BIOS bug. The BIOSs for ARM machines are not very advanced at the moment. For example they can't do any threading.

            Post a debug log if you like, we can take a look to see if anything gets logged before the crash.

            Are you sure the machine is stable in normal operation? As there is a chance it is a hardware fault.

            Comment


            • #7
              debug port print the following information when the system crashes,There is no problem with the hardware of the system, because there is no problem in testing the address test 4 cycles.
              Can you tell what is wrong with UEFI from the following log?




              ----------------------------------------------------------------------------------------------
              Synchronous Exception at 0x00000000F00AD414
              PC 0x0000F00AD414 (0x0000F0056000+0x00057414) [ 0] MemTest86FreeAARCH64.dll
              PC 0x0000F00AD380 (0x0000F0056000+0x00057380) [ 0] MemTest86FreeAARCH64.dll
              PC 0x0000F00AD5AC (0x0000F0056000+0x000575AC) [ 0] MemTest86FreeAARCH64.dll
              PC 0x0000F00679A0 (0x0000F0056000+0x000119A0) [ 0] MemTest86FreeAARCH64.dll
              PC 0x0000F00B58B0 (0x0000F0056000+0x0005F8B0) [ 0] MemTest86FreeAARCH64.dll
              PC 0x0000F9EE7E7C (0x0000F9EE1000+0x00006E7C) [ 1] DxeCore.dll
              PC 0x0000F07E9A70 (0x0000F0795000+0x00054A70) [ 2] BdsDxe.dll
              PC 0x0000F07EBB4C (0x0000F0795000+0x00056B4C) [ 2] BdsDxe.dll
              PC 0x0000F07EC03C (0x0000F0795000+0x0005703C) [ 2] BdsDxe.dll
              PC 0x0000F079706C (0x0000F0795000+0x0000206C) [ 2] BdsDxe.dll
              PC 0x0000F0797A0C (0x0000F0795000+0x00002A0C) [ 2] BdsDxe.dll
              PC 0x0000F9EE33EC (0x0000F9EE1000+0x000023EC) [ 3] DxeCore.dll
              PC 0x0000F9EE2454 (0x0000F9EE1000+0x00001454) [ 3] DxeCore.dll
              PC 0x0000F9EE2024 (0x0000F9EE1000+0x00001024) [ 3] DxeCore.dll
              PC 0x00008800B000
              PC 0x00008800B1C8
              PC 0x000088000C9C
              PC 0x000088000E74
              PC 0x000088000DDC

              [ 0] /home/psygig/memtest86/Build/MemTest86/RELEASE_GCC5/AARCH64/uMemTest86Pkg/uMemTest86/DEBUG/MemTest86FreeAARCH64.dll
              [ 1] /home/kunlun/work-2/FT-2000P-CPCI-LY-20220214-NewBranchV1.0/Code/Build/PhytiumPkg/Phytium2000plusPkg/Phytium/DEBUG_GCC49/AARCH64/MdeModulePkg/Core/Dxe/DxeMain/DEBUG/DxeCore.dll
              [ 2] /home/kunlun/work-2/FT-2000P-CPCI-LY-20220214-NewBranchV1.0/Code/Build/PhytiumPkg/Phytium2000plusPkg/Phytium/DEBUG_GCC49/AARCH64/KunLunModulePkg/BdsDxe/BdsDxe/DEBUG/BdsDxe.dll
              [ 3] /home/kunlun/work-2/FT-2000P-CPCI-LY-20220214-NewBranchV1.0/Code/Build/PhytiumPkg/Phytium2000plusPkg/Phytium/DEBUG_GCC49/AARCH64/MdeModulePkg/Core/Dxe/DxeMain/DEBUG/DxeCore.dll

              X0 0x0000000000000000 X1 0x0000000000000000 X2 0x00000000FFFFFFFF X3 0x0000003D79397BAF
              X4 0x0000000000000000 X5 0x0000000000000000 X6 0x0000000000000000 X7 0x0000000000000000
              X8 0x00000000FBFFDF38 X9 0x0000000000001000 X10 0x00000000F00FD70A X11 0x00000000F0178000
              X12 0x0000000000000001 X13 0x0000000000000000 X14 0x0000000000000000 X15 0x0000000000000000
              X16 0x00000000F9EF8324 X17 0x0000000000000000 X18 0x0000000000000000 X19 0x0000000000000000
              X20 0x0000000000000000 X21 0x0000000004000000 X22 0x0000000000000000 X23 0x0000000000000003
              X24 0x0000000000000000 X25 0xFFFFFFFFFFFFFFFC X26 0x0000000000000000 X27 0x00000000FFFFFFFF
              X28 0x0000000080001000 FP 0x00000000FBFFE320 LR 0x00000000F00AD380

              V0 0x0000000000000000 00000000478CD4E1 V1 0x0000000000000000 0000000049DBBA10
              V2 0x0002D40000000000 0000004080000000 V3 0x0000330D02020000 7F01011F0404041F
              V4 0x082FBD79004F77ED 109EF06B3C305BB5 V5 0x016400B1905351F7 0098737B11CB875F
              V6 0x009C445F83B77CDF 116D917519E63B3B V7 0x05295E1F75ED5941 960E1F9E9A3249A7
              V8 0x0000000000000000 2467BF1313F0A8FF V9 0x0000000000000000 530E057F41F043A7
              V10 0x0000000000000000 0735C4D28D3F2B8D V11 0x0000000000000000 100C876B0B7E2241
              V12 0x0000000000000000 0D1572FDEAA47223 V13 0x0000000000000000 84B412D5C0DE03B5
              V14 0x0000000000000000 038364DD3B69AB3E V15 0x0000000000000000 417033DF65C02996
              V16 0x448A637E2450147D 13D2F3FF9050AF53 V17 0x0426830D04EBC536 309297AF83CA6F73
              V18 0x0E05CB6019F156E5 2154ACC788F951FB V19 0xB12304A375B00FFE 08ED23D82BC851FD
              V20 0xD1706E6B0BA0E37C 0560C4D79A00E2A3 V21 0x09514FAAA37E8568 305001B1E12EDB71
              V22 0xC351A2929B0889D3 02E092F105AA7754 V23 0xB7580A7F12E389A7 827A1A2744A78567
              V24 0xD180CC1C247AB4D5 00A8061192319BBC V25 0xE57C63C70915D733 07C478EF42D28606
              V26 0x7690EEB229DCCB01 68F4292384D1BB7D V27 0x487C23CE1656EA80 10CAD13746742B54
              V28 0xD55C06212C9FCDAF 525FB1690F8ED8CB V29 0x13A11CBFABB262F3 DE1507F7692D0267
              V30 0x0310047F57C984B3 8ED87E3A4234E2B4 V31 0x94100E62F679F5E8 88D059E304D5DAB0

              SP 0x00000000FBFFE320 ELR 0x00000000F00AD414 SPSR 0xA0000209 FPSR 0x00000010
              ESR 0x96000004 FAR 0xFFFFFFFFFFFFFFFC

              ESR : EC 0x25 IL 0x1 ISS 0x00000004

              Data abort: Translation fault, zeroth level

              Stack dump:
              00000FBFFE220: 08ED23D82BC851FD B12304A375B00FFE 0560C4D79A00E2A3 D1706E6B0BA0E37C
              00000FBFFE240: 305001B1E12EDB71 09514FAAA37E8568 02E092F105AA7754 C351A2929B0889D3
              00000FBFFE260: 827A1A2744A78567 B7580A7F12E389A7 00A8061192319BBC D180CC1C247AB4D5
              00000FBFFE280: 07C478EF42D28606 E57C63C70915D733 68F4292384D1BB7D 7690EEB229DCCB01
              00000FBFFE2A0: 10CAD13746742B54 487C23CE1656EA80 525FB1690F8ED8CB D55C06212C9FCDAF
              00000FBFFE2C0: DE1507F7692D0267 13A11CBFABB262F3 8ED87E3A4234E2B4 0310047F57C984B3
              00000FBFFE2E0: 88D059E304D5DAB0 94100E62F679F5E8 00000000F00AD414 0000000020000209
              00000FBFFE300: 0000000000000010 0000000000000000 0000000000000000 0000000000000000
              > 00000FBFFE320: 00000000FBFFE390 00000000F00AD5AC 00000000F0174CB7 0000000000000000
              00000FBFFE340: 0000000000000003 0000000000000000 0000000004000000 0000000000000002
              00000FBFFE360: 0000000000000000 8000000000000015 0000000000000001 0000000000000000
              00000FBFFE380: 0000000000000002 FFFFFFFFF0175000 00000000FBFFE400 00000000F00679A0
              00000FBFFE3A0: 00000000F0174CB7 0000000000023CD3 00000000F35A7A18 0000000000000000
              00000FBFFE3C0: 0000000004000000 00000000F00AD458 0000000000000003 0000000000000000
              00000FBFFE3E0: 0000000000000001 0000000000000000 0000000000000000 0000000000000000
              00000FBFFE400: 00000000FBFFE760 00000000F00B58B0 00000000F0174CB7 00000000F00DAD28
              ASSERT [TcgDxe] /home/kunlun/kaifaban-0727/FT-2000Plus-S-KaiFaBan-ACPI-20191125/Code/ArmPkg/Library/DefaultExceptionHandlerLib/AArch64/DefaultExceptionHandler.c(271): ((BOOLEAN)(0==1)

              Comment


              • #8
                I did some searching on "Translation fault, zeroth level", which seems to be the key error message.

                This seems to be an MMU (memory management unit) address translation fault. Some details are here
                https://developer.arm.com/documentat...ng=en#BEIGHGCJ

                Quote: "A Translation fault can be generated at any level of lookup, and the reported fault code identifies the lookup level. A Translation fault is generated if bits[1:0] of a translation table descriptor identify the descriptor as either a Fault encoding or a reserved encoding".

                We aren't ARM UEFI Kernel programmers, so we are only guessing here, but maybe this is the result is a memory access is done on a reserved area of memory? But the BIOS reports which memory address ranges are safe to use to MemTest86. So it is maybe a UEFI BIOS bug?

                Again, post the debug log from MemTest86 if you like.
                https://www.memtest86.com/tech_debug-logs.html

                Comment

                Working...
                X