From owner-freebsd-questions@freebsd.org Wed May 20 16:07:41 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 9B9202DD886 for ; Wed, 20 May 2020 16:07:41 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from kicp.uchicago.edu (kicp.uchicago.edu [128.135.20.70]) by mx1.freebsd.org (Postfix) with ESMTP id 49RyMJ385Bz4P4y for ; Wed, 20 May 2020 16:07:40 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from [192.168.43.113] (unknown [172.58.142.165]) (Authenticated sender: galtsev) by kicp.uchicago.edu (Postfix) with ESMTPSA id 470DB4E676 for ; Wed, 20 May 2020 11:07:34 -0500 (CDT) Subject: Re: OT: Weird Hardware Problem To: freebsd-questions@freebsd.org References: <0a9f810d-7b4b-f4e6-4b7c-716044a9cf69@tundraware.com> <8b13e2f5-6ff4-ecc2-7036-c88cff0f5b6b@tundraware.com> From: Valeri Galtsev Message-ID: <8732b894-0962-3546-4697-4c2ae0658cb8@kicp.uchicago.edu> Date: Wed, 20 May 2020 11:07:32 -0500 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: <8b13e2f5-6ff4-ecc2-7036-c88cff0f5b6b@tundraware.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 49RyMJ385Bz4P4y X-Spamd-Bar: +++++++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=uchicago.edu (policy=none); spf=none (mx1.freebsd.org: domain of galtsev@kicp.uchicago.edu has no SPF policy when checking 128.135.20.70) smtp.mailfrom=galtsev@kicp.uchicago.edu X-Spamd-Result: default: False [7.03 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; RECEIVED_SPAMHAUS_XBL(5.00)[172.58.142.165:received]; RECEIVED_SPAMHAUS_PBL(0.00)[172.58.142.165:received]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; GREYLIST(0.00)[pass,meta]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-questions@freebsd.org]; NEURAL_SPAM_MEDIUM(0.89)[0.891]; RCPT_COUNT_ONE(0.00)[1]; NEURAL_SPAM_SHORT(0.22)[0.217]; NEURAL_SPAM_LONG(0.82)[0.817]; R_SPF_NA(0.00)[no SPF record]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:160, ipnet:128.135.0.0/16, country:US]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; DMARC_POLICY_SOFTFAIL(0.10)[uchicago.edu : No valid SPF, No valid DKIM,none] X-Spam: Yes 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: Wed, 20 May 2020 16:07:41 -0000 On 5/20/20 10:50 AM, Tim Daneliuk wrote: > On 5/19/20 8:46 AM, 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. > All signs point to an inadequate power supply. > > When I initially got the machine, I had to replace the onboard > supply because the fan bearings on it were bad and loud. The former > owner reported that the machine had - in fact - been experiencing > random reboots of late. > > I replaced the old supply with a "good" used 500W ATX supply and > the reboot problem was still noted as above. > > This morning, I pulled the used supply and put the only new PS I have > in stock - at 350W ATX unit - and tried to recreate the problem I'd > been able to force consistently before during Linux install. Voila! > It worked. > > Now I need to monitor this thing for the next day or so to ensure that > the problem is - indeed gone. > > Interesting that a new 350W supply does the trick when an apparently working > 500W didn't. As someone pointed out, this could well be old electrolytics > not holding the rail voltage well under stress. > Yes, it was I who mentioned electrolytic capacitors. And that goes about both PS and system board (the last mostly the ones situated around CPU). The trouble is: not filtering well enough ripple on the power leads of buses. Second problem (electronically related) would be: older components, mostly hard drives, start consume more power with age, i.e. higher current, thus increasing the level of ripple as ripple is mostly the voltage change after capacitor gives out some charge Dell is known to build workstations without much reserve on PS capacity (I have a feeling I told this already on this thread). Which means, older Dell workstations are more likely to be pushed to the "just marginally not powerful enough" power supply. Especially as parts inside PS age as well. And capacitors are more likely to leak electrolyte thus loosing capacitance if they are overheated. Instability with age will be more likely in machines with large number of mechanical hard drives, so storage servers build with PS of just right power are more likely to become "unstable". Bottom line: measure what your machine consumes, and give it PS twice as powerful as its maximum consumption under stress load. I'm happy you solved it! Valeri > > > ---------------------------------------------------------------------------- > Tim Daneliuk tundra@tundraware.com > PGP Key: http://www.tundraware.com/PGP/ > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > -- ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++