[Bug 243422] NVME controller failure: resetting (AMD Radeon R5 NVMe Series)

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243422

            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 at FreeBSD.org
          Reporter: shamaz.mazum at 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: <Generic NVMe Device> 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 — probably the first bug reported. It is about suspend/resume and I
do not use suspend/resume on my PC.
bug #232466 — again, this is about suspend/resume
bug #243148 — I am not sure, maybe this is the same problem as mine.
bug #243063 — This guy has a similar problem in bhyve guest.

I've decided to report another bug because this is maybe manufacturer specific
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.