Bug 110364 - [CI][DRMTIP] igt@gem_* - dmesg-fail/incomplete - Poison overwritten
Summary: [CI][DRMTIP] igt@gem_* - dmesg-fail/incomplete - Poison overwritten
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-09 07:00 UTC by Lakshmi
Modified: 2019-08-09 12:59 UTC (History)
1 user (show)

See Also:
i915 platform: ICL
i915 features: GEM/Other


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lakshmi 2019-04-09 07:00:22 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_250/fi-icl-y/igt@gem_ppgtt@blt-vs-render-ctxn.html

<6> [440.748701] Console: switching to colour dummy device 80x25
<6> [440.748750] [IGT] gem_ppgtt: executing
<6> [440.752909] [IGT] gem_ppgtt: starting subtest blt-vs-render-ctxN
<7> [441.753574] [drm:intel_edp_drrs_downclock_work [i915]] eDP Refresh Rate set to : 40Hz
<7> [443.498643] [drm:edp_panel_vdd_off_sync [i915]] Turning eDP port A VDD off
<7> [443.498823] [drm:edp_panel_vdd_off_sync [i915]] PP_STATUS: 0x80000008 PP_CONTROL: 0x00000067
<7> [443.498869] [drm:intel_power_well_disable [i915]] disabling DC off
<7> [443.498916] [drm:skl_enable_dc6 [i915]] Enabling DC6
<7> [443.498958] [drm:gen9_set_dc_state [i915]] Setting DC state from 00 to 02
<3> [458.547413] =============================================================================
<3> [458.547897] BUG kmalloc-4k (Tainted: G     U           ): Poison overwritten
<3> [458.547967] -----------------------------------------------------------------------------

<4> [458.548061] Disabling lock debugging due to kernel taint
<4> [458.548064] irq event stamp: 1656572
<3> [458.548069] INFO: 0x00000000b3d04456-0x0000000003c0a452. First byte 0x69 instead of 0x6b
<4> [458.548079] hardirqs last  enabled at (1656571): [<ffffffffb09b4d9c>] _raw_spin_unlock_irqrestore+0x4c/0x60
<4> [458.548085] hardirqs last disabled at (1656572): [<ffffffffb09b4c0d>] _raw_spin_lock_irqsave+0xd/0x50
<3> [458.548110] INFO: Slab 0x00000000af2732a9 objects=7 used=7 fp=0x          (null) flags=0x8000000000010200
<4> [458.548117] softirqs last  enabled at (1656084): [<ffffffffb0c0033a>] __do_softirq+0x33a/0x4b9
<3> [458.548143] INFO: Object 0x00000000db9be65c @offset=8872 fp=0x0000000092d2f87a
Comment 1 CI Bug Log 2019-04-09 07:02:21 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* ICL: igt@gem_ppgtt@blt-vs-render-ctxn - dmesg-fail - BUG kmalloc-4k (Tainted.*): Poison overwritten
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_250/fi-icl-y/igt@gem_ppgtt@blt-vs-render-ctxn.html
Comment 2 CI Bug Log 2019-04-09 07:07:35 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* ICL:  igt@runner@aborted - fail - Previous test: gem_ppgtt (blt-vs-render-ctxn)
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_250/fi-icl-y/igt@runner@aborted.html
Comment 3 Chris Wilson 2019-04-09 07:48:00 UTC
In the middle of nowhere, a block of 5 pointer-sized values had 0x2 removed. Sounds like a bunch of radixtree tags? That's the first thing that springs to mind as using a tight array of pointers and bit manipulation.
Comment 4 CI Bug Log 2019-04-09 09:57:21 UTC
A CI Bug Log filter associated to this bug has been updated:

{- ICL: igt@gem_ppgtt@blt-vs-render-ctxn - dmesg-fail - BUG kmalloc-4k (Tainted.*): Poison overwritten -}
{+ ICL: igt@gem_*- dmesg-fail/incomplete - Poison overwritten +}

New failures caught by the filter:

* https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_250/fi-icl-y/igt@gem_mmap_gtt@hang.html
Comment 5 Lakshmi 2019-08-09 12:59:21 UTC
Occurred once on drmtip_250 (4 months ago). Closing this issue as WORKSFORME.
Comment 6 CI Bug Log 2019-08-09 12:59:27 UTC
The CI Bug Log issue associated to this bug has been archived.

New failures matching the above filters will not be associated to this bug anymore.


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.