All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 62721] New: GPU lockup in Minecraft 1.5.1 with HyperZ
Date: Mon, 25 Mar 2013 12:25:24 +0000	[thread overview]
Message-ID: <bug-62721-502@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1848 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=62721

          Priority: medium
            Bug ID: 62721
          Assignee: dri-devel@lists.freedesktop.org
           Summary: GPU lockup in Minecraft 1.5.1 with HyperZ
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: maarten-baert@hotmail.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: 9.1
         Component: Drivers/DRI/R600
           Product: Mesa

Created attachment 76994
  --> https://bugs.freedesktop.org/attachment.cgi?id=76994&action=edit
dmesg output

Minecraft 1.5.1 locks up the GPU when HyperZ is enabled (which seems to be the
default). When it happens, the screen first freezes for a few seconds, then
becomes black for a few seconds, then the backlight turns off as well, and then
everything recovers. A few seconds later this usually happens again. The
easiest way to get out of this loop is to kill minecraft (I used
AltGr+PrintScreen+F).

I've never seen this happen with any of the older versions of minecraft, but
I'm not sure whether I was using the same kernel and driver versions back then.
Minecraft 1.5.1 has a very different engine than any of the previous versions
(it's about 3 times faster as well), so I think that's why it never happened
before.

I don't get any lockups when I run with R600_HYPERZ=0.

The lockups appear to happen more frequently when the window is larger (I
haven't seen it happen with the default size of 854x480, but at 1920x1080 it
happens all the time. It also happens more often when there's more activity in
Minecraft (e.g. redstone updates).

My card is a Radeon HD 5650M. I'm using Arch Linux, everything is up-to-date.
Kernel version 3.8.4, mesa version 9.1.1.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3260 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2013-03-25 12:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25 12:25 bugzilla-daemon [this message]
2013-03-25 12:35 ` [Bug 62721] GPU lockup in Minecraft 1.5.1 with HyperZ bugzilla-daemon
2013-04-16 10:19 ` bugzilla-daemon
2013-04-24 19:23 ` bugzilla-daemon
2013-04-26  2:21 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-62721-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.