[Intel-gfx] ✗ Fi.CI.BAT: warning for Split driver init step to phases (rev3)

[Imre Deak]

On Thu, 2016-03-17 at 11:32 +0000, Patchwork wrote:
> == Series Details ==
> 
> Series: Split driver init step to phases (rev3)
> URL   : https://patchwork.freedesktop.org/series/4509/
> State : warning
> 
> == Summary ==
> 
> Series 4509v3 Split driver init step to phases
> http://patchwork.freedesktop.org/api/1.0/series/4509/revisions/3/mbox
> /
> 
> Test drv_module_reload_basic:
>                 pass       -> DMESG-WARN (bsw-nuc-2)
>                 pass       -> DMESG-WARN (skl-i5k-2)
>                 pass       -> DMESG-WARN (bdw-ultra)
>                 pass       -> DMESG-WARN (skl-i7k-2)
>                 pass       -> DMESG-WARN (snb-x220t)
>                 pass       -> DMESG-WARN (skl-nuci5)
>                 pass       -> DMESG-WARN (bdw-nuci7)

All the above are expected "*ERROR* failed to init modeset" messages
due to forcing init failures. I asked Tomi to filter these out if the
corresponding failure injection message precedes this error message.

I can't see in the above list byt-nuc and hsw-gt2 where the CI report
also show errors/WARNs: on byt-nuc it's the pre-existing
SND_HDA/pin2port WARN, on hsw-gt2 it's the above expected modeset init
error.

> Test kms_flip:
>         Subgroup basic-flip-vs-dpms:
>                 dmesg-warn -> PASS       (bdw-ultra)
>         Subgroup basic-flip-vs-wf_vblank:
>                 fail       -> PASS       (snb-x220t)
> Test kms_pipe_crc_basic:
>         Subgroup read-crc-pipe-b:
>                 pass       -> DMESG-WARN (bdw-ultra)

The watermark programming while not powered pre-existing issue.

>         Subgroup read-crc-pipe-b-frame-sequence:
>                 dmesg-warn -> PASS       (snb-x220t)
>         Subgroup read-crc-pipe-c-frame-sequence:
>                 dmesg-warn -> PASS       (hsw-gt2)
> Test pm_rpm:
>         Subgroup basic-pci-d3-state:
>                 fail       -> DMESG-FAIL (snb-x220t)

The above watermark issue.

Also not on the above list:

- A couple of tests on byt-nuc with the above SND/pin2port WARN.
- igt at gem_ringfill@basic-default-s3 on bsw-nuc-2: a complicated looking
lockdep issue during suspend among cpu_hotplug.lock (via
gen8_ggtt_insert_entries__BKL->stop_machine), struct_mutex (via
drm_gem_mmap), mmap_sem (via kernfs_fop_write), s_active (via
device_del->kernfs_remove_by_name):
https://bugs.freedesktop.org/show_bug.cgi?id=94350

> 
> bdw-
> nuci7        total:194  pass:181  dwarn:1   dfail:0   fail:0   skip:1
> 2 
> bdw-
> ultra        total:194  pass:171  dwarn:2   dfail:0   fail:0   skip:2
> 1 
> bsw-nuc-
> 2        total:194  pass:155  dwarn:2   dfail:0   fail:0   skip:37 
> byt-
> nuc          total:194  pass:155  dwarn:4   dfail:0   fail:0   skip:3
> 5 
> hsw-
> gt2          total:194  pass:176  dwarn:1   dfail:0   fail:0   skip:1
> 7 
> skl-i5k-
> 2        total:194  pass:170  dwarn:1   dfail:0   fail:0   skip:23 
> skl-i7k-
> 2        total:194  pass:170  dwarn:1   dfail:0   fail:0   skip:23 
> skl-
> nuci5        total:194  pass:182  dwarn:1   dfail:0   fail:0   skip:1
> 1 
> snb-
> x220t        total:194  pass:159  dwarn:1   dfail:1   fail:0   skip:3
> 3 
> 
> Results at /archive/results/CI_IGT_test/Patchwork_1625/
> 
> 8a9a911d489fe160df173580277983dac5952ed0 drm-intel-nightly: 2016y-
> 03m-17d-10h-02m-10s UTC integration manifest
> b99e15d212c0d3595ccb0ce6cc20f627f237e69d drm/i915: Add fault
> injection support
> 708025ddfa837b37845b20d05af3c73bc0c7708e drm/i915: Fix power domain
> HW state cleanup on error path
> 54ae37dff154475dfe58998bfbedad9ec837321c drm/i915: Split out load
> time interface registration
> ad31b795a1f0d8901700ecbd63f943463d09fafa drm/i915: Split out load
> time HW initialization
> feac61f9eb8031a61ae9734e83e9fc9b0949c6b0 drm/i915: Split out load
> time MMIO initialization
> 69df569ebb5e3f93654526f1a03efb9703d82f94 drm/i915: Split out load
> time early initialization
> a21acc33f9510155bcc1a5001d2e2c11943b715a drm/i915: Move unload time
> opregion unregistration earlier
> 0a5a224a5da3cfd1c0e7d3e927ceefdb894083ca drm/i915: Move unload time
> GTT, MSI IRQ cleanup later
> 50da5444e07e95c40ceae1eb6521ba19214fb2c0 drm/i915: Move unload time
> display power domain uninit later
> ac894e86af964f1902a13cbf8e4ac6c82b8e383d drm/i915: Move load time
> audio component registration earlier
> 238ec5f2a1fa9180fbcbb1e19d44d9a69e84fd3e drm/i915: Move load time
> shrinker registration later
> 6fc3970b4da1f5131ad2a04345537e101a92cd16 drm/i915: Move load time
> runtime PM get later
> f1c9058738a0b840385e9bbe80011a97238dfd5d drm/i915: Move load time
> gem_load_init earlier
> 6d19d18371db8aa0ecd3a6165c82be9c3d785a0f drm/i915: Move load time
> runtime device info init earlier
> 58c8dfd1314f0933a1fd7e710060617d3896a198 drm/i915: Move load time
> init of clock gating hooks earlier
> 13d5acf73a511929c6a5a17974e82b7e87cdd191 drm/i915: Move load time
> init of display/audio hooks earlier
> 620da462f78e10859a5e377ff974fee178099458 drm/i915: Move load time IRQ
> SW init earlier
> da4d68b2404298afb9b4d44c3aed415b76fc3488 drm/i915: Move load time PCH
> detect, DPIO, power domain SW init earlier
> 145e6345dbd7b52172a7280f5c92d31019f4b8ef Fix MCHBAR cleanup on the
> driver init error path
>