dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 96271] TF2: GPU lockup on HD 7950
Date: Wed, 01 Jun 2016 03:51:58 +0000	[thread overview]
Message-ID: <bug-96271-502-aHIm5HUEUx@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-96271-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1711 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=96271

--- Comment #8 from Stephen Liang <hi+freedesktop@stephenliang.pw> ---
Created attachment 124225
  --> https://bugs.freedesktop.org/attachment.cgi?id=124225&action=edit
Kernel log, dmesg, gallium debug logs during GPU hang and system crash

No good but I've got quite a bit of information! I tried with this command:

R600_DEBUG=noce,nohyperz GALLIUM_DDEBUG="800 noflush" steam
steam://rungameid/440

The GPU recovered and I was able to alt-tab to gnome terminal and grab the
dmesg. See "dmesg_after_alt_tab.txt".

I then continued to play the game and it hung again. This time, the entire
screen froze with only the mouse being able to move. Luckily, this time I was
able to drop to TTY4, and grab a dmesg. See "dmesg_after_hard_hang.txt", there
is certainly a lot more output here with quite a bit of call traces which I've
never seen before.

Now, I decided to restart X since the mouse still moved so I wondered if this
is an X issue. So I ran "sudo service gdm restart" and it crashed the system
with a calltrace displayed on screen on text mode. On restart, I checked the
kernel logs and I can see a lot of call traces, so it seems whatever happened
ended up tainting the kernel requiring the system to need a hard reset. See
"kernel_log_during_gdm_restart.txt".

Finally, since I ran this with GALLIUM_DDEBUG="800 noflush", I was able to
collect another gallium debug that goes along with this. I really hope this
information helps capture the state of the system at the time of crash. Please
let me know if you want me to try anything else.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2750 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2016-06-01  3:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-29 21:07 [Bug 96271] TF2: GPU lockup on HD 7950 bugzilla-daemon
2016-05-29 21:09 ` bugzilla-daemon
2016-05-29 21:15 ` bugzilla-daemon
2016-05-30 22:01 ` bugzilla-daemon
2016-05-30 22:14 ` bugzilla-daemon
2016-05-30 23:17 ` bugzilla-daemon
2016-05-30 23:29 ` bugzilla-daemon
2016-05-31 11:03 ` bugzilla-daemon
2016-06-01  3:51 ` bugzilla-daemon [this message]
2017-04-28  8:11 ` bugzilla-daemon
2017-04-28 18:46 ` bugzilla-daemon
2018-03-31 23:40 ` 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-96271-502-aHIm5HUEUx@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