All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103900] [SUMO][TURKS] Launching War Thunder make GPU stuck, and then system is hard lockup
Date: Sat, 25 Nov 2017 07:41:47 +0000	[thread overview]
Message-ID: <bug-103900-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 103900
           Summary: [SUMO][TURKS] Launching War Thunder make GPU stuck,
                    and then system is hard lockup
           Product: Mesa
           Version: 17.3
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Drivers/Gallium/r600
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: russianneuromancer@ya.ru
        QA Contact: dri-devel@lists.freedesktop.org

Hello!

Launching War Thunder make GPU stuck, and then system is hard lockup. This
issue is starting to happen after upgrade from Mesa 17.2.2 with libdrm 2.4.83
to 17.3.0rc4 with libdrm 2.4.85 (from Padoka Stable PPA
https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/pkppa ) on Kubuntu
17.10 x86_64. As soon as I rollback to Mesa 17.2.2 and libdrm 2.4.83, GPU
lockup is no longer reproducible, but then there is another issue: bug 100387

Issue is reproducible on both of iGPU and dGPU. Please look into attached log.

Hardware: 
Acer Aspire 7560G, AMD A8-3500M
AMD Radeon HD 6620G iGPU, AMD Radeon HD 6650M dGPU.

Software:
Kubuntu 17.10 x86_64, Linux 4.14.1.
radeon DDX and modesetting DDX was tested, no difference.

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

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

             reply	other threads:[~2017-11-25  7:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-25  7:41 bugzilla-daemon [this message]
2017-11-25  7:42 ` [Bug 103900] [SUMO][TURKS] Launching War Thunder make GPU stuck, and then system is hard lockup bugzilla-daemon
2017-11-25 11:49 ` bugzilla-daemon
2018-01-25 18:54 ` bugzilla-daemon
2018-12-21 23:26 ` bugzilla-daemon
2019-03-27 15:19 ` bugzilla-daemon
2019-09-18 19:24 ` 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-103900-502@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 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.