From: Takashi Iwai <tiwai@suse.de>
To: Benjamin Kidwell <benjkidwell@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux-next Alsa hda_intel events/0 high CPU usage, bisected
Date: Tue, 10 Jun 2008 14:36:53 +0200 [thread overview]
Message-ID: <s5hve0ha2l6.wl%tiwai@suse.de> (raw)
In-Reply-To: <657223.15460.qm@web53708.mail.re2.yahoo.com>
At Tue, 10 Jun 2008 05:20:49 -0700 (PDT),
Benjamin Kidwell wrote:
>
> > --- Takashi Iwai <> wrote:
> >Try to run
> >
> > # echo 32 > /sys/modules/snd_hda_intel/parameters/bdl_pos_adj
> >and test again.
>
> Thanks, I think that value must be just about perfect! Tested as follows:
>
> (kill gdm)
> #modprobe -r snd_hda_intel
> #modprobe snd_hda_intel
> #echo 32 > /sys/module/snd_hda_intel/bdl_pos_adj
> (restart gdm, start playing sound)
>
> That caused events/0 CPU% to return to almost nothing and the XXX hda delay
> output did not trigger. I assume this means the latency has disappeared. For
> comparison, I repeated the above processand returned bdl_pos_adj to 1, and the
> delay printks reappeared and events/0 started showing significant cpu usage
> again. Another reset of the driver and I reset bdl_pos_adj to 32 -- no delay
> printks, almost no events/0 activity apparent.
>
> So setting bdl_pos_adj to 32 with all new patches applied makes everything
> perfect so far as I can tell. Thanks for the fix-ups for my buggy hardware,
> and for reminding me to use reply and Cc: correctly. Let me know if there's
> anything else I should test.
Thanks for quick testing!
The above value 32 is likely the size of FIFO. I guess ATI chip
reports the position with FIFO offset while ICH reports smaller delay.
I'll create one more patch to assign this value for ATI chipset.
BTW, my latest test patches can be found on the following git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-unstable-2.6.git
These are not for 2.6.27, but some of them should go to the linux-next
tree now.
Takashi
prev parent reply other threads:[~2008-06-10 12:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 21:07 Benjamin Kidwell
2008-06-06 21:15 ` Benjamin Kidwell
2008-06-07 9:38 ` Takashi Iwai
2008-06-07 9:38 ` Takashi Iwai
2008-06-08 1:56 ` Benjamin Kidwell
2008-06-09 11:11 ` Takashi Iwai
2008-06-09 11:13 ` Takashi Iwai
2008-06-09 13:13 ` Takashi Iwai
2008-06-09 22:09 ` Benjamin Kidwell
2008-06-10 10:13 ` Takashi Iwai
2008-06-10 12:20 ` Benjamin Kidwell
2008-06-10 12:36 ` Takashi Iwai [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=s5hve0ha2l6.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=benjkidwell@yahoo.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®