From nobody Tue Jun 21 00:19:05 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 8252F86A818 for ; Tue, 21 Jun 2022 00:19:19 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4LRnFL3Rtfz4ppq for ; Tue, 21 Jun 2022 00:19:18 +0000 (UTC) (envelope-from ultima1252@gmail.com) Received: by mail-lf1-x133.google.com with SMTP id a29so19725678lfk.2 for ; Mon, 20 Jun 2022 17:19:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FrTsWolTM/3RpQlDexHAGOajxRrbTeq57sZK1C5Binc=; b=FJ+RJozHbYR/yA6KRau/H8KWyuI2AE2vpJ3wnAUS0yeP3+5hMWMVIn4l+5N9zVXyyL HnsjhLUW2tRccp64FviSEKeKHOpThrJwz7zFKNfzd/wQu/ld31UmZVl2GVO4ZwXWw9Jq 2zrm4q7L5yr1DZjL6YjBQQAiF5HTmi+/6xWwHVjthB8pmhELQlIWbxSKtxTCZKO4Mbcy MPOBa1AbEVCM/OAJgkyKPCOGFVdN9k0NtIRBO7ni/v5kIx0LxUgPZwZEWmG21HoJwT2j oC0VwAdXAZ9CQjdDqwphZmsW0Y4n648uW4Wjb0S73Zfngxo6cpMIO56EfpBVKhFvmDj9 OPXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FrTsWolTM/3RpQlDexHAGOajxRrbTeq57sZK1C5Binc=; b=g8NiFXhkGXwJQo1hRoqeEkXk0LgULGXugrdOWxqFkOIxhr12AF9QV36k81/Hm9ov2s N6JLqhYMe3LAhfMGL52OcAt0l1/I8B6Px0nosUgr8Vowj4wbi6FzKTprXGQwXfwHdjhy d0U8Bu29mV+8bhfpGsae5egByeAxfWY/6Cp2qaHRTSksoT9oZ6LXyzXev2/Dk+hg/WbE C4OFf/7Q8qx9I7BaDDMr5vRNQa4+NgLG/f7AQ2KzA4dN66aLOcmfQaTlEKSqZFB0IcQ/ GMWQO5VEihbMr8q7oiHeibZ2YyCRYpgrWgcSSP4VhNNChWJYgUPIh4trQzJVP7O/n0kc JcqQ== X-Gm-Message-State: AJIora8HaV4Hq36rYGNRMbOiguzPsnTk9uAgPQhjlggUSW06izjLuyy7 /zd4mZaiYru2nmOqyrcvAt5LyTUZS7wukqv4p0DmK99u X-Google-Smtp-Source: AGRyM1uZe7C4TLcURn2zINySMgr0iOihohSwiVSayOdJq3vB7R73dpUGbDNcgR85oMb26sOHMIcSlH0DfdDRKtkdmrY= X-Received: by 2002:a05:6512:2808:b0:47f:51c4:1dea with SMTP id cf8-20020a056512280800b0047f51c41deamr11104242lfb.390.1655770757059; Mon, 20 Jun 2022 17:19:17 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Ultima Date: Mon, 20 Jun 2022 17:19:05 -0700 Message-ID: Subject: Re: MCE: Does this look possibly like a slot issue? To: Larry Rosenman Cc: Freebsd current Content-Type: multipart/alternative; boundary="000000000000cdd90a05e1ea2b38" X-Rspamd-Queue-Id: 4LRnFL3Rtfz4ppq X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20210112 header.b=FJ+RJozH; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of ultima1252@gmail.com designates 2a00:1450:4864:20::133 as permitted sender) smtp.mailfrom=ultima1252@gmail.com X-Spamd-Result: default: False [-2.98 / 15.00]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; FREEMAIL_FROM(0.00)[gmail.com]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; NEURAL_HAM_SHORT(-0.98)[-0.981]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; FREEMAIL_ENVFROM(0.00)[gmail.com]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; SUBJECT_ENDS_QUESTION(1.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20210112]; FROM_HAS_DN(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::133:from]; MLMMJ_DEST(0.00)[freebsd-current]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N --000000000000cdd90a05e1ea2b38 Content-Type: text/plain; charset="UTF-8" Hey Larry, It is possible it's the motherboard itself, but it's rare. The way I would determine this is to swap the DIMM module with another populated slot on the motherboard and see if the error migrated to the new slot or not. Also, this error doesn't necessarily mean there is a problem that needs to be addressed. If you have been running the system for many months and you see ECC errors a handful of times, it can probably be safely ignored. Best regards, Richard Gallamore On Mon, Jun 20, 2022 at 3:14 PM Larry Rosenman wrote: > I've gotten a BUNCH of these on my TrueNAS server. I've replaced this > DIMM a couple of times, and still the MCE's continue. > Is it possible it's Motherboard slot issue? > > Hardware event. This is not a software error. > MCE 8 > CPU 22 BANK 8 TSC 5aa4ecdd795a > MISC ac29890200046646 ADDR ee2f6e800 > TIME 1655762472 Mon Jun 20 17:01:12 2022 > MCG status: > Memory read ECC error > Memory corrected error count (CORE_ERR_CNT): 1 > Memory transaction Tracker ID (RTId): 46 > Memory DIMM ID of error: 0 > Memory channel ID of error: 1 > Memory ECC syndrome: ac298902 > STATUS 8c0000400001009f MCGSTATUS 0 > MCGCAP 1c09 APICID 34 SOCKETID 0 > CPUID Vendor Intel Family 6 Model 44 Step 2 > DDR3 DIMM 800 Mhz Other Width 72 Data Width 64 Size 4 GB > Device Locator: P2-DIMM2C > Bank Locator: BANK14 > Manufacturer: Hyundai > Serial Number: 40F3C20F > Asset Tag: > Part Number: HMT151R7BFR4C-H9 > > > > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 214-642-9640 E-Mail: ler@lerctr.org > US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 > > --000000000000cdd90a05e1ea2b38 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hey Larry,

