| Summary: | [HSW] Timed out CRC reading and watermark error (igt@kms_frontbuffer_tracking@fbc-suspend) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | cprigent <christophe.prigent> | ||||||||||
| Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||||
| Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||||||
| Severity: | normal | ||||||||||||
| Priority: | medium | CC: | dorota.czaplejewicz, intel-gfx-bugs, przanoni | ||||||||||
| Version: | unspecified | Keywords: | bisect_pending | ||||||||||
| Hardware: | x86-64 (AMD64) | ||||||||||||
| OS: | Linux (All) | ||||||||||||
| Whiteboard: | ReadyForDev | ||||||||||||
| i915 platform: | HSW | i915 features: | display/FBC, display/watermark | ||||||||||
| Attachments: |
|
||||||||||||
|
Description
cprigent
2016-12-21 15:35:08 UTC
Created attachment 128611 [details]
HSW__kms_frontbuffer_tracking__fbc-suspend__kern.log
This is a regression. Can you please bisect it? I confirm the regression: good 982bb30 bad 86a2672 bisect_pending Created attachment 128631 [details]
git-show-982bb30
Created attachment 128632 [details]
git-show-7155b05
Not sure it helps:
The merge base 7155b057c61e55eed27bf478ac9b8034c4c97582 is bad.
This means the bug has been fixed between 7155b057c61e55eed27bf478ac9b8034c4c97582 and [982bb302fdc49f8331f29103ff1c111645598d23].
(In reply to cprigent from comment #5) > Created attachment 128632 [details] > git-show-7155b05 > > Not sure it helps: > The merge base 7155b057c61e55eed27bf478ac9b8034c4c97582 is bad. > This means the bug has been fixed between > 7155b057c61e55eed27bf478ac9b8034c4c97582 and > [982bb302fdc49f8331f29103ff1c111645598d23]. I'm not 100% sure I understand what you mean here. Is the merge commit the *first* bad commit? Also, commit 982bb302fdc49f8331f29103ff1c111645598d23 doesn't exist anymore. Can you reproduce the bug with drm-intel-next-queued (instead of drm-tip)? Yes, this is why it does not help. This was the result of git bisect after only 3 iterations (comment 5), I will provide a new result ww04. We moved to drm-intel-next-queued and used EZBench. EZBench does not provide a bisect result, conclusion is the test result is unstable. It tested commits b403c8f, 7155b05, 2ec4584, f03ee46, 0b47a6b. *** Bug 100020 has been marked as a duplicate of this bug. *** This test still fails with the following configuration:
Software Configuration:
======================================
Component: drm
tag: libdrm-2.4.81-24-g3095cc8
commit: 3095cc8eaba1aa87ad38c04ae2b1eabe30f7e16c
Component: cairo
tag: 1.15.6-2-g57b4050
commit: 57b40507dda3f58dfc8635548d606b86dc7bcf51
Component: intel-gpu-tools
tag: intel-gpu-tools-1.19-57-g6fcc8e8
commit: 6fcc8e8b247661c7950b998e0b95141ffbd6b833
Component: piglit
tag: piglit-v1
commit: c8f4fd9eeb298a2ef0855927f22634f794ef3eff
Hardware Configuration:
======================================
platform : Haswell
motherboard model : Haswell
manufacturer : IntelCorp.
cpu : Intel® Core™ i5-4250U Processor
gpu : Intel® HD Graphics 5000
max memory ram : 16 GB
cpu core : 2
Still fails with commit ad6ab9f96437f0cb1f4d8a7840fd9eeb894eb12e According to https://intel-gfx-ci.01.org/tree/drm- tip/igt@kms_frontbuffer_tracking@fbc-suspend.html this test isn't failing anymore. Closing. $ : time sudo -E ./kms_frontbuffer_tracking --run-subtest fbc-suspend IGT-Version: 1.19-g1e99f8b (x86_64) (Linux: 4.14.0-rc3-drm-tip-ww40-commit-2f14e31+ x86_64) Primary screen: HDMI-A 1920x1200, crtc 0 Secondary screen: DP 1920x1200, crtc 1 FBC last action not supported Can't test PSR: no usable eDP screen. Sink CRC not supported: primary screen is not eDP rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Wed Oct 11 15:26:34 2017 rtcwake: assuming RTC uses UTC ... rtcwake: wakeup from "mem" using /dev/rtc0 at Wed Oct 11 15:27:01 2017 Subtest fbc-suspend: SUCCESS (25.437s) real 0m56.403s user 0m0.026s sys 0m0.388s |
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.