Bug 101185

Summary:	System hang during piglit tests
Product:	Mesa	Reporter:	Erno K <erno>
Component:	Drivers/Gallium/radeonsi	Assignee:	Default DRI bug account <dri-devel>
Status:	RESOLVED MOVED	QA Contact:	Default DRI bug account <dri-devel>
Severity:	normal
Priority:	medium	CC:	julien.isorce
Version:	git
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:
Attachments:	crash logs and piglit result json

Description Erno K 2017-05-25 11:51:35 UTC

Created attachment 131505 [details]
crash logs and piglit result json

I was running "piglit run tests/quick results/quick" yesterday and system suddenly stopped responding at test 36216/39353. I was forced to do 5 second power switch shut down. Today I ran the test again and it didn't hang the system but stopped progressing at 38239/39353 where I did Ctrl-C. Attached is backtrace of crashes. 

$ inxi -G
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Tonga PRO [Radeon R9 285/380]
           Display Server: X.Org 1.19.3 driver: amdgpu
           Resolution: 1920x1080@60.00hz, 1920x1080@60.00hz
           GLX Renderer: Gallium 0.4 on AMD TONGA (DRM 3.15.0 / 4.12.0-rc1-g2ea659a9ef48, LLVM 5.0.0)
           GLX Version: 3.0 Mesa 17.2.0-devel (git-1586768e74)

Comment 1 Timothy Arceri 2018-04-10 12:22:20 UTC

Unfortunately there are some known kernel issues with some tests. Currently I run this after building piglit to avoid the tests that cause issues:

rm bin/streaming-texture-leak
rm bin/fbo-maxsize
rm bin/tex3d-maxsize
rm bin/max-texture-size

Comment 2 GitLab Migration User 2019-09-25 17:59: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/1266.

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.