From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 65761] HD 7970M Hybrid - hangs and errors and rmmod causes crash
Date: Fri, 31 Jan 2014 20:00:59 +0000 [thread overview]
Message-ID: <bug-65761-2300-mJrlmhz55m@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-65761-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=65761
--- Comment #25 from Christoph Haag <haagch.christoph@googlemail.com> ---
Created attachment 124041
--> https://bugzilla.kernel.org/attachment.cgi?id=124041&action=edit
just some printk to easily see what's going on
Well, I don't really know how it is supposed to work. I figured the easiest
thing I could do right now was adding some printk() to the code to have an
overview of what is happening in dmesg -H | grep radeonpm.
After booting up with no X I see this:
[ +0,000016] radeonpm: runtime_idle
[ +4,000483] radeonpm: runtime_suspend
After starting X this is added:
[Jan31 19:04] radeonpm: runtime_resume
[ +1,126688] radeonpm: runtime_idle
[ +0,000203] radeonpm: runtime_idle
[ +0,000400] radeonpm: runtime_idle
[ +0,000232] radeonpm: runtime_idle
But then it never does anything again.
After this, I did the usual xrandr --setprovideroffloadsink radeon Intel and
started and exited DRI_PRIME=1 glxgears and stuff, but nothing with radeonpm
was printed to the log again.
After a while I tried exiting X and sure enough, another line:
[ +2,368895] radeonpm: runtime_suspend
And after starting X for the second time:
[ +19,119650] radeonpm: runtime_resume
[ +1,131037] radeonpm: runtime_idle
And then... nothing with radeonpm again. I have read a bit in the
Documentation/power/runtime_pm.txt and maybe I did not catch it but I haven't
really seen when you call pm_runtime_put_autosuspend whether it is supposed to
eventually call back radeon_pmops_runtime_suspend but I would think that's what
it does, right? So that just never happens until X is quit.
After boot with no X running I see this with for i in
/sys/class/drm/card0/device/power/*; do echo "$i: $(cat $i)"; done
/sys/class/drm/card0/device/power/async: enabled
/sys/class/drm/card0/device/power/autosuspend_delay_ms: 5000
/sys/class/drm/card0/device/power/control: auto
/sys/class/drm/card0/device/power/runtime_active_kids: 0
/sys/class/drm/card0/device/power/runtime_active_time: 13260
/sys/class/drm/card0/device/power/runtime_enabled: enabled
/sys/class/drm/card0/device/power/runtime_status: suspended
/sys/class/drm/card0/device/power/runtime_suspended_time: 218426
/sys/class/drm/card0/device/power/runtime_usage: 0
[snipped some wakeup* stuff]
The GPU is off, fan is not running, etc.
After starting X I see this:
/sys/class/drm/card0/device/power/async: enabled
/sys/class/drm/card0/device/power/autosuspend_delay_ms: 5000
/sys/class/drm/card0/device/power/control: auto
/sys/class/drm/card0/device/power/runtime_active_kids: 0
/sys/class/drm/card0/device/power/runtime_active_time: 185230
/sys/class/drm/card0/device/power/runtime_enabled: enabled
/sys/class/drm/card0/device/power/runtime_status: active
/sys/class/drm/card0/device/power/runtime_suspended_time: 226856
/sys/class/drm/card0/device/power/runtime_usage: 0
runtime_status is always active in X...
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-01-31 20:01 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 16:49 [Bug 65761] New: HD 7970M Hybrid - hangs and errors and rmmod causes crash bugzilla-daemon
2013-11-25 17:15 ` [Bug 65761] " bugzilla-daemon
2013-11-26 20:03 ` bugzilla-daemon
2013-11-30 12:12 ` bugzilla-daemon
2013-12-06 22:21 ` bugzilla-daemon
2013-12-06 22:34 ` bugzilla-daemon
2013-12-07 1:06 ` bugzilla-daemon
2013-12-07 1:17 ` bugzilla-daemon
2013-12-24 15:45 ` bugzilla-daemon
2013-12-24 19:43 ` bugzilla-daemon
2013-12-24 19:45 ` bugzilla-daemon
2013-12-24 21:40 ` bugzilla-daemon
2014-01-06 11:57 ` bugzilla-daemon
2014-01-06 21:52 ` bugzilla-daemon
2014-01-19 23:22 ` bugzilla-daemon
2014-01-21 0:15 ` bugzilla-daemon
2014-01-21 0:23 ` bugzilla-daemon
2014-01-21 0:55 ` bugzilla-daemon
2014-01-21 21:58 ` bugzilla-daemon
2014-01-22 1:53 ` bugzilla-daemon
2014-01-22 1:53 ` bugzilla-daemon
2014-01-22 1:53 ` bugzilla-daemon
2014-01-24 2:20 ` bugzilla-daemon
2014-01-31 0:10 ` bugzilla-daemon
2014-01-31 14:14 ` bugzilla-daemon
2014-01-31 20:00 ` bugzilla-daemon [this message]
2014-01-31 20:46 ` bugzilla-daemon
2014-01-31 21:24 ` bugzilla-daemon
2014-01-31 23:00 ` bugzilla-daemon
2014-02-01 0:08 ` bugzilla-daemon
2014-02-02 23:58 ` bugzilla-daemon
2014-02-06 13:48 ` bugzilla-daemon
2014-02-07 0:49 ` bugzilla-daemon
2014-02-07 14:52 ` bugzilla-daemon
2014-02-07 22:39 ` bugzilla-daemon
2014-02-07 22:44 ` bugzilla-daemon
2014-02-07 22:47 ` bugzilla-daemon
2014-02-11 1:58 ` bugzilla-daemon
2014-02-11 7:30 ` bugzilla-daemon
2014-02-12 7:55 ` bugzilla-daemon
2014-02-12 9:41 ` bugzilla-daemon
2014-02-13 2:53 ` bugzilla-daemon
2014-02-13 9:00 ` bugzilla-daemon
2014-02-13 12:12 ` bugzilla-daemon
2014-02-14 2:59 ` bugzilla-daemon
2014-02-15 17:33 ` bugzilla-daemon
2014-02-17 17:04 ` bugzilla-daemon
2014-02-19 0:45 ` bugzilla-daemon
2014-02-19 0:46 ` bugzilla-daemon
2014-02-19 1:26 ` bugzilla-daemon
2014-02-19 2:45 ` bugzilla-daemon
2014-03-03 0:19 ` bugzilla-daemon
2014-03-03 0:20 ` bugzilla-daemon
2014-03-03 8:22 ` bugzilla-daemon
2014-03-03 23:16 ` bugzilla-daemon
2014-03-03 23:25 ` bugzilla-daemon
2014-04-01 9:00 ` bugzilla-daemon
2015-01-04 1:09 ` 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-65761-2300-mJrlmhz55m@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 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).