Created attachment 99830 [details] dmesg ==System Environment== -------------------------- Regression: Yes. It's a igt regression issue, the result before was skipped Non-working platforms: SNB ==kernel== -------------------------- origin/drm-intel-nightly: c37f30ddc2921eccbf0be87c7742b56fbde53a81(fails) drm-intel-nightly: 2014y-05m-23d-13h-57m-55s integration manifest origin/drm-intel-next-queued: f83d6518a13020e3cf7abbcc6b4e6d34459d9a9f(fails) ddrm/i915: Kill private_default_ctx off origin/drm-intel-fixes: c1240bd2842f6ec26d7dc1d9c845a197a41d33fe(skips) drm/i915: Prevent negative relocation deltas from wrapping ==Bug detailed description== ----------------------------- igt/gem_userptr_blits causes core dumped sporadically The reproducible rate is about 1 out of 5. Output: ./gem_userptr_blitsIGT-Version: 1.6-gff3c122 (x86_64) (Linux: 3.15.0-rc3_drm-intel-next-queued_f83d65_20140525+ x86_64) Aperture size is 2048 MiB Total RAM is 7901 MiB Subtest input-checking: SUCCESS Subtest usage-restrictions: SUCCESS Subtest invalid-mapping: SUCCESS Subtest forbidden-operations: SUCCESS Testing unsynchronized mappings... Subtest create-destroy-unsync: SUCCESS Subtest unsync-overlap: SUCCESS Subtest unsync-unmap: SUCCESS Subtest unsync-unmap-cycles: SUCCESS Subtest unsync-unmap-after-close: SUCCESS Using 2x1365 1MiB buffers Verifying initialisation... Cyclic blits cpu->gpu, forward... Cyclic blits gpu->cpu, backward... Random blits... Subtest coherency-unsync: SUCCESS Subtest dmabuf-unsync: SUCCESS Subtest forked-unsync-normal: SUCCESS Subtest forked-unsync-interruptible: SUCCESS Test requirement not met in function forking_evictions, file eviction_common.c:181: Last errno: 0, Success Test requirement: (!(intel_get_total_ram_mb() / 4 < intel_get_total_swap_mb())) Subtest forked-unsync-swapping-normal: SKIP Test requirement not met in function forking_evictions, file eviction_common.c:181: Last errno: 0, Success Test requirement: (!(intel_get_total_ram_mb() / 4 < intel_get_total_swap_mb())) Subtest forked-unsync-swapping-interruptible: SKIP Subtest forked-unsync-multifd-normal: SUCCESS Subtest forked-unsync-multifd-interruptible: SUCCESS Test requirement not met in function forking_evictions, file eviction_common.c:181: Last errno: 0, Success Test requirement: (!(intel_get_total_ram_mb() / 4 < intel_get_total_swap_mb())) Subtest forked-unsync-swapping-multifd-normal: SKIP Test requirement not met in function forking_evictions, file eviction_common.c:181: Last errno: 0, Success Test requirement: (!(intel_get_total_ram_mb() / 4 < intel_get_total_swap_mb())) Subtest forked-unsync-swapping-multifd-interruptible: SKIP child 1 died with signal 9, Killed Subtest forked-unsync-mempressure-normal: FAIL Unhandled failure in child 0 gem_userptr_blits: igt_core.c:859: children_exit_handler: Assertion `ret == 0' failed. Aborted (core dumped) ==Reproduce steps== ---------------------------- 1. ./gem_userptr_blits ==Bisect results== ---------------------------- commit 9911f3f0cf202444f1ef2399f5961605880b7360 Author: Chris Wilson <chris@chris-wilson.co.uk> AuthorDate: Thu May 22 10:20:33 2014 +0100 Commit: Chris Wilson <chris@chris-wilson.co.uk> CommitDate: Thu May 22 10:22:04 2014 +0100 igt/gem_userptr_blits: Fix up last minute API changes When the patch was merged, the ioctl numbers had to be adjusted to leave no holes. Also there was a final piece of munging of the API to downgrade unsynced userptr for export over dma-buf. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Chris, can you explain why you removed "bisected"?
Because the bisection result is irrelevant. Flagging when the test is first turned on does not give any useful information as to why the test failed - i.e. there was never a time when the test passed. If you bisected the kernel and found that it failed after the inclusion of userptr, that would be significant.
I've seen similar spurious OOM killers on my own memory constrained machines with gem_userptr_blits, so something with our shrinker code and userptr objects is still amiss.
*** This bug has been marked as a duplicate of bug 79245 ***
Closing resolved+duplicate due to duplicate of duplicate of the closed+fixed.
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.