Bug 108716 - [CI][BAT] igt@drv_selftest@live_hugepages - incomplete
Summary: [CI][BAT] igt@drv_selftest@live_hugepages - incomplete
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: high normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-12 11:22 UTC by Martin Peres
Modified: 2019-03-08 10:35 UTC (History)
1 user (show)

See Also:
i915 platform: SKL
i915 features: GEM/PPGTT


Attachments

Description Martin Peres 2018-11-12 11:22:21 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5116/fi-skl-6700k2/igt@drv_selftest@live_hugepages.html

<6> [486.909579] i915: Performing live selftests with st_random_seed=0x3cf72c0e st_timeout=1000
<6> [486.911156] failed to allocate THP, finishing test early
<7> [486.911556] [drm:intel_power_well_enable [i915]] enabling always-on
<7> [486.911610] [drm:intel_power_well_enable [i915]] enabling DC off
<7> [486.911909] [drm:gen9_set_dc_state [i915]] Setting DC state from 02 to 00
<7> [487.913082] igt_write_huge timed out on engine=1, offset_low=8ea00000 offset_high=ffff712f0000, max_page_size=10000
<7> [488.914170] igt_write_huge timed out on engine=0, offset_low=94000000 offset_high=ffff6bdf0000, max_page_size=10000
<7> [489.915182] igt_write_huge timed out on engine=2, offset_low=23e00000 offset_high=ffffdbed0000, max_page_size=10000
<7> [490.916346] igt_write_huge timed out on engine=1, offset_low=22800000 offset_high=ffffdd430000, max_page_size=10000
<7> [491.917193] igt_write_huge timed out on engine=6, offset_low=49ba00000 offset_high=fffb64400000, max_page_size=200000
<7> [492.918125] igt_write_huge timed out on engine=2, offset_low=24600000 offset_high=ffffdb410000, max_page_size=10000
<7> [493.919100] igt_write_huge timed out on engine=6, offset_low=4bc200000 offset_high=fffb43a00000, max_page_size=200000
<7> [494.920584] igt_write_huge timed out on engine=1, offset_low=22600000 offset_high=ffffdd410000, max_page_size=10000
<7> [495.922788] igt_write_huge timed out on engine=0, offset_low=22e00000 offset_high=ffffdcdb0000, max_page_size=10000
<7> [496.924225] igt_write_huge timed out on engine=2, offset_low=4c2a00000 offset_high=fffb3d200000, max_page_size=200000
<7> [497.925583] igt_write_huge timed out on engine=1, offset_low=4bee00000 offset_high=fffb40e00000, max_page_size=200000
<7> [498.926711] igt_write_huge timed out on engine=6, offset_low=23400000 offset_high=ffffdc6f0000, max_page_size=10000
<7> [499.928356] igt_write_huge timed out on engine=6, offset_low=4c1e00000 offset_high=fffb3de00000, max_page_size=200000
<7> [500.929453] igt_write_huge timed out on engine=6, offset_low=4bc200000 offset_high=fffb43a00000, max_page_size=200000
<6> [500.930714] finishing test early, gemfs unable to allocate huge-page(s) with size=2097152
<7> [501.931378] igt_write_huge timed out on engine=0, offset_low=ab600000 offset_high=ffff546f0000, max_page_size=10000
<7> [502.932038] igt_write_huge timed out on engine=1, offset_low=8be00000 offset_high=ffff73e10000, max_page_size=10000
Comment 1 Chris Wilson 2018-11-12 11:26:52 UTC
Normal info messages. No reason for the incomplete captured.
Comment 2 Francesco Balestrieri 2018-11-17 10:00:55 UTC
Seen once 330 runs ago, I suggest to at least make it "high"
Comment 3 Martin Peres 2018-11-17 10:03:06 UTC
(In reply to Francesco Balestrieri from comment #2)
> Seen once 330 runs ago, I suggest to at least make it "high"

Sure thing. Done!
Comment 4 Francesco Balestrieri 2019-01-09 08:34:54 UTC
Seen once in two months, closing.
Comment 5 Martin Peres 2019-03-08 10:35:35 UTC
(In reply to Francesco Balestrieri from comment #4)
> Seen once in two months, closing.

Another month and still nothing. This bug is unactionnable. Closing!
Comment 6 CI Bug Log 2019-03-08 10:35:45 UTC
The CI Bug Log issue associated to this bug has been archived.

New failures matching the above filters will not be associated to this bug anymore.


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.