Bug 111796 - [CI][SHARDS] igt@gem_eio@in-flight-suspend - crash - Received signal SIGSEGV
Summary: [CI][SHARDS] igt@gem_eio@in-flight-suspend - crash - Received signal SIGSEGV
Alias: None
Product: DRI
Classification: Unclassified
Component: IGT (show other bugs)
Version: DRI git
Hardware: Other All
: low minor
Assignee: Default DRI bug account
QA Contact:
Depends on:
Reported: 2019-09-24 06:26 UTC by Lakshmi
Modified: 2019-11-12 07:41 UTC (History)
1 user (show)

See Also:
i915 platform: BXT
i915 features: GEM/Other


Description Lakshmi 2019-09-24 06:26:07 UTC

Starting subtest: in-flight-suspend
Received signal SIGSEGV.
Stack trace: 
 #0 [fatal_sig_handler+0xd6]
 #1 [killpg+0x40]
 #2 [_dl_find_dso_for_object+0x3194]
 #3 [igt_spin_free+0x66]
 #4 [__real_main890+0xd07]
 #5 [main+0x27]
 #6 [__libc_start_main+0xe7]
 #7 [_start+0x2a]
Subtest in-flight-suspend: CRASH (1.619s)
(gem_eio:8150) igt_debugfs-WARNING: clients:
             command   pid dev master a   uid      magic
             gem_eio  8150   0   n    y     0          0
             gem_eio  8150   0   n    y     0          0
             gem_eio  8150   0   y    y     0          0
Comment 1 CI Bug Log 2019-09-24 06:27:38 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* APL: igt@gem_eio@in-flight-suspend - crash - Received signal SIGSEGV
  (No new failures associated)
Comment 2 Chris Wilson 2019-09-24 07:04:45 UTC
The curse of the unwanted fixture.
Comment 3 Francesco Balestrieri 2019-10-10 06:23:52 UTC
Once in 2 weeks / 18 runs, plus Chris' comment. Minor severity says me.
Comment 4 Martin Peres 2019-11-12 07:41:54 UTC
-- 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/igt-gpu-tools/issues/33.

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.