Bug 73088 - [HyperZ] Juniper (6770): Gone Home / Unigine Heaven 4.0 lock up system after several minutes of use
Summary: [HyperZ] Juniper (6770): Gone Home / Unigine Heaven 4.0 lock up system after ...
Status: RESOLVED MOVED
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:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 75112
  Show dependency treegraph
 
Reported: 2013-12-28 06:14 UTC by appletorch
Modified: 2019-09-18 19:12 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg.log (72.87 KB, text/plain)
2013-12-28 06:14 UTC, appletorch
Details
dmesg (66.83 KB, text/plain)
2013-12-28 06:15 UTC, appletorch
Details
Journalctl of the crash (12.16 KB, text/plain)
2014-01-01 14:50 UTC, dawide2211
Details

Description appletorch 2013-12-28 06:14:33 UTC
Created attachment 91246 [details]
Xorg.log

Gone Home and Unigine Heaven 4.0 lock up my system after a few minutes of operation when using this ppa: https://launchpad.net/~oibaf/+archive/graphics-drivers/
When using mesa 9.2.1 provided in ubuntu 13.10 this does not occur with Gone Home. Same lock up issue happens when using ubuntu 14.04 development with mesa 10.0.1. In all cases I had radeon.audio=1, radeon.dpm=1, and R600_DEBUG=sb.
Comment 1 appletorch 2013-12-28 06:15:08 UTC
Created attachment 91247 [details]
dmesg
Comment 2 dawide2211 2014-01-01 14:50:39 UTC
Created attachment 91390 [details]
Journalctl of the crash

I confirm that this also happens on my Sapphire hd 6750 1Gb gddr5 Juniper. Playing graphically intensive games for few minutes ( like Left 4 Dead 2 or Dota 2 on high) completely crash the system. I attached the best log of the crash I found. I'm using arch linux 64 bit, kernel 3.12.6, mesa 10.0.1.
Comment 3 Alex Deucher 2014-01-02 17:55:46 UTC
Does it work ok if you disable hyperZ?  R600_DEBUG=nohyperz
Comment 4 appletorch 2014-01-02 20:33:32 UTC
The problem still occurs for me when using R600_DEBUG=nohyperz.
Comment 5 dawide2211 2014-01-12 01:14:13 UTC
After disabling hyperz my card no longer crashed. I guess it's a problem with this feature.
Comment 6 David Heidelberg (okias) 2014-05-17 21:55:15 UTC
Unigine Heaven 4.0 tested on 6550D with and without R600_DEBUG=hyperz.

I didn't noticed performance boost, but no glitches, crashes or anything. Worked well.
Comment 7 Marek Olšák 2014-09-01 21:12:20 UTC
appletorch, could you please test current Mesa git and see if it's fixed?
Comment 8 Marek Olšák 2014-09-01 21:28:21 UTC
Please don't forget to set this environment variable:

R600_DEBUG=hyperz
Comment 9 appletorch 2014-09-02 15:52:07 UTC
(In reply to comment #7)
> appletorch, could you please test current Mesa git and see if it's fixed?

Will do once I have a working monitor again, hopefully by the end of this week.
Comment 10 appletorch 2014-09-13 05:33:24 UTC
Unigine Heaven ran without issue. Gone home was giving me segfaults when trying to start it on my new installation so I wasn't able to test that.
Comment 11 GitLab Migration User 2019-09-18 19:12: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/478.


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.