From nobody Thu Dec 7 23:44:07 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 4SmW7t1W40z53pnM for ; Thu, 7 Dec 2023 23:44:10 +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 4SmW7s5fwvz3bZy for ; Thu, 7 Dec 2023 23:44:09 +0000 (UTC) (envelope-from pete@nomadlogic.org) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomadlogic.org; s=04242021; t=1701992647; 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=VSnQTWGs1LNvpfDMCLB26FWZSIKDxeESs4Y74OZ4EbA=; b=BffRX15zEXeWKH4LvHKJLWVLUTpY9nu9vszA5XjRXgwgtwWljRbDqQsuc0ChHEJNy1x1kt EkWDNLOQE/CBYNAV4qy89q6X4TRkRyTSnWISR0xOC5bwgDrmnuplacJbxj+ffWlDPWQq4m frj7Nk4UwLZYEHrtugyBH6uDAgmwQFU= 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 b9910b89 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Thu, 7 Dec 2023 23:44:07 +0000 (UTC) Message-ID: Date: Thu, 7 Dec 2023 15:44:07 -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-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:29802, ipnet:66.165.240.0/22, country:US] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4SmW7s5fwvz3bZy On 12/7/23 2:49 PM, Warner Losh wrote: > > > On Thu, Dec 7, 2023 at 3:38 PM Pete Wright > wrote: > > > > 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. > > > What the message means is that (a) we stopped getting interrupts from > the device and (b) when we went to check on the status of the device it > read back like missing hardware. > > So is this from inside the VM running under bhyve, or in the host that's > hosting the VM? We have different next steps depending on where it is. > OK awesome thanks for that context, so this is on a bare metal workstation. -pete -- Pete Wright pete@nomadlogic.org