[Bug 106062] [CI] igt at drv_module_reload@basic-no-display - i915: unknown parameter 'enable_guc_loading' ignored && WARNING: CPU: 7 PID: 1530 at lib/plist.c:42 plist_check_prev_next+0x2d/0x40

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Apr 16 08:43:42 UTC 2018


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

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

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

--- Comment #2 from Chris Wilson <chris at chris-wilson.co.uk> ---
I believe,

commit 9f172f6fbd243759c808d97bd83c95e49325b2c9
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Sat Apr 14 10:12:33 2018 +0100

    drm/i915: Call i915_perf_fini() on init_hw error unwind

    We have to cleanup after i915_perf_init(), even on the error path, as it
    passes a pointer into the module to the sysfs core. If we fail to
    unregister the sysctl table, we leave a dangling pointer which then may
    explode anytime later.

    Fixes: 9f9b2792b6d3 ("drm/i915/perf: reuse timestamp frequency from device
info")
    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
    Cc: Lionel Landwerlin <lionel.g.landwerlin at intel.com>
    Cc: Matthew Auld <matthew.auld at intel.com>
    Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin at intel.com>
    Reviewed-by: Michal Wajdeczko <michal.wajdeczko at intel.com>
    Link:
https://patchwork.freedesktop.org/patch/msgid/20180414091233.32224-1-chris@chris-wilson.co.uk

It's hard to be sure since it causes memcorruption and dies in various ways on
subsequent tests.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee 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/20180416/bcacada9/attachment.html>


More information about the intel-gfx-bugs mailing list