All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 203879] New: hard freeze on high single threaded load when Xorg is active (AMD Ryzen 7 2700X CPU, AMD Radeon RX 580 GPU)
Date: Wed, 12 Jun 2019 19:44:25 +0000	[thread overview]
Message-ID: <bug-203879-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=203879

            Bug ID: 203879
           Summary: hard freeze on high single threaded load when Xorg is
                    active (AMD Ryzen 7 2700X CPU, AMD Radeon RX 580 GPU)
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.19.37-3 (Debian 4.19.0-5-amd64) and others
                    (including mainline versions)
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: claude@mathr.co.uk
        Regression: No

Created attachment 283233
  --> https://bugzilla.kernel.org/attachment.cgi?id=283233&action=edit
dmesg from 4.19.0-5-amd64 with amdgpu.dc=1 (no freeze yet)

I am developing a CPU-based program to render fractals, which I usually run
with "nice -n 20".  The main calculations are multi-threaded, using 16 threads
on AMD Ryzen 7 2700X Eight-Core Processor.  However, final image PNG saving is
single-threaded.  During the single-threaded workload only (as observed by htop
and program status prints), it can happen that the system freezes hard (no ssh,
stuck mouse pointer, no NumLock LED toggle, no magic SysRq, only physical power
button for hard power-off works).

This freeze only happens when Xorg is running on the active virtual terminal: I
tried to see if some kernel log messages would be displayed before freeze by
switching to a console with Ctrl-Alt-F1 after launching my program, but with
the terminal active it doesn't seem to freeze.

The freeze does not always occur, but usually happens before a dozen images are
saved (sequential process is full-threaded workload, followed by
single-threaded workload, repeated).  This can take a few hours.

With the virtual terminal active instead of Xorg, I have rendered 100+ images
in a row without any issues.  Of course, I can't use other X applications at
the same time, so this is an annoying workaround.

I mostly run the regular Debian Buster kernel but I have had this freeze occur
with other self-compiled kernels of various versions (newer than the Debian
kernel, without Debian patches).  I also had the freeze with both amdgpu.dc=1
(default) and amdgpu.dc=0 options.

$ uname -a
Linux eiskaffee 4.19.0-5-amd64 #1 SMP Debian 4.19.37-3 (2019-05-15) x86_64
GNU/Linux

$ apt-cache policy linux-image-4.19.0-5-amd64
linux-image-4.19.0-5-amd64:
  Installed: 4.19.37-3
  Candidate: 4.19.37-3
  Version table:
 *** 4.19.37-3 990
        990 http://ftp.uk.debian.org/debian buster/main amd64 Packages
        500 http://ftp.uk.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-06-12 19:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-12 19:44 bugzilla-daemon [this message]
2019-06-12 23:04 ` [Bug 203879] hard freeze on high single threaded load when Xorg is active (AMD Ryzen 7 2700X CPU, AMD Radeon RX 580 GPU) bugzilla-daemon
2019-06-13  7:41 ` bugzilla-daemon
2019-06-13 15:34 ` bugzilla-daemon
2019-06-17 20:01 ` bugzilla-daemon
2019-07-12 14:35 ` [Bug 203879] hard freeze on high single threaded load (AMD Ryzen 7 2700X CPU) bugzilla-daemon
2019-07-13  1:16 ` bugzilla-daemon
2019-07-13  1:17 ` bugzilla-daemon
2019-07-16 14:07 ` bugzilla-daemon
2019-08-18  0:40 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-203879-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.