From nobody Sun Oct 15 15:53:45 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 4S7lCp3fxJz4x67j for ; Sun, 15 Oct 2023 15:53:58 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x62a.google.com (mail-ej1-x62a.google.com [IPv6:2a00:1450:4864:20::62a]) (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 4S7lCp1jxBz4LXT for ; Sun, 15 Oct 2023 15:53:58 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x62a.google.com with SMTP id a640c23a62f3a-9b9faf05f51so556248366b.2 for ; Sun, 15 Oct 2023 08:53:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1697385236; x=1697990036; 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=N/qWBypwdt97uZ3VUAtEaB6v/USS12p8qyjM/7R0Apc=; b=w3RAw2b5nrQsyWgceeTQjqcyeue0gTPgsSooFfVz0XutBDfDpVni+aoxxKyG/MDuHz JTAyiW17puKKZiswxf+P4D0jQMh1kmkTc/WImIEAjDlzJwsllrZ85cABACvOEXdaky5P DQz5CacEOkYFGRCYR6ifbQ5w5Px/kZCufJuQln1S8FaBEXbEnkwOZhlVJq0CAg5RU8Jn eMt7kvmCTWjfrxtfAe8QgUzaum98HcGB+PNqnnLwbMU7merLWLIjPMpngv3cTLFOAbiC lUBFMsIbWD9Mi09c4gWEWkRGyLx2lSbusq0vvvOUif2MkCxTDgQWjSES0EOdDTTc4uWU VbqQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697385236; x=1697990036; 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=N/qWBypwdt97uZ3VUAtEaB6v/USS12p8qyjM/7R0Apc=; b=EA21eHQ2ZBefM0CvJMISuUSt2AY0aTeaivfnCJL8vBqygQrOitNGvMU+0UyjalyfmW E/wYggz1F063ENQ2o6YL8SO1aPScyPjcyQyWeIWl3Mn+Mmcxno6mwvQKHzeio/flepNO oMv+jrBadP6dMwVOc+Plsw94E7u/aX2raY8N/GzUmNbRdKun/Xpo6So4PKAfR/Mh9DL1 XEKQrNqMaQK2YwHYY6HCjI67knfq2AnlT2cZ+Fi5GfwmHldGypi9DY1C5cosEnoT6BYU 1npVHpK8n5GB0CRHmICWg00Y8Pqj+qDglg7hE5qEw3lt93YE43fm1qvUdEP8EPhu8rb/ Knfw== X-Gm-Message-State: AOJu0Yx8N3WYoPN231vHOK0OOSW3Bojw0eh82+/VA3anU0ju49Va81iu 7MWBf/2AZILvZKIbvmjBOkCWTpuhsPFkwwXiryXXIw== X-Google-Smtp-Source: AGHT+IGGGz3JXyizET5NW8Ny97mVB91q/pk/r2KFKSGD0ZWPwY9+EUviB0ORqwCr/XZcZx3lk3ea8cAXzi/5kyAXJPA= X-Received: by 2002:a17:906:dc94:b0:9c0:d6c2:99af with SMTP id cs20-20020a170906dc9400b009c0d6c299afmr1808175ejc.76.1697385236282; Sun, 15 Oct 2023 08:53:56 -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: From: Warner Losh Date: Sun, 15 Oct 2023 09:53:45 -0600 Message-ID: Subject: Re: nvme timeout issues with hardware and bhyve vm's To: void Cc: freebsd-current Content-Type: multipart/alternative; boundary="0000000000000e4f9c0607c34c4c" 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: 4S7lCp1jxBz4LXT --0000000000000e4f9c0607c34c4c Content-Type: text/plain; charset="UTF-8" On Sun, Oct 15, 2023, 9:47 AM void wrote: > On Sun, 15 Oct 2023, at 15:35, Warner Losh wrote: > > > 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. > > The problem manifested with a source upgrade on the 30th September. > > > 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... > > If you can tell me what to do, i'm happy to test. > > Additionally, I can provide a connected instance to you for destructive > testing on arm64. It would take me about 24hrs to set up as I'd > need to backup the disk. Let me know if you need it. > The one with the uboot traceback? I can't help you there. The report is confusing. I don't know the error / problem being reported to even know what to look at. Or is it a different thing? I'm so confused at this point. I also think we need to recreate it on as a!clean system as possible. Weird problems in the boot chain prior to loader.efi, I have little interest in and no time to look at... Warner > --0000000000000e4f9c0607c34c4c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sun, Oct 15, 2023, 9:47 AM void <void@f-m.fm> wrote:
On Sun, 15 Oct 2023, at 15:35, Warner Losh wrote:

> 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,=C2=A0 the= n there
> are known issues and you'll need to try those first.

The problem manifested with a source upgrade on the 30th September.

> 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 <= br> > time to look at complex problems it can take a while to track down. >
> I'll need a simple reproducer to look at things...

If you can tell me what to do, i'm happy to test.

Additionally, I can provide a connected instance to you for destructive testing on arm64. It would take me about 24hrs to set up as I'd
need to backup the disk. Let me know if you need it.
=

The one with the uboot = traceback? I can't help you there. The report is confusing. I don't= know the error / problem being reported to even know what to look at.=C2= =A0 Or is it a different thing? I'm so confused at this point. I also t= hink we need to recreate it on as a!clean system as possible. Weird problem= s in the boot chain prior to loader.efi, I have little interest in and no t= ime to look at...

Warner= =C2=A0
--0000000000000e4f9c0607c34c4c--