From: "Daniel Eklöf" <daniel-pl05T3eHY++zQB+pC5nmwQ@public.gmane.org>
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: NV50: xv fullscreen issues
Date: Sat, 27 Dec 2008 13:49:38 +0100 [thread overview]
Message-ID: <200812271349.42624.daniel@ekloef.se> (raw)
In-Reply-To: <200812271236.37993.daniel-pl05T3eHY++zQB+pC5nmwQ@public.gmane.org>
> > > After having crashed gmplayer (with the code lines above re-enabled), I
> > > also notice that screen updates are a bit shaky - sometimes the screen
> > > isn't updated until I press a key or move the mouse (e.g. typing 'ls'
> > > doesn't list any files until I press another key, web pages aren't
> > > displayed until I move the mouse and so on). At this point, I sometimes
> > > also see an unusually high CPU load from X (around 75%). Sometimes X
> > > freezes, sometimes not.
> >
> > I don't see this on my systems, but i'll look into it when i'm back in
> > action.
>
> After some more testing, I can say for sure that this isn't really related
> to the xv fullscreen issue. xv in fullscreen was just a way to trigger it.
> I'm not sure exactly what triggers it though - starting certain GUI
> programs triggers it, while other programs do not. In any case, I'm pretty
> sure the high CPU load is always there when I see the screen update issue.
> When this happens, X is stuck inside nouveau_dma_wait:
>
> (gdb) bt
> #0 0x00007f63f5f18df8 in nouveau_dma_wait (userchan=<value optimized out>,
> size=2) at nouveau_dma.c:88
> #1 0x00007f63f5f4f01d in nouveau_dma_begin (userchan=0x241aaf0,
> grobj=0x241a900, method=4916, size=1,
> file=0x7f63f5f5b630 "NV50EXAPrepareComposite", line=695) at
> nouveau_dma.h:118
> #2 0x00007f63f5f509b0 in NV50EXAPrepareComposite (op=<value optimized
> out>, pspict=0x3eb9210, pmpict=0x3bad6c0, pdpict=0x3543430,
> pspix=0x2f21de0, pmpix=0x522f4c0, pdpix=0x5a39230) at nv50_exa.c:695
> #3 0x00007f63f457de6a in ?? () from /usr/lib64/X11/modules//libexa.so
> #4 0x00007f63f457f097 in exaComposite () from
> /usr/lib64/X11/modules//libexa.so
> #5 0x000000000053029f in ?? ()
> #6 0x000000000051f0ad in ?? ()
> #7 0x0000000000447ef6 in Dispatch ()
> #8 0x000000000042d82d in main ()
>
Oh, and I almost forgot; the logs are full (as in ~500M in two days) of
Dec 26 18:29:47 tiny [drm] PGRAPH_ERROR - nSource:
PROTECTION_ERROR,x00000000:0x000003ec
Dec 26 18:29:47 tiny [drm] PGRAPH_ERROR - nSource: PROTECTION_ERROR, nStatus:
Dec 26 18:29:47 tiny [drm] PGRAPH_ERROR - Ch 2/0 Class 0x502d Mthd 0x08dc Data
0x00000000:0x000003ec
Dec 26 18:29:47 tiny [drm] PGRAPH_ERROR - nSource: PROTECTION_ERROR, nStatus:
Dec 26 18:29:47 tiny [drm] PGRAPH_ERROR - Ch 2/0 Class 0x502d Mthd 0x08dc Data
0x00000000:0x000003ec
Dec 26 18:29:47 tiny [drm] PGRAPH_ERROR - nSource: PROTECTION_ERROR, nStatus:
Dec 26 18:29:47 tiny [drm] PGRAPH_ERROR - Ch 2/0 Class 0x502d Mthd 0x08dc Data
0x00000000:0x000003ec
prev parent reply other threads:[~2008-12-27 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-26 0:40 NV50: xv fullscreen issues Daniel Eklöf
[not found] ` <200812260140.38609.daniel-pl05T3eHY++zQB+pC5nmwQ@public.gmane.org>
2008-12-26 23:25 ` Ben Skeggs
[not found] ` <fc5b84ad0812261525g58be27fdrf4649ab68c8e36a2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-12-27 11:36 ` Daniel Eklöf
[not found] ` <200812271236.37993.daniel-pl05T3eHY++zQB+pC5nmwQ@public.gmane.org>
2008-12-27 12:18 ` Maarten Maathuis
2008-12-27 12:49 ` Daniel Eklöf [this message]
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=200812271349.42624.daniel@ekloef.se \
--to=daniel-pl05t3ehy++zqb+pc5nmwq@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.