From owner-freebsd-questions@freebsd.org Wed Jan 22 16:48:25 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 D7D7F1F5704 for ; Wed, 22 Jan 2020 16:48:25 +0000 (UTC) (envelope-from chris@cretaforce.gr) Received: from relay3.cretaforce.gr (relay3.cretaforce.gr [195.201.253.216]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.cretaforce.gr", Issuer "RapidSSL RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 482rvD1kB5z4FBS for ; Wed, 22 Jan 2020 16:48:23 +0000 (UTC) (envelope-from chris@cretaforce.gr) Received: from server1.cretaforce.gr (server1.cretaforce.gr [138.201.248.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.cretaforce.gr", Issuer "RapidSSL RSA CA 2018" (verified OK)) by smtp1.cretaforce.gr (Postfix) with ESMTPS id ADC991F440 for ; Wed, 22 Jan 2020 18:48:21 +0200 (EET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cretaforce.gr; s=cretaforce; t=1579711701; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ag9n302nlnMz6OCypAhWlmwdkCrZo8FoBGBp4ECngZ8=; b=m3WKC219j6Zsx8yBdIe4U2/8p7H2FxEzeaUNyGzrlP3GeLx42NKZ4O3p2EpFi8Ngl8ELOt q0uEKwcWfxB+H/Hn/4NkNZLikYV/SZyTJbN5EXUDkwXxYElxNo0Vg07W5P8TZ0zpa/Kbtj JbTILXaBIFQgEXm4zioPL6llCdVKkjc= Received: from christoss-air.fritz.box (ppp-94-64-150-254.home.otenet.gr [94.64.150.254]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: chris@cretaforce.gr) by server1.cretaforce.gr (Postfix) with ESMTPSA id 731F02730B for ; Wed, 22 Jan 2020 18:48:21 +0200 (EET) From: Christos Chatzaras Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.40.2.2.4\)) Subject: Re: 12.1 RELEASE General Protection Fault (Trap 9) Date: Wed, 22 Jan 2020 18:48:20 +0200 References: <22046a36-12d3-032a-6325-24e18b1a855b@lateapex.net> <693acc2b-b573-9fba-ab73-91d28f27e8ac@infracaninophile.co.uk> To: FreeBSD Mailing List In-Reply-To: <693acc2b-b573-9fba-ab73-91d28f27e8ac@infracaninophile.co.uk> Message-Id: <5A315787-F2FA-48BC-81BC-6668C1C08493@cretaforce.gr> X-Mailer: Apple Mail (2.3608.40.2.2.4) X-Rspamd-Queue-Id: 482rvD1kB5z4FBS X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=cretaforce.gr header.s=cretaforce header.b=m3WKC219; dmarc=none; spf=pass (mx1.freebsd.org: domain of chris@cretaforce.gr designates 195.201.253.216 as permitted sender) smtp.mailfrom=chris@cretaforce.gr X-Spamd-Result: default: False [-3.96 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[cretaforce.gr:s=cretaforce]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:195.201.253.216]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; DMARC_NA(0.00)[cretaforce.gr]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_LOW(-1.00)[cretaforce.gr.dwl.dnswl.org : 127.0.5.1]; RCVD_COUNT_THREE(0.00)[3]; IP_SCORE(-0.86)[ipnet: 195.201.0.0/16(-2.75), asn: 24940(-1.54), country: DE(-0.02)]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[cretaforce.gr:+]; MV_CASE(0.50)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; RCVD_IN_DNSWL_LOW(-0.10)[216.253.201.195.list.dnswl.org : 127.0.5.1]; RECEIVED_SPAMHAUS_PBL(0.00)[254.150.64.94.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:195.201.0.0/16, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[] 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 16:48:25 -0000 > On 22 Jan 2020, at 18:36, matthew@freebsd.org = wrote: >=20 > On 22/01/2020 15:12, Jason Van Patten wrote: >> Since sometime before Christmas (as far as I know), my NAS has = started randomly crashing, reloading, and saving cores in /var/crash. = It was doing this with 12.0 and now with 12.1. My gut tells me it's = hardware related, but I'm not quite sure. The various bits and pieces = are: >=20 > Given the crashes do not appear to be associated with any particular = activity, I think you're on the money with your diagnosis that it is = hardware related. >=20 > Did you change any of the hardware on this system recently? If you've = added more disks or such, then you may have overloaded the PSU. If the = PSU can't produce voltages in spec, then you will see random crashes, = although I doubt in that case you'ld always see 'General PRotection = Fault'. Unless this is a new machine, or you've changed some of the = hardware this is unlikely to be the diagnosis. >=20 > Otherwise, suspect hardware problems. In rough order of expense, = least to most: >=20 > * Bad heatsink, failed case fan, CPU thermal paste not up to snuff > or other cause that may lead to your system overheating >=20 > * Bad memory >=20 > * Bad CPU >=20 > The first of these is relatively cheap and easy to handle: make sure = you're getting unimpeded airflow through the chassis -- clean any = filters, make sure fans are spinning correctly and that heatsinks have = good thermal contact, if necessary by renewing any thermal paste. = Monitoring the CPU temperature will help here -- if you see the CPU = temperature increasing just before everything goes kaput, that's a = fairly solid diagnostic. For an i7, you should be able to use the = coretemp(4) kernel module and read-off the temperature from the = dev.cpu.%d.temperature sysctls. >=20 > Memory problems can frequently be diagnosed by use of a memory checker = like sysutils/memtest86+ -- if this says you have a problem, then you do = have a problem. However, it may not catch every possible memory problem = so it can wrongly give you an 'all clear'. It's pretty accurate in = practice though. A more definitive test is to swap out any suspect RAM = modules and see if the problem goes away. >=20 > The worst case is a bad CPU. memtest86+ will diagnose some CPU = faults, but it is less effective on CPU problems. If there is a CPU = problem, it will be a pretty subtle one, as typical symptoms of CPU = problems are the system won't boot and the BIOS makes horrible beeping = noises when you try. >=20 > Even so, this isn't a definitive list. I've heard tales about trying = to diagnose this sort of problem where someone had bit by bit swapped = out all of the components of a system except for the case, and the = problem still occurred. Turned out the case was slightly bent and that = put enough stress on the motherboard to cause some intermittent = electrical connectivity. >=20 > Cheers, >=20 > Matthew 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.=