From nobody Fri Dec 08 00:19:12 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 4SmWwc29xFz52sfK for ; Fri, 8 Dec 2023 00:19:28 +0000 (UTC) (envelope-from ctuffli@gmail.com) Received: from mail-vs1-f54.google.com (mail-vs1-f54.google.com [209.85.217.54]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SmWwb41Szz4FLj for ; Fri, 8 Dec 2023 00:19:27 +0000 (UTC) (envelope-from ctuffli@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-vs1-f54.google.com with SMTP id ada2fe7eead31-46495e57cdeso345830137.3 for ; Thu, 07 Dec 2023 16:19:27 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701994764; x=1702599564; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=HAVrHdtV1jEq+MCAk+4FhZjIcnz9rKMTam6ZnqeuaJY=; b=tcdpEAHmkNM10HJMaFRZfv3jL2MkgFf/x+4OgUSvVx9IU0U3IT9BmFO/FL0kv+BfGj Q3k4O1hqwxVK6iTYg0F+w3wEJr1O+jAyDyGAe429CoVdA4j9sXhArlufRiY6vHrLv4BH 2mBV95pexAUZpZxHDqnEQjblUzKaBxNquLTJldqTP+/MW5g7e7m2IgGyq7usiFCxnu86 dh6TBeFHhmSKQne/RutvI520d+Bppb5FajbZWv6aSYMAN5yCFfKM46pwJFQ+/xsULQ61 mquIKpWJ6KZZJ5Q96tbFKSFFKcz9Z2oTfwELD5t7nO132tX6FSOLSaepABp9hlgj9QHS 9lyg== X-Gm-Message-State: AOJu0Yx1NRIaoYTf1Ey51WGtxYC8+VCBsFdn6ZkDUGSrJrsiHc9QiTwo rMz8brbyJzg67IagoGcVF2+6WYTtYTo= X-Google-Smtp-Source: AGHT+IFrv8OOwBRqBpyqw61GCd2HfCWaNGLLcvwmJ9HrDSPwIxwlvULf8Uun15XXAs83LymKr4bszA== X-Received: by 2002:a1f:cc42:0:b0:495:bd61:a184 with SMTP id c63-20020a1fcc42000000b00495bd61a184mr1989096vkg.2.1701994764262; Thu, 07 Dec 2023 16:19:24 -0800 (PST) Received: from mail-vs1-f53.google.com (mail-vs1-f53.google.com. [209.85.217.53]) by smtp.gmail.com with ESMTPSA id o189-20020a1f73c6000000b004b2bf0a3e95sm84190vkc.31.2023.12.07.16.19.23 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 07 Dec 2023 16:19:24 -0800 (PST) Received: by mail-vs1-f53.google.com with SMTP id ada2fe7eead31-46495e57cdeso345823137.3 for ; Thu, 07 Dec 2023 16:19:23 -0800 (PST) X-Received: by 2002:a1f:6ecb:0:b0:4b3:da:e36f with SMTP id j194-20020a1f6ecb000000b004b300dae36fmr2227160vkc.9.1701994763577; Thu, 07 Dec 2023 16:19:23 -0800 (PST) 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 References: <90d3e532-8ea7-4eea-8e31-8c363285a156@nomadlogic.org> <0ad493d5-1c1e-4370-977a-118f46ebd677@nomadlogic.org> <0c4f8149-89dd-4635-a5ed-4766fffd2553@nomadlogic.org> In-Reply-To: From: Chuck Tuffli Date: Thu, 7 Dec 2023 16:19:12 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: nvme timeout issues with hardware and bhyve vm's To: Pete Wright Cc: Warner Losh , FreeBSD Current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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:15169, ipnet:209.85.128.0/17, country:US] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4SmWwb41Szz4FLj On Thu, Dec 7, 2023 at 2:39=E2=80=AFPM Pete Wright wr= ote: ... > 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? Does the device support Persistent Log pages (LID=3D0x0d)? If so, it might be interesting to dump those. --chuck