Created attachment 112634 [details] dmesg ==System Environment== -------------------------- Regression: not sure, fail rate:2/4 no-working platforms: BDW ==kernel== -------------------------- drm-intel-nightly/d6bc7a6a0a7573350e8be8ec54002c20d1dbe1e0 commit d6bc7a6a0a7573350e8be8ec54002c20d1dbe1e0 Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Tue Jan 20 15:10:59 2015 +0100 drm-intel-nightly: 2015y-01m-20d-14h-10m-40s UTC integration manifest ==Bug detailed description== ----------------------------- It causes system on BDW drm-intel-nightly kernel.Fail rate: 2/4. The call trace is similar with bug 88652. root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./gem_evict_alignment --run-subtest major-hang IGT-Version: 1.9-g3d65ff7 (x86_64) (Linux: 3.19.0-rc4_drm-intel-nightly_d6bc7a_20150121+ x86_64) Test requirement not met in function intel_require_memory, file intel_os.c:244: Test requirement: !(total <= required) Estimated that we need 12884905984 bytes for the test, but only have 3916431360 bytes available (RAM) Subtest major-hang: SKIP (0.014s) root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# ./gem_evict_alignment --run-subtest major-hang Call Trace: [ 289.615019] [<ffffffff813ff889>] ? scsi_host_alloc_command+0x3e/0x9e [ 289.618221] [<ffffffff813ff9dd>] ? scsi_get_command+0x16/0x128 [ 289.621397] [<ffffffff81407768>] ? scsi_prep_fn+0x58/0x139 [ 289.624559] [<ffffffff81325efc>] ? blk_peek_request+0xf7/0x216 [ 289.627711] [<ffffffff81407b3b>] ? scsi_request_fn+0x2f/0x5cc [ 289.630881] [<ffffffff813235a4>] ? __blk_run_queue+0x29/0x31 [ 289.634054] [<ffffffff813265cd>] ? blk_queue_bio+0x27d/0x2bc [ 289.637234] [<ffffffff81324533>] ? generic_make_request+0x93/0xd0 [ 289.640396] [<ffffffff8132466f>] ? submit_bio+0xff/0x11d [ 289.643539] [<ffffffff8113a9b1>] ? _submit_bh+0x104/0x122 [ 289.646636] [<ffffffff8113ade5>] ? ll_rw_block+0x6d/0x77 [ 289.649693] [<ffffffff8113b9da>] ? __breadahead+0x2c/0x40 [ 289.652736] [<ffffffff811b81f9>] ? __ext4_get_inode_loc+0x287/0x396 [ 289.655748] [<ffffffff811ba217>] ? ext4_iget+0x58/0x8e4 [ 289.658720] [<ffffffff8110e859>] ? kmem_cache_alloc+0x27/0x113 [ 289.661678] [<ffffffff811c28ac>] ? ext4_lookup+0xce/0x12d [ 289.664621] [<ffffffff8111b1ca>] ? lookup_real+0x23/0x3d [ 289.667550] [<ffffffff8111baaf>] ? __lookup_hash+0x2a/0x31 [ 289.670461] [<ffffffff8111bfee>] ? lookup_slow+0x3c/0xa2 [ 289.673357] [<ffffffff8111e407>] ? link_path_walk+0x227/0x74a [ 289.676263] [<ffffffff8110e859>] ? kmem_cache_alloc+0x27/0x113 [ 289.679142] [<ffffffff8111f671>] ? path_openat+0x1e4/0x560 [ 289.681996] [<ffffffff81120577>] ? do_filp_open+0x2b/0x6f [ 289.684822] [<ffffffff81117cfb>] ? do_open_execat+0x7b/0x138 [ 289.687643] [<ffffffff81117dde>] ? open_exec+0x26/0x2b [ 289.690458] [<ffffffff81151ba4>] ? load_elf_binary+0x157/0x15af [ 289.693234] [<ffffffff811186cd>] ? copy_strings.isra.24+0x247/0x29a [ 289.695975] [<ffffffff811187c7>] ? search_binary_handler+0x71/0x17a [ 289.698656] [<ffffffff8111989a>] ? do_execveat_common.isra.29+0x46d/0x641 [ 289.701306] [<ffffffff81119a91>] ? do_execve+0x23/0x28 [ 289.703906] [<ffffffff81119c95>] ? SyS_execve+0x23/0x2a [ 289.706511] [<ffffffff8179f529>] ? stub_execve+0x69/0xa0 [ 289.709086] Code: e9 4d 89 f8 4c 89 f1 48 89 ea 48 89 de 41 ff 14 24 49 83 c4 10 49 83 3c 24 00 eb 36 eb 38 49 63 44 24 20 4d 8b 04 24 48 8d 4a 01 <48> 8b 5c 05 00 48 89 e8 65 49 0f c7 08 0f 94 c0 84 c0 0f 85 78 [ 289.712062] RIP [<ffffffff8110e90b>] kmem_cache_alloc+0xd9/0x113 [ 289.714785] RSP <ffff8801442f7668> [ 289.717511] ---[ end trace c5be55bf5fe86734 ]--- ==Reproduce steps== ---------------------------- 1../gem_evict_alignment --run-subtest major-hang
Seems like there's a problem outside of i915. See also bug 88688.
Still the same memory corruption caused by i915... *** This bug has been marked as a duplicate of bug 88688 ***
Run 5 cycles, it works well.
Closing old verified.
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.