From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93288] dpm malfunction on radeon hawaii r9 390X
Date: Tue, 08 Dec 2015 02:20:26 +0000 [thread overview]
Message-ID: <bug-93288-502-7GPBWBFYdP@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93288-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1579 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93288
--- Comment #5 from Thomas DEBESSE <dev@illwieckz.net> ---
I reproduced it right now. For the first time in my life it does not at gnome
session loading, I started the Unigine Valley Benchmark to stress test a little
the GPU.
`dmesg | grep ERROR` said:
[ 425.896560] [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for
more than 5secs aborting
[ 425.896593] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck
executing BD42 (len 254, WS 0, PS 4) @ 0xBD6C
[ 425.896621] [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck
executing B2B6 (len 145, WS 0, PS 8) @ 0xB341
[ 426.113327] [drm:ci_dpm_enable [radeon]] *ERROR* ci_start_dpm failed
[ 426.113372] [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume
failed
[ 426.903401] [drm:cik_ring_test [radeon]] *ERROR* radeon: ring 0 test failed
(scratch(0x3010C)=0xCAFEDEAD)
[ 426.903456] [drm:cik_resume [radeon]] *ERROR* cik startup failed on resume
[ 426.903573] [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume
failed
[ 436.916775] [drm:radeon_vce_ib_test [radeon]] *ERROR* radeon: fence wait
failed (-35).
[ 436.916816] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed
testing IB on ring 6 (-35).
[ 436.952672] [drm:radeon_vce_ib_test [radeon]] *ERROR* radeon: fence wait
failed (-35).
[ 436.952712] [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed
testing IB on ring 7 (-35).
see the full dmesg log I will attach
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2334 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-12-08 2:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 1:13 [Bug 93288] dpm malfunction on radeon hawaii r9 390X bugzilla-daemon
2015-12-08 1:18 ` bugzilla-daemon
2015-12-08 1:18 ` bugzilla-daemon
2015-12-08 1:20 ` bugzilla-daemon
2015-12-08 1:23 ` bugzilla-daemon
2015-12-08 2:20 ` bugzilla-daemon [this message]
2015-12-08 2:21 ` bugzilla-daemon
2015-12-08 2:21 ` bugzilla-daemon
2015-12-08 2:34 ` bugzilla-daemon
2015-12-09 5:48 ` bugzilla-daemon
2015-12-09 16:37 ` bugzilla-daemon
2016-01-14 13:33 ` [Bug 93288] dpm malfunction on radeon grenada " bugzilla-daemon
2016-01-14 13:34 ` bugzilla-daemon
2016-08-18 0:04 ` bugzilla-daemon
2016-08-18 0:07 ` bugzilla-daemon
2016-08-18 0:32 ` 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-93288-502-7GPBWBFYdP@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