From nobody Sun Oct 15 15:27:55 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 4S7kfB4msZz4x4Tt for ; Sun, 15 Oct 2023 15:28:18 +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) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4S7kf95sMTz4G1G for ; Sun, 15 Oct 2023 15:28:17 +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=JCF12pwf; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=Yyne5sbq; 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 845EC5C026E for ; Sun, 15 Oct 2023 11:28:16 -0400 (EDT) Received: from imap46 ([10.202.2.96]) by compute6.internal (MEProxy); Sun, 15 Oct 2023 11:28:16 -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=1697383696; x=1697470096; bh=qv ehus+Y7ZeGXVJ6tDMieyUeKV4fKx9mG3rFOCnD38I=; b=JCF12pwfHbUIomU11c CLvZPpkmqyqWw2TsFoSbBCCassVlLyR9sEYduqyjndDQXUlHJPk7TpKEq/rrhoLc HhugNp5eoZfPQEPo2HOh1tT19MgH4DgfJuvJnNIMbMJ0GEVpZBDmaDBE0JPFIG+B gjUChvm+VPJtkS0kqJMCdPxbESlRVbfykVsr00fkfLFut/5LtFVDJesrHDB1MaAA eBJErIcFlfdvbqG6r0weshCECGQbqQO5x/RMlIsZ0BFAJVf6dMZBjHktZctX5jYw Jh8D+4UFLJA7bjSM8y1Rp2faBCkGtFA5EGbNDTpG+j/LUBqqcht3IByrbrYOTUU0 GeLw== 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=1697383696; x=1697470096; bh=qvehus+Y7ZeGX VJ6tDMieyUeKV4fKx9mG3rFOCnD38I=; b=Yyne5sbqHwQsLyCIc8LIyEWldqeLC ih5kr7oUbRz5Lw1ssvTsvhlCYeHTqoxhfuQ9LHtePmF+iyfiVXrjt8eUrKRTX8cd Y+/R6vGcHORCNt1JyCIeD9TnvqwewipFTrt0ZEDixg43CnU2V/G4JkyKhiCMm7hg ku1GPQrqxT/orXYavAM/kkCLxMpPu/UO1xNnOk0AehGDfkVPJMuZWarOJdFORxg0 Mi3MEVHpwULQkfPHfebNH89DB3OY92xB0PMElXZk+D+PFAVZiNBp/Q1bw7DZJQjt uc1UQTv278Q2HxXcwT1ki7ZduqRS1wfkWMOhX5/dqJLeZqnj40WAXfSRA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrieekgdekgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgr thhtvghrnhepieeiheeutdduieekudeikedvffeggfefvedvfeehffeguddthedttedvhf evkefhnecuffhomhgrihhnpehfrhgvvggsshgurdhorhhgnecuvehluhhsthgvrhfuihii vgeptdenucfrrghrrghmpehmrghilhhfrhhomhepvhhoihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 43F0A2A20085; Sun, 15 Oct 2023 11:28:16 -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: <2d93d966-dc4e-4448-a182-95eb8e2e13e7@app.fastmail.com> In-Reply-To: <90d3e532-8ea7-4eea-8e31-8c363285a156@nomadlogic.org> References: <90d3e532-8ea7-4eea-8e31-8c363285a156@nomadlogic.org> Date: Sun, 15 Oct 2023 15:27:55 +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 [-5.07 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.98)[-0.979]; 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]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.27:from]; XM_UA_NO_VERSION(0.01)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; 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:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[] X-Rspamd-Queue-Id: 4S7kf95sMTz4G1G Hi, On Fri, 13 Oct 2023, at 03:40, Pete Wright wrote: > I had similar issues on my workstation as well. Scrubbing the NVMe > device on my real-hardware workstation hasn't turned up any issues, but > the system has locked up a handful of times. > > Just curious if others have seen the same, or if someone could point me > in the right direction... I've seen similar issues (zpool timeout) in a quite different context (arm64, usb3-connected disk, not-vm) which i posted about here: https://lists.freebsd.org/archives/freebsd-arm/2023-September/003122.html Unsure if these have been fixed yet?