From nobody Fri Jun 30 17:25:27 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 4Qt2Jz6czPz4kvLm for ; Fri, 30 Jun 2023 17:25:39 +0000 (UTC) (envelope-from ctuffli@gmail.com) Received: from mail-qt1-f171.google.com (mail-qt1-f171.google.com [209.85.160.171]) (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 4Qt2Jz4TBvz3sR6; Fri, 30 Jun 2023 17:25:39 +0000 (UTC) (envelope-from ctuffli@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-qt1-f171.google.com with SMTP id d75a77b69052e-3fde82c8ca7so17527241cf.3; Fri, 30 Jun 2023 10:25:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688145938; x=1690737938; 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=YbaopXoYt/GQHWYEfYkV+s7vVd8IipQ2PCughWEpitc=; b=Tv9+4dRND4doA/l1x3frWfdXQd3TG5Sqree66ZuK/Yd3z1Ee/WPC8A5ZL6ljnK3YZ/ bOxuXzS4HxuCwoJjnIL6M87vMxHYk/1LabsAeuBxbvyUntoNDMZkU1E0GEBXdoDFZc+h a3E+Tamy8CeCXt3KxOKqpy/lc68iY/YJ1P99uHGDsW7Q83S5ROZ2RPonOKgFU6tXamTo bJ24+BvmwL6AdHE4feY1/QQH3oil4/Q85OBmT6/Vwfi3sabru8hpjEyH5oFWK/0FL0pP 32E2XNMoWfMhvkAjI4q6wzz0NZGFagydwefb7Blw508/YGbwEP34j45N+5IVWImpDxWu lr4Q== X-Gm-Message-State: ABy/qLa4DHPMAu7sIKeNQETLv1R7DHGjYM9DSbDyMi8iZo4x98jJDUua qtW0zMv5WpfuBmbk612H+nGVBujc/o4= X-Google-Smtp-Source: ACHHUZ4J5GAdwTMz5PsUSRj2EKQIQmWrRiM/1W6iI+e6gKA/dVeJRdfi2yrAPHvqiTxrR30RT5PXhQ== X-Received: by 2002:a05:622a:294:b0:3f5:3f0f:3744 with SMTP id z20-20020a05622a029400b003f53f0f3744mr4596669qtw.52.1688145938358; Fri, 30 Jun 2023 10:25:38 -0700 (PDT) Received: from mail-qt1-f177.google.com (mail-qt1-f177.google.com. [209.85.160.177]) by smtp.gmail.com with ESMTPSA id r15-20020ac85e8f000000b00403214e8862sm3377565qtx.33.2023.06.30.10.25.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 30 Jun 2023 10:25:38 -0700 (PDT) Received: by mail-qt1-f177.google.com with SMTP id d75a77b69052e-40320e38b64so17488431cf.2; Fri, 30 Jun 2023 10:25:38 -0700 (PDT) X-Received: by 2002:ac8:7d8f:0:b0:403:2fe0:a437 with SMTP id c15-20020ac87d8f000000b004032fe0a437mr4241666qtd.3.1688145937977; Fri, 30 Jun 2023 10:25:37 -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: <664978DE-B510-4C14-A559-541C3AB00D50@FreeBSD.org> In-Reply-To: <664978DE-B510-4C14-A559-541C3AB00D50@FreeBSD.org> From: Chuck Tuffli Date: Fri, 30 Jun 2023 10:25:27 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: nvme related(?) panic on recent -CURRENT To: Juraj Lutter Cc: FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4Qt2Jz4TBvz3sR6 X-Spamd-Bar: ---- 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-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N On Thu, Jun 29, 2023 at 12:47=E2=80=AFPM Juraj Lutter wr= ote: > > With recent -current, following occured: > > db> bt > Tracing pid 0 tid 100063 td 0xfffffe00c5c35e40 > kdb_enter() at kdb_enter+0x32/frame 0xfffffe00c5e31c90 > vpanic() at vpanic+0x181/frame 0xfffffe00c5e31ce0 > panic() at panic+0x43/frame 0xfffffe00c5e31d40 > nvme_ctrlr_identify() at nvme_ctrlr_identify+0x10e/frame 0xfffffe00c5e31d= 90 > nvme_ctrlr_start() at nvme_ctrlr_start+0x91/frame 0xfffffe00c5e31e10 > nvme_ctrlr_reset_task() at nvme_ctrlr_reset_task+0xec/frame 0xfffffe00c5e= 31e40 > taskqueue_run_locked() at taskqueue_run_locked+0x182/frame 0xfffffe00c5e3= 1ec0 > taskqueue_thread_loop() at taskqueue_thread_loop+0xc2/frame 0xfffffe00c5e= 31ef0 > fork_exit() at fork_exit+0x7d/frame 0xfffffe00c5e31f30 > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00c5e31f30 > --- trap 0, rip =3D 0, rsp =3D 0, rbp =3D 0 =E2=80=94 > > machine is a bhyve guest. Did bhyve log any warnings or errors? I'm curious if its NVMe emulation did something dumb or itself noticed an issue. --chuck