Bug 111191 - [CI][BAT] igt@kms_chamelium@common-hpd-after-suspend - fail - previous timer already enabled
Summary: [CI][BAT] igt@kms_chamelium@common-hpd-after-suspend - fail - previous timer ...
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: not set not set
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-22 12:56 UTC by Martin Peres
Modified: 2019-09-10 09:31 UTC (History)
1 user (show)

See Also:
i915 platform: SKL
i915 features: display/Other


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Peres 2019-07-22 12:56:09 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5106/fi-skl-6700k2/igt@kms_chamelium@common-hpd-after-suspend.html

Starting subtest: common-hpd-after-suspend
(kms_chamelium:2981) igt_chamelium-CRITICAL: Test assertion failure function chamelium_rpc, file ../lib/igt_chamelium.c:349:
(kms_chamelium:2981) igt_chamelium-CRITICAL: Failed assertion: !chamelium->env.fault_occurred
(kms_chamelium:2981) igt_chamelium-CRITICAL: Chamelium RPC call failed: RPC failed at server.  <class 'chameleond.devices.input_flow.InputFlowError'>:previous timer already enabled
Comment 1 CI Bug Log 2019-07-22 12:57:05 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* SKL: igt@kms_chamelium@common-hpd-after-suspend - fail - previous timer already enabled
  - https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5106/fi-skl-6700k2/igt@kms_chamelium@common-hpd-after-suspend.html
  - https://intel-gfx-ci.01.org/tree/drm-tip/Trybot_4645/fi-skl-6700k2/igt@kms_chamelium@common-hpd-after-suspend.html
Comment 2 Lakshmi 2019-09-10 09:31:59 UTC
Priority/severity is set to default. This issue occurred only once on IGT_5106 (1 month, 2 weeks old).


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.