All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 75711] New: Radeon: GPU recovery is unable to recover from GPU lockups (R9 270 - error in VDPAU).
Date: Thu, 08 May 2014 02:06:08 +0000	[thread overview]
Message-ID: <bug-75711-2300@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=75711

            Bug ID: 75711
           Summary: Radeon: GPU recovery is unable to recover from GPU
                    lockups (R9 270 - error in VDPAU).
           Product: Drivers
           Version: 2.5
    Kernel Version: 3.15-rc4
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: t3st3r@mail.ru
        Regression: No

Created attachment 135361
  --> https://bugzilla.kernel.org/attachment.cgi?id=135361&action=edit
Failed GPU recovery - R9 270, VDPAU.

There are some cases when Radeon GPUs can lock up on some MESA errors and so
on. While it MESA bugs and somesuch, there is what I believe to be kernel side
bug as well. 

Kernel side problem is how kernel handles GPU recovery procedure. Right now GPU
recovery would fail most of time on virtually any MESA bug and any GPUs, system
would be left in completely unusable state due to lack of graphic output. 

This bug has been caught on 3.15-rc4 kernel running with recent MESA (oibaf PPA
on Ubuntu 14.04). GPU deadlock on R9 270 occured during VDPAU usage. As usually
;) GPU recovery failed to recover this GPU as well.

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

                 reply	other threads:[~2014-05-08  2:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-75711-2300@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.