Bug 111148 - [CI][DRMTIP][GUC] igt@i915_suspend@debugfs-reader - dmesg-warn - *ERROR* no sub-buffer to capture logs
Summary: [CI][DRMTIP][GUC] igt@i915_suspend@debugfs-reader - dmesg-warn - *ERROR* no s...
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Robert M. Fosha
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-16 10:50 UTC by Lakshmi
Modified: 2019-09-10 23:08 UTC (History)
2 users (show)

See Also:
i915 platform: BXT
i915 features: firmware/guc


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lakshmi 2019-07-16 10:50:00 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_322/fi-apl-guc/igt@i915_suspend@debugfs-reader.html

<7> [283.845077] [drm:drm_detect_monitor_audio] Monitor has basic audio support
<7> [283.845523] [drm:drm_helper_hpd_irq_event] [CONNECTOR:100:DP-1] status updated from connected to connected
<7> [283.845637] [drm:intel_dp_detect [i915]] [CONNECTOR:109:DP-2]
<7> [283.845669] [drm:drm_helper_hpd_irq_event] [CONNECTOR:109:DP-2] status updated from disconnected to disconnected
<6> [283.847766] ahci 0000:00:12.0: port does not support device sleep
<3> [284.248566] [drm:guc_log_capture_logs [i915]] *ERROR* no sub-buffer to capture logs
<3> [284.249306] [drm:guc_log_capture_logs [i915]] *ERROR* no sub-buffer to capture logs
<3> [284.249956] [drm:guc_log_capture_logs [i915]] *ERROR* no sub-buffer to capture logs
<3> [284.250782] [drm:guc_log_capture_logs [i915]] *ERROR* no sub-buffer to capture logs
<3> [284.251431] [drm:guc_log_capture_logs [i915]] *ERROR* no sub-buffer to capture logs
<3> [284.251900] [drm:guc_log_capture_logs [i915]] *ERROR* no sub-buffer to capture logs
<3> [284.252529] [drm:guc_log_capture_logs [i915]] *ERROR* no sub-buffer to capture logs
<3> [284.253155] [drm:guc_log_capture_logs [i915]] *ERROR* no sub-buffer to capture logs
<3> [284.253607] [drm:guc_log_capture_logs [i915]] *ERROR* no sub-buffer to capture logs
<3> [284.254020] [drm:guc_log_capture_logs [i915]] *ERROR* no sub-buffer to capture logs
<7> [284.802924] [drm:i915_audio_component_get_eld [i915]] Not valid for port B
<7> [284.803055] [drm:i915_audio_component_get_eld [i915]] Not valid for port B
<7> [284.803182] [drm:i915_audio_component_get_eld [i915]] Not valid for port C
<7> [284.803309] [drm:i915_audio_component_get_eld [i915]] Not valid for port C
<7> [284.803435] [drm:i915_audio_component_get_eld [i915]] Not valid for port C
<7> [284.803562] [drm:i915_audio_component_get_eld [i915]] Not valid for port D
<7> [284.803688] [drm:i915_audio_component_get_eld [i915]] Not valid for port D
<7> [284.803839] [drm:i915_audio_component_get_eld [i915]] Not valid for port D
<6> [284.842931] OOM killer enabled.
<6> [284.842939] Restarting tasks ... done.
<6> [284.893606] video LNXVIDEO:00: Restoring backlight state
<6> [284.893618] PM: suspend exit
<7> [284.942996] [drm:intel_power_well_enable [i915]] enabling dpio-common-a
<7> [284.947866] [drm:intel_power_well_disable [i915]] disabling dpio-common-a
<5> [284.977581] i915 0000:00:02.0: GuC log buffer overflow
<7> [285.029033] [drm:intel_power_well_enable [i915]] enabling dpio-common-a
<7> [285.029254] [drm:intel_power_well_disable [i915]] disabling dpio-common-a
<7> [285.102959] [drm:intel_power_well_enable [i915]] enabling dpio-common-a
<7> [285.103125] [drm:intel_power_well_disable [i915]] disabling dpio-common-a
<7> [285.178891] [drm:intel_power_well_enable [i915]] enabling dpio-common-a
<7> [285.179062] [drm:intel_power_well_disable [i915]] disabling dpio-common-a
<7> [285.254095] [drm:intel_power_well_enable [i915]] enabling dpio-common-a
<7> [285.254320] [drm:intel_power_well_disable [i915]] disabling dpio-common-a
<7> [285.330313] [drm:intel_power_well_enable [i915]] enabling dpio-common-a
<7> [285.330479] [drm:intel_power_well_disable [i915]] disabling dpio-common-a
<7> [285.407081] [drm:intel_power_well_enable [i915]] enabling dpio-common-a
<7> [285.407257] [drm:intel_power_well_disable [i915]] disabling dpio-common-a
<7> [285.482162] [drm:intel_power_well_enable [i915]] enabling dpio-common-a
<7> [285.482387] [drm:intel_power_well_disable [i915]] disabling dpio-common-a
<7> [285.556478] [drm:intel_power_well_enable [i915]] enabling dpio-common-a
<7> [285.556642] [drm:intel_power_well_disable [i915]] disabling dpio-common-a
<7> [285.632692] [drm:intel_power_well_enable [i915]] enabling dpio-common-a
<7> [285.632946] [drm:intel_power_well_disable [i915]] disabling dpio-common-a
<7> [285.707422] [drm:intel_power_well_enable [i915]] enabling dpio-common-a
<7> [285.707587] [drm:intel_power_well_disable [i915]] disabling dpio-common-a
<7> [285.782928] [drm:intel_power_well_enable [i915]] enabling dpio-common-a
<7> [285.783143] [drm:intel_power_well_disable [i915]] disabling dpio-common-a
<7> [285.857986] [drm:intel_power_well_enable [i915]] enabling dpio-common-a
<7> [285.858207] [drm:intel_power_well_disable [i915]] disabling dpio-common-a
<6> [285.897164] [IGT] i915_suspend: exiting, ret=0
<5> [285.897842] Setting dangerous option reset - tainting kernel
<6> [285.910388] Console: switching to colour frame buffer device 240x67
Comment 1 CI Bug Log 2019-07-16 10:50:34 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* GUC: igt@i915_suspend@debugfs-reader - dmesg-warn - *ERROR* no sub-buffer to capture logs
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_322/fi-apl-guc/igt@i915_suspend@debugfs-reader.html
Comment 2 Jon Ewins 2019-08-21 01:23:53 UTC
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.
Comment 3 Jon Ewins 2019-09-10 01:16:14 UTC
Same issue as 109536 and 111165. Proposed fix tested and passing.  Patches in prep for posting.
Comment 4 Robert M. Fosha 2019-09-10 23:08:04 UTC
RFC patch sent out for review: drm/i915/guc: Enable guc logging on guc log relay write.

While creating and testing the patch also noticed that the IGT tool intel_guc_logger needs to be updated for the new relay implementation. Will create another patch to update the IGT tool.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.