From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111524] GPU doesn't work after resume
Date: Fri, 30 Aug 2019 06:21:20 +0000 [thread overview]
Message-ID: <bug-111524-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3591 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111524
Bug ID: 111524
Summary: GPU doesn't work after resume
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: not set
Priority: not set
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: samuel@sieb.net
CPU is AMD A9-9420 RADEON R5
GPU is: 00:01.0 0300: 1002:98e4 (rev da)
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Stoney [Radeon R2/R3/R4/R5 Graphics] (rev da) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device 8330
Flags: bus master, fast devsel, latency 0, IRQ 35
Memory at e0000000 (64-bit, prefetchable) [size=256M]
Memory at f0800000 (64-bit, prefetchable) [size=8M]
I/O ports at 4000 [size=256]
Memory at f0400000 (32-bit, non-prefetchable) [size=256K]
Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities: [48] Vendor Specific Information: Len=08 <?>
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010
<?>
Capabilities: [270] Secondary PCI Express <?>
Capabilities: [2b0] Address Translation Service (ATS)
Capabilities: [2c0] Page Request Interface (PRI)
Capabilities: [2d0] Process Address Space ID (PASID)
Kernel driver in use: amdgpu
Kernel modules: amdgpu
If I suspend the laptop then on resume the GPU does not work. I've tried with
a 5.0 and a 5.2 kernel, same issue. dc=0 or dc=1 doesn't make any obvious
difference. I have gpu recovery enabled, otherwise it really hangs. With
Xorg, the screen looks the same as when suspended. With Wayland, there is
bunch of garbage around. In both cases, the mouse moves around, but there are
no screen updates. The following output shows up in dmesg with the last line
repeating endlessly, probably correlated with screen update attempts:
[ 48.337053] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout,
signaled seq=73, emitted seq=75
[ 48.337202] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information:
process gnome-shell pid 977 thread gnome-shel:cs0 pid 1005
[ 48.337206] [drm] IP block:gfx_v8_0 is hung!
[ 48.337319] amdgpu 0000:00:01.0: GPU reset begin!
[ 48.337761] amdgpu 0000:00:01.0: GRBM_SOFT_RESET=0x000F0001
[ 48.337817] amdgpu 0000:00:01.0: SRBM_SOFT_RESET=0x00000100
[ 48.468854] [drm] recover vram bo from shadow start
[ 48.468855] [drm] recover vram bo from shadow done
[ 48.468857] [drm] Skip scheduling IBs!
[ 48.500792] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[ 48.502030] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[ 48.503933] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[ 49.144048] amdgpu 0000:00:01.0: GPU reset(2) succeeded!
[ 49.147491] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[ 53.186659] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
[ 56.651026] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize
parser -125!
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 4886 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2019-08-30 6:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 6:21 bugzilla-daemon [this message]
2019-08-30 6:22 ` [Bug 111524] AMD A9 R5 GPU doesn't work after resume bugzilla-daemon
2019-08-30 12:56 ` bugzilla-daemon
2019-09-02 5:43 ` bugzilla-daemon
2019-09-02 5:44 ` bugzilla-daemon
2019-09-02 18:34 ` bugzilla-daemon
2019-11-19 9:50 ` 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-111524-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.