From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105240] GPU lock-up when running QT5 based celestia
Date: Sun, 25 Feb 2018 10:14:42 +0000 [thread overview]
Message-ID: <bug-105240-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2649 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105240
Bug ID: 105240
Summary: GPU lock-up when running QT5 based celestia
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: 375gnu@gmail.com
Created attachment 137587
--> https://bugs.freedesktop.org/attachment.cgi?id=137587&action=edit
apitrace trace
GPU: HD7750
Kernel: 4.14.17 (Debian package)
Driver: both radeon and amdgpu
Mesa: 17.3.4
LLVM: 5
When I start QT5 fork of celestia, my GPU gets locked. With radeon I have a few
seconds to switch to a terminal, with amdgpu I don't, sometimes everything is
locked so even REISUB doesn't help.
Even apitrace dump-images locks.
Feb 24 23:07:50 deneb kernel: [ 7701.664110] radeon 0000:01:00.0: ring 0
stalled for more than 10244msec
Feb 24 23:07:50 deneb kernel: [ 7701.664118] radeon 0000:01:00.0: ring 3
stalled for more than 10244msec
Feb 24 23:07:50 deneb kernel: [ 7701.664129] radeon 0000:01:00.0: GPU lockup
(current fence id 0x0000000000168b3f last fence id 0x0000000000168cdb on ring
3)
Feb 24 23:07:50 deneb kernel: [ 7701.664513] radeon 0000:01:00.0: GPU lockup
(current fence id 0x00000000000ae7cc last fence id 0x00000000000ae85f on ring
0)
Feb 24 23:07:50 deneb kernel: [ 7701.718269] do_general_protection: 15
callbacks suppressed
Feb 24 23:07:50 deneb kernel: [ 7701.718272] traps: goldendict[4507] general
protection ip:7f3bf7cc3185 sp:7ffedf2ba330 error:0 in
libc-2.26.so[7f3bf7c8c000+1ad000]
Feb 24 23:07:50 deneb kernel: [ 7701.936036] radeon_dp_aux_transfer_native: 74
callbacks suppressed
Feb 24 23:07:50 deneb kernel: [ 7702.176091] radeon 0000:01:00.0: ring 3
stalled for more than 10756msec
Feb 24 23:07:50 deneb kernel: [ 7702.176135] radeon 0000:01:00.0: ring 0
stalled for more than 10756msec
Feb 24 23:07:50 deneb kernel: [ 7702.176142] radeon 0000:01:00.0: GPU lockup
(current fence id 0x00000000000ae7cc last fence id 0x00000000000ae85f on ring
0)
Feb 24 23:07:50 deneb kernel: [ 7702.176485] radeon 0000:01:00.0: GPU lockup
(current fence id 0x0000000000168b3f last fence id 0x0000000000168ced on ring
3)
Feb 24 23:07:51 deneb kernel: [ 7702.688091] radeon 0000:01:00.0: ring 0
stalled for more than 11268msec
Feb 24 23:07:51 deneb kernel: [ 7702.688096] radeon 0000:01:00.0: ring 3
stalled for more than 11268msec
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4060 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
next reply other threads:[~2018-02-25 10:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-25 10:14 bugzilla-daemon [this message]
2018-03-21 18:12 ` [Bug 105240] GPU lock-up when running QT5 based celestia bugzilla-daemon
2018-03-21 18:12 ` 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-105240-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).