Bug 74428 - hyperz causes gpu hang in Counter-strike: Source
Summary: hyperz causes gpu hang in Counter-strike: Source
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r600 (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
Depends on:
Blocks: 75112
  Show dependency treegraph
Reported: 2014-02-03 06:07 UTC by vimregisters
Modified: 2019-09-18 19:13 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

normal setup (radeon.dpm=1) (24.00 KB, text/plain)
2014-02-03 06:07 UTC, vimregisters
power_dpm_state=performance; power_dpm_force_performance_level=high (42.06 KB, text/plain)
2014-02-03 06:09 UTC, vimregisters
radeon.dpm=0 (24.79 KB, text/plain)
2014-02-03 06:10 UTC, vimregisters

Description vimregisters 2014-02-03 06:07:48 UTC
Created attachment 93259 [details]
normal setup (radeon.dpm=1)

Linux 3.13
AMD A8-3530MX APU [BeaverCreek Radeon HD6620G (SUMO)]
Mesa 10.1.0-devel (git-9f26ad0)

Counter-strike: Source would play just fine. After a while though, it can bring the whole system down.

Here are a couple netconsole logs of the incident.
Comment 1 vimregisters 2014-02-03 06:09:26 UTC
Created attachment 93260 [details]
power_dpm_state=performance; power_dpm_force_performance_level=high
Comment 2 vimregisters 2014-02-03 06:10:11 UTC
Created attachment 93261 [details]
Comment 3 Alex Deucher 2014-02-03 15:00:34 UTC
Does disabling hyperz help?  set env var:  R600_DEBUG=nohyperz
Comment 4 vimregisters 2014-02-03 21:51:28 UTC
Yes. Nothing goes wrong with hyperz disabled.
Comment 5 Marek Olšák 2014-09-01 20:55:05 UTC
Is this fixed with current Mesa git?

If not, could you please make and upload a trace file using apitrace:


Comment 6 Corey Richardson 2014-09-13 19:37:13 UTC
I can't reproduce this on git-f976b4c.
Comment 7 David Heidelberg (okias) 2014-09-20 20:27:51 UTC
kernel 3.16.2,
Mesa-3D today git,
HD 6550D on 3870K

Counter Strike Global Offensive (also Source engine) - worked without any lockup.
Comment 8 mirh 2018-09-26 10:32:03 UTC
vimregisters, can we close this then?
Comment 9 GitLab Migration User 2019-09-18 19:13:24 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/490.

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.