Hi, I've solved my problems. I've searched faqs and found this one: a.. Xv is terribly slow and takes 30% CPU time or more. What's wrong? b.. As of 06/05/2003, there is a confirmed bug in the SuSE 8.2 XFree 4.3 packages and probably in XFree 4.3 packages of some other distributions as well. I know of at least Debian's 4.3.0pre1v1 containing this bug, too. This is no SiS driver bug and there is no real workaround available. However, on some systems, especially Athlon based ones, it helps setting the option XvUseMemcpy to false. Later versions of XFree86 will hopefully fix this problem rendering this option unneccessary. (Technical explanation: There is a problem with memory access in these versions of XFree86, rendering memcpy-operations to video RAM extremely slow. SiS hardware is not the only one affected, there were numerous complaints from users of other hardware, too. This bug is also known as the "O_SYNC bug". If you want to know more, search the archive of the xdevel mailing list for a thread named "Athlon related mystery".) Setting XvUseMemcpy to 0 solved my problems. It seems that this setting is still important (I have Suse 9.0, xfree 4.4 and still had problems). Thanks to Thomas for this info. Regards, Robert. ----- Original Message ----- From: "Robert Rozman" <rozman@xxxxxxxxxxxxx> To: <xfree86@xxxxxxxxxxx> Sent: Friday, March 19, 2004 11:58 PM Subject: Re: Asus Pundit (sis 651) : High CPU usage in xv ? > Hi, > > I have upgraded to xfree 4.4 (also latest sis_drv.o) and it doesn't help (at > least in noticeable way) - cpu is still high, xvtest gives around 220 FPS > > I'm attaching log and kindly ask for any idea, help or advice how to solve > this. Are there any tools to properly track this problem inside xv ? > > > Thanks in advance, > > regards, > > Robert Rozman > > ----- Original Message ----- > From: "Robert Rozman" <rozman@xxxxxxxxxxxxx> > To: <xfree86@xxxxxxxxxxx> > Sent: Thursday, March 18, 2004 9:38 AM > Subject: Re: Asus Pundit (sis 651) : High CPU usage in xv ? > > > > Hi, > > > > I'm still fighting with high cpu usage in xv extension whem playing media > > files (xine, mplayer, vlc) under Suse 9.0 , xfree 4.3.0-29 and sis 651 > with > > latest sis drivers. > > > > All log outputs seems fine, just xvtest is at low 200 FPS and cpu is hig > > (30-50%) when playing video that does rescaling. > > > > Are there any utities to check what is going on in xv extension > (xine-check > > reports all fine) ? > > What should I try to find solution ? > > > > I'm attaching xvinfo (all other relevant logs are attached to my previous > > posts) if anything suspicious is in there ? > > > > PS.: system performance was OKsome time ago, then did some upgrades and > now > > it won't perform as needed - so I guess there is someking of settings > > problem... > > > > I kindly ask for any advice, help, cause this is too hard for me as > newbie. > > > > Thanks for any help in advance, > > > > regards, > > > > Robert. > > > > ----- Original Message ----- > > From: "Robert Rozman" <rozman@xxxxxxxxxxxxx> > > To: <xfree86@xxxxxxxxxxx> > > Sent: Tuesday, March 16, 2004 10:39 AM > > Subject: Re: Asus Pundit (sis 651) : High CPU usage for X in > > mplayer - are these values sane ? > > > > > > > Hi, > > > > > > I've tried reduceing memory to 32M in bios. > > > > > > That particular warning goes away, but high cpu problem persists. > > > > > > Short answers: > > > > > cat /proc/mtrr > > > > > > reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1 > > > > > reg01: base=0x1c000000 ( 448MB), size= 64MB: uncachable, count=1 > > > > > reg02: base=0xdc000000 (3520MB), size= 64MB: write-combining, > count=1 > > > > > reg03: base=0xe8000000 (3712MB), size= 32MB: write-combining, > count=1 > > > > > reg04: base=0xe1400000 (3604MB), size= 4MB: write-combining, > count=1 > > > > > > > > Is that from before or after starting X? > > > > > > > After starting X. > > > > > > > Do you have a console framebuffer driver running? > > > > > > > > > > Probably is running from bootsplash feature integrated in Suse 9.0 > > > > > > > > (WW) SIS(0): Failed to set up write-combining range > > > > (0xe8000000,0x4000000) > > > > > > > > The reason for your problem is that, for some reason, MTRR setup > fails, > > > > although it obviously is supported by your kernel. At the moment I > > > > cannot think of a reason for this. > > > > > > > > Does this warning message go away if you change the amount of video > RAM > > > > to, say, 32MB in the BIOS setup? > > > > > > Yes, it goes away. > > > > > > > > > > > (BTW: Why do you set "forcecrt1" to "false" when it appears that you > > > > neither have a TV, LCD or secondary VGA connected?) > > > There is note in example-config that one can override automatic > detection > > > with this one. I've commented it our, but no difference. > > > > > > I'm attaching new Xfree.log in case it helps. > > > > > > Thanks in advance for all help, > > > > > > Robert. > > > > > > > > > ----- Original Message ----- > > > From: "Thomas Winischhofer" <thomas@xxxxxxxxxxxxxxxx> > > > To: <xfree86@xxxxxxxxxxx> > > > Sent: Monday, March 15, 2004 1:12 AM > > > Subject: Re: Asus Pundit (sis 651) : High CPU usage for X in > > > mplayer - are these values sane ? > > > > > > > > > > Robert Rozman wrote: > > > > > Hi, > > > > > > > > > > I'm sending files requested to give proper help. Like I said it > seems > > > like > > > > > Xv is not working (I get lower cpu if I set -vo x11 in mplayer). I > > > suspect > > > > > that software scaling is going on, but don't know what to do to > > correct > > > this > > > > > ( I get CPU for X 40-50% and for mplayer or mythtv frontend about > > 20%). > > > I > > > > > have Asus pundit, with P4 2.4 G. > > > > > > > > > > I'll appreciate any help, since this is the only major problem > left... > > > > > > > > > > I have: > > > > > > > > > > uname -a -> Linux pundit 2.4.21-144-default #1 Fri Nov 14 00:01:36 > UTC > > > 2003 > > > > > i686 i686 i386 GNU/Linux > > > > > > > > > > cat /proc/mtrr > > > > > > reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1 > > > > > reg01: base=0x1c000000 ( 448MB), size= 64MB: uncachable, count=1 > > > > > reg02: base=0xdc000000 (3520MB), size= 64MB: write-combining, > count=1 > > > > > reg03: base=0xe8000000 (3712MB), size= 32MB: write-combining, > count=1 > > > > > reg04: base=0xe1400000 (3604MB), size= 4MB: write-combining, > count=1 > > > > > > > > Is that from before or after starting X? > > > > > > > > Do you have a console framebuffer driver running? > > > > > > > > > (WW) SIS(0): Failed to set up write-combining range > > > > (0xe8000000,0x4000000) > > > > > > > > The reason for your problem is that, for some reason, MTRR setup > fails, > > > > although it obviously is supported by your kernel. At the moment I > > > > cannot think of a reason for this. > > > > > > > > Does this warning message go away if you change the amount of video > RAM > > > > to, say, 32MB in the BIOS setup? > > > > > > > > (BTW: Why do you set "forcecrt1" to "false" when it appears that you > > > > neither have a TV, LCD or secondary VGA connected?) > > > > > > > > Thomas > > > > > > > > -- > > > > Thomas Winischhofer > > > > Vienna/Austria > > > > thomas AT winischhofer DOT net http://www.winischhofer.net/ > > > > twini AT xfree86 DOT org > > > > _______________________________________________ > > > > XFree86 mailing list > > > > XFree86@xxxxxxxxxxx > > > > http://XFree86.Org/mailman/listinfo/xfree86 > > > > > > _______________________________________________ XFree86 mailing list XFree86@xxxxxxxxxxx http://XFree86.Org/mailman/listinfo/xfree86
