[Bug 289605] graphics/drm-61-kmod amdgpu screen freeze

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

            Bug ID: 289605
           Summary: graphics/drm-61-kmod amdgpu screen freeze
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: x11@FreeBSD.org
          Reporter: freebsd.68fba@nospam.spacesurfer.com
             Flags: maintainer-feedback?(x11@FreeBSD.org)
          Assignee: x11@FreeBSD.org

I am running an xorg session with the amdgpu driver on a radeon graphics card
identified as 'Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X]' by
pciconf -lvvv, it loads the polaris12 firware.
I am using the latest 14.3 kernel with the latest drm-61-kmod
(drm-61-kmod-6.1.128.1403000_5)

Occasionally starting chromium will result in a permanently blank window with
chrome process "chrome: --type=gpu-process" stuck permanently on 100% CPU. This
process cannot be killed (with SIGINT or SIGKILL) or stopped (with SIGSTOP).
All the other chromium processes that start at the same time also cannot be
killed.

Starting any new chromium processes will also result in a blank window, but
their processes do not use any CPU and can be killed. The rest of the system
will generally be fine until eventually some graphics related operation (such
as opening a dialog box from eclipse) will result in the screen totally
freezing. The mouse pointer will still move but nothing works, including trying
to switch to a terminal (CTRL-ALT-F1).

Other than graphics related programs the system is fine and responsive. So I
can get access to the machine via ssh, trying to kill xorg will work but some
graphics programs cannot be killed and the screen remains frozen.

This machine and hardware have been stable for years and this problem appears
to have started when I upgraded from 14.2 to 14.3
Note that drm-61-kmod is the only one that works with 14.3. 515 is not stable
(crashes almost immediately)

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