| Summary: | [HyperZ] Juniper (6770): Gone Home / Unigine Heaven 4.0 lock up system after several minutes of use | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | appletorch |
| Component: | Drivers/Gallium/r600 | Assignee: | Default DRI bug account <dri-devel> |
| Status: | RESOLVED MOVED | QA Contact: | |
| Severity: | normal | ||
| Priority: | medium | ||
| Version: | git | ||
| Hardware: | x86-64 (AMD64) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Bug Depends on: | |||
| Bug Blocks: | 75112 | ||
| Attachments: |
Xorg.log
dmesg Journalctl of the crash |
||
|
Description
appletorch
2013-12-28 06:14:33 UTC
Created attachment 91247 [details]
dmesg
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.
Does it work ok if you disable hyperZ? R600_DEBUG=nohyperz The problem still occurs for me when using R600_DEBUG=nohyperz. After disabling hyperz my card no longer crashed. I guess it's a problem with this feature. 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. appletorch, could you please test current Mesa git and see if it's fixed? Please don't forget to set this environment variable: R600_DEBUG=hyperz (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. 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. -- 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.