From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 70701] With DPM enabled, Radeon 4570 (R710) doesn't remain in Single_Disp state
Date: Tue, 18 Feb 2014 20:15:17 +0000 [thread overview]
Message-ID: <bug-70701-2300-TyRrfi5AgC@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-70701-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=70701
--- Comment #4 from Abhinav K <abhinav.kumar.in@gmail.com> ---
Thanks a lot.
I am seeing these vblank_time values. But everything seems fine with no screen
blanking or screen artifacts. Clocks and temperature is also under control.
[ 22.542092] tg3 0000:08:00.0 eth0: Link is up at 100 Mbps, full duplex
[ 22.542096] tg3 0000:08:00.0 eth0: Flow control is on for TX and on for RX
[ 22.542117] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 24.364133] [drm] vblank_time: 294
[ 25.180308] [drm] vblank_time: 294
[ 1337.236122] [drm] vblank_time: 4294967295
[ 1337.340217] [drm] vblank_time: 4294967295
[ 1937.476218] [drm] vblank_time: 294
[ 1938.936214] [drm] vblank_time: 4294967295
[ 2537.836213] [drm] vblank_time: 294
[ 2539.296439] [drm] vblank_time: 4294967295
[ 7282.380994] perf samples too long (2502 > 2500), lowering
kernel.perf_event_max_sample_rate to 50000
[11578.016133] [drm] vblank_time: 294
abhinav@abhinav-Mintk:~ > sudo cat /sys/kernel/debug/dri/64/radeon_pm_info
uvd vclk: 0 dclk: 0
power level 0 sclk: 22000 mclk: 30000 vddc: 900
abhinav@abhinav-Mintk:~ >
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-02-18 20:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 8:49 [Bug 70701] New: With DPM enabled, Radeon 4570 (R710) doesn't remain in Single_Disp state bugzilla-daemon
2014-02-17 17:47 ` [Bug 70701] " bugzilla-daemon
2014-02-18 11:14 ` bugzilla-daemon
2014-02-18 14:23 ` bugzilla-daemon
2014-02-18 20:15 ` bugzilla-daemon [this message]
2014-02-27 22:00 ` 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-70701-2300-TyRrfi5AgC@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.