From nobody Thu Dec 7 22:38:37 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 4SmThS4RPzz53kN3 for ; Thu, 7 Dec 2023 22:38:48 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [66.165.241.226]) (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 4SmThR0ZY3z3Nm2 for ; Thu, 7 Dec 2023 22:38:47 +0000 (UTC) (envelope-from pete@nomadlogic.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=nomadlogic.org header.s=04242021 header.b=dipBMxDg; spf=pass (mx1.freebsd.org: domain of pete@nomadlogic.org designates 66.165.241.226 as permitted sender) smtp.mailfrom=pete@nomadlogic.org; dmarc=pass (policy=quarantine) header.from=nomadlogic.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomadlogic.org; s=04242021; t=1701988718; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=QTANYxtBfVGjHsqhqZcODUXkF5P9yPX0UOBF2xVn3DU=; b=dipBMxDgH1mVmKERKvKPbJKNjML1zpDTP7vWAuVI9YMFp3mgLHqTNez35/Eu9aj/B9QNPQ RINYd0OZJ5fSIC1l8/ksaZ0XlhJLpkktTgwj+DbF6DPgZQ/9aH0RqWRPgUawyxliPIWd2e Qf6uRMyZtaZheH0TEPaE/kZNcs68Lu8= Received: from [192.168.1.240] (024-024-168-214.inf.spectrum.com [24.24.168.214]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id fc295d87 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Thu, 7 Dec 2023 22:38:38 +0000 (UTC) Message-ID: Date: Thu, 7 Dec 2023 14:38:37 -0800 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 Thunderbird Subject: Re: nvme timeout issues with hardware and bhyve vm's Content-Language: en-US To: Warner Losh Cc: FreeBSD Current References: <90d3e532-8ea7-4eea-8e31-8c363285a156@nomadlogic.org> <0ad493d5-1c1e-4370-977a-118f46ebd677@nomadlogic.org> <0c4f8149-89dd-4635-a5ed-4766fffd2553@nomadlogic.org> From: Pete Wright In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-3.95 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.96)[-0.960]; DMARC_POLICY_ALLOW(-0.50)[nomadlogic.org,quarantine]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[nomadlogic.org:s=04242021]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:29802, ipnet:66.165.240.0/22, country:US]; FROM_EQ_ENVFROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[nomadlogic.org:+]; ARC_NA(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; RCVD_TLS_ALL(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4SmThR0ZY3z3Nm2 X-Spamd-Bar: --- On 10/13/23 7:34 PM, Warner Losh wrote: > > > the messages i posted in the start of the thread are from the VM itself > (13.2-RELEASE).  The zpool on the hypervisor (13.2-RELEASE) showed no > such issues. > > Based on your comment about the improvements in 14 I'll focus my > efforts > on my workstation, it seemed to happen regularly so hopefully i can > find > a repo case. > > > Let me now if you see similar messages in stable/14. I think I've fixed > all the > issues with timeouts, though you shouldn't ever seem them in a vm setup > unless something else weird is going on. > Hi Warner, just resurfacing this thread because I've had a few lockups on my workstation running 14.0-STABLE. I was able to capture a photo of the hang and this seems to be the most important line: nvme0: Resetting controller due to a timeout and possible hot unplug. When I scan the device after reboot I don't see any errors, but if there is a particular thing I should check via nvmecontrol please let me know. Also, since it mentions possible hot unplug I wonder if this is hardware/firmware related to my system? Anyway, haven't found a repro case yet but it has locked up a few times the past two weeks. -pete -- Pete Wright pete@nomadlogic.org