<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - X log ballooning in size with "drmmode_wait_vblank failed for scanout update" and "get vblank counter failed"" href="https://bugs.freedesktop.org/show_bug.cgi?id=105308#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - X log ballooning in size with "drmmode_wait_vblank failed for scanout update" and "get vblank counter failed"" href="https://bugs.freedesktop.org/show_bug.cgi?id=105308">bug 105308</a> from <a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> Michel Dänzer</a> <pre>(In reply to Bob Ham from <a href="show_bug.cgi?id=105308#c0">comment #0</a>) > > [ 668.860] (WW) AMDGPU(0): flip queue failed in amdgpu_scanout_flip: > Invalid argument, TearFree inactive until next modeset Did anything in particular happen, or did you do anything in particular, around this time (about 11 minutes after system boot)? > The kernel also reported this although I've no idea when in relation to > other events: > > [57903.995504] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* > amdgpu_cs_list_validate(validated) failed. > [57903.995539] [drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to process the > buffer list -22! The timestamps should be comparable, so this happened much later and is probably not directly related. Looks like the kernel ran out of memory or some other resource while processing GPU commands. Please attach the output of xrandr --verbose while the problem is occurring.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>