From owner-freebsd-questions@freebsd.org Tue May 19 13:59:57 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 A87A22D89DC for ; Tue, 19 May 2020 13:59:57 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from bede.qeng-ho.org (bede.qeng-ho.org [217.155.128.241]) (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 49RHZN3THhz4Yyr for ; Tue, 19 May 2020 13:59:56 +0000 (UTC) (envelope-from freebsd@qeng-ho.org) Received: from arthur.home.qeng-ho.org (arthur.home.qeng-ho.org [172.23.1.2]) by bede.qeng-ho.org (Postfix) with ESMTP id 77F0110193; Tue, 19 May 2020 14:59:48 +0100 (BST) Subject: Re: OT: Weird Hardware Problem To: Tim Daneliuk , FreeBSD Mailing List References: <0a9f810d-7b4b-f4e6-4b7c-716044a9cf69@tundraware.com> From: Arthur Chance Message-ID: Date: Tue, 19 May 2020 14:59:48 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; 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 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 49RHZN3THhz4Yyr X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of freebsd@qeng-ho.org designates 217.155.128.241 as permitted sender) smtp.mailfrom=freebsd@qeng-ho.org X-Spamd-Result: default: False [-1.34 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.69)[-0.690]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:217.155.128.240/29]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[qeng-ho.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; NEURAL_HAM_SHORT(-0.35)[-0.346]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:13037, ipnet:217.155.0.0/16, country:GB]; MIME_TRACE(0.00)[0:+]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] 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 13:59:57 -0000 On 19/05/2020 14: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? I've got an i7-4790K (I presume you missed the K) in my desktop and Intel announced the CPU had problems with the TSX instruction set extension shortly after I got it, and that those instructions should be disabled in the BIOS. Other than that I've seen no suggestion anything else is buggy. > 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. If you hadn't changed the power supply I'd have suggested you look at that, but otherwise not a clue. -- Fat Earther: One who believes the world is round but has put on too much weight round the middle.