From nobody Sun Oct 15 16:05:57 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 4S7lVn2ZQSz4x775 for ; Sun, 15 Oct 2023 16:06:57 +0000 (UTC) (envelope-from void@f-m.fm) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4S7lVm5jdCz4NXc for ; Sun, 15 Oct 2023 16:06:56 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm3 header.b=gE0EUZQY; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=veruOWEg; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 66.111.4.27 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 567F05C0271 for ; Sun, 15 Oct 2023 12:06:56 -0400 (EDT) Received: from imap46 ([10.202.2.96]) by compute6.internal (MEProxy); Sun, 15 Oct 2023 12:06:56 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm3; t=1697386016; x=1697472416; bh=pj hm7D9I4EiwbC6PMRDg6o55gWXUkrJKM5s2iF9ekJU=; b=gE0EUZQYLV/ErEHK0x D8W1t6q/YiFAouxnQ0FXFvl0NVNqJUlr+EK6dF8CJwp6sg4wAwRxghcDx0Ya/pqy x0zYysSTWvuFt7BrRKbpGdumZuOXUZO/8uKG+ma2tCL/OgXRg5GiZkWul0Z7wsls C337lTsE3SkmYUM8aJh3ED+YWobSGUwpIZpMH7DcXR5RXArKlBL7S7agkCmEKiSC bhwrQbnXgeQ+Tu8krFFRU7s51rPr0HNJTuK/gPL4YMtT/PSfKBAtl91VdHtJM9j6 XF9g5BJMi7CL/YAcNEcZMxPoVOSAyNZIPSw01wY6/mJ957ssJF5SwcoK70F1FC30 Vonw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; t=1697386016; x=1697472416; bh=pjhm7D9I4Eiwb C6PMRDg6o55gWXUkrJKM5s2iF9ekJU=; b=veruOWEgtHs4dS2Yuouq595qDzD7p GZqrqDcbWstgb1VngXXI8mltGMbFb0zTGP7ZON9ui0FgGy1tA4mrvCiNAO8IsVLE zvagwuq78zPYBNWnfxRaQmoZ2I5oK8OzSrifVUcYAhAZkK4TgVPZdXPx+T4rFdF3 /K9ng7Ss1SmPT2uRgT1Won2+uvBm6gsNaYOIj+U23vJRYVImCExKRahB6hogYsWI /oZsJ7t+PJoREp/YyrswPItftV4Lppk8Z7kfd9sDRcUsXQH32PcrCfbbznMLPK8g n3lKkh1FLPp1SW2VAhpG6Df1JQvGlLN3ENnVkezqS7+ZpiUy5mlteHlGg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrieekgdelvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgr thhtvghrnhepieetvdeuhedthedtvdfhuefhveehvdeiledvieffheevleehgeefudelje dukedvnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep vhhoihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 12A442A20085; Sun, 15 Oct 2023 12:06:55 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.9.0-alpha0-1019-ged83ad8595-fm-20231002.001-ged83ad85 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 Message-Id: <43001417-6398-4f9c-bbaf-1ff89782fdec@app.fastmail.com> In-Reply-To: References: <90d3e532-8ea7-4eea-8e31-8c363285a156@nomadlogic.org> <2d93d966-dc4e-4448-a182-95eb8e2e13e7@app.fastmail.com> Date: Sun, 15 Oct 2023 16:05:57 +0000 From: void To: freebsd-current Subject: Re: nvme timeout issues with hardware and bhyve vm's Content-Type: text/plain X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.99 / 15.00]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.90)[-0.898]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm3,messagingengine.com:s=fm3]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.27:c]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.27:from]; XM_UA_NO_VERSION(0.01)[]; FROM_EQ_ENVFROM(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; FROM_HAS_DN(0.00)[]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[] X-Rspamd-Queue-Id: 4S7lVm5jdCz4NXc On Sun, 15 Oct 2023, at 15:53, Warner Losh wrote: > 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... The problem being reported on the 30th Sept is a panic on booting zroot because the disk couldn't be found by the loader, presumably because usb3 needed time to settle, because making it wait a while resulted in a bootable system. But all the waiting does is workaround. I don't know how to fix it permanently. The problem gets to (i guess it's called stage1 boot) where i can select what kernel to boot. At that point, i thought u-boot had completed. The reason I'm mentioning this in this thread is because the OP is reporting an issue looking on the face of it very similar to the one I saw, and i thought mentioning this here might be helpful.