From nobody Mon Feb 2 16:16:37 2026 X-Original-To: freebsd-stable@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 4f4Wvr4xQ6z6Qgm7 for ; Mon, 02 Feb 2026 16:16:40 +0000 (UTC) (envelope-from pz-freebsd-stable@ziemba.us) Received: from osmtp.ziemba.us (tc-v.ziemba.us [149.28.207.195]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4f4Wvq28Jcz3Kx6 for ; Mon, 02 Feb 2026 16:16:38 +0000 (UTC) (envelope-from pz-freebsd-stable@ziemba.us) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=ziemba.us header.s=hairball header.b=cnVO4pBH; dmarc=none; spf=pass (mx1.freebsd.org: domain of pz-freebsd-stable@ziemba.us designates 149.28.207.195 as permitted sender) smtp.mailfrom=pz-freebsd-stable@ziemba.us Received: from osmtp.ziemba.us (cyrus.ziemba.us [10.0.0.33]) by dkim.ziemba.us (8.18.1/8.18.1) with ESMTP id 612GGbTK007372 for ; Mon, 2 Feb 2026 08:16:37 -0800 (PST) (envelope-from pz-freebsd-stable@ziemba.us) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ziemba.us; s=hairball; t=1770048997; bh=YO+S3qnJ5SwbJkVQ0Lg5PkIODbJVGKnycEEhfrACpH4=; h=Date:From:Cc:Subject:References:In-Reply-To; z=Date:=20Mon,=202=20Feb=202026=2008:16:37=20-0800|From:=20"G.=20Pa ul=20Ziemba"=20|Cc:=20"freebsd-stable @freebsd.org"=20|Subject:=20Re:=20Miss ing=20MCA=20error=20messages=20for=20bad=20ECC|References:=20<10ln vch$2e5i$1@usenet.ziemba.us>=0D=0A=20<8AF202C7-89A5-4520-9B87-74B1 7ECE5562@gid.co.uk>|In-Reply-To:=20<8AF202C7-89A5-4520-9B87-74B17E CE5562@gid.co.uk>; b=cnVO4pBHGwh56JSuUmzYXn28elnaiZz21IOpGh+Gtpxmg+Xk0La4TFOU8xS/+LSKD z/oR8RfuOrjmwZnL9y+ouTwb737tO7I55EJLv08o5185/Wos9Kaq9zt2Vx6d5yVy9Z AcmCTVszUvPg8vtAx9EinTjLI44AvradfDdSnIEBsUyQV8Ei7YklLdy1wajTz+/6J1 VZzTzXQ2StQZnSHzUXIU8EAAwBpV68sFFh4BYtb/pWjTRRVFyMgn7QR5LSKeg64duu wKFnJl2cJ6poN4bG2tCulAAmg4VqIDd6dmzhKlaXiprlOzzYANA+WGZanDnIb62XUP iW12GZyIKKQRA== X-Authentication-Warning: hairball.ziemba.us: Host cyrus.ziemba.us [10.0.0.33] claimed to be osmtp.ziemba.us Received: from hairball.ziemba.us (localhost [127.0.0.1]) by hairball.ziemba.us (8.18.1/8.18.1) with ESMTP id 612GGbPC007369 for ; Mon, 2 Feb 2026 08:16:37 -0800 (PST) (envelope-from pz-freebsd-stable@ziemba.us) Received: (from paul@localhost) by hairball.ziemba.us (8.18.1/8.18.1/Submit) id 612GGbaU007368 for freebsd-stable@freebsd.org; Mon, 2 Feb 2026 08:16:37 -0800 (PST) (envelope-from pz-freebsd-stable@hairball.ziemba.us) X-Authentication-Warning: hairball.ziemba.us: paul set sender to pz-freebsd-stable@hairball.ziemba.us using -f Date: Mon, 2 Feb 2026 08:16:37 -0800 From: "G. Paul Ziemba" Cc: "freebsd-stable@freebsd.org" Subject: Re: Missing MCA error messages for bad ECC Message-ID: References: <10lnvch$2e5i$1@usenet.ziemba.us> <8AF202C7-89A5-4520-9B87-74B17ECE5562@gid.co.uk> List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8AF202C7-89A5-4520-9B87-74B17ECE5562@gid.co.uk> X-Spamd-Result: default: False [-1.40 / 15.00]; MISSING_TO(2.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.90)[-0.897]; R_DKIM_ALLOW(-0.20)[ziemba.us:s=hairball]; R_SPF_ALLOW(-0.20)[+ip4:149.28.207.195]; MIME_GOOD(-0.10)[text/plain]; MID_RHS_MATCH_FROMTLD(0.00)[]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:20473, ipnet:149.28.192.0/19, country:US]; MISSING_XM_UA(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; MLMMJ_DEST(0.00)[freebsd-stable@freebsd.org]; DMARC_NA(0.00)[ziemba.us]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; HAS_XAW(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; TO_DN_EQ_ADDR_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-stable@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[ziemba.us:+] X-Rspamd-Queue-Id: 4f4Wvq28Jcz3Kx6 X-Spamd-Bar: - Bob, thanks for your suggestions. The motherboard is a plain X11SCA (no -F ipmi) I don't know of a way to read the power supply voltages in software while FreeBSD is running, but I did reboot into the BIOS setup and read voltages there, and they look normal to me: VCPU: 1.136 VDIMM: 1.224 12V: 12.233 5VCC: 5.184 3.3V_DL: 3.327 3.3VCC: 3.424 VSB: 3.328 VBAT: 3.104 VCC1_8_DL_PCM: 1.816 The BIOS versions are given as: "ver 1.2 Build Date 12/5/19" near the top of the screen; and "version 2.19.0045 (c) [AMI]" at the bottom of the screen I didn't see a setting that (apparently to me) might control how events might be filtered, but there WAS an event log that had completely filled up with messages of the form: smbios 0x02 DIMMB1 with many for DIMMB1 and DIMMB2. I haven't found any documentation yet of "0x02" other than a few online posts calling it either a single-bit or a multi-bit ECC memory error. I'm still favoring a diagnosis of two bad DIMMs; I just wish there were a way to cause these errors to show up in FreeBSD somewhere so I could detect them on a running system. On Sun, Feb 01, 2026 at 08:30:56PM +0000, Bob Bishop wrote: > Hi, > > > On 1 Feb 2026, at 16:35, G. Paul Ziemba wrote: > > > > OS: 14.2-STABLE as of 250403 > > > > I seem to have at least one bad ECC DIMM > > Check the power supply voltages are within tolerance if you haven???t already. > > > and was expecting to see MCA > > messages in /var/log/messages or to the console (which I have recently > > redirected to /var/log/console.log via syslog.conf: > > > > console.info /var/log/console.log > > > > but I can't find anything in any of my logs. Why am I not seeing them? > > If you have the -F variant of the board that supports IPMI, it may be that the BMC is capturing the errors so check the BMC event log. Possibly there is a setting on the BMC to control what gets passed to MCA. > > Also check the BIOS event logging; I don???t see settings in the BIOS to control MCA events. > > And check the BIOS version is up to date. > > > Background: > > > > Motherboard: Supermicro X11SCA > > CPU: Xeon E-2176G > > Chipset: C246 > > Memory: 4x SK Hynix HMA82GU7CJR8N-VK (16GB ECC) > > > > Bios reports ECC on its startup screen and dmidecode reports > > > > Total Width: 72 bits > > Data Width: 64 bits > > > > for each of the dimms. > > > > Amanda started reporting checksum errors on large backup files in its > > holding disk. I discovered that a large file (200GB) on any of three > > disks on this system yields different sha512sum values every time I > > run it on the same file. SMART data looks OK on all disks. > > > > memtest86+ finds three bad spots in memory, at 42G, 47G and 53G. I have > > 4x16GB dimms installed, so I think that corresponds to two bad dimms. > > > > % sysctl hw.mca > > hw.mca.cmc_throttle: 60 > > hw.mca.force_scan: 0 > > hw.mca.interval: 300 > > hw.mca.maxcount: -1 > > hw.mca.count: 0 > > hw.mca.erratum383: 0 > > hw.mca.intel6h_HSD131: 0 > > hw.mca.amd10h_L1TP: 1 > > hw.mca.log_corrected: 1 > > hw.mca.enabled: 1 > > > > Thanks for any insights. > > -- > > G. Paul Ziemba > > FreeBSD unix: > > 8:31AM up 2 days, 14:38, 11 users, load averages: 0.71, 0.43, 0.39 > > > > > -- > Bob Bishop t: +44 (0)118 940 1243 > rb@gid.co.uk m: +44 (0)783 626 4518 > > > > > -- G. Paul Ziemba FreeBSD unix: 7:51AM up 35 mins, 2 users, load averages: 0.32, 0.56, 0.47