All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91667] Tonga Oopses with uvd + agd5f drm-next-4.3-wip
Date: Mon, 17 Aug 2015 16:08:47 +0000	[thread overview]
Message-ID: <bug-91667-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 91667
           Summary: Tonga Oopses with uvd + agd5f drm-next-4.3-wip
           Product: DRI
           Version: DRI git
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: adf.lists@gmail.com

Created attachment 117730
  --> https://bugs.freedesktop.org/attachment.cgi?id=117730&action=edit
Oops 1

Tried the newly updated agd5f drm-next-4.3-wip today and got some oopses with
uvd.

These are provoked by repeatedly starting a vid with mpplayer - a known issue,
but the change for me on Tonga is getting the Oopses.

On other kernels amdgpu/amd-staging/drm-fixes the same test would provoke a
ring 9 lock (rarely ring 0) and a failed reset, which at least would leave me
alive enough to get a VT.

I notice GPU stall detection has now been disabled - but testing various
4.3-wips over some weeks I have never got one anyway. Doing something like this
test or running valley would just lock the display and log nothing. SysRq
worked OK as it still does - just now I get some logging (though not for the
one Unigine Valley lock I just provoked).

I am now running mesa/drm mesa/mesa Git Xorg with DRI3 enabled.

While testing I noticed the tree got another update  - retested and still get
the same.

The first 2 are from the older tree, the second long as secondary Oopses were
provoked.

The third is current.

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

[-- Attachment #1.2: Type: text/html, Size: 2973 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:[~2015-08-17 16:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-17 16:08 bugzilla-daemon [this message]
2015-08-17 16:09 ` [Bug 91667] Tonga Oopses with uvd + agd5f drm-next-4.3-wip bugzilla-daemon
2015-08-17 16:10 ` bugzilla-daemon
2016-09-15 18:18 ` 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-91667-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.