All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93614] Tonga general protection fault in libdrm_amdgpu at di.fm
Date: Sat, 16 Jan 2016 16:27:08 +0000	[thread overview]
Message-ID: <bug-93614-502-B7lUNRTt51@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93614-502@http.bugs.freedesktop.org/>


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

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

Brian Paterni <bpaterni@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #4 from Brian Paterni <bpaterni@gmail.com> ---
Not sure exactly which package provided the fix, but now I'm no longer seeing
the fault, and also the stream on di.fm launches more consistently now.
Recently updated packages and versions:

libdrm: 2.4.66-2
mesa:   11.1.1-2

Thanks to all working on this! :)

Closing this bug

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

[-- Attachment #1.2: Type: text/html, Size: 2240 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

      parent reply	other threads:[~2016-01-16 16:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-06 20:22 [Bug 93614] Tonga general protection fault in libdrm_amdgpu at di.fm bugzilla-daemon
2016-01-06 20:25 ` bugzilla-daemon
2016-01-07  1:34 ` bugzilla-daemon
2016-01-07  2:40 ` bugzilla-daemon
2016-01-16 16:27 ` bugzilla-daemon [this message]

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-93614-502-B7lUNRTt51@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.