Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
Admin message
The migration is almost done, at least the rest should happen in the background. There are still a few technical difference between the old cluster and the new ones, and they are summarized in this issue. Please pay attention to the TL:DR at the end of the comment.
[TGL] Warning "Combo PHY A HW state changed unexpectedly"
This warning was introduced because of the new combo phy sequence implemented in "drm/i915/display: Implement new combo phy initialization step".
This is probably due a old IFWI firmware being used in CI but issue will be kept open until fixed by IFWI upgrade or code changes.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items
0
Link issues together to show that they're related.
Learn more.
A CI Bug Log filter associated to this bug has been updated by Lakshmi Vudum:
Description: TGL: igAll t@i915_pm_rpm@i2cests - dmesg-warn - Combo PHY A HW state changed unexpectedly
Equivalent query: runconfig_tag IS IN ["DRM-TIP"] AND (machine_name IS IN ["fi-tgl-u", "re-tgl-u", "fi-tgl-u2", "shard-tglb1", "shard-tglb2", "shard-tglb3", "shard-tglb4", "shard-tglb5", "shard-tglb6", "re-tgl1-display", "re-tgl2-display", "shard-tglb7", "shard-tglb8", "shard-tglb0", "fi-tgl-y", "re-tgl-y", "shard-tglb9", "re-tgl-cham", "fi-tgl-guc", "re-tgl-u2", "fi-tgl-dsi", "ba-tgl-1", "custom-tgl-joshikun", "tgl-u-lpddr-ba", "re-tgl-u3", "fi-tgl-h"] OR machine_tag IS IN ["TGL"] AND ((testsuite_name = "IGT" AND test_name IS IN ["igt@i915_pm_rpm@i2c"])) AND ((testsuite_name = "IGT" AND status_name IS IN ["dmesg-warn"])) AND dmesg ~= 'Combo PHY A HW state changed unexpectedly'
Looking at the HSD(22010518810) of the new step, it requires changes in IFWI.
So I check the checked the IFWI versions of TGL shards:
shard-tglb1:
DMI: Intel Corporation Tiger Lake Client Platform/TigerLake U DDR4 SODIMM RVP, BIOS TGLSFWI1.R00.3197.A00.2005110542 05/11/2020
shard-tglb3:
DMI: Intel Corporation Tiger Lake Client Platform/TigerLake U DDR4 SODIMM RVP, BIOS TGLSFWI1.R00.3197.A00.2005110542 05/11/2020
shard-tglb2:
DMI: Intel Corporation Tiger Lake Client Platform/TigerLake U DDR4 SODIMM RVP, BIOS TGLSFWI1.R00.3197.A00.2005110542 05/11/2020
All of those are previous to the release of the IFWI with the required changes, can we have a IFWI upgrade in CI? The upgraded IFWI will fix this issue, this issue do not happen in my TGL with a updated IFWI.
It also affects dg1. By this point isn't time to accept that the old fw is bust, and ignore the discrepancy if it does not lead to further issues. For which a dbg message suffices.
A CI Bug Log filter associated to this bug has been updated by Lakshmi Vudum:
Description: TGL: All tests - dmesg-warn/incomplete - Combo PHY A HW state changed unexpectedly
Equivalent query: runconfig_tag IS IN ["DRM-TIP"] AND (machine_name IS IN ["fi-tgl-u", "re-tgl-u", "fi-tgl-u2", "shard-tglb1", "shard-tglb2", "shard-tglb3", "shard-tglb4", "shard-tglb5", "shard-tglb6", "re-tgl1-display", "re-tgl2-display", "shard-tglb7", "shard-tglb8", "shard-tglb0", "fi-tgl-y", "re-tgl-y", "shard-tglb9", "re-tgl-cham", "fi-tgl-guc", "re-tgl-u2", "fi-tgl-dsi", "ba-tgl-1", "custom-tgl-joshikun", "tgl-u-lpddr-ba", "re-tgl-u3", "fi-tgl-h"] OR machine_tag IS IN ["TGL"]) AND ((testsuite_name = "IGT" AND status_name IS IN ["incomplete", "dmesg-warn"])) AND dmesg ~= 'Combo PHY A HW state changed unexpectedly'
A CI Bug Log filter associated to this bug has been updated by Lakshmi Vudum:
Description: TGL: All tests - dmesg-warn/incomplete - Combo PHY A HW state changed unexpectedly
Equivalent query: runconfig_tag IS IN ["DRM-TIP"] AND (machine_name IS IN ["fi-tgl-u", "re-tgl-u", "fi-tgl-u2", "shard-tglb1", "shard-tglb2", "shard-tglb3", "shard-tglb4", "shard-tglb5", "shard-tglb6", "re-tgl1-display", "re-tgl2-display", "shard-tglb7", "shard-tglb8", "shard-tglb0", "fi-tgl-y", "re-tgl-y", "shard-tglb9", "re-tgl-cham", "fi-tgl-guc", "re-tgl-u2", "fi-tgl-dsi", "ba-tgl-1", "custom-tgl-joshikun", "tgl-u-lpddr-ba", "re-tgl-u3", "fi-tgl-h"] OR machine_tag IS IN ["TGL"] AND ((testsuite_name = "IGT" AND status_name IS IN ["incomplete", "dmesg-warn"])) AND dmesg ~= 'Combo PHY A HW state changed unexpectedly'
Saw the same problem with a DG1 with older firmware.
I agree to change to debug just for this 2 platforms, otherwise we could be hiding unknown issues under it.