dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 83998] New: Oopses on R9270X using UVD since radeon/uvd: use PIPE_USAGE_STAGING for msg&fb buffers
Date: Wed, 17 Sep 2014 14:14:07 +0000	[thread overview]
Message-ID: <bug-83998-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 83998
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Oopses on R9270X using UVD since radeon/uvd: use
                    PIPE_USAGE_STAGING for msg&fb buffers
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: adf.lists@gmail.com
          Hardware: Other
            Status: NEW
           Version: git
         Component: Drivers/Gallium/radeonsi
           Product: Mesa

R9270X Getting rareish Oopses and once oomkiller since -

commit 6327b584155d040ae089e65fd6747186bdd9666b
Author: Christian König <christian.koenig@amd.com>
Date:   Thu Sep 11 09:50:00 2014 +0200

    radeon/uvd: use PIPE_USAGE_STAGING for msg&fb buffers

    That better matches the actual userspace use case, the
    kernel will force it to VRAM if the hardware requires it.

To trigger this I need to repeatedly start mplayer using uvd - it's takes some
time, I ended up making a script to do it for me while AFK.

I am 99% sure the above is it - I spent a day and a half trying on the commit
before (radeon/video: use the hw to initial clear the buffers) with no crash.

The Oopses don't mention radeon or uvd.

They will hit as soon as mplayer launches before it renders anything - screen
locked, no mouse cursor or vt switch but SysRq works, box is still up in some
ways for a while (one time I had music playing for 30s-1min after).

One time oomkiller put on its blindfold and ran around killing :-)

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

[-- Attachment #1.2: Type: text/html, Size: 3153 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:[~2014-09-17 14:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-17 14:14 bugzilla-daemon [this message]
2014-09-17 14:23 ` [Bug 83998] Oopses on R9270X using UVD since radeon/uvd: use PIPE_USAGE_STAGING for msg&fb buffers bugzilla-daemon
2014-09-17 14:23 ` bugzilla-daemon
2014-09-17 20:44 ` bugzilla-daemon
2014-09-18  1:34 ` bugzilla-daemon
2014-11-19 22:44 ` bugzilla-daemon
2014-11-19 22:47 ` bugzilla-daemon
2014-12-01 14:07 ` bugzilla-daemon
2014-12-04 21:36 ` bugzilla-daemon
2014-12-05 10:46 ` bugzilla-daemon
2014-12-08  6:11 ` bugzilla-daemon
2015-07-30 12:38 ` 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-83998-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox