From nobody Sun Jul 31 01:22:37 2022 X-Original-To: questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4LwNm36dkQz4X987 for ; Sun, 31 Jul 2022 01:22:43 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Received: from mx0.riseup.net (mx0.riseup.net [198.252.153.6]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx0.riseup.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4LwNm275Y3z3Snl for ; Sun, 31 Jul 2022 01:22:42 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Received: from fews2.riseup.net (fews2-pn.riseup.net [10.0.1.84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.riseup.net", Issuer "R3" (not verified)) by mx0.riseup.net (Postfix) with ESMTPS id 4LwNm075Ncz9tF4 for ; Sun, 31 Jul 2022 01:22:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1659230561; bh=LtGxK1Usdi2ORZpFffpbZgPdWOiFgVssncUDq2Tm3zE=; h=Date:From:To:Subject:In-Reply-To:References:From; b=Jp14kJceNH4MApsKuKUoSH5WanjrKsJu3HnzuyErEGdh8GZoi+7eSbVPcujs6kGGU oGPp2lsnfM6yd3auT4mdadDBSAbRLcG1QnnHYzNHA940qwWFgJh/TL2dcnwTr9aNbl FtlH005fLORJ9qvP5GETPTLQwkQ4Px5610gg7Hi8= X-Riseup-User-ID: B166B4CC7B7D2B01A6B5310ABAC6D8E1A6958677C461CE79E4B6044DE992DB1E Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews2.riseup.net (Postfix) with ESMTPSA id 4LwNm02pjnz214k for ; Sun, 31 Jul 2022 01:22:40 +0000 (UTC) Date: Sun, 31 Jul 2022 03:22:37 +0200 From: Ralf Mardorf To: questions@freebsd.org Subject: Re: OT: Strange interaction between NIC, SSD and motherboard Message-ID: <20220731032237.35633e06@archlinux> In-Reply-To: <48992616-0875-4a9c-8f87-0b7dbb658ce7@holgerdanske.com> References: <9b92958b-0b67-0622-f5ec-b145fb8b569c@holgerdanske.com> <20220730090027.0c5705ab@archlinux> <20220730140413.3e7fc4c9@archlinux> <20220730141612.4e77eb84@archlinux> <20220730231809.5d21787f@archlinux> <48992616-0875-4a9c-8f87-0b7dbb658ce7@holgerdanske.com> List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4LwNm275Y3z3Snl X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=Jp14kJce; dmarc=pass (policy=none) header.from=riseup.net; spf=pass (mx1.freebsd.org: domain of ralf-mardorf@riseup.net designates 198.252.153.6 as permitted sender) smtp.mailfrom=ralf-mardorf@riseup.net X-Spamd-Result: default: False [-3.60 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; R_SPF_ALLOW(-0.20)[+a:mx0.riseup.net]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; RCVD_IN_DNSWL_LOW(-0.10)[198.252.153.6:from]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[questions@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US]; MIME_TRACE(0.00)[0:+]; DKIM_TRACE(0.00)[riseup.net:+]; RCPT_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DWL_DNSWL_NONE(0.00)[riseup.net:dkim]; TO_DN_NONE(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[] X-ThisMailContainsUnwantedMimeParts: N On Sat, 30 Jul 2022 16:54:52 -0700, David Christensen wrote: >Have you tested the power supply with a hardware power supply tester? >[snip] >If you disconnect everything from the motherboard except for [snip] A step to do before David's suggestions is to stay with everything connected and taking a look at the voltage monitoring of the BIOS. > CMOS [snip] Apropos BIOS, most of the times when my PCs suffered from Voodoo, replacing the battery stopped the spell. There were no battery warnings, no loss of the time or any similar expected signs, but unexpected effects happened, e.g. the graphics seemed to be borked. When replacing the battery, the whole CMOS thingy gets reset. By replacing the battery you might kill two birds with one stone. For the reset it's not required to replace the battery ;). However, when I replaced the battery I often got rid of strange issues. The issues were solved by the new batteries and/or by resetting the CMOS thingy. I don't know what actually solved the issues.