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: Thu, 07 Jan 2016 02:40:20 +0000 [thread overview]
Message-ID: <bug-93614-502-j9sIifW227@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93614-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 873 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93614
--- Comment #3 from Brian Paterni <bpaterni@gmail.com> ---
Created attachment 120850
--> https://bugs.freedesktop.org/attachment.cgi?id=120850&action=edit
gdb captured backtrace of segmentation fault
So it turns out I am able to stream successfully from di.fm, I think I may have
just needed to sign up(!) :-)
Regardless though, launching of the web player does seem to be a bit spotty.
Though I'm not sure if it caused by this bug or something else...
(In reply to Michel Dänzer from comment #2)
> We need to see a backtrace of a crash.
I was able to get the attached backtrace by attaching to the browser's
flashplugin subprocess! Hopefully it does help. To reproduce, all that seems
necessary is to visit di.fm.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1922 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
next prev parent reply other threads:[~2016-01-07 2:40 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 [this message]
2016-01-16 16:27 ` 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-93614-502-j9sIifW227@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;
as well as URLs for NNTP newsgroup(s).