[Bug 210123] New: drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]]

* [Bug 210123] New: drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]] - flip_done time out with vmwgfx
@ 2020-11-09 21:05 bugzilla-daemon
  2020-11-09 21:16 ` [Bug 210123] " bugzilla-daemon
                   ` (7 more replies)
  0 siblings, 8 replies; 9+ messages in thread
From: bugzilla-daemon @ 2020-11-09 21:05 UTC (permalink / raw)
  To: dri-devel

https://bugzilla.kernel.org/show_bug.cgi?id=210123

            Bug ID: 210123
           Summary: drm:drm_atomic_helper_wait_for_dependencies
                    [drm_kms_helper]] - flip_done time out with vmwgfx
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.3.18-24.9.1
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: stefan+kernel@mayr-stefan.de
        Regression: No

Since we upgraded SUSE Linux Enterprise Server 15 from kernel 4.12.14-197.45.1
(SLES15 SP1) to 5.3.18-24.9.1 (SLES15 SP2) or later we see the following error
messages on some virtual machines:

[102215.857602] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]]
*ERROR* [CRTC:38:crtc-0] flip_done timed out
[102226.097847] [drm:drm_atomic_helper_wait_for_dependencies [drm_kms_helper]]
*ERROR* [PLANE:34:plane-0] flip_done timed out

We were also provided some more current kernels from SUSE support:
- 5.3.18 with updated modules 
- 5.8.15
- 5.9.1

The issue stays the same. All affected machines are running in runlevel 3. The
only graphical "thing" is the boot screen and when this error appears in the
logs this screen is sitting at an empty login prompt.
All virtual machines are running in a VMware environment on ESXi-Hosts with
versions between 6.0.x and 6.7.x. We could not track it down to specific ESXi
versions, load on the ESXi host or even the virtual machine. This happens on
different versions, loaded and also on idle hosts and virtual machines.

The issue goes away when we add vmwgfx to the grub module_blacklist.

I know our kernel versions are somehow SUSE specific. But what changed between
4.12 and 5.3 and later that may cause this message between drm and vmwgfx?

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

^ permalink raw reply	[flat|nested] 9+ messages in thread