few tests - dmesg-warn - GT0: GUC: excessive init time: 578ms!

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1368/bat-mtlp-8/igt@gem_ctx_persistence@many-contexts.html

<4> [473.074884] i915 0000:00:02.0: [drm] GT0: GUC: excessive init time: 578ms! [freq = 2200MHz, before = 2200MHz, status = 0x8002F034, count = 0, ret = 0]
<7> [473.080156] i915 0000:00:02.0: [drm:guc_enable_communication [i915]] GT0: GUC: communication enabled
```

added BAT_BUG feature: firmware/guc platform: MTL_P labels

mentioned in issue #8634 (closed)

The CI Bug Log issue associated to this bug has been updated by ysainanx.

New filters associated

• MTL_P: few tests - dmesg-warn - GT0: GUC: excessive init time: 1053ms! (No new failures associated)

changed the description

changed title from few tests - dmesg-warn - GT0: GUC: excessive init time: 1053ms! to few tests - dmesg-warn - GT0: GUC: excessive init time: 578ms!

Issue was split from a similar DG2 issue (8634). Updated description to remove the DG2 signature and have the MTL signature instead.

On CI, this issue didn't happen since the bug was created. Closing this isssue as can not reproduce.

closed

A CI Bug Log filter associated to this bug has been updated by tillipix.

Description: DG2 MTL_P: few tests - dmesg-warn - GT0: GUC: excessive init time: 1053ms!

Equivalent query: runconfig_tag IS IN ["DRM-TIP"] AND machine_tag IS IN ["MTL-P", "DG2"] AND ((testsuite_name = "IGT" AND test_name IS IN ["igt@gem_eio@kms"])) AND ((testsuite_name = "IGT" AND status_name IS IN ["dmesg-warn"])) AND dmesg ~= 'GT0: GUC: excessive init time: .*ms!'

New failures caught by the filter:

• https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1438/bat-dg2-9/igt@gem_eio@kms.html

added platform: DG2 label

reopened

Similar issue on DG2

The log on: https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1438/bat-dg2-9/igt@gem_eio@kms.html#dmesg-warnings24648 is not an valid reproduce of this issue.

From the error message: <4> [301.737279] i915 0000:03:00.0: [drm] GT0: GUC: excessive init time: 367ms! [status = 0x8002F034, count = 0, ret = 0] <4> [301.737400] i915 0000:03:00.0: [drm] GT0: GUC: excessive init time: [freq = 1200MHz, before = 100MHz, perf_limit_reasons = 0x31020002]

Indicate the GuC is trying change frequency from 100Mhz to 1200Mhz, when GuC running at 100Mhz, which is known could slow down the GuC init.

Now this issue could be split into 2:

1. for high frequency (this one)
2. for low frequency. The low frequency case should be duplicated of existing issue #9656 (closed) Can we update the CI filter to screen out the low frequency cases?

Closing this issue (#8847 (closed)) as was not seen for more than 21 days

closed

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.