Bug 84900 - [ILK/BYT Bisected]igt/kms_force_connector core dumped
Summary: [ILK/BYT Bisected]igt/kms_force_connector core dumped
Status: CLOSED DUPLICATE of bug 84771
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: high normal
Assignee: Thomas Wood
QA Contact: Intel GFX Bugs mailing list
Keywords: bisect_pending
Depends on:
Reported: 2014-10-11 07:30 UTC by lu hua
Modified: 2017-10-06 14:34 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

dmesg (101.36 KB, text/plain)
2014-10-11 07:30 UTC, lu hua
no flags Details

Description lu hua 2014-10-11 07:30:40 UTC
Created attachment 107700 [details]

==System Environment==
Regression: not sure
Non-working platforms: BYT


==Bug detailed description==
It's aborted on ILK/BYT with -nightly kernel, it also has issue on earlier kernel. But automation testing was pass on earlier kernel.

IGT-Version: 1.8-gb7d80d1 (x86_64) (Linux: 3.17.0_drm-intel-nightly_ea4bec_20141011+ x86_64)
kms_force_connector: igt_core.c:360: common_exit_handler: Assertion `sig != 0 || igt_exit_called' failed.
Aborted (core dumped)

==Reproduce steps==
1. ./kms_force_connector
Comment 1 lu hua 2014-10-11 07:53:52 UTC
It's igt regression.
good commit: b23329f08662e6d15220006cffa0344231b27b04
bad commit: b7d80d104758fb4c90723246aed943c0097c6156
Comment 2 Paulo Zanoni 2014-10-13 17:59:22 UTC
Can you please bisect this for us?
Comment 3 lu hua 2014-10-14 02:49:44 UTC
Bisect shows: 5782eca1e19e85a04ad402fa4094aa1b5f9c53ce is the first bad commit
commit 5782eca1e19e85a04ad402fa4094aa1b5f9c53ce
Author:     Tim Gore <tim.gore@intel.com>
AuthorDate: Wed Oct 1 13:25:20 2014 +0100
Commit:     Daniel Vetter <daniel.vetter@ffwll.ch>
CommitDate: Wed Oct 1 14:44:30 2014 +0200

    lib/igt_core.c: disable lowmemorykiller during tests

    Several IGT tests cycle through a lot of GEM memory and
    when running these tests on Android they tend to get
    killed by the lowmemorykiller. The lowmemorykiller really
    is not usefull in this context and is just preventing the
    test from doing its job. This commit adds a function to
    disable the lowmemorykiller by writing "9999" to its
    oom adj parameter, which means it will never "select"
    any process to kill. The normal linux oom killer is still
    there to protect the kernel.
    The low memory killer is disabled during the common
    init function and then re-enabled by the exit handler.
    To make this work for single tests the exit handler is now
    installed in the common init function also so that it is
    invoked for all tests.
    This is just a hack to get round the fact that the i915
    driver uses the concept of purgeable memory which is not
    understood by the lowmemorykiller. If this ever gets
    fixed then this patch can be removed.

    Signed-off-by: Tim Gore <tim.gore@intel.com>
    [danvet: A bit of polish (coding style, static and rename
    check_igt_exit to common_exit_handler, drop the is_disabled check
    since we only call this once now).]
    Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Comment 4 Tim Gore 2014-10-14 15:20:47 UTC
There is a fix for this from Thomas Wood in the pipeline.
Comment 5 Thomas Wood 2014-10-15 10:15:00 UTC
This is a duplicate of bug 84771.

*** This bug has been marked as a duplicate of bug 84771 ***
Comment 6 Elizabeth 2017-10-06 14:34:50 UTC
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.