From nobody Sun Oct 15 15:35:18 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 4S7kpX55Vwz4x4t0 for ; Sun, 15 Oct 2023 15:35:32 +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 4S7kpX2N8dz4H8n for ; Sun, 15 Oct 2023 15:35:32 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x632.google.com with SMTP id a640c23a62f3a-9bf0ac97fdeso140480966b.2 for ; Sun, 15 Oct 2023 08:35:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1697384130; x=1697988930; 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=/t9GH0CCKbZDG+gj2p1snkvmp6K+hoy4aOOcnhF4Jj8=; b=cBqiDS29u1Gn4zDadL3BT6sH4Xgh7EPYx0YrkHSBBLqErLgg7SGgar7XbAIffrYq3U cVTFtRIYMgZQKYjDAGOKnbhYzkDtzL8S2fBqTUxPkc8uQtZ8voG5XfPUGRWUGbkZXh0H 95Mc3kFHUQUnYcl6m2GMPMEM/r+JYFJkBlJiGNKbqX0Vepo78T6boB7mQsfZGxVnCcxE rwp3dLBPgkzyy+JSLYVLRXMpQ9oKeWInyCYsX5RJ1Xhscbo5LAKeVZCw0HyDFpRkw4/I sCkGnb48m4rXrKs6q47iZs5qxp+p7Umt7bSsaQacf7EOc9stes5gw9r0NVGN68XIDTge /sQw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697384130; x=1697988930; 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=/t9GH0CCKbZDG+gj2p1snkvmp6K+hoy4aOOcnhF4Jj8=; b=lmYx+xTKgMOGtzbyzdyoMyF/iH+SNR0E3fuvvN85zwV0f5D7gHzXFLlQCFwxhBmEYC qyXxCexTHwmnYeXLupilyZ4+jo8CHmTtjl/eT4Kol4MvB9CycRS7nYFXDH9gIIAZiq+4 3RPLVICJekNWvmjc+ANNMQ9lZPtiXVr7yTIR/AFNDxmBJjVmbc1U1VRWWjzbd+WSdHBU CbdRij/Sy45bXi8lYjYEEk1M2b1j8d2DkcHmsImEd9A6dhORfB8xgFmU0HtytEKYdoAn Dtz3Z0AA1oU/L8+Zndm4RXdujkp1O7D5JfHez9T2SN+GElMm6ai4KnE3qUKilOxnhJeU ZnhA== X-Gm-Message-State: AOJu0Yz66n0xf/OglP5ZAy1dGGzc1FDC42EVt18cNfIvhnDhCll1d0Zo af8s+tgwJN3jDH3JsUlmiZM9ERkq7tp3ND9n9j9t1Gmfxt4xxHbWne0= X-Google-Smtp-Source: AGHT+IGJaOJr6D3QAAGnjI9iXi0Qtv5iyVNurQlMU3p+kjxgD42sAMHY1bN7uhwxXStFbfVBYOKlm0BWGj2Ui1lE/0I= X-Received: by 2002:a17:906:d54f:b0:9be:7de2:927c with SMTP id cr15-20020a170906d54f00b009be7de2927cmr3579904ejc.70.1697384129777; Sun, 15 Oct 2023 08:35:29 -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> <2d93d966-dc4e-4448-a182-95eb8e2e13e7@app.fastmail.com> In-Reply-To: <2d93d966-dc4e-4448-a182-95eb8e2e13e7@app.fastmail.com> From: Warner Losh Date: Sun, 15 Oct 2023 09:35:18 -0600 Message-ID: Subject: Re: nvme timeout issues with hardware and bhyve vm's To: void Cc: freebsd-current Content-Type: multipart/alternative; boundary="0000000000001a6abe0607c30a7a" 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: 4S7kpX2N8dz4H8n --0000000000001a6abe0607c30a7a Content-Type: text/plain; charset="UTF-8" On Sun, Oct 15, 2023, 9:28 AM void wrote: > Hi, > > On Fri, 13 Oct 2023, at 03:40, Pete Wright wrote: > > I had similar issues on my workstation as well. Scrubbing the NVMe > > device on my real-hardware workstation hasn't turned up any issues, but > > the system has locked up a handful of times. > > > > Just curious if others have seen the same, or if someone could point me > > in the right direction... > > I've seen similar issues (zpool timeout) in a quite different context > (arm64, usb3-connected disk, not-vm) which i posted about here: > > https://lists.freebsd.org/archives/freebsd-arm/2023-September/003122.html > > Unsure if these have been fixed yet? > I've fixed all known nvme issues in current that aren't caused by other parts of the system. If it isn't a very recent 15 or 14, then there are known issues and you'll need to try those first. On arm it could be a lot of things. I keep seeing problems in other area that are hard to track down.... without the systems in hand and time to look at complex problems it can take a while to track down. I'll need a simple reproducer to look at things... Warner > --0000000000001a6abe0607c30a7a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sun, Oct 15, 2023, 9:28 AM void <void@f-m.fm> wrote:
Hi,

On Fri, 13 Oct 2023, at 03:40, Pete Wright wrote:
> I had similar issues on my workstation as well.=C2=A0 Scrubbing the NV= Me
> device on my real-hardware workstation hasn't turned up any issues= , but
> the system has locked up a handful of times.
>
> Just curious if others have seen the same, or if someone could point m= e
> in the right direction...

I've seen similar issues (zpool timeout) in a quite different context <= br> (arm64, usb3-connected disk, not-vm) which i posted about here:

https://lists.fr= eebsd.org/archives/freebsd-arm/2023-September/003122.html

Unsure if these have been fixed yet?

I've fixed all known nvme issues = in current that aren't caused by other parts of the system. If it isn&#= 39;t a very recent 15 or 14,=C2=A0 then there are known issues and you'= ll need to try those first.

On arm it could be a lot of things. I keep seeing problems in other are= a that are hard to track down.... without the systems in hand and time to l= ook at complex problems it can take a while to track down.

I'll need a simple reproducer to loo= k at things...=C2=A0

War= ner=C2=A0
--0000000000001a6abe0607c30a7a--