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
Equinix is shutting down its operations with us on April 30, 2025. They have graciously supported us for almost 5 years, but all good things come to an end.
Given the time frame, it's going to be hard to make a smooth transition of the cluster to somewhere else (TBD). Please expect in the next months some hiccups in the service and probably at least a full week of downtime to transfer gitlab to a different place.
All help is appreciated.
Project 'drm/intel' was moved to 'drm/i915/kernel'. Please update any links and bookmarks that may still have the old path.
few kms tests - dmesg-warn/dmesg-fail - DSB 0 timed out waiting for idle
A CI Bug Log filter associated to this bug has been updated by rveesamx.
Description: MTL_P ADL_P: few kms tests - dmesg-warn/dmesg-fail - DSB 0 timed out waiting for idle
Equivalent query: runconfig_tag IS IN ["DRM-TIP"] AND machine_tag IS IN ["ADL-S", "MTL-P", "ADL"] AND ((testsuite_name = "IGT" AND test_name IS IN ["igt@kms_color@ctm-0-75@pipe-a", "igt@kms_color@ctm-signed@pipe-c", "igt@kms_color@ctm-0-25@pipe-b", "igt@kms_color@ctm-0-25@pipe-a", "igt@kms_color@degamma", "igt@kms_big_fb@linear-8bpp-rotate-0", "igt@kms_color@degamma@pipe-a", "igt@kms_color@ctm-signed", "igt@kms_big_fb@linear-8bpp-rotate-180", "igt@kms_big_fb@x-tiled-8bpp-rotate-180", "igt@kms_color@ctm-0-75", "igt@kms_color@ctm-0-25", "igt@kms_big_fb@4-tiled-8bpp-rotate-180"])) AND ((testsuite_name = "IGT" AND status_name IS IN ["dmesg-warn", "dmesg-fail"])) AND dmesg ~= 'DSB 0 timed out waiting for idle'
A CI Bug Log filter associated to this bug has been updated by Vinay.
Description: MTL_P ADL_P: few kms tests - dmesg-warn/dmesg-fail - DSB 0 timed out waiting for idle
Equivalent query: runconfig_tag IS IN ["DRM-TIP"] AND machine_tag IS IN ["ADL-S", "MTL-P", "ADL"] AND ((testsuite_name = "IGT" AND test_name IS IN ["igt@kms_color@ctm-0-75@pipe-a", "igt@kms_color@ctm-red-to-blue", "igt@kms_color@ctm-signed@pipe-c", "igt@kms_color@ctm-0-25@pipe-b", "igt@kms_color@ctm-0-25@pipe-a", "igt@kms_color@degactmma-red-to-blue@pipe-c", "igt@kms_big_fb@linear-8bpp-rotate-0", "igt@kms_color@degamma", "igt@kms_color@degamma@pipe-a", "igt@kms_color@ctm-signed", "igt@kms_big_fb@linear-8bpp-rotate-180", "igt@kms_big_fb@x-tiled-8bpp-rotate-180", "igt@kms_color@ctm-0-75", "igt@kms_color@ctm-0-25", "igt@kms_big_fb@4-tiled-8bpp-rotate-180"])) AND ((testsuite_name = "IGT" AND status_name IS IN ["dmesg-warn", "dmesg-fail"])) AND dmesg ~= 'DSB 0 timed out waiting for idle'
I am not sure this is related, but I see this for a few seconds after boot. I think this is related because it started at the same time as these errors, and I don't see any other errors.
Not really. Based on the DSB_CURRENT_HEAD it looks like the hardware didn't stop executing when it reached DSB_TAIL and instead continued executing random junk past it. Eventually we get tired of waiting for it and just whack it on the head.
This seems to be an ADL-S... We seem to have one of those in CI, but for some reason it's not participating in the idle runs, and bat runs might not do any LUT tests I guess.
I'm observing the same problem on i7-1165G7 (Tiger Lake), with both the endless variations of DSB 0 timed out waiting for idle error and the initial image corruption on one of the monitors.
Fedora kernels from 6.7.0-200-fc39.x86_64 (no data for 6.7.rc) to 6.8.0-0.rc6.49.fc40.x86_64, Wayland (Sway), with or without external displays.
Reproducibility seems to depend on the adaptive sync being enabled on one of the active outputs.
Let me know if you want more info, dmesg with drm.debug, etc. Bisecting might be problematic though, with SecureBoot and Fedora's overcomplicated kernel source setup.
Machine info
Linux 6.8.0-0.rc6.49.fc40.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Feb 26 18:38:52 UTC 2024 x86_64 GNU/LinuxSystem Information Manufacturer: LENOVO Product Name: 20XYCTO1WW Version: ThinkPad X1 Yoga Gen 6 UUID: a379217a-b55b-11eb-80f0-38f3abd43c05 Wake-up Type: Power Switch SKU Number: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 Family: ThinkPad X1 Yoga Gen 6 00:02.0 VGA compatible controller [0300]: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:22d4] Flags: bus master, fast devsel, latency 0, IRQ 157, IOMMU group 8 Memory at 603c000000 (64-bit, non-prefetchable) [size=16M] Memory at 4000000000 (64-bit, prefetchable) [size=256M] I/O ports at 3000 [size=64] Expansion ROM at 000c0000 [virtual] [disabled] [size=128K] Capabilities: [40] Vendor Specific Information: Len=0c <?> Capabilities: [70] Express Root Complex Integrated Endpoint, IntMsgNum 0 Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable+ 64bit- Capabilities: [d0] Power Management version 2 Capabilities: [100] Process Address Space ID (PASID) Capabilities: [200] Address Translation Service (ATS) Capabilities: [300] Page Request Interface (PRI) Capabilities: [320] Single Root I/O Virtualization (SR-IOV) Kernel driver in use: i915 Kernel modules: i915, xeDP-6 "Dell Inc. DELL U2715H H7YCC5A40C1S (DP-6)"DP-2 "Dell Inc. DELL S2721DGF 2JHW523 (DP-2)"eDP-1 "AU Optronics 0xD291 (eDP-1)"
commit 41429d9b68367596eb3d6d5961e6295c284622a7Author: Ville Syrjälä <ville.syrjala@linux.intel.com>Date: Wed Mar 6 06:08:05 2024 +0200 drm/i915/dsb: Fix DSB vblank waits when using VRR
and
commit 810e4519a1b34b5a0ff0eab32e5b184f533c5ee9Author: Ville Syrjälä <ville.syrjala@linux.intel.com>Date: Wed Mar 6 06:08:04 2024 +0200 drm/i915/vrr: Generate VRR "safe window" for DSB
And now I'm getting these new errors from time to time:
[252063.249149] Fence expiration time out i915-0000:00:02.0:Xwayland[2388861]:2496![252063.257497] Fence expiration time out i915-0000:00:02.0:Discord[2400980]:8![252063.282168] Fence expiration time out i915-0000:00:02.0:Discord[2400980]:a![252236.305395] Fence expiration time out i915-0000:00:02.0:Renderer[1979]:4be63e![252236.312394] Fence expiration time out i915-0000:00:02.0:Renderer[1979]:4be640![252236.313383] Fence expiration time out i915-0000:00:02.0:Renderer[1979]:4be642!
The corresponding applications hang and have to be killed... I'm not sure that this follows from the previous issue, but I don't think I changed anything else on my system besides the two patches above. Does anybody else see this?