igt@drm_mm@drm_mm@drm_test_mm_reserve - abort - Test assertion failure function __igt_kunit, Failed assertion: igt_kernel_tainted(&taints) == 0, error: 512 != 0

http://gfx-ci.igk.intel.com/cibuglog-ng/testresult/1606333605?query_key=0b5b23ffaf70702a60805c01762ef8b7e13dad55

Stdout	
Starting dynamic subtest: drm_test_mm_reserve
Stack trace:
  #0 ../../../usr/src/igt-gpu-tools/lib/igt_core.c:1988 __igt_fail_assert()
runner: This test was killed due to a kernel taint (0x40200).



This test caused an abort condition: Kernel badly tainted (0x40200, 0x200) (check dmesg for details):
	TAINT_WARN: WARN_ON has happened.

Stderr	
Starting dynamic subtest: drm_test_mm_reserve
(drm_mm:1316) igt_kmod-CRITICAL: Test assertion failure function __igt_kunit, file ../../../usr/src/igt-gpu-tools/lib/igt_kmod.c:1283:
(drm_mm:1316) igt_kmod-CRITICAL: Failed assertion: igt_kernel_tainted(&taints) == 0
(drm_mm:1316) igt_kmod-CRITICAL: error: 512 != 0
Received signal SIGQUIT.
Stack trace: 
 #0 [fatal_sig_handler+0x10f]
 #1 [killpg+0x40]
 #2 [dwfl_module_eh_cfi+0x35b]
 #3 [dwfl_module_addrname+0xe5]
 #4 [dwfl_module_addrsym+0xe0]
 #5 [print_backtrace+0x15c]
 #6 [__igt_fail_assert+0x10a]
 #7 [__igt_kunit.isra.0+0xbc4]
 #8 [<unknown>+0xbc4]

added feature: GEM platform: KBL labels

The CI Bug Log issue associated to this bug has been updated by Ewelina Musial.

New filters associated

• KBL: igt@drm_mm@drm_mm@drm_test_mm_reserve - abort - Test assertion failure function __igt_kunit, Failed assertion: igt_kernel_tainted(&taints) == 0, error: 512 != 0
  • https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1436/fi-kbl-soraka/igt@drm_mm@drm_mm@drm_test_mm_reserve.html
  • https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1439/fi-kbl-soraka/igt@drm_mm@drm_mm@drm_test_mm_reserve.html
  • https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1441/fi-kbl-soraka/igt@drm_mm@drm_mm@drm_test_mm_reserve.html

changed the description

Closing this issue (#10508 (closed)) as was not seen for more than 21 days

closed

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.