From nobody Fri Oct 13 17:47:36 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 4S6Yr04qKwz4wYWr for ; Fri, 13 Oct 2023 17:47:44 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mail.nomadlogic.org (mail.nomadlogic.org [66.165.241.226]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.nomadlogic.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4S6Yr023NKz4M9j for ; Fri, 13 Oct 2023 17:47:44 +0000 (UTC) (envelope-from pete@nomadlogic.org) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nomadlogic.org; s=04242021; t=1697219257; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=6IjYQStR+shGBrNznB5LGFbmzTAsq6U2l0icSoWa/ns=; b=s5n1gT9Bw8xhiFwceEzuc9Xq5NUv0dT1dIk5ZFlLlBLKY5PCqRfOwDAJmOYZ28g3Z26bXY nR4GNDLoPU77ZaCJUNindW6Wlkvsc71rDb3V7DyTYNieBtoqB4m2qpLQhAhWqLhJtj/qdc VxrmZLBZW9vRDuC86sYYNNLFeTCDPQc= Received: from [192.168.1.240] (cpe-24-24-168-214.socal.res.rr.com [24.24.168.214]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 7ce3c543 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Fri, 13 Oct 2023 17:47:36 +0000 (UTC) Message-ID: <0c4f8149-89dd-4635-a5ed-4766fffd2553@nomadlogic.org> Date: Fri, 13 Oct 2023 10:47:36 -0700 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 User-Agent: Mozilla Thunderbird Subject: Re: nvme timeout issues with hardware and bhyve vm's Content-Language: en-US To: Warner Losh Cc: FreeBSD Current References: <90d3e532-8ea7-4eea-8e31-8c363285a156@nomadlogic.org> <0ad493d5-1c1e-4370-977a-118f46ebd677@nomadlogic.org> From: Pete Wright In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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:29802, ipnet:66.165.240.0/22, country:US] X-Rspamd-Queue-Id: 4S6Yr023NKz4M9j On 10/13/23 6:24 AM, Warner Losh wrote: > > > On Thu, Oct 12, 2023, 10:53 PM Pete Wright > wrote: > > > > On 10/12/23 8:45 PM, Warner Losh wrote: > > What version is that kernel? > > oh dang i sent this to the wrong list, i'm not running current.  the > hypervisor and vm are both 13.2 and my workstation is a recent 14.0 > pre-release build.  i'll do more homework tomorrow and post to > questions > or a more appropriate list. > > > Are the messages from the VM? Stable/14 should have the important nvme > changes I've made lately. The bhyve in 13.2 is lacking a number of nvme > fixes that have gone into current and stable/14. It's hard to say where > the fault is coming from. > the messages i posted in the start of the thread are from the VM itself (13.2-RELEASE). The zpool on the hypervisor (13.2-RELEASE) showed no such issues. Based on your comment about the improvements in 14 I'll focus my efforts on my workstation, it seemed to happen regularly so hopefully i can find a repo case. thanks warner! -pete -- Pete Wright pete@nomadlogic.org