From nobody Sun Oct 15 15:46:26 2023 X-Original-To: freebsd-current@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 4S7l3z1TQsz4x5qW for ; Sun, 15 Oct 2023 15:47:11 +0000 (UTC) (envelope-from void@f-m.fm) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4S7l3x63fkz4KK7 for ; Sun, 15 Oct 2023 15:47:09 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm3 header.b="lfs/HjHN"; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=tSfDr6BV; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 66.111.4.27 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 5F5C95C01C1 for ; Sun, 15 Oct 2023 11:47:09 -0400 (EDT) Received: from imap46 ([10.202.2.96]) by compute6.internal (MEProxy); Sun, 15 Oct 2023 11:47:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm3; t=1697384829; x=1697471229; bh=6k kgrqULiBiKOvdp7KBjRimeP2JUYC+XwfIPNMvRFrc=; b=lfs/HjHN3xKijegrbP OKvDAgUquDEwJccQRPrq68Fou1pnARGcPpGEZSHeCfs8qSQzngrlMZQc6awapO+t R9uMvXnwi7/5wuvGppubTIj4n2XlsU6+y1BXn/An86rnvDu3mf5VxIk8UdSNc5ek fLKTn8EnrfMkrtyqJDyYRfxUGXfeXxvxu9KwgrQoafSlTQQ6IhvaoSJnn/c8c3Ed kkBhcMSC4SDb/duf6JKEQPE76bTGeYq6caEUc1QmOkVNia6C0thrFJNzJHEA3Fi4 6DKp57j+sT8PuIDmZflzJrKGLE0xopmq5S8NtckYIjcT8ZdVuObUCA2Fsrv8F+oB fc9A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; t=1697384829; x=1697471229; bh=6kkgrqULiBiKO vdp7KBjRimeP2JUYC+XwfIPNMvRFrc=; b=tSfDr6BVkDDms9vzkWbCM/14qEqb1 Nap7gLCCVlmVWtDDKZIhIxZe1t02g6xOnWQJjONJl76/P+56bmv1dYTRBWKn0iJg b6qTe4r2Fke1pP3MRhGZRLI7mi/2rTwZ3AcerK6rI5ZTOoK2r3FvhNayHcM//yQY x/XemTeTLSWbGsmKGUv+4I8DnwyIn/D2sh0GGYhvWzJ2IrVUKaUNaOLhtkaXUUtA abhGqX3pZIz1CHQIsLzcb9brQUn4cRx25BrfTh7zBf5pAaUEU60qYCZhBadNnUot 3hnsXX+VsfflJwLSLeXJEq89qwW9jdHOAjY8rJwu0JrkMsY4AAhwnEwMw== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrieekgdekkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgr thhtvghrnhepieetvdeuhedthedtvdfhuefhveehvdeiledvieffheevleehgeefudelje dukedvnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep vhhoihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 1E6B82A20085; Sun, 15 Oct 2023 11:47:09 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.9.0-alpha0-1019-ged83ad8595-fm-20231002.001-ged83ad85 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 Message-Id: In-Reply-To: References: <90d3e532-8ea7-4eea-8e31-8c363285a156@nomadlogic.org> <2d93d966-dc4e-4448-a182-95eb8e2e13e7@app.fastmail.com> Date: Sun, 15 Oct 2023 15:46:26 +0000 From: void To: freebsd-current Subject: Re: nvme timeout issues with hardware and bhyve vm's Content-Type: text/plain X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.94 / 15.00]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.85)[-0.849]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm3,messagingengine.com:s=fm3]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.27:c]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.27:from]; XM_UA_NO_VERSION(0.01)[]; FROM_EQ_ENVFROM(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; FROM_HAS_DN(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[] X-Rspamd-Queue-Id: 4S7l3x63fkz4KK7 On Sun, 15 Oct 2023, at 15:35, Warner Losh wrote: > I've fixed all known nvme issues in current that aren't caused by other > parts of the system. If it isn't a very recent 15 or 14, then there > are known issues and you'll need to try those first. The problem manifested with a source upgrade on the 30th September. > On arm it could be a lot of things. I keep seeing problems in other > area that are hard to track down.... without the systems in hand and > time to look at complex problems it can take a while to track down. > > I'll need a simple reproducer to look at things... If you can tell me what to do, i'm happy to test. Additionally, I can provide a connected instance to you for destructive testing on arm64. It would take me about 24hrs to set up as I'd need to backup the disk. Let me know if you need it. --