From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92258] Opening context menu in Steam could lead to radeon kernel module crash
Date: Thu, 15 Oct 2015 22:59:12 +0000 [thread overview]
Message-ID: <bug-92258-502-UzSlGu9dV9@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92258-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 867 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92258
--- Comment #1 from russianneuromancer@ya.ru ---
Created attachment 118908
--> https://bugs.freedesktop.org/attachment.cgi?id=118908&action=edit
netconsole log
With Linux 4.3rc5 system became unresponsive after crash, there is even no
reaction when I press NumLock button (NumLock led doesn't change state) but
kernel continue to send backtraces via netconsole for some time. netconsole.log
is attached.
This crash happen only if Steam started on Radeon HD 6650M via DRI_PRIME.
This crash seems like could be triggered only by DRI3 and GLAMOR combination,
at least I was unable to easily reproduce it with DRI2&EXA and DRI3&EXA
combinations (DRI2&GLAMOR crash Xorg on Steam start, so I unable to test this
issue with this combination).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1797 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:[~2015-10-15 22:59 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 17:33 [Bug 92258] Opening context menu in Steam could lead to radeon kernel module crash bugzilla-daemon
2015-10-15 22:59 ` bugzilla-daemon [this message]
2015-10-15 23:19 ` bugzilla-daemon
2015-10-16 2:28 ` [Bug 92258] Opening context menu in Steam running via DRI_PRIME with enabled DRI3 " bugzilla-daemon
2015-10-16 10:22 ` bugzilla-daemon
2015-10-16 10:24 ` [Bug 92258] [regression] " bugzilla-daemon
2015-10-16 13:50 ` bugzilla-daemon
2015-10-16 13:51 ` bugzilla-daemon
2015-10-17 15:51 ` bugzilla-daemon
2015-11-12 6:47 ` bugzilla-daemon
2015-11-12 11:58 ` bugzilla-daemon
2015-11-19 2:17 ` bugzilla-daemon
2015-11-19 8:23 ` bugzilla-daemon
2015-11-19 8:29 ` bugzilla-daemon
2015-11-23 16:31 ` bugzilla-daemon
2015-11-24 11:13 ` bugzilla-daemon
2015-11-26 9:08 ` bugzilla-daemon
2016-02-10 20:10 ` [Bug 92258] [regression] Opening " bugzilla-daemon
2016-02-10 20:12 ` bugzilla-daemon
2016-03-27 13:21 ` bugzilla-daemon
2016-03-28 23:44 ` bugzilla-daemon
2016-03-28 23:48 ` bugzilla-daemon
2016-03-29 12:00 ` bugzilla-daemon
2016-03-29 23:50 ` bugzilla-daemon
2016-03-30 2:53 ` bugzilla-daemon
2016-03-30 17:07 ` bugzilla-daemon
2016-03-30 17:42 ` bugzilla-daemon
2016-03-30 17:47 ` bugzilla-daemon
2016-03-30 18:51 ` bugzilla-daemon
2016-03-30 18:53 ` bugzilla-daemon
2016-03-30 19:06 ` bugzilla-daemon
2016-03-31 2:25 ` bugzilla-daemon
2016-03-31 10:37 ` bugzilla-daemon
2016-03-31 12:17 ` bugzilla-daemon
2016-03-31 13:20 ` bugzilla-daemon
2016-03-31 13:50 ` bugzilla-daemon
2016-03-31 13:52 ` bugzilla-daemon
2016-04-07 16:15 ` bugzilla-daemon
2016-04-07 16:43 ` bugzilla-daemon
2016-04-07 21:33 ` bugzilla-daemon
2016-04-07 22:12 ` bugzilla-daemon
2016-04-07 22:19 ` bugzilla-daemon
2016-04-18 22:44 ` bugzilla-daemon
2016-04-18 22:53 ` bugzilla-daemon
2016-04-19 4:13 ` bugzilla-daemon
2016-04-25 22:55 ` bugzilla-daemon
2016-04-27 8:27 ` bugzilla-daemon
2016-04-28 15:23 ` bugzilla-daemon
2016-05-11 8:38 ` bugzilla-daemon
2016-05-12 2:52 ` bugzilla-daemon
2016-05-12 22:15 ` bugzilla-daemon
2016-11-30 6:27 ` bugzilla-daemon
2016-12-17 7:22 ` bugzilla-daemon
2017-04-19 14:58 ` bugzilla-daemon
2017-04-19 16:36 ` bugzilla-daemon
2019-11-19 9:09 ` 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-92258-502-UzSlGu9dV9@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