From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105915] [IGT] igt@kms_cursor_crc@cursor-128x128-rapid-movement / cursor-256x256-rapid-movement igt-debugfs-WARNING: Warning on condition crc->crc[i] == 0xffffffff in function crc_sanity_checks, file igt_debugfs.c:833
Date: Thu, 05 Apr 2018 20:28:31 +0000 [thread overview]
Message-ID: <bug-105915-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2409 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105915
Bug ID: 105915
Summary: [IGT] igt@kms_cursor_crc@cursor-128x128-rapid-movement
/ cursor-256x256-rapid-movement igt-debugfs-WARNING:
Warning on condition crc->crc[i] == 0xffffffff in
function crc_sanity_checks, file igt_debugfs.c:833
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: IGT
Assignee: dri-devel@lists.freedesktop.org
Reporter: ricardo.o.perez@intel.com
Created attachment 138642
--> https://bugs.freedesktop.org/attachment.cgi?id=138642&action=edit
dmesg and kern-logs
CNL QA systems are showing a WARN with the following tests:
igt@kms_cursor_crc@cursor-128x128-rapid-movement
igt@kms_cursor_crc@cursor-256x256-rapid-movement
Software Version:
IGT-Version: 1.22-g0721161 (x86_64) (Linux:
4.16.0-rc6-drm-intel-qa-ww12-commit-4db112a+ x86_64)
Warn:
Beginning cursor-256x256-rapid-movement on pipe A, connector eDP-1
cursor-256x256-rapid-movement on pipe A, connector eDP-1: PASSED
Beginning cursor-256x256-rapid-movement on pipe A, connector HDMI-A-1
cursor-256x256-rapid-movement on pipe A, connector HDMI-A-1: PASSED
Beginning cursor-256x256-rapid-movement on pipe B, connector eDP-1
cursor-256x256-rapid-movement on pipe B, connector eDP-1: PASSED
Beginning cursor-256x256-rapid-movement on pipe B, connector HDMI-A-1
cursor-256x256-rapid-movement on pipe B, connector HDMI-A-1: PASSED
Beginning cursor-256x256-rapid-movement on pipe C, connector eDP-1
cursor-256x256-rapid-movement on pipe C, connector eDP-1: PASSED
Beginning cursor-256x256-rapid-movement on pipe C, connector HDMI-A-1
cursor-256x256-rapid-movement on pipe C, connector HDMI-A-1: PASSED
Subtest cursor-256x256-rapid-movement: SUCCESS (4.677s)
-------------
kms_cursor_crc:18385) igt-debugfs-WARNING: Warning on condition crc->crc[i] ==
0xffffffff in function crc_sanity_checks, file igt_debugfs.c:833
(kms_cursor_crc:18385) igt-debugfs-WARNING: Suspicious CRC: it looks like the
CRC read back was from a register in a powered down well
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3973 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 reply other threads:[~2018-04-05 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 20:28 bugzilla-daemon [this message]
2019-02-25 10:03 ` [Bug 105915] [IGT] igt@kms_cursor_crc@cursor-128x128-rapid-movement / cursor-256x256-rapid-movement igt-debugfs-WARNING: Warning on condition crc->crc[i] == 0xffffffff in function crc_sanity_checks, file igt_debugfs.c:833 bugzilla-daemon
2019-02-25 10:04 ` 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-105915-502@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 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.