From: "Ni@m" <niam.niam@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: sound is interrupting with new kernels
Date: Sun, 29 Jul 2007 01:31:49 +0300 [thread overview]
Message-ID: <a9e22dff0707281531m38bfe702nc2b60aea4deea2ba@mail.gmail.com> (raw)
In-Reply-To: <20070723122813.GA9420@elte.hu>
On 7/23/07, Ingo Molnar <mingo@elte.hu> wrote:
>
> could you try CONFIG_HZ_1000 instead of the 250 you are using currently?
> Also, please enable CONFIG_SCHED_DEBUG to improve the output of
> cfs-debug-info.sh.
>
> Ingo
>
Hi, Igno.
Sorry for so long response, I hadn't opportunity to reboot machine for
new kernel.
I've built 2.6.22 with CONFIG_HZ_1000 and CONFIG_PREEMPT - nothing changed =(.
Interesting that in Totem(Gnome vp) sound isn't interrupting during
video watching.
I'll try other kernels later to find out what is working good for my case.
In gxine(xine-based) sound is interrupting too!
>firstly, could you check whether the ogg123/mpg321 console apps work
>without any audio skipping? If they work fine, does Amarok work fine?
>(Amarok is an X apps that has a high-quality latency design - most other
>X based players are affected by X communication latencies.)
I'm not using amarok but audacious. It's seems that's everything is
alright with it.
I'll send more tests results later.
Best wishes!
Dima
next prev parent reply other threads:[~2007-07-28 22:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-21 22:10 sound is interrupting with new kernels Ni@m
2007-07-23 0:16 ` Michal Piotrowski
2007-07-23 3:01 ` Ni@m
2007-07-23 4:25 ` Ni@m
2007-07-23 12:02 ` Ingo Molnar
2007-07-23 12:28 ` Ingo Molnar
2007-07-28 22:31 ` Ni@m [this message]
[not found] ` <a9e22dff0707290415lf7588cfx19155d531c9c5a3f@mail.gmail.com>
2007-07-29 11:16 ` Fwd: " Ni@m
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=a9e22dff0707281531m38bfe702nc2b60aea4deea2ba@mail.gmail.com \
--to=niam.niam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.k.k.piotrowski@gmail.com \
--cc=mingo@elte.hu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox