From nobody Thu Dec 07 23:49:29 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 4SmWG41RMdz53ptr for ; Thu, 7 Dec 2023 23:49:32 +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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4SmWG36Wwsz3cSK; Thu, 7 Dec 2023 23:49:31 +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=1701992970; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=ZogneQpV8kLBCw8K9/WmfTZ4gSVCIkvr8uKsaWeRUKo=; b=CedN+6UdedYYjpGe4VbpeqpHXP5R554LPJIOFqpdwolwb8HLLM/yt/gcaMsUGKFVxIRm2t 8usSXF3wdpXXfmpn/mKUL20CF8FY9E0krLtBQOilbyjKph9VLtkqKc4eJhT0qUPa30QNph Ma+SftE7MkebAMvExGOqtkbAPW9BhUM= Received: from [192.168.1.240] (024-024-168-214.inf.spectrum.com [24.24.168.214]) by mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id fd23d911 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Thu, 7 Dec 2023 23:49:30 +0000 (UTC) Message-ID: <4384561a-2600-43fc-bba8-e7f5e2c676a3@nomadlogic.org> Date: Thu, 7 Dec 2023 15:49:29 -0800 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: Craig Leres , Tomoaki AOKI , freebsd-current@freebsd.org References: <90d3e532-8ea7-4eea-8e31-8c363285a156@nomadlogic.org> <0ad493d5-1c1e-4370-977a-118f46ebd677@nomadlogic.org> <0c4f8149-89dd-4635-a5ed-4766fffd2553@nomadlogic.org> <20231208080929.cfd9fca421fea81d89d2380b@dec.sakura.ne.jp> <60642a1e-1603-495f-a2d3-5f3d3c82e474@freebsd.org> From: Pete Wright In-Reply-To: <60642a1e-1603-495f-a2d3-5f3d3c82e474@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4SmWG36Wwsz3cSK On 12/7/23 3:16 PM, Craig Leres wrote: > On 12/7/23 15:09, Tomoaki AOKI wrote: >> If I myself encounter this kind of problem ON BARE METAL HARDWARE, >> I would usually suspect >> >>   *Overheating caused hang of NVMe controller or PCI bridge on SSD, or > > This would also be my first guess. > > Five years ago I had an nmve in an intel nuc that would sometimes "go to > sleep", here's the thread > > > https://lists.freebsd.org/pipermail/freebsd-hackers/2018-May/052783.html > > @imp helpfully suggested running "nvmecontrol logpage -p 2 nvme0" which > showed mine was hot (60° C/140° F)! I adjusted the fan settings in the > bios and have never had an issue since. > oh interesting, i'll run that next time it locks up. the box is well ventilated, but that's not to say its not overheating. right now its at: Temperature: 314 K, 40.85 C, 105.53 F nvemecontrol doesn't list any errors or warnings though: Media errors: 0 No. error info log entries: 0 Warning Temp Composite Time: 0 Error Temp Composite Time: 0 thanks for the tip! -pete -- Pete Wright pete@nomadlogic.org