Bug 111616 - [CI][DRMTIP] igt@gem_pwrite@huge-cpu-fbr - timeout - Received signal SIGQUIT.
Summary: [CI][DRMTIP] igt@gem_pwrite@huge-cpu-fbr - timeout - Received signal SIGQUIT.
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: not set not set
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
Depends on:
Reported: 2019-09-09 12:30 UTC by Lakshmi
Modified: 2019-09-13 15:41 UTC (History)
1 user (show)

See Also:
i915 platform: BSW/CHT
i915 features: GEM/Other


Description Lakshmi 2019-09-09 12:30:25 UTC
Starting subtest: huge-cpu-fbr
Received signal SIGQUIT.
Stack trace: 
 #0 [fatal_sig_handler+0xd6]
 #1 [killpg+0x40]
 #2 [ioctl+0x7]
 #3 [drmIoctl+0x28]
 #4 [__gem_write+0x3e]
 #5 [gem_write+0x9]
 #6 [test_big_cpu+0x127]
 #7 [__real_main260+0xc59]
 #8 [main+0x34]
 #9 [__libc_start_main+0xe7]
 #10 [_start+0x2a]
Comment 1 CI Bug Log 2019-09-09 12:31:50 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* BSW: igt@gem_pwrite@huge-cpu-fbr - timeout - Received signal SIGQUIT
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_363/fi-bsw-n3050/igt@gem_pwrite@huge-cpu-fbr.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_364/fi-bsw-n3050/igt@gem_pwrite@huge-cpu-fbr.html
Comment 2 Chris Wilson 2019-09-09 12:40:53 UTC
Hmm, first run completed in 33s. Something to bear in mind is that on bsw, we use the stop_machine() workaround for GGTT updates, so is especially slow.
Comment 3 Chris Wilson 2019-09-10 11:17:04 UTC
drmtip_365 is happier, even though its runtime was longer! drmtip_365 changes was basically e7fe60181cc8 Revert "x86/apic: Include the LDR when clearing out APIC registers". Seems to indicate a fluke.
Comment 4 Chris Wilson 2019-09-13 15:41:06 UTC
And spontaneously stopped again.

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.