From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 197327] radeon 0000:01:00.0: failed VCE resume (-110).
Date: Thu, 08 Feb 2018 20:23:53 +0000 [thread overview]
Message-ID: <bug-197327-2300-mvW1Xc7gxp@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-197327-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=197327
Eugene (ken20001@ukr.net) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ken20001@ukr.net
--- Comment #4 from Eugene (ken20001@ukr.net) ---
$ uname -a
Linux GA-MA790FX-DQ6 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25
10:13:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ lspci | grep -i vga
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland
PRO [Radeon R7 240/340]
$ dmesg | grep -i "failed VCE resume" -A7 -B20
[ 1.890001] [TTM] Initializing DMA pool allocator
[ 1.890025] [drm] radeon: 1024M of VRAM memory ready
[ 1.890026] [drm] radeon: 2048M of GTT memory ready.
[ 1.890034] [drm] Loading oland Microcode
[ 1.890191] [drm] Internal thermal controller with fan control
[ 1.890268] [drm] probing gen 2 caps for device 1002:5978 = 300d02/0
[ 1.897887] [drm] radeon: dpm initialized
[ 1.903155] [drm] Found VCE firmware/feedback version 50.0.1 / 17!
[ 1.903218] [drm] GART: num cpu pages 524288, num gpu pages 524288
[ 1.906208] [drm] probing gen 2 caps for device 1002:5978 = 300d02/0
[ 1.906211] [drm] PCIE gen 2 link speeds already enabled
[ 1.912329] r8169 0000:03:00.0 enp3s0: renamed from eth1
[ 1.921990] [drm] PCIE GART of 2048M enabled (table at 0x00000000001D6000).
[ 1.922107] radeon 0000:01:00.0: WB enabled
[ 1.922110] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr
0x0000000040000c00 and cpu addr 0xffff99599f7e5c00
[ 1.922112] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr
0x0000000040000c04 and cpu addr 0xffff99599f7e5c04
[ 1.922114] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr
0x0000000040000c08 and cpu addr 0xffff99599f7e5c08
[ 1.922115] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr
0x0000000040000c0c and cpu addr 0xffff99599f7e5c0c
[ 1.922116] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr
0x0000000040000c10 and cpu addr 0xffff99599f7e5c10
[ 1.922515] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr
0x0000000000075a18 and cpu addr 0xffffb8da41435a18
[ 2.022790] radeon 0000:01:00.0: failed VCE resume (-110).
[ 2.022848] firewire_ohci 0000:06:0e.0: added OHCI v1.10 device as card 0, 4
IR + 8 IT contexts, quirks 0x2
[ 2.022858] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 2.022859] [drm] Driver supports precise vblank timestamp query.
[ 2.022860] radeon 0000:01:00.0: radeon: MSI limited to 32-bit
[ 2.022908] radeon 0000:01:00.0: radeon: using MSI.
[ 2.022946] [drm] radeon: irq initialized.
[ 2.026917] ata9.00: ATAPI: Optiarc DVD RW AD-7170A, 1.02, max UDMA/66
P.S. dmesg is in attachment
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-02-08 20:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 20:59 [Bug 197327] New: radeon 0000:01:00.0: failed VCE resume (-110) bugzilla-daemon
2017-10-20 8:57 ` [Bug 197327] " bugzilla-daemon
2017-10-20 14:57 ` bugzilla-daemon
2018-01-23 14:22 ` bugzilla-daemon
2018-02-08 20:23 ` bugzilla-daemon [this message]
2018-02-08 20:26 ` bugzilla-daemon
2018-04-03 8:06 ` bugzilla-daemon
2018-06-18 19:11 ` bugzilla-daemon
2019-04-15 8:18 ` bugzilla-daemon
2019-07-14 21:02 ` bugzilla-daemon
2019-08-23 6:49 ` bugzilla-daemon
2021-02-16 5:11 ` 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-197327-2300-mvW1Xc7gxp@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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.