Announcement

Collapse
No announcement yet.

Dell R620 - Log File Help

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

  • Dell R620 - Log File Help

    I have been having issues with a Dell R620 throwing errors in XCP-NG that appear to relate to memory. So i purchased MemTest64 pro and ran it over the weekend.

    I didn't get any "errors", but it did have some aborted errors.
    Code:
    2020-08-24 07:05:24 - WARNING - waited for 10s for CPU #4 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:24 - WARNING - waited for 10s for CPU #6 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:24 - WARNING - waited for 10s for CPU #8 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:24 - WARNING - waited for 10s for CPU #10 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:24 - WARNING - waited for 10s for CPU #12 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:24 - WARNING - waited for 10s for CPU #14 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:24 - WARNING - waited for 10s for CPU #16 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:24 - WARNING - waited for 10s for CPU #18 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:24 - WARNING - waited for 10s for CPU #20 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:24 - WARNING - waited for 10s for CPU #22 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:24 - WARNING - waited for 10s for CPU #24 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:24 - WARNING - waited for 10s for CPU #26 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:24 - WARNING - waited for 10s for CPU #28 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:24 - WARNING - waited for 10s for CPU #30 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:34 - RunMemoryRangeTest - aborted waiting for CPU #2 to finish (Wait time = 20001ms, BSP test time = 3045ms)
    2020-08-24 07:05:34 - WARNING - waited for 20s for CPU #4 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:34 - RunMemoryRangeTest - aborted waiting for CPU #4 to finish (Wait time = 20030ms, BSP test time = 3045ms)
    2020-08-24 07:05:34 - WARNING - waited for 20s for CPU #6 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:34 - RunMemoryRangeTest - aborted waiting for CPU #6 to finish (Wait time = 20054ms, BSP test time = 3045ms)
    2020-08-24 07:05:34 - WARNING - waited for 20s for CPU #8 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:34 - RunMemoryRangeTest - aborted waiting for CPU #8 to finish (Wait time = 20078ms, BSP test time = 3045ms)
    2020-08-24 07:05:34 - WARNING - waited for 20s for CPU #10 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:34 - RunMemoryRangeTest - aborted waiting for CPU #10 to finish (Wait time = 20114ms, BSP test time = 3045ms)
    2020-08-24 07:05:34 - WARNING - waited for 20s for CPU #12 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:34 - RunMemoryRangeTest - aborted waiting for CPU #12 to finish (Wait time = 20138ms, BSP test time = 3045ms)
    2020-08-24 07:05:34 - WARNING - waited for 20s for CPU #14 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:34 - RunMemoryRangeTest - aborted waiting for CPU #14 to finish (Wait time = 20163ms, BSP test time = 3045ms)
    2020-08-24 07:05:34 - WARNING - waited for 20s for CPU #16 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:34 - RunMemoryRangeTest - aborted waiting for CPU #16 to finish (Wait time = 20186ms, BSP test time = 3045ms)
    2020-08-24 07:05:34 - WARNING - waited for 20s for CPU #18 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:34 - RunMemoryRangeTest - aborted waiting for CPU #18 to finish (Wait time = 20210ms, BSP test time = 3045ms)
    2020-08-24 07:05:34 - WARNING - waited for 20s for CPU #20 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:34 - RunMemoryRangeTest - aborted waiting for CPU #20 to finish (Wait time = 20234ms, BSP test time = 3045ms)
    2020-08-24 07:05:34 - WARNING - waited for 20s for CPU #22 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:34 - RunMemoryRangeTest - aborted waiting for CPU #22 to finish (Wait time = 20258ms, BSP test time = 3045ms)
    2020-08-24 07:05:34 - WARNING - waited for 20s for CPU #24 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:35 - RunMemoryRangeTest - aborted waiting for CPU #24 to finish (Wait time = 20298ms, BSP test time = 3045ms)
    2020-08-24 07:05:35 - WARNING - waited for 20s for CPU #26 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:35 - RunMemoryRangeTest - aborted waiting for CPU #26 to finish (Wait time = 20326ms, BSP test time = 3045ms)
    2020-08-24 07:05:35 - WARNING - waited for 20s for CPU #28 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:35 - RunMemoryRangeTest - aborted waiting for CPU #28 to finish (Wait time = 20372ms, BSP test time = 3045ms)
    2020-08-24 07:05:35 - WARNING - waited for 20s for CPU #30 to finish (BSP test time = 3045ms)
    2020-08-24 07:05:35 - RunMemoryRangeTest - aborted waiting for CPU #30 to finish (Wait time = 20396ms, BSP test time = 3045ms)
    It also hung when trying to reboot with a scary error....but upon googling, it appears that was a boot error. (screenshot attached)

    Can anyone point me in the correct direction to look next.

    Thank you in advance.
    Attached Files

  • #2
    We have no idea what XCP-NG is.

    That crash in your screen shot was in "cpumpdxe".
    This seems to be something from Intel (nothing to do with MemTest86). The description is,

    "CPU DXE Driver that configures multi-processor environment, logs data to datahub
    for processor subclass and cache subclass, and installs CPU Architecture Protocol and MP [Multi-Processor]
    Services Protocol".


    The crash type was breakpoint. Which is strange as it implies it was deliberately coded to stop here.

    The "aborted waiting for CPU" error from MemTest86 suggests that CPU cores appears to have hung (ie. "timed out) when running the memory tests. The main Boot strap processor (BSP) CPU has completed (in 3 secs), and timed out waiting (20 secs) for other CPU cores to finish. Normally this indicates a UEFI BIOS bug related to multi-threading.

    Note: Boot strap processor (BSP) is a UEFI term used to indicate the CPU core / thread that is launched first when the PC boots, before any other threads are started.
    Last edited by keith; Aug-25-2020, 11:36 PM.

    Comment

    Working...
    X