All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 102233] OpenCL segmentation fault on AMD Radeon (Kaveri+R7) with memtestCL
Date: Tue, 15 Aug 2017 14:06:16 +0000	[thread overview]
Message-ID: <bug-102233-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 102233
           Summary: OpenCL segmentation fault on AMD Radeon (Kaveri+R7)
                    with memtestCL
           Product: Mesa
           Version: git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: critical
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: senad.jahic@gmx.com
        QA Contact: dri-devel@lists.freedesktop.org
            Blocks: 99553

Hardware:
AMD A8-7600 with Radeon™ R7 Series
Sapphire R7 240 4GB
ASUS R7 240 4GB

OS: Ubuntu server 17.04 64bit (headless mode).
OpenCL Driver: Padoka


Description:
clinfo works, shows all three GPU platforms.
Sometimes I get segmentation fault using memtestCL.
I get 100% crashes with YACMiner (crypto mining software).


I've traced memtestCL down to this line:
https://github.com/ihaque/memtestCL/blob/607499a54dcac9b846fcc827dc5980d8e5f66cec/memtestCL_cli.cpp#L126

On repeating runs, clGetDeviceIDs sometimes returns 0 for num_cpu and sometimes
1.
If it returns 1, clGetDeviceInfo later crashes when called with device id that
does not exist.

If I hardcode "num_devices=3" at offending line, I can run memtestCL on all
three devices successfully without faults.


Referenced Bugs:

https://bugs.freedesktop.org/show_bug.cgi?id=99553
[Bug 99553] Tracker bug for runnning OpenCL applications on Clover
-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3553 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-08-15 14:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-15 14:06 bugzilla-daemon [this message]
2017-09-15 22:41 ` [Bug 102233] OpenCL segmentation fault on AMD Radeon (Kaveri+R7) with memtestCL bugzilla-daemon
2017-11-04 22:59 ` bugzilla-daemon
2017-12-22 12:16 ` bugzilla-daemon
2017-12-22 12:17 ` bugzilla-daemon
2018-05-10 19:06 ` 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-102233-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.