From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93079] Tonga faults and oopses on agd5f drm-fixes-4.4
Date: Mon, 23 Nov 2015 15:54:09 +0000 [thread overview]
Message-ID: <bug-93079-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 954 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93079
Bug ID: 93079
Summary: Tonga faults and oopses on agd5f drm-fixes-4.4
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 120050
--> https://bugs.freedesktop.org/attachment.cgi?id=120050&action=edit
some backtraces
Haven't tried agd5f drm-fixes-4.4 before today.
It seems that it is unstable on R9 285.
Twice I've been close to submitting a bisect, but false goods have spoilt
things.
Varying backtraces attached.
Will try to bisect again but it's not going to be quick.
I am stable on powerplay and was OK on 4.4-next-wip.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2303 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 reply other threads:[~2015-11-23 15:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-23 15:54 bugzilla-daemon [this message]
2015-11-23 15:55 ` [Bug 93079] Tonga faults and oopses on agd5f drm-fixes-4.4 bugzilla-daemon
2015-11-23 20:58 ` [Bug 93079] Tonga faults and oopses on agd5f drm-fixes-4.4 since fix incorrect mutex usage v3 bugzilla-daemon
2015-11-25 10:04 ` bugzilla-daemon
2015-11-25 10:05 ` bugzilla-daemon
2015-11-26 9:39 ` bugzilla-daemon
2015-12-02 13:18 ` bugzilla-daemon
2015-12-02 21:46 ` bugzilla-daemon
2015-12-13 10:33 ` 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-93079-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.