From nobody Thu Jun 29 20:01:16 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 4QsTqF641mz4jppf for ; Thu, 29 Jun 2023 20:01:29 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (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 4QsTqF5bNhz3R8g for ; Thu, 29 Jun 2023 20:01:29 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-lf1-x135.google.com with SMTP id 2adb3069b0e04-4fb960b7c9dso1778842e87.0 for ; Thu, 29 Jun 2023 13:01:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1688068888; x=1690660888; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=85DDZ0BUKPm30L7EItvgLz52uyegL73rRKt/tPSBeHo=; b=Zie63uwTSQ2kKs5QMz1nVxvamL2cNNkbLB3NgY1tf0q4pI6G4hYHrHoFE4v3qG5KmV y7n9Jr8YVN6/xi75l7h+bLWUySF3FMoAUN0ymdJrTREob2B2nlnlin4lNbxfOtWniXys GmgzkTytrPXRln+mqrQwZCX+9sOGJvAHolkNRK+YvKM0Rzdg7G1WpgkobNxuH9X5cPiA EgBX6ds4zXlCDs6hVvaW8aahCyvOZPx+mpt4ejihO82/VwDraztWJhrQ1zVEBaGH4BGT dFJvD/ITz6ZFuGRJLnzS32SIkBsslIdhU2aOwHhak/MRG2GEOwRgBFHt1n+U3aVmMsJ0 AzLw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688068888; x=1690660888; 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=85DDZ0BUKPm30L7EItvgLz52uyegL73rRKt/tPSBeHo=; b=dl4OoHe5W4fa++pE9Q3Y3umFJJNvGMUmzSDjotkhT8RMVofo7hKjAUQVTawFmfSiY8 ZjpR/Ez7tOnH0YgqIKgJBYB4BQB3nsscjsVSbCGgklDTzKocYdClDmyX2bUOrT4sCYCN kc2J13ltuiTBFGPhVV7CceasprqnsojcpH/JpL8w4u94Kh2j5MzFhvGjMdQEm3FiSGaq jSknt5MKr8G3Dv3LZCuMuuLT1SO7guFvskl6wqvHBk6vC33DWJBPOZndx7pclI4Zc1Vd /PAapCmHT/jzjKe7+PbfJ5aa1WZDHvhqQDbPDxfCKcA5u5kZZ53bgz/lmyOIrj6X7rrA Cyrw== X-Gm-Message-State: ABy/qLY9XQzkdnysq2b8RXanj9Iqeu+k/0hckqZFA+Pt4rGz5ZcHGNJi mhBmm1CkWZAVaVLU6KzxHCHtUoA74O8OsZnbZxUMJJAWydJ2p+P0 X-Google-Smtp-Source: APBJJlGAbDfJc8h52vwB4R+5aYTsKqOKNyCl1FSrjTcBp5sO6O00oYjSTFMU5AVLwXaNZ7pvNKnoVGB6Fs2R7ShtW4o= X-Received: by 2002:a19:ab0a:0:b0:4fb:822d:83ab with SMTP id u10-20020a19ab0a000000b004fb822d83abmr642913lfe.20.1688068887640; Thu, 29 Jun 2023 13:01:27 -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: Warner Losh Date: Thu, 29 Jun 2023 14:01:16 -0600 Message-ID: Subject: Re: nvme related(?) panic on recent -CURRENT To: Juraj Lutter Cc: FreeBSD CURRENT Content-Type: multipart/alternative; boundary="000000000000679eaf05ff4a2af6" X-Rspamd-Queue-Id: 4QsTqF5bNhz3R8g X-Spamd-Bar: ---- 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-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000679eaf05ff4a2af6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable What's the panic string? On Thu, Jun 29, 2023, 1:47 PM Juraj Lutter wrote: > 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 > 0xfffffe00c5e31e40 > taskqueue_run_locked() at taskqueue_run_locked+0x182/frame > 0xfffffe00c5e31ec0 > taskqueue_thread_loop() at taskqueue_thread_loop+0xc2/frame > 0xfffffe00c5e31ef0 > 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. > > otis > > > =E2=80=94 > Juraj Lutter > XMPP: juraj (at) lutter.sk > GSM: +421907986576 > > > --000000000000679eaf05ff4a2af6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
What's the panic string?

On Thu, Jun 29, 2023, 1:47 PM= Juraj Lutter <otis@freebsd.org&= gt; wrote:
With recent -current, fo= llowing 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 0xfffffe00c5e31d90=
nvme_ctrlr_start() at nvme_ctrlr_start+0x91/frame 0xfffffe00c5e31e10
nvme_ctrlr_reset_task() at nvme_ctrlr_reset_task+0xec/frame 0xfffffe00c5e31= e40
taskqueue_run_locked() at taskqueue_run_locked+0x182/frame 0xfffffe00c5e31e= c0
taskqueue_thread_loop() at taskqueue_thread_loop+0xc2/frame 0xfffffe00c5e31= ef0
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.

otis


=E2=80=94
Juraj Lutter
XMPP: juraj (at) lutter.sk
GSM: +421907986576


--000000000000679eaf05ff4a2af6--