[Bug 111165] [CI][BAT][guc] igt at debugfs_test@read_all_entries_display_off - dmesg-warn - WARN_ON(!intel_guc_log_relay_enabled(log))
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Aug 21 01:23:50 UTC 2019
https://bugs.freedesktop.org/show_bug.cgi?id=111165
--- Comment #12 from Jon Ewins <jon.ewins at intel.com> ---
The relay log is a developer only feature and an extension of the standard GuC
logging mechanism. Its testing should not be part of the BAT set. It is being
implicitly enabled by existing tests, which provide no consumer for the logs.
The issue is that IGT tests that cycle through reading the debugfs entries will
call the open file op for the guc_log_relay control file and this currently
causes the file to be both created and the logging to be started. These tests
have no consumer for the logs which go on to overflow, run out of sub-buffers
or misbehave in suspend and reset handling.
A proposed change, that will follow as RFC patches, is to separate the creation
and logging start, updating the guc_log_relay_write function, which currently
just flushes the log, to also support starting the logging based on the value
written.
An additional new test to actually explicitly test this relay log developer
feature will follow separately.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190821/47725804/attachment.html>
More information about the intel-gfx-bugs
mailing list