From nobody Mon Jun 26 17:25:42 2023 X-Original-To: bugs@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 4QqZVv2p1mz4kZZy for ; Mon, 26 Jun 2023 17:25:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QqZVv1kvgz3NZ0 for ; Mon, 26 Jun 2023 17:25:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1687800343; 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=Y/vD7p14Fkgo9fuJ7no7gkf00Nyf1cW4VJLrlvPjsbM=; b=ndmy5uFN06FuwA6BTiBB509znbvcvm15kjNYpt7rOsB5SqWM5ufMueApmMv2L2QpsexJqI j8ty5eNLezVdsrMc377c3UqE52sy84ypfZvNwbJwjYYBa/vgXT7/NSHbH+GvnfN0RTKPOR rE/stNy9N4cK3GaPVzXFNIPUx73AY3HASx4BtWBcELsrHnkT8yAgu/vNCaQfXL5IQNyW/H MPwZhOL3d18q8toE7Qq4H3tw5ZljgSmRc2HoTnRAkcLDzk3+dw3HglGQGXZdTiQbZjrpky Bs1DvFNYaqKkojigRFFCX+joKX8S9/d+HZU3+gW5VAjJGk86b0WxyJEs+2C9Rg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1687800343; a=rsa-sha256; cv=none; b=gv86bitGU2qo6KOiDWiNxdh17ESbIMaZbZjsK/gz0xyaGmfsDmw/CMlJywHe/Qf6012Gj+ sNF0DEmr5oacYqd4DbcJe+l8C6Q0SJ9d9SUmpivbb9JkTxI8D8fx7HDWoql8xM5I114C6H gceIQJXNDQw7iXU4tkuJXq9q/E3vCsfQ1mk67BYZlAQL469/qVtmjpcwLTi59r/O7w7P57 olvWnbtHR/4z3+/fc+27pZ7oTvwb7UyBCmumpTpi69VBAE15bW0X5ilHy3BGU5U4R4Cr0s tWa6CIlu2eh5SihMx0Xfob8WpwBPOYQEre8TlsXM1LuKdmW8dru9Gb3iMsc/Tg== Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4QqZVv0rGnzJqV for ; Mon, 26 Jun 2023 17:25:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 35QHPhC1098514 for ; Mon, 26 Jun 2023 17:25:43 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 35QHPhVG098513 for bugs@FreeBSD.org; Mon, 26 Jun 2023 17:25:43 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 262969] NVMe - Resetting controller due to a timeout and possible hot unplug Date: Mon, 26 Jun 2023 17:25:42 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 13.1-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: firemeteor@users.sourceforge.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-bugs@freebsd.org MIME-Version: 1.0 X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262969 --- Comment #14 from Timothy Guo --- (In reply to crb from comment #11) I would like to share my follow up experience of this issue. In short, the problem magically goes away after I wipe the disk and recreat= ed the pool from backup. The same system (hardware and SW) has been working without issue for about half a year now. Unfortunately, I couldn't locate a conclusive offender during the entire procedure. One thing I would like to note also is the 3.3V rail of the PSU. When I was still suffering from the issue, I also discovered 3.3V rail under-voltage, probably thanks to the hint from @crb's bug. I first read the out of range Voltage value from BIOS, and then confirmed the issue through direct measurement with a Voltage meter directly from the PSU pin-out. So it's true that the issue could really be power related. But it's unfortunate that I c= an't tell who is the offender, is the NVME drawing too much power due to firmware bug? Or is a failing PSU leading to NVME failure? I contacted my PSU vendor and got the feedback that the wire connector may = be aged and increased the resistance. Maybe my Voltage measuring attempt fixed= the wiring connection, maybe the wipe-out and rebuild worked-around a potential firmware bug. The issue just suddenly goes away, as it suddenly comes (Note= : I couldn't remember any re-assembling of the hardware build when it suddenly comes, though.) The only part that I'm sure is the power failure is real and highly related= . A stronger PSU might have simply avoided the problem altogether? --=20 You are receiving this mail because: You are the assignee for the bug.=