[Bug 110817] [CI][DRMTIP][GUC] GUC: igt at debugfs_test@((read_all_entries_display_off)|(read_all_entries)|(read_all_entries_display_on))|i915_pm_rpm at debugfs-read|i915_suspend at debugfs-reader - dmesg warn - *ERROR* GuC log buffer overflow

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Jun 18 10:40:51 UTC 2019


https://bugs.freedesktop.org/show_bug.cgi?id=110817

Chris Wilson <chris at chris-wilson.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Chris Wilson <chris at chris-wilson.co.uk> ---
Should be squelched by:

commit 4951dc0178ba144619e9c20ed71f7ff006282bbf (HEAD -> drm-intel-next-queued,
drm-intel/for-linux-next, drm-intel/drm-intel-next-queued)
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Mon Jun 17 11:09:17 2019 +0100

    drm/i915/guc: Reduce verbosity on log overflows

    If the user is clearing the log buffer too slowly, we overflow. As this
    is an expected condition, and the driver tries to handle it, reduce the
    error message down to a notice.

    Michal mentioned that another cause would be incorrect reset handling,
    so we don't want to lose the notification entirely.

    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110817
    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Cc: Michal Wajdeczko <michal.wajdeczko at intel.com>
    Cc: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
    Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
    Link:
https://patchwork.freedesktop.org/patch/msgid/20190617100917.13110-1-chris@chris-wilson.co.uk

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20190618/156dfdbe/attachment.html>


More information about the intel-gfx-bugs mailing list