From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 113341] New: GPU Lockup on AMD Kaveri
Date: Sat, 27 Feb 2016 20:18:57 +0000 [thread overview]
Message-ID: <bug-113341-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=113341
Bug ID: 113341
Summary: GPU Lockup on AMD Kaveri
Product: Drivers
Version: 2.5
Kernel Version: 4.4.2
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: linux@bernd-steinhauser.de
Regression: No
Created attachment 206321
--> https://bugzilla.kernel.org/attachment.cgi?id=206321&action=edit
journal log from the time of the gpu lockup.
GPU is an AMD Kaveri: 1002:130f
Happened when I started an application (way before the application actually
showen) on KDE Plasma 5.5.
The kernel version was 4.4.2 with an additional vblank fix applied (see [1]).
Since I wasn't prepared for this and ssh wasn't activated and I couldn't save
dmesg output. Instead I'll attach what I found in the journal.
[1] https://bugs.freedesktop.org/show_bug.cgi?id=93746
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2016-02-27 20:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 20:18 bugzilla-daemon [this message]
2016-02-29 1:25 ` [Bug 113341] GPU Lockup on AMD Kaveri bugzilla-daemon
2016-02-29 5:33 ` bugzilla-daemon
2016-02-29 5:37 ` bugzilla-daemon
2016-03-05 11:47 ` bugzilla-daemon
2016-03-05 11:48 ` bugzilla-daemon
2016-03-07 9:27 ` bugzilla-daemon
2016-03-07 14:11 ` bugzilla-daemon
2016-03-08 1:50 ` bugzilla-daemon
2016-03-11 18:14 ` bugzilla-daemon
2016-03-30 17:46 ` bugzilla-daemon
2016-06-03 5:22 ` 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-113341-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.