dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 95247] System hangs after ~10 minutes when using Radeon R9 390
Date: Tue, 03 May 2016 06:53:52 +0000	[thread overview]
Message-ID: <bug-95247-502-jTrQ5K7Bgx@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-95247-502@http.bugs.freedesktop.org/>


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

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

--- Comment #2 from Sandeep <sandy.8925@gmail.com> ---
May 02 23:37:32 GetsugaTenshou kernel: [drm:ci_dpm_enable [radeon]] *ERROR*
ci_start_dpm failed
May 02 23:37:32 GetsugaTenshou kernel: [drm:radeon_pm_resume [radeon]] *ERROR*
radeon: dpm resume failed
May 02 23:37:32 GetsugaTenshou kernel: [drm] probing gen 2 caps for device
8086:1901 = 261ad03/e
May 02 23:37:32 GetsugaTenshou kernel: [drm] PCIE gen 3 link speeds already
enabled
May 02 23:37:32 GetsugaTenshou kernel: [drm] PCIE GART of 2048M enabled (table
at 0x0000000000324000).
May 02 23:37:32 GetsugaTenshou kernel: radeon 0000:01:00.0: WB enabled
May 02 23:37:32 GetsugaTenshou kernel: radeon 0000:01:00.0: fence driver on
ring 0 use gpu addr 0x0000000200000c00 and cpu addr 0xffff880459248c00
May 02 23:37:32 GetsugaTenshou kernel: radeon 0000:01:00.0: fence driver on
ring 1 use gpu addr 0x0000000200000c04 and cpu addr 0xffff880459248c04
May 02 23:37:32 GetsugaTenshou kernel: radeon 0000:01:00.0: fence driver on
ring 2 use gpu addr 0x0000000200000c08 and cpu addr 0xffff880459248c08
May 02 23:37:32 GetsugaTenshou kernel: radeon 0000:01:00.0: fence driver on
ring 3 use gpu addr 0x0000000200000c0c and cpu addr 0xffff880459248c0c
May 02 23:37:32 GetsugaTenshou kernel: radeon 0000:01:00.0: fence driver on
ring 4 use gpu addr 0x0000000200000c10 and cpu addr 0xffff880459248c10
May 02 23:37:32 GetsugaTenshou kernel: radeon 0000:01:00.0: fence driver on
ring 5 use gpu addr 0x0000000000076c98 and cpu addr 0xffffc90004c36c98
May 02 23:37:32 GetsugaTenshou kernel: radeon 0000:01:00.0: fence driver on
ring 6 use gpu addr 0x0000000200000c18 and cpu addr 0xffff880459248c18
May 02 23:37:32 GetsugaTenshou kernel: radeon 0000:01:00.0: fence driver on
ring 7 use gpu addr 0x0000000200000c1c and cpu addr 0xffff880459248c1c
May 02 23:37:32 GetsugaTenshou kernel: [drm] ring test on 0 succeeded in 4
usecs
May 02 23:37:32 GetsugaTenshou kernel: [drm] ring test on 1 succeeded in 3
usecs
May 02 23:37:32 GetsugaTenshou kernel: [drm] ring test on 2 succeeded in 2
usecs
May 02 23:37:32 GetsugaTenshou kernel: [drm] ring test on 3 succeeded in 5
usecs
May 02 23:37:32 GetsugaTenshou kernel: [drm] ring test on 4 succeeded in 5
usecs
May 02 23:37:32 GetsugaTenshou kernel: [drm] ring test on 5 succeeded in 2
usecs
May 02 23:37:32 GetsugaTenshou kernel: sysrq: SysRq : Emergency Sync
May 02 23:37:32 GetsugaTenshou kernel: [drm] UVD initialized successfully.
May 02 23:37:32 GetsugaTenshou kernel: [drm] ring test on 6 succeeded in 1168
usecs
May 02 23:37:32 GetsugaTenshou kernel: [drm] ring test on 7 succeeded in 4
usecs
May 02 23:37:32 GetsugaTenshou kernel: [drm] VCE initialized successfully.
May 02 23:37:32 GetsugaTenshou kernel: [drm:radeon_pm_resume [radeon]] *ERROR*
radeon: dpm resume failed
May 02 23:37:32 GetsugaTenshou kernel: [drm] ib test on ring 0 succeeded in 0
usecs
May 02 23:37:32 GetsugaTenshou kernel: [drm] ib test on ring 1 succeeded in 0
usecs

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

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

  parent reply	other threads:[~2016-05-03  6:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-03  6:46 [Bug 95247] System hangs after ~10 minutes when using Radeon R9 390 bugzilla-daemon
2016-05-03  6:51 ` bugzilla-daemon
2016-05-03  6:53 ` bugzilla-daemon [this message]
2016-05-04  7:31 ` bugzilla-daemon
2016-05-12  5:40 ` bugzilla-daemon
2016-06-04 19:38 ` bugzilla-daemon
2016-06-06  3:36 ` bugzilla-daemon
2016-08-06 20:35 ` bugzilla-daemon
2016-10-10  4:39 ` bugzilla-daemon
2019-11-19  9:16 ` 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-95247-502-jTrQ5K7Bgx@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).