https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5366/shard-glk1/igt@i915_suspend@shrink.html <4> [1028.974227] i915_suspend invoked oom-killer: gfp_mask=0x6200ca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=1000 <4> [1028.981797] CPU: 0 PID: 8781 Comm: i915_suspend Tainted: G U 5.0.0-rc1-CI-CI_DRM_5366+ #1 <3> [1028.983043] Out of memory: Kill process 8781 (i915_suspend) score 1760 or sacrifice child <3> [1028.983828] Killed process 8781 (i915_suspend) total-vm:7969692kB, anon-rss:0kB, file-rss:0kB, shmem-rss:7491552kB <4> [1039.495856] i915_suspend invoked oom-killer: gfp_mask=0x6200ca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=1000 <4> [1039.495862] CPU: 1 PID: 8782 Comm: i915_suspend Tainted: G U 5.0.0-rc1-CI-CI_DRM_5366+ #1 <3> [1039.519727] Out of memory: Kill process 8782 (i915_suspend) score 1760 or sacrifice child <3> [1039.519769] Killed process 8782 (i915_suspend) total-vm:7969692kB, anon-rss:0kB, file-rss:0kB, shmem-rss:7490908kB <3> [1039.527858] Out of memory: Kill process 8778 (i915_suspend) score 1671 or sacrifice child <3> [1039.546162] Out of memory: Kill process 8778 (i915_suspend) score 1671 or sacrifice child <3> [1039.548750] Out of memory: Kill process 8778 (i915_suspend) score 1671 or sacrifice child
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * All machines: igt@i915_suspend@shrink - dmesg-warn - i915_suspend invoked oom-killer - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5366/shard-glk1/igt@i915_suspend@shrink.html - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5366/shard-hsw8/igt@i915_suspend@shrink.html - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5366/shard-kbl5/igt@i915_suspend@shrink.html - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2186/shard-glk8/igt@i915_suspend@shrink.html - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2186/shard-kbl7/igt@i915_suspend@shrink.html - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5367/shard-glk2/igt@i915_suspend@shrink.html - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5367/shard-hsw3/igt@i915_suspend@shrink.html - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5367/shard-kbl7/igt@i915_suspend@shrink.html - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2187/shard-glk6/igt@i915_suspend@shrink.html - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2187/shard-hsw1/igt@i915_suspend@shrink.html - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_2187/shard-kbl2/igt@i915_suspend@shrink.html - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5368/shard-glk7/igt@i915_suspend@shrink.html - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5368/shard-hsw1/igt@i915_suspend@shrink.html - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5368/shard-kbl4/igt@i915_suspend@shrink.html - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5368/shard-snb4/igt@i915_suspend@shrink.html
That's the point of the test -- check suspend under oom conditions.
(In reply to Chris Wilson from comment #2) > That's the point of the test -- check suspend under oom conditions. We really need to stop testing it then. It creates these 100+ MB logs sporadically...
A CI Bug Log filter associated to this bug has been updated: {- All machines: igt@i915_suspend@shrink - dmesg-warn - i915_suspend invoked oom-killer -} {+ All machines: igt@i915_suspend@shrink - dmesg-warn - Out of memory: Kill process +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_187/fi-bdw-gvtdvm/igt@i915_suspend@shrink.html * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_187/fi-kbl-7567u/igt@i915_suspend@shrink.html * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5377/shard-hsw6/igt@i915_suspend@shrink.html * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_188/fi-bsw-kefka/igt@i915_suspend@shrink.html
The test got removed, so no problems anymore!
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.