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 89534] GPU lockup with wine
Date: Sat, 03 Oct 2015 09:33:36 +0000	[thread overview]
Message-ID: <bug-89534-502-cbvjrdX7H5@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-89534-502@http.bugs.freedesktop.org/>


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

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

--- Comment #23 from John <john.ettedgui@gmail.com> ---
This time I thought of trying with a clean wine profile (yes I'm still using
wine for this...) and did not install anything but the game in it (no DX or
other lib).

Well... that didn't change much.
Without nine my computer didn't crash for a few seconds in game, but then I was
taken to tty1 with a lot of
[  178.083898] radeon 0000:01:00.0: ring 4 stalled for more than 10070msec
[  178.083901] radeon 0000:01:00.0: GPU lockup (current fence id
0x0000000000010d3c last fence id 0x0000000000010df7 on ring 4)

I have the full dmesg if needed.


With nine on, it crashed quicker and completely killed the computer, I had to
restart it manually.
I am guessing it's an issue within the kernel for the hard lock, but no clue
why nothing else runs into it, and why this game does so easily..

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

[-- Attachment #1.2: Type: text/html, Size: 1676 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

  parent reply	other threads:[~2015-10-03  9:33 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 13:13 [Bug 89534] GPU lockup with wine bugzilla-daemon
2015-03-11 13:16 ` bugzilla-daemon
2015-03-11 14:18 ` bugzilla-daemon
2015-03-11 14:19 ` bugzilla-daemon
2015-03-12  7:40 ` bugzilla-daemon
2015-03-12 13:34 ` bugzilla-daemon
2015-03-13  7:16 ` bugzilla-daemon
2015-03-13  7:17 ` bugzilla-daemon
2015-03-13  7:18 ` bugzilla-daemon
2015-03-13  7:18 ` bugzilla-daemon
2015-03-13  7:19 ` bugzilla-daemon
2015-03-13  7:20 ` bugzilla-daemon
2015-03-13  7:20 ` bugzilla-daemon
2015-03-19 21:09 ` bugzilla-daemon
2015-04-13  7:25 ` bugzilla-daemon
2015-04-29 14:58 ` bugzilla-daemon
2015-04-30 20:29 ` bugzilla-daemon
2015-04-30 20:31 ` bugzilla-daemon
2015-04-30 20:33 ` bugzilla-daemon
2015-04-30 21:27 ` bugzilla-daemon
2015-05-01  1:01 ` bugzilla-daemon
2015-05-01  2:57 ` bugzilla-daemon
2015-09-22 10:45 ` bugzilla-daemon
2015-09-22 10:47 ` bugzilla-daemon
2015-10-03  9:33 ` bugzilla-daemon [this message]
2015-10-03  9:46 ` bugzilla-daemon
2015-10-03  9:50 ` bugzilla-daemon
2015-10-03  9:51 ` [Bug 89534] radeonsi GPU lockup / crash " bugzilla-daemon
2015-10-12 23:07 ` bugzilla-daemon
2015-12-02 11:23 ` bugzilla-daemon
2016-05-23 23:05 ` bugzilla-daemon
2016-07-03 19:17 ` bugzilla-daemon
2016-07-05 15:40 ` bugzilla-daemon
2016-07-05 19:00 ` bugzilla-daemon
2016-12-08 16:30 ` bugzilla-daemon
2016-12-08 16:45 ` 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-89534-502-cbvjrdX7H5@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