Bug 77907

Summary:	OpenCL test 'Arithm/Absdiff.Mat/20' from OpenCV hangs HD5470M
Product:	Mesa	Reporter:	Bruno Jiménez <brunojimen>
Component:	Drivers/Gallium/r600	Assignee:	Default DRI bug account <dri-devel>
Status:	RESOLVED MOVED	QA Contact:
Severity:	normal
Priority:	medium
Version:	git
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Bug Depends on:
Bug Blocks:	99553
Attachments:	Here's an excerpt of dmesg from when this happens Here's the disassembled cs I got using gdb and R600_DEBUG=cs,compute Here's the lockup code I obtained using R600_DEBUG=trace_cs

Description Bruno Jiménez 2014-04-24 23:04:08 UTC

The effects are that when running that test, the screen freezes for a while, then goes to black, then shows back my desktop, happening this some times.

After some debugging, the hang seems to occur with the compute shader sent to the GPU, as the system freezes when it waits for the GPU to finish.

My system is Arch Linux with:
- AMD CEDAR 5470M
- kernel 3.14.1-1
- llvm at revision 207118
- mesa at commit 352e06d
- opencv at commit bb4199b

Comment 1 Bruno Jiménez 2014-04-24 23:06:41 UTC

Created attachment 97922 [details]
Here's an excerpt of dmesg from when this happens

Comment 2 Bruno Jiménez 2014-04-24 23:08:42 UTC

Created attachment 97923 [details]
Here's the disassembled cs I got using gdb and R600_DEBUG=cs,compute

Comment 3 Bruno Jiménez 2014-04-24 23:11:05 UTC

Created attachment 97924 [details]
Here's the lockup code I obtained using R600_DEBUG=trace_cs

This code does indeed hang my GPU in the same way (as far as I can see) that the test does.

Comment 4 GitLab Migration User 2019-09-18 19:16:00 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/506.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.