From nobody Sun Jul 03 08:39:46 2022 X-Original-To: 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 7E8B787E784 for ; Sun, 3 Jul 2022 08:39:58 +0000 (UTC) (envelope-from yuri@aetern.org) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (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 4LbMnT3Z2Pz4jpn for ; Sun, 3 Jul 2022 08:39:57 +0000 (UTC) (envelope-from yuri@aetern.org) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id 33CD432005D8 for ; Sun, 3 Jul 2022 04:39:49 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Sun, 03 Jul 2022 04:39:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aetern.org; h=cc :content-transfer-encoding:content-type:date:date:from:from :in-reply-to:message-id:mime-version:reply-to:sender:subject :subject:to:to; s=fm1; t=1656837588; x=1656923988; bh=uJC0Rfqxd5 oY+VHHLdUlbKobEqjlM27PX+x1aVsXwmw=; b=GcWdmZxKj2x5YEj8OB7jeDJvDi oGf1jE0ilSFSKKABR6wGL+qskyQip+BcG4ZpZAx7dVAwA8grCKfOG5HEpSQIRIOF b8lcnVKG+vL664OmyqVS/mfHzEAAazhFmj29tFsUVRmQOn7nXSmRnL4ihnqRhntB W4MhGxuljC8w1HvqMphZYcnXHaTcCl2NS0+1XxaRumvNHMfOVcavEzse13b+pE9Z r9FeIVVD/Xs1mQw7INy5HLNw9QMJ4zoNfWrxsCjNvCEfpaerbzVGdOUSTP409oPc mTH/Wv3fPGpdCwVh+WOWmxgJAeRlI2Vb+ylcrtugZeS8fg+RVWgIXEwFqkTA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:date:feedback-id:feedback-id:from:from:in-reply-to :message-id:mime-version:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; t=1656837588; x=1656923988; bh=uJC0Rfqxd5oY+VHHLdUlbKobEqjl M27PX+x1aVsXwmw=; b=noDfRWLjBP/ukwFVtENfUDWX6c3fkJhZs4khAhasET3u z9Bi2gR7NzwwrUStolZJBiXdnjBLAYisS+ygSIYgRq8V/3nToje42qMzVuqcU1aI jcfHb6IoG9T8yCtpaQdPQ2/SKRlTZ9nxw5S/JEj6kNUWh4r3c0i6Cq1ZZI7IJl3r NWacgrgifnw0dXysVTyFAvWjZzFjqPHnQ89HHTFaqvveU9JUcwVDQmqZ3GiSlBU9 n6swx9aF3+T5bdPJmIFFAtAl1e9R66yDim3xi+z90s6WMySLmLGiXpRE88o5niup 3Fii4ps8pWzDbG/gu/7TJoOVnS4y9Qdai/eLszwhDA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrudehjedgtdekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfvhffutgfgsehtjeertd dtfeejnecuhfhrohhmpegjuhhrihcuoeihuhhrihesrggvthgvrhhnrdhorhhgqeenucgg tffrrghtthgvrhhnpeffvefffefgteeuudekhfefvdfhjeetgfejffffieetvdfhfeejff ekleegjefftdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhr ohhmpeihuhhrihesrggvthgvrhhnrdhorhhg X-ME-Proxy: Feedback-ID: i0d79475b:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Sun, 3 Jul 2022 04:39:48 -0400 (EDT) Message-ID: <262c9b6c-cfc9-090d-3cd9-2727e977fa3c@aetern.org> Date: Sun, 3 Jul 2022 11:39:46 +0300 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 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Content-Language: en-US To: current@freebsd.org From: Yuri Subject: emulated nvme on vmware workstation whines Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4LbMnT3Z2Pz4jpn X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=aetern.org header.s=fm1 header.b=GcWdmZxK; dkim=pass header.d=messagingengine.com header.s=fm2 header.b=noDfRWLj; dmarc=none; spf=pass (mx1.freebsd.org: domain of yuri@aetern.org designates 64.147.123.24 as permitted sender) smtp.mailfrom=yuri@aetern.org X-Spamd-Result: default: False [-4.60 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[aetern.org:s=fm1,messagingengine.com:s=fm2]; FREEFALL_USER(0.00)[yuri]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.24]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[current@freebsd.org]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; RCVD_COUNT_THREE(0.00)[4]; DMARC_NA(0.00)[aetern.org]; DKIM_TRACE(0.00)[aetern.org:+,messagingengine.com:+]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; MLMMJ_DEST(0.00)[current]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.24:from] X-ThisMailContainsUnwantedMimeParts: N I started seeing the following whines from emulated nvme on vmware workstation some time ago, and it seems to happen almost exclusively during the nightly periodic run: Jul 3 03:01:47 titan kernel: nvme0: RECOVERY_START 48053105730250 vs 48051555254036 Jul 3 03:01:47 titan kernel: nvme0: timeout with nothing complete, resetting Jul 3 03:01:47 titan kernel: nvme0: Resetting controller due to a timeout. Jul 3 03:01:47 titan kernel: nvme0: RECOVERY_WAITING Jul 3 03:01:47 titan kernel: nvme0: resetting controller Jul 3 03:01:47 titan kernel: nvme0: temperature threshold not supported Jul 3 03:01:47 titan kernel: nvme0: resubmitting queued i/o Jul 3 03:01:47 titan kernel: nvme0: READ sqid:10 cid:0 nsid:1 lba:8931648 len:8 Jul 3 03:01:47 titan kernel: nvme0: aborting outstanding i/o Jul 3 03:02:23 titan kernel: nvme0: RECOVERY_START 48207341204759 vs 48207032791553 Jul 3 03:02:23 titan kernel: nvme0: RECOVERY_START 48207722834338 vs 48207032791553 Jul 3 03:02:23 titan kernel: nvme0: timeout with nothing complete, resetting Jul 3 03:02:23 titan kernel: nvme0: Resetting controller due to a timeout. Jul 3 03:02:23 titan kernel: nvme0: RECOVERY_WAITING Jul 3 03:02:23 titan kernel: nvme0: resetting controller Jul 3 03:02:23 titan kernel: nvme0: temperature threshold not supported Jul 3 03:02:23 titan kernel: nvme0: aborting outstanding i/o Jul 3 03:02:23 titan kernel: nvme0: resubmitting queued i/o Jul 3 03:02:23 titan kernel: nvme0: WRITE sqid:1 cid:0 nsid:1 lba:27806528 len:8 Jul 3 03:02:23 titan kernel: nvme0: aborting outstanding i/o It does not seem to break anything, i.e. no errors from periodic, zpool status and zpool scrub do not show any issues as well, so I'm just wondering if there is some obvious reason for this. I am staying current with, well, -CURRENT and VMware Workstation versions (now at 16.2.3), and do not remember when exactly this started. There are no other VMs doing anything at that time, host system is pretty idle as well.