[Bug 248659] random NVMe hick ups and system freezes

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Fri Aug 14 18:27:07 UTC 2020


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

            Bug ID: 248659
           Summary: random NVMe hick ups and system freezes
           Product: Base System
           Version: CURRENT
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: bugs at FreeBSD.org
          Reporter: driesm.michiels at gmail.com

When doing very low intensive stuff (like checking out the ports tree over WIFI
g at like 6 MB/s) on my laptop (Lenovo T490) running KDE5, my disk IO seems to
partially stall for a few seconds and then just continue. I have also observed
frequent system freezes/deadlocks with no debug info what so ever, no kernel
dump, etc. I'm leaning towards VFS deadlocks although I'm kind off in the
shadow on how to proceed further to debug this issue. The reason I suspect the
VFS stack is that I also observe the random freezes when not running any GUI,
just console based interaction. Maybe a driver that I'm loading?

See video link for what I'm experiencing (https://youtu.be/1_ll4OBefjo).

I am running 13-CURRENT and have a Samsung NVMe drive (PM981a) running the UFS
file system. I have disable SU-journaling but doesn't seem to help. I really
like the look and feel of KDE5 on my laptop although its just not usable in
this state with frequent data loss due to the system freezes and hard resets.
Trim is disabled through tunefs on this drive as I've read that could be a
cause for the problem I describe. Although any of the filesystem settings don't
seem to help.

I'd very much appreciate someone bearing with me into debugging this issue.
I have also tried disabling all debugging related features in the kernel that
should be disabled in stable branches but that didn't help either, so will
probably reenable to debug.

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


More information about the freebsd-bugs mailing list