Summary: | [CI][BAT] igt@i915_selftest@live_mman - dmesg-warn - BUG drm_i915_gem_object: Poison overwritten | ||
---|---|---|---|
Product: | DRI | Reporter: | Martin Peres <martin.peres> |
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Status: | RESOLVED NOTOURBUG | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | normal | ||
Priority: | highest | CC: | intel-gfx-bugs |
Version: | XOrg git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | ReadyForDev | ||
i915 platform: | BSW/CHT | i915 features: | GEM/Other |
Description
Martin Peres
2019-07-01 13:31:04 UTC
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * BSW: igt@i915_selftest@live_mman - dmesg-warn - BUG drm_i915_gem_object: Poison overwritten - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13466/fi-bsw-n3050/igt@i915_selftest@live_mman.html If I am not mistaken, that is a stray 64b write of 1, 144 bytes into a i915_gem_object On my kernel that would put it around: offsetof(drm_gem_object.vma_node)=24 offsetofend(drm_gem_object.vma_node)=208 ... offsetof(drm_gem_object.vma_node.vm_node.rb_hole_addr)=144 That doesn't seem particularly valid for a rbtree_node.parent, so either it's a completely stray write, my counting is wrong and its not 144 bytes in, or there's a massive layout difference between my kernel and CI. Plonked in commit 3e03b51fcdedb947fdaaff36252f4daf3caf20be (HEAD -> topic/core-for-CI, drm-intel/topic/core-for-CI) Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Mon Jul 1 15:29:03 2019 +0100 mm: Show slab debug as offsets from section base not hashed pointers for better debug (i.e no unreliable counting by me) and writing this off as notourbug until we get a fresh hit. |
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.