From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89521] New: Radeon driver fails to set dpm power state after resume from S3
Date: Wed, 10 Dec 2014 17:32:54 +0000 [thread overview]
Message-ID: <bug-89521-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=89521
Bug ID: 89521
Summary: Radeon driver fails to set dpm power state after
resume from S3
Product: Drivers
Version: 2.5
Kernel Version: 3.18.0
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: anhermann@gmx.net
Regression: No
Created attachment 160341
--> https://bugzilla.kernel.org/attachment.cgi?id=160341&action=edit
dmesg output from 3 resume cycles
Using a Radeon R9 270X and kernel 3.18.0 I get the following error message only
after resume from S3 state:
[drm:si_dpm_set_power_state] *ERROR* si_set_sw_state failed
I would like to notice that this also happened with older kernel versions (3.17
and 3.16 with radeon.dpm=1) and other cards. My other PC has a HD 5450 with the
same problem (slightly other ERROR string as its not SI).
Besides the error message, I cannot see any strange behaviour, performance is
good, no freezes etc. . But it sounds like performance level switching is not
working correctly?
I added the dmesg output showing three resume cycles with the mentioned error
message as attachment.
Thanks
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2014-12-10 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 17:32 bugzilla-daemon [this message]
2016-02-19 9:20 ` [Bug 89521] Radeon driver fails to set dpm power state after resume from S3 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-89521-2300@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.