From: Takashi Iwai <tiwai@suse.de>
To: "Éric Piel" <Eric.Piel@tremplin-utc.net>
Cc: Jaroslav Kysela <perex@perex.cz>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
alsa-devel@alsa-project.org, Frank Griffin <ftg@roadrunner.com>
Subject: Re: [REGRESSION bisected] Sound goes too fast due to commit 7b3a177b0
Date: Fri, 16 Apr 2010 09:53:09 +0200 [thread overview]
Message-ID: <s5hzl13u93u.wl%tiwai@suse.de> (raw)
In-Reply-To: <4BC782E5.7070900@tremplin-utc.net>
At Thu, 15 Apr 2010 23:19:33 +0200,
Éric Piel wrote:
>
> Op 14-04-10 18:01, Takashi Iwai schreef:
> :
> >>
> >> I don't fully grasp the meaning of bdl_pos_adj, so I don't know if it's
> >> a bug to not play correctly when forcing it to 0. Is it?
> >
> > It might be that this was for reducing the load by position
> > correction mechanism. You might see the hd-audio kernel thread in a
> > high CPU usage. This might be fixed also by position_fix=1, though.
> Yes, I had added this option after a regression in the previous kernel
> which causes the hd-audio thread to take 50% of a CPU. Eventually, it
> was fixed and not needed anymore. So I guess in the case of my laptop,
> this is not really a regression, because everything is fine with the
> default values.
>
> In the case of Frank, this looks more like a regression, or at least a
> bug to solve, because this happens with the default options. However,
> this report should be taken with care, because this happens on a
> 2.6.33.2 kernel made by Mandriva, containing many alsa patches of
> 2.6.34. Frank, how possible would it be to test a 2.6.34-rc4 kernel from
> Linus?
>
> If this bug is confirmed, Takashi, do you know any way to choose
> automatically position_fix=1 when needed?
There is a quirk table in sound/pci/hda_intel.c to check PCI SSID.
I already added an entry for Frank's machine on sound git tree which
will be included in the pull request I'm going to send soon.
(Sorry the mail went outside since Frank's reply was private.)
thanks,
Takashi
next prev parent reply other threads:[~2010-04-16 7:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 21:54 Éric Piel
2010-04-14 6:08 ` Takashi Iwai
2010-04-14 11:22 ` Éric Piel
2010-04-14 11:54 ` Éric Piel
2010-04-14 13:39 ` Takashi Iwai
2010-04-14 14:36 ` Éric Piel
2010-04-14 15:39 ` Frank Griffin
2010-04-14 16:02 ` Takashi Iwai
2010-04-14 16:01 ` Takashi Iwai
2010-04-15 21:19 ` Éric Piel
2010-04-16 7:53 ` Takashi Iwai [this message]
2010-04-16 10:35 ` Frank Griffin
2010-04-16 10:33 ` Frank Griffin
2010-04-17 15:21 ` Frank Griffin
2010-06-17 20:17 ` Mirix
2010-06-18 12:11 ` Takashi Iwai
2010-06-18 15:25 ` Miro Moman
2010-04-16 14:55 ` Maciej Rutecki
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=s5hzl13u93u.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Eric.Piel@tremplin-utc.net \
--cc=alsa-devel@alsa-project.org \
--cc=ftg@roadrunner.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=rjw@sisk.pl \
/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®