From nobody Sun Jul 31 08:51:49 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 4LwZkN4Ytgz4XdhY for ; Sun, 31 Jul 2022 08:51:56 +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 4LwZkM4B0pz3FNF for ; Sun, 31 Jul 2022 08:51:55 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Received: from fews1.riseup.net (fews1-pn.riseup.net [10.0.1.83]) (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 4LwZkK52dQz9s4M for ; Sun, 31 Jul 2022 08:51:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1659257513; bh=4yAroSg0E8mkpZoFEF0nbMFTrrS1Te5stJxLuKcWgZo=; h=Date:From:To:Subject:In-Reply-To:References:From; b=cyYWbEXc5xYjQKxUhNcKeHDjbSq0jxY1YLlzqb37udsrm2rFFApYIKHTDJSSnt1HP 0dUPP88OYE4/g81PCxDZa/TvsS61sw3swYmN3Q7kpkovlz/T6xqda0tlhpEZZE2yDv 7otPywvEyWZllpaKbHE7Z5bwWcB8UAp8Bd4/VdwA= X-Riseup-User-ID: DC387D5C1C63FB88C96AFA2D1A39F0DE103B7719860280F8AE16D03B5303CA12 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews1.riseup.net (Postfix) with ESMTPSA id 4LwZkK0mz0z5vfs for ; Sun, 31 Jul 2022 08:51:52 +0000 (UTC) Date: Sun, 31 Jul 2022 10:51:49 +0200 From: Ralf Mardorf To: questions@freebsd.org Subject: Re: OT: Strange interaction between NIC, SSD and motherboard Message-ID: <20220731105149.2b893c93@archlinux> In-Reply-To: <0de31c8f-ca6b-f23e-ae03-79c02b506454@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> <0de31c8f-ca6b-f23e-ae03-79c02b506454@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: 4LwZkM4B0pz3FNF X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=cyYWbEXc; 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_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; MID_RHS_NOT_FQDN(0.50)[]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; R_SPF_ALLOW(-0.20)[+a:mx0.riseup.net]; 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 19:27:27 -0700, David Christensen wrote: >On 7/30/22 19:04, Ralf Mardorf wrote: >> On Fri, 29 Jul 2022 20:10:32 -0400, Aryeh Friedman wrote: >>> BIOS Information >>> Vendor: American Megatrends Inc. >>> Version: 1.90 >>> Release Date: 07/05/2019 >> >> This BIOS version or any other with this release date does not exist >> for B450 TOMAHAWK,see >> https://www.msi.com/Motherboard/B450-TOMAHAWK/support . > > >Another clue that I STFW and found the wrong motherboard... On Sat, 30 Jul 2022 19:25:31 -0700, David Christensen wrote: >My WAG is that there is a bug that involves the motherboard firmware, >the NIC firmware, and/or the SSD firmware. I would pick one device >and replace it. The link's B450 TOMAHAWK received an update that "Improved PCI-E device compatibility", release date 2019-11-11, IOW after 07/05/2019. Maybe for the OP's B450 TOMAHAWK BIOS such an update does exist, too. The two updates after that update mention AGESA updates. I can't comment on AGESA, but for the OP it might be worth to search the web for AGESA before updating the BIOS if AGESA is involved, since downgrades are sometimes impossible. A German article warns, seemingly AGESA updates could cause issues. OTOH if one AGESA update does cause trouble, a following AGESA update might fix that. [DE] https://www.pcgameshardware.de/Mainboard-Hardware-154107/News/AMDAGESAv21205NeueFirmwareistmitVorsichtzugeniessen-1389632/