Bug 84106 - GPU faults with Xonotic 0.7
Summary: GPU faults with Xonotic 0.7
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-19 21:19 UTC by darkbasic
Modified: 2019-11-19 08:56 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
dmesg (185.75 KB, text/plain)
2014-09-19 21:19 UTC, darkbasic
no flags Details

Description darkbasic 2014-09-19 21:19:52 UTC
Created attachment 106566 [details]
dmesg

I have an HD 7950 with latest graphic stack from git, including LLVM 3.6 git from today. kernel is drm-next-3.18-wip from today (3.17.0-rc5-drm-next-3.18-wip).
I was running some benchmarks (http://openbenchmarking.org/result/1409197-SO-1407298SO78) while I noticed sometimes the picture froze and then after a second or two it kept running the benchmark ultra fast. when the benchmark finished I noticed lots of GPU faults in dmesg: https://paste.lugons.org/show/5981/
Comment 1 darkbasic 2014-09-19 21:27:36 UTC
I forgot to say you have to run Xonotic with the Phoronix Test Suite "Ultimate" settings (which should be everything maxed out).
Comment 2 darkbasic 2014-09-19 21:42:48 UTC
'relief mapping' causes the GPU faults, anyway even without this setting the framerate still drops to 0 in some points of the benchmark
Comment 3 smoki 2014-09-19 22:57:05 UTC
 Reproducible on Kabini, does not happen with llvm 3.5 so it is probably current  llvm regression.
Comment 4 Hohahiu 2014-09-20 01:10:28 UTC
Isn't it a duplicate of https://bugs.freedesktop.org/show_bug.cgi?id=84089 ?
Comment 5 smoki 2014-09-22 03:59:58 UTC
(In reply to comment #4)
> Isn't it a duplicate of https://bugs.freedesktop.org/show_bug.cgi?id=84089 ?

 Seems like, there are many duplicates of bug 75276
Comment 6 Michel Dänzer 2014-09-22 05:52:24 UTC
(In reply to comment #2)
> 'relief mapping' causes the GPU faults, anyway even without this setting the
> framerate still drops to 0 in some points of the benchmark

I think the framerate drops are due to VRAM thrashing and not directly related to the GPU faults.
Comment 7 Martin Peres 2019-11-19 08:56:48 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/drm/amd/issues/539.


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.