All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 36421] New: RV710: GPU lockup running portal2 in wine.
Date: Wed, 20 Apr 2011 05:45:34 -0700 (PDT)	[thread overview]
Message-ID: <bug-36421-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: RV710: GPU lockup running portal2 in wine.
           Product: Mesa
           Version: git
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: NightNord@gmail.com


Created an attachment (id=45860)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=45860)
kernel traces for GPU lockup

OpenGL renderer string: Gallium 0.4 on AMD RV710
OpenGL version string: 2.1 Mesa 7.11-devel (git-c98fa6b)

After finishing loading any level game shows black screen (like monitor goes
off), than screen goes back to live filled with some flickering garbage.
netconsole on other hosts reports GPU lockup traces from kernel. Leaving game
in this state for a while leads to complete kernel hangup.

I failed to reproduce this on any other non-native 3d-application (read: game),
neither on any native (still, I don't have access to much of them).

Changing various in-game settings to lowest possible doesn't help, nor
switching dxlevel (they seems to disable this feature).

Attaching traces log from netconsole. I may also attach wine output, as it
contains information about GL calls, but maybe it will be better to post wine
bug for this?

If there is any way to get some error-state (like one from intel cards in
similar bugs here) or opengl calls trace - I'll happily provide them.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2011-04-20 12:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-20 12:45 bugzilla-daemon [this message]
2011-05-01  6:38 ` [Bug 36421] RV710: GPU lockup running portal2 in wine bugzilla-daemon
2011-05-01  6:39 ` bugzilla-daemon
2011-05-01  6:41 ` bugzilla-daemon
2011-05-01 11:02 ` bugzilla-daemon
2011-05-16 19:50 ` bugzilla-daemon
2011-05-17 16:57 ` bugzilla-daemon
2011-06-14 11:59 ` bugzilla-daemon
2012-03-23 17:15 ` bugzilla-daemon
2012-03-23 18:26 ` 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-36421-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.