From owner-freebsd-questions@freebsd.org Tue May 19 18:23:51 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 EAA5C2F0E71 for ; Tue, 19 May 2020 18:23:51 +0000 (UTC) (envelope-from dpchrist@holgerdanske.com) Received: from holgerdanske.com (holgerdanske.com [IPv6:2001:470:0:19b::b869:801b]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "holgerdanske.com", Issuer "holgerdanske.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 49RPQs06ZZz3gmb for ; Tue, 19 May 2020 18:23:48 +0000 (UTC) (envelope-from dpchrist@holgerdanske.com) Received: from 99.100.19.101 ([99.100.19.101]) by holgerdanske.com with ESMTPSA (TLS_AES_128_GCM_SHA256:TLSv1.3:Kx=any:Au=any:Enc=AESGCM(128):Mac=AEAD) (SMTP-AUTH username dpchrist@holgerdanske.com, mechanism PLAIN) for ; Tue, 19 May 2020 11:23:40 -0700 Subject: Re: OT: Weird Hardware Problem To: freebsd-questions@freebsd.org References: <0a9f810d-7b4b-f4e6-4b7c-716044a9cf69@tundraware.com> From: David Christensen Message-ID: Date: Tue, 19 May 2020 11:23:40 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.7.0 MIME-Version: 1.0 In-Reply-To: <0a9f810d-7b4b-f4e6-4b7c-716044a9cf69@tundraware.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 49RPQs06ZZz3gmb X-Spamd-Bar: ++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of dpchrist@holgerdanske.com has no SPF policy when checking 2001:470:0:19b::b869:801b) smtp.mailfrom=dpchrist@holgerdanske.com X-Spamd-Result: default: False [2.30 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_SPAM_SHORT(0.44)[0.444]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; TO_DN_NONE(0.00)[]; AUTH_NA(1.00)[]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_SPAM_MEDIUM(0.96)[0.960]; DMARC_NA(0.00)[holgerdanske.com]; R_SPF_NA(0.00)[no SPF record]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:6939, ipnet:2001:470::/32, country:US]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2020 18:23:52 -0000 On 2020-05-19 06:46, Tim Daneliuk wrote: > I was recently given a Dell Inspiron 3847 which has an i7-4790 and 16G > of memory. Perfect for multibooting BSD and Linux. It needed a new power > supply but now that this is installed, it's exhibiting a very strange > problem. > > The machine will work for hours flawless and then - for no apparent reason - > reboot randomly. The former owner reports that this was also happening > when they last had it running Win8. > > I've run very heavy loads on it with load averages up to almost 50 - no > problem. I've run overnight memory tests which return 0 errors. > I've run CPU stress tests flawlessly and temperatures were fine. > > One hint here: I can consistently force the problem to happen if I start > a Linux installation and request full disk encryption as part of the install. > I doubt it has anything to with encryption per se, but there is some kind > of pattern of use that it causing the reboot. > > Has anyone else ever seen something like this and/or have resolution? > > Is there a known bug with that processor? > > My first instinct was to blame flakey memory (DDR 1600 2x8G Hynix) but - > as I said - memory testing is flawless. > > Thoughts and ideas most welcome. I have not seen these suggestions yet: 1. Have you tried connecting the system drive to another port? 2. Have you tried replacing the SATA cable? 3. Have you tried replacing the system drive? David