From nobody Sat Oct 14 02:34:26 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 4S6nWf2krJz4x8mb for ; Sat, 14 Oct 2023 02:34:22 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x632.google.com (mail-ej1-x632.google.com [IPv6:2a00:1450:4864:20::632]) (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 4S6nWd5qkkz4FHD for ; Sat, 14 Oct 2023 02:34:21 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x632.google.com with SMTP id a640c23a62f3a-9b2cee55056so467025166b.3 for ; Fri, 13 Oct 2023 19:34:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1697250860; x=1697855660; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Hj1Cj0uX5MOmkHBdeuZKZgp819CvW/N6KkEGJFM/OtY=; b=qsk7Augo58qJi1TiOzEcTw8LVuJjtjVx1/K2zoUCun4ZmdSiC9RjOCyIYHZHC9Ga0q WpEQynjY1eEIRLARlI/yTrXtmsox+kpMywrN8Ew6SR9im2Z+2Q2c/DtrhmPFSnORmlx/ YvxRM+GqiwFLmxLePgzLoQZEMljrwgSYrDLDcOrbPuvWqZh0jx7t8TuemOV7vd3cASrm 1IbWKQh2kEeeSTXTN+ToiSeRq7dOm4PbJhgLe6Gc2HdNLDXPM8UnDWY7BxyKLxNO7v0O C288Kg/qLoneKaT4GbNxBec7QGreoWHir6ZF12wgrGUlS4AWoL9kcHLlsmklp20B5wDC aWnA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697250860; x=1697855660; h=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=Hj1Cj0uX5MOmkHBdeuZKZgp819CvW/N6KkEGJFM/OtY=; b=NF3waoNTcvg2m/EYny+nBZHZ34NzE6DUHeUCYDBgkHs0DvMjSChFwD7RJtfhrChLN0 pqysqHwK81hYWEtZe9S1U/5S9C7NTLJesuVO9tb2ZdYOomL95qAx5sZyuehzELRxpgep uSmSk1X6p5wAT8NSktPNLX+WfSyiejyINdF6wO6BU/mzUOOat+0BoPB9Jx9lpjwrbc0r YXjvr7XvYQaZH/pWnlQuh0ll9PBDTSEHnLiHPCvw3zVn6mvcwAGBYGUn9GAzuZHRP20w ZKq5mnvhyyHyvEeKRX9bqPkLwl2OdIUpmU9oskNe00d+565Rp3zyI7uSmR04lAf+h7tG mCDw== X-Gm-Message-State: AOJu0YwDdUrkiA6sZF606w2kBQCjYtiAjbGFRLs6QIyZ9KqbnYoSnlGD 6LNxfonP9lZP2zU7KMrFpz60Z2KnXbSiajW7aTLeOTqUuIDqlOw4 X-Google-Smtp-Source: AGHT+IH0Rg4p5idbnYsnHVsvMsm0V7OxyUSMQM/fJf3Wl3hgyiWwccUlUmxeHcuIZtxElK1DDQxmH5k+SVhJcYjoHW8= X-Received: by 2002:a17:906:cb:b0:9ae:4eb7:ae8b with SMTP id 11-20020a17090600cb00b009ae4eb7ae8bmr28269273eji.7.1697250860196; Fri, 13 Oct 2023 19:34:20 -0700 (PDT) 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: <0c4f8149-89dd-4635-a5ed-4766fffd2553@nomadlogic.org> From: Warner Losh Date: Fri, 13 Oct 2023 20:34:26 -0600 Message-ID: Subject: Re: nvme timeout issues with hardware and bhyve vm's To: Pete Wright Cc: FreeBSD Current Content-Type: multipart/alternative; boundary="0000000000009df5b20607a40240" X-Spamd-Bar: ---- 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:2a00:1450::/32, country:US] X-Rspamd-Queue-Id: 4S6nWd5qkkz4FHD --0000000000009df5b20607a40240 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Oct 13, 2023 at 11:47=E2=80=AFAM Pete Wright = wrote: > > > On 10/13/23 6:24 AM, Warner Losh wrote: > > > > > > On Thu, Oct 12, 2023, 10:53 PM Pete Wright > > wrote: > > > > > > > > On 10/12/23 8:45 PM, Warner Losh wrote: > > > What version is that kernel? > > > > oh dang i sent this to the wrong list, i'm not running current. th= e > > hypervisor and vm are both 13.2 and my workstation is a recent 14.0 > > pre-release build. i'll do more homework tomorrow and post to > > questions > > or a more appropriate list. > > > > > > Are the messages from the VM? Stable/14 should have the important nvme > > changes I've made lately. The bhyve in 13.2 is lacking a number of nvme > > fixes that have gone into current and stable/14. It's hard to say where > > the fault is coming from. > > > > > 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. Warner --0000000000009df5b20607a40240 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Fri, Oct 13, 2023 at 11:47=E2=80= =AFAM Pete Wright <pete@nomadlogi= c.org> wrote:


On 10/13/23 6:24 AM, Warner Losh wrote:
>
>
> On Thu, Oct 12, 2023, 10:53 PM Pete Wright <pete@nomadlogic.org
> <mailto:pe= te@nomadlogic.org>> wrote:
>
>
>
>=C2=A0 =C2=A0 =C2=A0On 10/12/23 8:45 PM, Warner Losh wrote:
>=C2=A0 =C2=A0 =C2=A0 > What version is that kernel?
>
>=C2=A0 =C2=A0 =C2=A0oh dang i sent this to the wrong list, i'm not = running current.=C2=A0 the
>=C2=A0 =C2=A0 =C2=A0hypervisor and vm are both 13.2 and my workstation = is a recent 14.0
>=C2=A0 =C2=A0 =C2=A0pre-release build.=C2=A0 i'll do more homework = tomorrow and post to
>=C2=A0 =C2=A0 =C2=A0questions
>=C2=A0 =C2=A0 =C2=A0or a more appropriate list.
>
>
> Are the messages from the VM? Stable/14 should have the important nvme=
> changes I've made lately. The bhyve in 13.2 is lacking a number of= nvme
> fixes that have gone into current and stable/14. It's hard to say = where
> the fault is coming from.
>


the messages i posted in the start of the thread are from the VM itself (13.2-RELEASE).=C2=A0 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 effort= s
on my workstation, it seemed to happen regularly so hopefully i can find a repo case.

Let me now if you see simi= lar messages in stable/14. I think I've fixed all the=C2=A0
i= ssues with timeouts, though you shouldn't ever seem them in a vm setup<= /div>
unless something else weird is going on.

Warner
--0000000000009df5b20607a40240--