<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - weston-launch no output - black screen" href="https://bugs.freedesktop.org/show_bug.cgi?id=75761#c32">Comment # 32</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - weston-launch no output - black screen" href="https://bugs.freedesktop.org/show_bug.cgi?id=75761">bug 75761</a> from <a class="email" href="mailto:ppaalanen@gmail.com" title="Pekka Paalanen <ppaalanen@gmail.com>"> Pekka Paalanen</a> <pre>(In reply to <a href="show_bug.cgi?id=75761#c31">comment #31</a>) > Created <a href="attachment.cgi?id=100199" name="attach_100199" title="weston log with pixman">attachment 100199</a> <a href="attachment.cgi?id=100199&action=edit" title="weston log with pixman">[details]</a> > weston log with pixman Something is seriously wrong here: [09:58:29.402] queueing pageflip failed: Permission denied But I see you have another weston session afterwards, which seems to run, but: [12:26:36.371] page_flip_handler: time 0.000000 frame 603 [12:26:36.371] got pageflip event [12:26:36.388] page_flip_handler: time 0.000000 frame 603 [12:26:36.388] got pageflip event [12:26:36.404] page_flip_handler: time 0.000000 frame 603 [12:26:36.404] got pageflip event [12:26:36.421] page_flip_handler: time 0.000000 frame 603 [12:26:36.421] got pageflip event [12:26:36.437] page_flip_handler: time 0.000000 frame 603 [12:26:36.438] got pageflip event [12:26:36.454] page_flip_handler: time 0.000000 frame 603 That means that the kernel DRM driver does not provide timestamps and it does not even advance the vblank counter(?) if I understood right. So at least for you, the problem is that the kernel DRM does not report proper pageflip timestamps. I would consider this as a kernel driver bug, but if the kernel developers insist, I suppose we could also hack around it in Weston by providing fake timestamps, disabling the Presentation extension (somewhat similar X11 Present, not yet merged) and yelling loudly. But I'd rather the driver got fixed. As far as I see, bad timestamps are enough to make Weston stay black (fade-in animation not advancing), yet appear to work just fine. So at least we (Weston devs) should detect when the kernel driver is faulty, and abort Weston. Weston, and also the intention in Wayland, is to rely on the proper pageflip timestamps from the kernel for timing... well, everything visual, so we really would like it to work.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>