Bug 111861 - [CI][DRMTIP] igt@gem_pwrite@big-cpu-fbr - timeout - Received signal SIGQUIT
Summary: [CI][DRMTIP] igt@gem_pwrite@big-cpu-fbr - timeout - Received signal SIGQUIT
Status: RESOLVED FIXED
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
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-30 09:40 UTC by Lakshmi
Modified: 2019-10-04 16:13 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lakshmi 2019-09-30 09:40:29 UTC
Err	
Starting subtest: big-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+0x331]
 #7 [__real_main260+0xabc]
 #8 [main+0x34]
 #9 [__libc_start_main+0xe7]
 #10 [_start+0x2a]

[39.046783] Initializing watchdogs
[39.047110]   /dev/watchdog0
[39.074028] [01/92] (960s left) gem_pwrite (big-cpu-fbr)
Starting subtest: big-cpu-fbr
[439.413447] Timeout. Killing the current test with SIGQUIT.
[444.651530] Closing watchdogs
[444.667250] Initializing watchdogs
Comment 1 CI Bug Log 2019-09-30 09:41:44 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* APL: igt@gem_pwrite@big-cpu-fbr - timeout - Received signal SIGQUIT 
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3471/shard-apl1/igt@gem_pwrite@big-cpu-fbr.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_379/fi-apl-guc/igt@gem_pwrite@big-cpu-fbr.html
Comment 2 Chris Wilson 2019-10-04 16:13:10 UTC
commit 7e8057626640cfedbae000c5032be32269713687
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Fri Oct 4 14:40:02 2019 +0100

    drm/i915: Drop struct_mutex from around i915_retire_requests()

I think.


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.