From owner-freebsd-questions@freebsd.org Wed Jan 22 18:42:48 2020 Return-Path: Delivered-To: freebsd-questions@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 19DDB1F9675 for ; Wed, 22 Jan 2020 18:42:48 +0000 (UTC) (envelope-from jvp@lateapex.net) Received: from batman.lateapex.net (batman.lateapex.net [208.43.252.246]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "imap.lateapex.net", Issuer "Let's Encrypt Authority X3" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 482vRB3Zdmz4NCv for ; Wed, 22 Jan 2020 18:42:45 +0000 (UTC) (envelope-from jvp@lateapex.net) Received: from deathstroke.private.lateapex.net (joker.lateapex.net [108.28.193.210]) (authenticated bits=0) by batman.lateapex.net (8.15.2/8.15.2) with ESMTPSA id 00MIgiYs046259 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Wed, 22 Jan 2020 13:42:44 -0500 (EST) (envelope-from jvp@lateapex.net) X-Authentication-Warning: batman.lateapex.net: Host joker.lateapex.net [108.28.193.210] claimed to be deathstroke.private.lateapex.net Subject: Re: 12.1 RELEASE General Protection Fault (Trap 9) To: FreeBSD Mailing List References: <22046a36-12d3-032a-6325-24e18b1a855b@lateapex.net> <693acc2b-b573-9fba-ab73-91d28f27e8ac@infracaninophile.co.uk> <5A315787-F2FA-48BC-81BC-6668C1C08493@cretaforce.gr> From: Jason Van Patten Message-ID: <30dab369-bbbe-3f31-1f62-3dde7d4dba99@lateapex.net> Date: Wed, 22 Jan 2020 13:42:39 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: <5A315787-F2FA-48BC-81BC-6668C1C08493@cretaforce.gr> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Milter: Spamilter DataSet=MTA-Peer; receiver=batman.lateapex.net; sender-ip=108.28.193.210; sender-helo=deathstroke.private.lateapex.net; X-Milter: Spamilter DataSet=GeoIP; receiver=batman.lateapex.net; ip=108.28.193.210; CC=--; X-Milter: Spamilter DataSet=SessionId; receiver=batman.lateapex.net; sessionid='8953bb743dccf358a5baead14b4d029a'; X-Rspamd-Queue-Id: 482vRB3Zdmz4NCv X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of jvp@lateapex.net designates 208.43.252.246 as permitted sender) smtp.mailfrom=jvp@lateapex.net X-Spamd-Result: default: False [-1.45 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; NEURAL_HAM_MEDIUM(-0.77)[-0.770,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+a:smtp.lateapex.net]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_HAM_LONG(-0.71)[-0.712,0]; DMARC_NA(0.00)[lateapex.net]; TO_DN_ALL(0.00)[]; IP_SCORE(0.33)[asn: 36351(1.70), country: US(-0.05)]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:36351, ipnet:208.43.224.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jan 2020 18:42:48 -0000 On 1/22/20 11:48 AM, Christos Chatzaras wrote: > > I had similar crashes and it was bad RAM. > > I recommend to check RAM using the userland memtester if downtime is > not an option. > > Keep in mind that it's better to use memtest86+ as it can check all > RAM. _______________________________________________ Thank you and Matthew for your answers. My assumption was memory, but I wasn't sure of the errors and core could prove that out without taking the system down for 4+ hours to do a memtest86. To be honest, the 2 minute random downtime for the reboots is actually less problematic than the 4+ hours it could take. Heh. DDR3 is cheap enough; I'll just swap that out and see if it does the deed. And while I'm at it, I'll re-do the processor's heat sink/fan setup. I tend to doubt that's the culprit as most chips will just slow themselves down if they get too warm. And again: this machine is basically sleeping. Its load average is basically 0, all the time. So odds of it being a CPU temperature issue are slim-to-none. -- Jason Van Patten