From owner-freebsd-bugs@freebsd.org Sat Jan 18 08:31:59 2020 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2A18E22CD2E for ; Sat, 18 Jan 2020 08:31:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 480B4H0R2Jz3Dvj for ; Sat, 18 Jan 2020 08:31:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 0ECD322CD2D; Sat, 18 Jan 2020 08:31:59 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0E91422CD2C for ; Sat, 18 Jan 2020 08:31:59 +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) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 480B4G6k6Vz3Dvg for ; Sat, 18 Jan 2020 08:31:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id C85AE1F30D for ; Sat, 18 Jan 2020 08:31:58 +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 00I8VwGP094161 for ; Sat, 18 Jan 2020 08:31:58 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 00I8Vwqe094160 for bugs@FreeBSD.org; Sat, 18 Jan 2020 08:31:58 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 243422] NVME controller failure: resetting (AMD Radeon R5 NVMe Series) Date: Sat, 18 Jan 2020 08:31:58 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: shamaz.mazum@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Jan 2020 08:31:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D243422 Bug ID: 243422 Summary: NVME controller failure: resetting (AMD Radeon R5 NVMe Series) Product: Base System Version: 12.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: shamaz.mazum@gmail.com Hello. I use a machine running FreeBSD 12.1-RELEASE and equipped with AMD Radeon R5 NVMe 120Gb drive. When I try to write something on this NVMe drive (I have UFS on it), I constantly get these errors in : nvme0: Resetting controller due to a timeout. nvme0: Resetting controller due to a timeout. nvme0: Resetting controller due to a timeout. nvme0: Resetting controller due to a timeout. nvme0: Resetting controller due to a timeout. nvme0: Resetting controller due to a timeout. nvme0: resetting controller nvme0: aborting outstanding i/o nvme0: aborting outstanding i/o nvme0: aborting outstanding i/o nvme0: aborting outstanding i/o nvme0: aborting outstanding i/o nvme0: aborting outstanding i/o nvme0: aborting outstanding i/o This is a message on drive attach: nvme0: mem 0xfe900000-0xfe903fff irq 24 at device 0.0= on pci1 The write speed decreases greatly and sometimes written files are corrupt. While reading, on the contrary, all works just fine and read speed is really impressive. There are many bugs reported considering NVMe. Here is what I found and how this differs from my situation: bug #211713 =E2=80=94 probably the first bug reported. It is about suspend/= resume and I do not use suspend/resume on my PC. bug #232466 =E2=80=94 again, this is about suspend/resume bug #243148 =E2=80=94 I am not sure, maybe this is the same problem as mine. bug #243063 =E2=80=94 This guy has a similar problem in bhyve guest. I've decided to report another bug because this is maybe manufacturer speci= fic bug (some of the bugs I posted above are closed and people have their NVMe drives working). So, I am sorry if it's a duplicate. --=20 You are receiving this mail because: You are the assignee for the bug.=