Bug 111208 - [CI][BAT] boot - fail - no link is up in the logs
Summary: [CI][BAT] boot - fail - no link is up in the logs
Status: NEW
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: 2019-07-24 13:53 UTC by Martin Peres
Modified: 2019-07-31 09:20 UTC (History)
2 users (show)

See Also:
i915 platform: ALL
i915 features: CI Infra


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Comment 1 CI Bug Log 2019-07-24 13:54:02 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* fi-cml-u shard-iclb4: boot - fail
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6540/fi-cml-u/boot.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6537/shard-iclb4/boot.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6544/fi-cml-u/boot.html
Comment 2 CI Bug Log 2019-07-25 08:32:12 UTC
A CI Bug Log filter associated to this bug has been updated:

{- fi-cml-u shard-iclb4: boot - fail -}
{+ fi-cml-u shard-iclb*: boot - fail +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6546/shard-iclb6/boot.html
Comment 3 Lakshmi 2019-07-26 08:03:22 UTC
@Arek, Can you add the bug assessment here?
Comment 4 CI Bug Log 2019-07-26 08:05:45 UTC
A CI Bug Log filter associated to this bug has been updated:

{- fi-cml-u shard-iclb*: boot - fail -}
{+ fi-cml-u shard-iclb* fi-icl-y: boot - fail +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6552/fi-icl-y/boot.html
Comment 5 CI Bug Log 2019-07-29 07:21:53 UTC
A CI Bug Log filter associated to this bug has been updated:

{- fi-cml-u shard-iclb* fi-icl-y: boot - fail -}
{+ fi-byt-squawks, fi-skl-lmem, fi-cml-u, shard-iclb*, fi-icl-y, fi-icl-guc, fi-icl-dsi : boot - fail +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6562/fi-icl-guc/boot.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6564/fi-icl-dsi/boot.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6565/fi-skl-lmem/boot.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6569/fi-byt-squawks/boot.html
Comment 6 Arek Hiler 2019-07-29 11:31:02 UTC
This is kind of catch-all bug for all the boot failures, even though it claims that no "link is up" in the logs. 

Even if we look at a successful boot for a run that we got result from (e.g. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6545/fi-cml-u/boot0.log)  there is nothing about network link in the boot dmesg.

So a boot failure here is defined as follows:

1. machine was responding and we deployed the new testing assets (kernel, IGT, etc.) - at this point it's marked as "should participate in the run"
2. we haven't got any results of the machine, this can mean multiple thing:
 a) machine haven't booted to the testing kernel correctly
 b) Jenkins failed to connect to the machine
 c) igt_runner/piglit/... failed to produce results.json
 d) ...?

Sadly, we don't have any way of automatically telling one from the other yet. We are concerned only with stderr, -out and dmesg. We would need to also import the Jenkins' log in and probably some other extra data to be able to effectively filter the known issues.

At this point this should be considered as purely infrastructure issue/limitation and the results should be examined manually for any visible patterns until we improve. Customer impact: none.
Comment 7 CI Bug Log 2019-07-31 09:20:01 UTC
A CI Bug Log filter associated to this bug has been updated:

{- fi-byt-squawks, fi-skl-lmem, fi-cml-u, shard-iclb*, fi-icl-y, fi-icl-guc, fi-icl-dsi : boot - fail -}
{+ All machines: boot - fail +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6583/fi-byt-j1900/boot.html
  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6582/shard-skl2/boot.html


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.