Bug 109329

Summary: Luxmark freezes the system
Product: Mesa Reporter: Fabian Maurer <dark.shadow4>
Component: Drivers/Gallium/radeonsiAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact: Default DRI bug account <dri-devel>
Severity: normal    
Priority: medium    
Version: 18.3   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Bug Depends on:    
Bug Blocks: 99553    
Attachments: journalctl log

Description Fabian Maurer 2019-01-12 13:04:43 UTC
Created attachment 143077 [details]
journalctl log

Running luxmark (OpenCL) freezes the system.
Only help is to reboot with REISUB command.

dmesg log (from journalctl) attached.

System:
-Arch Linux
-AMD Radeon 285
-AMD Radeon R9 200 Series (TONGA, DRM 3.27.0, 4.20.1-arch1-1-ARCH, LLVM 7.0.0)
-Mesa 18.3.1
Comment 1 Jan Vesely 2019-02-26 17:36:15 UTC
(In reply to Fabian Maurer from comment #0)
> Created attachment 143077 [details]
> journalctl log
> 
> Running luxmark (OpenCL) freezes the system.
> Only help is to reboot with REISUB command.
> 
> dmesg log (from journalctl) attached.
> 
> System:
> -Arch Linux
> -AMD Radeon 285
> -AMD Radeon R9 200 Series (TONGA, DRM 3.27.0, 4.20.1-arch1-1-ARCH, LLVM
> 7.0.0)
> -Mesa 18.3.1

which scene are you trying to run?
Comment 2 Fabian Maurer 2019-03-01 17:14:30 UTC
The default scene, I guess.
Sorry, I don't know what exactly you mean - I just run the program without any parameters, and then it freezes.

I'd test more, but currently luxmark doesn't build on my system.
Comment 3 GitLab Migration User 2019-09-25 18:44:25 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/1353.

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.