All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99488] [r600g]OpenCL driver causes process to hang in ImageMagick's Gaussian Blur kernel
Date: Sun, 22 Jan 2017 07:23:32 +0000	[thread overview]
Message-ID: <bug-99488-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2130 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=99488

            Bug ID: 99488
           Summary: [r600g]OpenCL driver causes process to hang in
                    ImageMagick's Gaussian Blur kernel
           Product: Mesa
           Version: git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: nixscripter@gmail.com
        QA Contact: dri-devel@lists.freedesktop.org

(Bug number three. I can almost taste victory...)

If I compile ImageMagick with OpenCL support, the current version will hang
when I invoke the Gaussian blur operation. More specifically, the CPU will run
at 100%, and memory consumed by the process will increase indefinitely at 19 MB
per second, but nothing will happen.

The blur operation is done internally for many other operations, so this issue
is more crippling than it first appears.

To reproduce:

1. Get the current tree of ImageMagick from GitHub:
https://github.com/ImageMagick/ImageMagick

2. Compile it with OpenCL and HDRI support (--enable-opencl --enable-hdri
flags).

3. Get an image, and try to perform a simple Gaussian blur:

convert input.png -blur 0x20 output.png

4. The hang will occur... at least, on my system.

I mentioned this in another bug, and was told that on different hardware than
mine (I have a Radeon HD 5700, which is an Evergreen chipset) all of the
ImageMagick self-tests pass.

The source code for all OpenCL kernels is in
MagickCore/accelerate-kernels-private.h. Several functions are involved with
blurring, and unfortunately it's difficult to identify the source of the hang.
I would be happy to provide debugging information if I could be advised on how
to collect it.

LLVM version: r292714
Mesa version: commit bb5db5564

ImageMagick version: commit 43a09ba75 (Note: the next git revision was broken
by upstream)

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

[-- Attachment #1.2: Type: text/html, Size: 3572 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2017-01-22  7:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-22  7:23 bugzilla-daemon [this message]
2017-01-26 19:44 ` [Bug 99488] [r600g]OpenCL driver causes process to hang in ImageMagick's Gaussian Blur kernel bugzilla-daemon
2017-02-03  2:02 ` bugzilla-daemon
2017-02-03  2:48 ` bugzilla-daemon
2017-02-03  2:52 ` [Bug 99488] [r600g]OpenCL driver causes ImageMagick to hang on JPEG input in " bugzilla-daemon
2017-02-03  3:39 ` bugzilla-daemon
2017-02-03  9:01 ` bugzilla-daemon
2017-02-04 22:47 ` bugzilla-daemon
2017-02-05 16:37 ` bugzilla-daemon
2017-02-05 21:57 ` bugzilla-daemon
2017-02-21 23:20 ` bugzilla-daemon
2017-02-24  3:09 ` bugzilla-daemon
2017-02-26  4:46 ` bugzilla-daemon
2017-02-26  4:47 ` bugzilla-daemon
2017-02-26  6:38 ` bugzilla-daemon
2017-02-26 17:24 ` [Bug 99488] [r600g]ImageMagick issues " bugzilla-daemon
2017-02-26 17:26 ` bugzilla-daemon
2017-02-26 17:36 ` bugzilla-daemon
2017-05-07  0:39 ` bugzilla-daemon
2017-05-24  5:12 ` bugzilla-daemon
2017-05-30  6:38 ` bugzilla-daemon
2017-06-05  1:38 ` 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-99488-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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.