From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 73418] OpenCL hangs graphics on CAYMAN Date: Tue, 14 Jan 2014 07:04:56 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0332934405==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 72EFE88E27 for ; Mon, 13 Jan 2014 23:04:56 -0800 (PST) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces@lists.freedesktop.org Errors-To: dri-devel-bounces@lists.freedesktop.org To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0332934405== Content-Type: multipart/alternative; boundary="1389683096.E5AA0.25065"; charset="us-ascii" --1389683096.E5AA0.25065 Date: Tue, 14 Jan 2014 07:04:56 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=73418 --- Comment #3 from christophe.choquet2@free.fr --- - If I run the OpenCL hello_world without starting the X server, it is running fine. No hangs even if I run it multiple times. X starts properly after. - If I run hello_world within an X session, it hangs ever two tries. - If I start X server and run it in console, black screen/hang when returning to the X session With ddd, I have tracked the issue down to the point it hangs: (gdb) bt #0 radeon_drm_ws_queue_cs (ws=0x60b2e0, cs=0x7ffff7f6a010) at radeon_drm_winsys.c:555 #1 0x00007ffff293a7e8 in radeon_drm_cs_flush (rcs=0x7ffff7f6a010, flags=2, cs_trace_id=0) at radeon_drm_cs.c:567 #2 0x00007ffff2950f6d in r600_context_flush (ctx=0x6251d0, flags=2) at r600_hw_context.c:356 #3 0x00007ffff2951f3b in r600_flush (ctx=0x6251d0, flags=0) at r600_pipe.c:88 #4 0x00007ffff2952056 in r600_flush_gfx_ring (ctx=0x6251d0, flags=0) at r600_pipe.c:120 #5 0x00007ffff2952034 in r600_flush_from_st (ctx=0x6251d0, fence=0x7fffffffb390, flags=0) at r600_pipe.c:115 #6 0x00007ffff6c0718a in clover::command_queue::flush (this=0x642000) at core/queue.cpp:48 #7 0x00007ffff6c182f2 in clover::hard_event::wait (this=0xaca350) at core/event.cpp:124 #8 0x00007ffff6c60811 in clFinish (d_q=0x642008) at api/event.cpp:268 #9 0x000000000040136c in main (argc=1, argv=0x7fffffffdd58) at hello_world.c:193 If I run line 563 pipe_semaphore_signal(&ws->cs_queued) the system hang. The calling parameters are in a mesa dev list post. -- You are receiving this mail because: You are the assignee for the bug. --1389683096.E5AA0.25065 Date: Tue, 14 Jan 2014 07:04:56 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 3 on bug 73418 from 
- If I run the OpenCL hello_world without starting the X server, it is running
fine. No hangs even if I run it multiple times. X starts properly after.

- If I run hello_world within an X session, it hangs ever two tries.

- If I start X server and run it in console, black screen/hang when returning
to the X session

With ddd, I have tracked the issue down to the point it hangs:
(gdb) bt
#0  radeon_drm_ws_queue_cs (ws=0x60b2e0, cs=0x7ffff7f6a010) at
radeon_drm_winsys.c:555
#1  0x00007ffff293a7e8 in radeon_drm_cs_flush (rcs=0x7ffff7f6a010, flags=2,
cs_trace_id=0) at radeon_drm_cs.c:567
#2  0x00007ffff2950f6d in r600_context_flush (ctx=0x6251d0, flags=2) at
r600_hw_context.c:356
#3  0x00007ffff2951f3b in r600_flush (ctx=0x6251d0, flags=0) at r600_pipe.c:88
#4  0x00007ffff2952056 in r600_flush_gfx_ring (ctx=0x6251d0, flags=0) at
r600_pipe.c:120
#5  0x00007ffff2952034 in r600_flush_from_st (ctx=0x6251d0,
fence=0x7fffffffb390, flags=0) at r600_pipe.c:115
#6  0x00007ffff6c0718a in clover::command_queue::flush (this=0x642000) at
core/queue.cpp:48
#7  0x00007ffff6c182f2 in clover::hard_event::wait (this=0xaca350) at
core/event.cpp:124
#8  0x00007ffff6c60811 in clFinish (d_q=0x642008) at api/event.cpp:268
#9  0x000000000040136c in main (argc=1, argv=0x7fffffffdd58) at
hello_world.c:193

If I run line 563 pipe_semaphore_signal(&ws->cs_queued) the system hang.

The calling parameters are in a mesa dev list post.

You are receiving this mail because:
  • You are the assignee for the bug.
--1389683096.E5AA0.25065-- --===============0332934405== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel --===============0332934405==--