LKML Archive on
help / color / mirror / Atom feed
From: Stan Bubrouski <>
Cc: Andi Kleen <>,
	"" <>
Subject: Re: Bad X-performance on 2.6.6 & 2.6.7-rc1 on x86-64
Date: Wed, 26 May 2004 19:51:43 -0400	[thread overview]
Message-ID: <1085615502.4543.26.camel@duergar> (raw)
In-Reply-To: <20040526122658.2121389e@highlander.Home.LAN>

On Wed, 2004-05-26 at 06:26, Malte Schröder wrote:
> > And Malte, are you using emu10k1 driver per chance?
> Yes, emu10k1/alsa on sb audigy.

I asked because I'm using the emu10k1 driver and I've noticed frequent
bizarre behviour when watching videos in xine AND mplayer...

While this could be written off as a xine bug, my friends who have other
audio cards can watch the same files without issue in both media
players.  I hadn't thought much of it, until now.

So here's the low-down... I'm thinking there are some bad bugs in the
emu10k1 driver (not surprisingly, it's given me problems for *4* years,
using OSS and ALSA, though I must say the OSS driver seems to be ALOT

For completeness could you test the OSS emu10k driver (which supports
PCM, while the ALSA driver does not) and see if you experience better
overall performance?  Like less CPU utilization etc... I'm very
interested in finding out where the bottlenecks are.  The emu10k1 driver
isn't perfect and neither are xine or mplayer so I'd like figure out
what  exactly  is going on here.  I'll of course do the same.  It's just
kind of hard to judge for me seeing as my system is now 4 years old.


  reply	other threads:[~2004-05-26 23:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2004-05-24 19:31 ` Bad X-performance on 2.6.6 & 2.6.7-rc1 on x86-64 Andi Kleen
2004-05-25 10:26   ` Malte Schröder
2004-05-25 12:36     ` Andi Kleen
2004-05-25 21:20       ` Stan Bubrouski
2004-05-25 21:32         ` Tomasz Torcz
2004-05-26 10:28           ` Malte Schröder
2004-05-26 10:26         ` Malte Schröder
2004-05-26 23:51           ` Stan Bubrouski [this message]
2004-05-27  8:57             ` Malte Schröder
2004-05-24 16:00 Malte Schröder

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:

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

  git send-email \
    --in-reply-to=1085615502.4543.26.camel@duergar \ \ \ \ \

* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).