| Summary: | [CI][SHARDS] igt@kms_busy@extended_*_render-[abc] - dmesg-warn - Asynchronous wait on fence i915:kms_busy\[\d+\]/0:1 timed out \(hint:intel_atomic_commit_ready | ||
|---|---|---|---|
| Product: | DRI | Reporter: | Martin Peres <martin.peres> |
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Status: | CLOSED NOTABUG | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
| Severity: | enhancement | ||
| Priority: | high | CC: | intel-gfx-bugs |
| Version: | XOrg git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | ReadyForDev | ||
| i915 platform: | BXT, GLK, HSW, KBL, SNB | i915 features: | CI Infra |
|
Description
Martin Peres
2018-09-17 07:04:11 UTC
On HSW and SNB, the message is a little different: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4833/shard-snb6/igt@kms_busy@extended-modeset-hang-newfb-render-b.html [48.567442] Asynchronous wait on fence i915:rcs0:f timed out (hint:intel_atomic_commit_ready+0x0/0x4c [i915]) A bug in the test runner; it is mistaking KERN_NOTICE for a warning. I was expecting it to have been fixed. Not a bug, a feature. --piglit-style-dmesg was an explicitly requested feature and is in use in CI atm. To ween out the other differences first I suppose. That will disappear when we can actually get to the point where we can remove that flag. Up to Tomi and Martin (?) when they can run enough test rounds to be confident pre-merge doesn't get more noisy. https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_114/fi-ilk-650/igt@kms_busy@extended-pageflip-hang-newfb-render-b.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_113/fi-byt-clapper/igt@kms_busy@extended-pageflip-hang-newfb-render-b.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_114/fi-byt-n2820/igt@kms_busy@extended-pageflip-hang-newfb-render-a.html [618.939579] Asynchronous wait on fence i915:rcs0:9599 timed out (hint:intel_atomic_commit_ready+0x0/0x4c [i915]) Doing some more investigation. This is expected behavior. So the dmesg-warn in this case is invalid.. Then invalid as bug? (In reply to Maarten Lankhorst from comment #5) > Doing some more investigation. This is expected behavior. So the dmesg-warn > in this case is invalid.. Thanks, closing as NOTABUG. I created https://bugs.freedesktop.org/show_bug.cgi?id=109921 for the IGT issue. |
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.