Bug 110715 - [CI][BAT] igt@gem_exec_gttfill@basic - incomplete
Summary: [CI][BAT] igt@gem_exec_gttfill@basic - incomplete
Status: RESOLVED NOTOURBUG
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: highest normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-20 10:56 UTC by Martin Peres
Modified: 2019-07-02 11:33 UTC (History)
1 user (show)

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


Attachments

Comment 1 CI Bug Log 2019-05-20 10:57:08 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* all machines: igt@gem_exec_gttfill@basic - incomplete
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6098/fi-blb-e6850/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6098/fi-cfl-8700k/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6098/fi-cml-u/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6098/fi-cml-u2/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6098/fi-kbl-7567u/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6098/fi-kbl-8809g/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6098/fi-skl-6600u/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6098/fi-skl-guc/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6098/fi-skl-lmem/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3005/fi-blb-e6850/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3005/fi-cfl-8700k/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3005/fi-cml-u/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3005/fi-cml-u2/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3005/fi-kbl-7567u/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3005/fi-kbl-8809g/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3005/fi-skl-6600u/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3005/fi-skl-guc/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3005/fi-skl-lmem/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3005/fi-whl-u/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3006/fi-blb-e6850/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3006/fi-cfl-8700k/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3006/fi-cml-u/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3006/fi-cml-u2/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3006/fi-kbl-7567u/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3006/fi-kbl-8809g/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3006/fi-skl-6600u/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3006/fi-skl-guc/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3006/fi-skl-lmem/igt@gem_exec_gttfill@basic.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3006/fi-whl-u/igt@gem_exec_gttfill@basic.html
Comment 2 Chris Wilson 2019-05-20 11:34:14 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6098/fi-icl-y/pstore0-1558346266_Panic_1.log

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6098/fi-kbl-8809g/pstore0-1558346223_Panic_1.log

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6098/fi-icl-u2/pstore0-1558346310_Panic_1.log

<4>[   63.053065] CPU: 1 PID: 275 Comm: jbd2/nvme0n1p2- Tainted: G     U            5.2.0-rc1-CI-CI_DRM_6098+ #1
<4>[   63.053109] Hardware name: Intel Corporation Ice Lake Client Platform/IceLake U DDR4 SODIMM PD RVP TLC, BIOS ICLSFWR1.R00.3175.A00.1904261428 04/26/2019
<4>[   63.053166] Call Trace:
<4>[   63.053186]  dump_stack+0x67/0x9b
<4>[   63.053207]  panic+0x12b/0x2cd
<4>[   63.053235]  ext4_handle_error+0xa1/0xb0
<4>[   63.053258]  __ext4_error_inode+0xe9/0x2b0
<4>[   63.053288]  ? bit_wait+0x50/0x50
<4>[   63.053311]  __ext4_ext_check+0x12e/0x350
<4>[   63.053341]  __read_extent_tree_block+0xb6/0x280
<4>[   63.053365]  ? ext4_find_extent+0x134/0x2d0
<4>[   63.053389]  ext4_find_extent+0x134/0x2d0
<4>[   63.053423]  ext4_ext_map_blocks+0x78/0x1450
<4>[   63.053450]  ? lock_acquire+0xa6/0x1c0
<4>[   63.053472]  ? ext4_map_blocks+0x2ff/0x5b0
<4>[   63.053500]  ext4_map_blocks+0x3de/0x5b0
<4>[   63.053522]  ? __lock_acquire+0x530/0x24c0
<4>[   63.053549]  _ext4_get_block+0x6d/0x100
<4>[   63.053573]  generic_block_bmap+0x46/0x70
<4>[   63.053603]  jbd2_journal_bmap+0x21/0x70
<4>[   63.053626]  jbd2_journal_get_descriptor_buffer+0x2e/0xf0
<4>[   63.053655]  jbd2_journal_commit_transaction+0xcd4/0x1db0
<4>[   63.053686]  ? debug_object_deactivate+0x137/0x160
<4>[   63.053716]  ? _raw_spin_unlock_irqrestore+0x39/0x60
<4>[   63.053742]  ? debug_object_deactivate+0x137/0x160
<4>[   63.053777]  ? try_to_del_timer_sync+0x57/0x80
<4>[   63.053804]  ? kjournald2+0xc4/0x2a0
<4>[   63.053823]  kjournald2+0xc4/0x2a0
<4>[   63.053842]  ? _raw_spin_unlock_irqrestore+0x4c/0x60
<4>[   63.053869]  ? wait_woken+0xa0/0xa0
<4>[   63.053892]  ? commit_timeout+0x10/0x10
<4>[   63.053922]  kthread+0x119/0x130
<4>[   63.053941]  ? kthread_park+0x80/0x80

Hints towards ext4 being unhappy?
Comment 3 CI Bug Log 2019-05-21 10:44:23 UTC
A CI Bug Log filter associated to this bug has been updated:

{- all machines: igt@gem_exec_gttfill@basic - incomplete -}
{+ all machines: random gem tests - incomplete +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6098/fi-bwr-2160/igt@gem_mmap@basic-small-bo.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4997/fi-bwr-2160/igt@gem_mmap@basic-small-bo.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6099/fi-bwr-2160/igt@gem_mmap@basic-small-bo.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6100/fi-bwr-2160/igt@gem_mmap@basic-small-bo.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6101/fi-bwr-2160/igt@gem_mmap@basic-small-bo.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4998/fi-bwr-2160/igt@gem_mmap@basic-small-bo.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6102/fi-bwr-2160/igt@gem_mmap@basic-small-bo.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6107/fi-bwr-2160/igt@gem_mmap@basic-small-bo.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4999/fi-bwr-2160/igt@gem_mmap@basic-small-bo.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4999/fi-gdg-551/igt@gem_mmap@basic-small-bo.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6108/fi-bwr-2160/igt@gem_mmap@basic-small-bo.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6108/fi-gdg-551/igt@gem_mmap@basic-small-bo.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6109/fi-bwr-2160/igt@gem_mmap@basic-small-bo.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6109/fi-gdg-551/igt@gem_mmap@basic-small-bo.html
Comment 4 Chris Wilson 2019-05-21 11:48:24 UTC
commit 2e61c6dc24a0b82e70efd8a746bec398dbe0e774
Author: Petri Latvala <petri.latvala@intel.com>
Date:   Tue May 21 12:55:33 2019 +0300

    Revert "ext4: protect journal inode's blocks using block_validity"
    
    This reverts commit 345c0dbf3a30872d9b204db96b5857cd00808cae.
    
    Link: https://patchwork.freedesktop.org/patch/msgid/20190521095533.2056-1-petri.latvala@intel.com
Comment 5 CI Bug Log 2019-07-02 11:33:18 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.