linux-kernel - Re: [REGRESSION bisected] Sound goes too fast due to commit 7b3a177b0

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4BC5D2F4.4010500@tremplin-utc.net>
Date:	Wed, 14 Apr 2010 16:36:36 +0200
From:	Éric Piel <eric.piel@...mplin-utc.net>
To:	Takashi Iwai <tiwai@...e.de>
CC:	Jaroslav Kysela <perex@...ex.cz>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	alsa-devel@...a-project.org, Frank Griffin <ftg@...drunner.com>
Subject: Re: [REGRESSION bisected] Sound goes too fast due to commit 7b3a177b0

On 14/04/10 15:39, Takashi Iwai wrote:
:
> 
> bdl_pos_adj is really a workaround for devices that report wrong DMA
> position (or at the wrong timing).  I guess position_fix=1 may fix
> better.
> 
> Although the driver already has a dynamic switching of position_fix
> method, it checks only the very first read.  If it gives a (more or
> less) sane value, it prefers the position-buffer method (corresponding
> to position_fix=2) rather than reading LPIB register
> (position_fix=1).
> 
> It seems, however, that more devices work sanely with LPIB reg
> nowdays.  This wasn't the case formerly.  So, it might be better to
> use position_fix=1 as default for modern systems...
Frank,
Could you check that for you too adding "position_fix=1" fixes the problem?

To do so, edit /etc/modprobe.conf and add this line at end:
options snd-hda-intel position_fix=1

You need to reboot for this to be taken into account.

Cheers,
Eric
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/