https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5219/fi-icl-u4/igt@kms_chamelium@common-hpd-after-suspend.html Starting subtest: common-hpd-after-suspend Received signal SIGQUIT. Stack trace: #0 [fatal_sig_handler+0xd6] #1 [killpg+0x40] #2 [pselect+0x59] #3 [xmlrpc_server_info_disallow_auth_ntlm+0x389] #4 [xmlrpc_server_info_disallow_auth_ntlm+0x786] #5 [xmlrpc_server_info_disallow_auth_ntlm+0xd1f] #6 [xmlrpc_client_call2+0xa8] #7 [xmlrpc_client_call2f_va+0x9e] #8 [__chamelium_rpc.constprop.6+0xc5] #9 [chamelium_wait_reachable+0x65] #10 [try_suspend_resume_hpd.constprop.42+0x15e] #11 [test_suspend_resume_hpd_common.constprop.40+0x8c] #12 [__real_main2611+0x1bf9] #13 [main+0x27] #14 [__libc_start_main+0xe7] #15 [_start+0x2a]
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * ICL: igt@kms_chamelium@common-hpd-after-suspend - timeout - Received signal SIGQUIT - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14707/fi-icl-u4/igt@kms_chamelium@common-hpd-after-suspend.html - https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5219/fi-icl-u4/igt@kms_chamelium@common-hpd-after-suspend.html
Looks like chamelium api rpc call crashes, regardless of what causes this - that is a clear bug in IGT/Chamelium api.
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * CFL: igt@i915_selftest@live_execlists - incomplete - BUG: kernel NULL pointer dereference, address: 0000000000000010 (No new failures associated) * CFL: igt@runner@aborted - fail - Previous test: i915_selftest (live_execlists) (No new failures associated)
These xmlrpc_server_info_disallow_auth_ntlm calls in the stack trace look erroneous, since this function only contains a single instruction (setting a structure field to a given value). We're probably missing debug information for xmlrpc-c, so we can't trust the stack trace inside the lib anyway. The fact that we get SIGQUIT is weird. The lib contains a bunch of abort() calls which may be called from xmlrpc_client_call2, however abort() triggers SIGABRT, not SIGQUIT. I have no clue why this happens atm. In any case, this is a bug in IGT as Stan said.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/491.
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.