From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 84614] radeon gpu crash /kernel crash when using dynamic light in borderlands 2
Date: Mon, 06 Oct 2014 06:54:33 +0000 [thread overview]
Message-ID: <bug-84614-502-XPvDCjsnB4@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-84614-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 918 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=84614
--- Comment #4 from Michel Dänzer <michel@daenzer.net> ---
(In reply to Filipp Andjelo from comment #3)
> Almost the same problem here, full system crash, but I can't even reach the
> main menu. System is completely dead on the first rendering frame of the
> scene you see in the main menu.
Almost, but not quite the same problem then. Please file your own report.
Paulo, please attach the full /var/log/Xorg.0.log and the output of dmesg
showing the radeon driver initialization.
(In reply to Paulo Dias from comment #2)
> how can i do that? the kernel freezes and not even sysrq keys work anymore,
> i need to power off the pc.
Since you were able to retrieve the GPU fault messages from the kernel, you
might be able to retrieve a working apitrace as well.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1899 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:[~2014-10-06 6:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-03 0:37 [Bug 84614] New: radeon gpu crash /kernel crash when using dynamic light in borderlands 2 bugzilla-daemon
2014-10-03 1:01 ` [Bug 84614] " bugzilla-daemon
2014-10-03 3:48 ` bugzilla-daemon
2014-10-04 9:22 ` bugzilla-daemon
2014-10-06 6:54 ` bugzilla-daemon [this message]
2014-10-06 16:46 ` bugzilla-daemon
2014-10-07 1:45 ` bugzilla-daemon
2014-10-07 15:13 ` bugzilla-daemon
2014-10-08 0:46 ` bugzilla-daemon
2014-10-08 0:47 ` bugzilla-daemon
2014-10-08 1:04 ` bugzilla-daemon
2014-10-10 5:05 ` bugzilla-daemon
2014-10-10 5:19 ` bugzilla-daemon
2014-10-10 8:26 ` bugzilla-daemon
2014-10-10 10:17 ` bugzilla-daemon
2014-10-10 16:30 ` bugzilla-daemon
2014-10-10 19:00 ` bugzilla-daemon
2014-10-11 20:36 ` bugzilla-daemon
2014-10-14 3:07 ` bugzilla-daemon
2015-08-24 22:17 ` bugzilla-daemon
2015-08-26 14:08 ` bugzilla-daemon
2015-08-28 15:26 ` 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-84614-502-XPvDCjsnB4@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