From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106548] Failed GfxDrv_DriverAcceptanceQuery.GL_GPU_FREQ_OVERRIDE_MDAPI
Date: Fri, 25 May 2018 13:46:42 +0000 [thread overview]
Message-ID: <bug-106548-502-V9rGNVPazp@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106548-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1794 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106548
--- Comment #10 from Francesco Balestrieri <francesco.balestrieri@intel.com> ---
Indeed, after some more investigation I found out that the test case uses (via
MDAPI) the root-only interface:
/sys/devices/pci0000:00/0000:00:02.0/drm/card0/gt_boost_freq_mhz
/sys/devices/pci0000:00/0000:00:02.0/drm/card0/gt_max_freq_mhz
/sys/devices/pci0000:00/0000:00:02.0/drm/card0/gt_min_freq_mhz
to ask the kernel to maintain a static GPU frequency, and then reads it back to
check that it stays within a range of the requested value. The test fails
because the value it reads back is not what it requested (reproduced with
drm-tip). I still don't have dmesg output with debug logs enabled but I'l try
to get it next week.
For the records, this is what the test prints out once it is run as root:
[ RUN ] GfxDrv_DriverAcceptanceQuery.GL_GPU_FREQ_OVERRIDE_MDAPI
AvgGpuCoreFrequencyMHz = 947 ( expected in range [855, 950] )
AvgGpuCoreFrequencyMHz = 948 ( expected in range [855, 950] )
AvgGpuCoreFrequencyMHz = 948 ( expected in range [855, 950] )
AvgGpuCoreFrequencyMHz = 947 ( expected in range [855, 950] )
AvgGpuCoreFrequencyMHz = 948 ( expected in range [855, 950] )
AvgGpuCoreFrequencyMHz = 947 ( expected in range [855, 950] )
AvgGpuCoreFrequencyMHz = 948 ( expected in range [855, 950] )
AvgGpuCoreFrequencyMHz = 947 ( expected in range [855, 950] )
AvgGpuCoreFrequencyMHz = 947 ( expected in range [855, 950] )
AvgGpuCoreFrequencyMHz = 797 ( expected in range [855, 950] ) =>
OUT OF RANGE!
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2648 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
next prev parent reply other threads:[~2018-05-25 13:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 8:27 [Bug 106548] Failed GfxDrv_DriverAcceptanceQuery.GL_GPU_FREQ_OVERRIDE_MDAPI bugzilla-daemon
2018-05-17 10:12 ` bugzilla-daemon
2018-05-17 10:13 ` bugzilla-daemon
2018-05-17 10:35 ` bugzilla-daemon
2018-05-17 14:39 ` bugzilla-daemon
2018-05-19 5:20 ` bugzilla-daemon
2018-05-21 8:50 ` bugzilla-daemon
2018-05-21 10:38 ` bugzilla-daemon
2018-05-24 18:11 ` bugzilla-daemon
2018-05-25 7:50 ` bugzilla-daemon
2018-05-25 7:55 ` bugzilla-daemon
2018-05-25 13:46 ` bugzilla-daemon [this message]
2018-05-25 14:05 ` bugzilla-daemon
2018-05-25 15:30 ` bugzilla-daemon
2018-05-25 15:49 ` bugzilla-daemon
2019-09-18 19:41 ` 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-106548-502-V9rGNVPazp@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