All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 75761] weston-launch no output - black screen
Date: Sat, 31 May 2014 08:32:23 +0000	[thread overview]
Message-ID: <bug-75761-8800-CbGxaVCLPW@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-75761-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 931 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=75761

--- Comment #29 from Pekka Paalanen <ppaalanen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
Hmm, a third remote possibility came to mind. If the timestamp delivered with
the DRM pageflip event does not advance, I suppose Weston's fade-in animation
might not advance either and therefore it never fades in. However this is hard
for me to believe, as I think it would have caused problems with Xorg, too...
wouldn't it?

Or maybe Xorg is only looking at the vblank counters, and you'd actually need a
program using GLX_OML_sync_control to even see the timestamps?

One could check the timestamps by:
weston_log("%s: time %u.%06u frame %u\n", __func__, sec, usec, frame);
in compositor-drm.c page_flip_handler() function.

Mm, I'd like to see a weston log with that when you have the black screen
problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1685 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2014-05-31  8:32 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-75761-8800@http.bugs.freedesktop.org/>
     [not found] ` <bug-75761-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-04-09  9:29   ` [Bug 75761] weston-launch no output - black screen bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-09  9:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-09  9:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-10 22:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-10 22:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-10 22:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-10 22:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-10 22:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-10 23:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-10 23:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-17 11:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-17 12:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-17 12:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-17 12:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-28 18:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-28 18:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-30  9:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-31  3:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-31  8:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-31  8:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2014-05-31 11:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-05-31 12:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-01 10:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-01 10:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-01 12:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-10  1:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-14 22:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-14 23:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-15  0:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-15  0:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-15 18:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-17  0:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-21 22:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-08-21 22:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-75761-8800-CbGxaVCLPW@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.