=C2=A0It is possi= ble it's the motherboard itself, but it's rare. The way I
would determine this is to swap the DIMM module with another
pop= ulated slot on the motherboard and see if the error migrated
to t= he new slot or not. Also, this error doesn't necessarily mean
there is a problem that needs to be addressed. If you have been
= running the system for many months and you see ECC errors a
handf= ul of times, it can probably be safely ignored.

Be= st regards,
Richard Gallamore

On Mon, Jun 20, 2022 at 3= :14 PM Larry Rosenman <ler@lerctr.org<= /a>> wrote:
I= 've gotten a BUNCH of these on my TrueNAS server.=C2=A0 I've replac= ed this
DIMM a couple of times, and still the MCE's continue.
Is it possible it's Motherboard slot issue?

Hardware event. This is not a software error.
MCE 8
CPU 22 BANK 8 TSC 5aa4ecdd795a
MISC ac29890200046646 ADDR ee2f6e800
TIME 1655762472 Mon Jun 20 17:01:12 2022
MCG status:
Memory read ECC error
Memory corrected error count (CORE_ERR_CNT): 1
Memory transaction Tracker ID (RTId): 46
Memory DIMM ID of error: 0
Memory channel ID of error: 1
Memory ECC syndrome: ac298902
STATUS 8c0000400001009f MCGSTATUS 0
MCGCAP 1c09 APICID 34 SOCKETID 0
CPUID Vendor Intel Family 6 Model 44 Step 2
DDR3 DIMM 800 Mhz Other Width 72 Data Width 64 Size 4 GB
Device Locator: P2-DIMM2C
Bank Locator: BANK14
Manufacturer: Hyundai
Serial Number: 40F3C20F
Asset Tag:
Part Number: HMT151R7BFR4C-H9



--
Larry Rosenman=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0http://www.lerctr.org/~ler
Phone: +1 214-642-9640=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0E-Mail: ler@l= erctr.org
US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106

--000000000000cdd90a05e1ea2b38--