From: Martin Wolf <mwolf@adiumentum.com>
To: alsa-devel@alsa-project.org
Subject: Re: problem with bisecting a bug in the alsa driver
Date: Tue, 31 Aug 2010 21:09:55 +0200 [thread overview]
Message-ID: <4C7D5383.1090306@adiumentum.com> (raw)
In-Reply-To: <4C7A9FE9.5090500@adiumentum.com>
can you send me a working .config file for bisecting the kernel?
my system contains a P35 chipset core2duo
ext4 filesystem
ahci sata
intel hd audio (here is the problem)
because if i use the standard ubuntu 10.04 settings it takes ages to
compile...
Am 29.08.2010 19:59, schrieb Martin:
> i also tried with
>
> bdl_pos_adj=256
>
> the "error" in the last line went away but the crackling is still there
>
> Am 29.08.2010 19:28, schrieb Jaroslav Kysela:
>> On Sun, 29 Aug 2010, Martin wrote:
>>
>>
>>> hi,
>>>
>>> thanks for the quick help.
>>> here is the diff.txt
>>>
>> I would try to play with these two module parameters:
>>
>> bdl_pos_adj : 1,-1,-1,-1,-1,-1,-1,-1
>> enable_msi : -1
>>
>> Try to set 'enable_msi=0' and 'bdl_pos_adj=16' for the snd-hda-intel
>> module.
>>
>> Jaroslav
>>
>> -----
>> Jaroslav Kysela<perex@perex.cz>
>> Linux Kernel Sound Maintainer
>> ALSA Project, Red Hat, Inc.
>>
>> _______________________________________________
>> Alsa-devel mailing list
>> Alsa-devel@alsa-project.org
>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>>
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
--
Adiumentum GmbH
Gf. Martin Wolf
Banderbacherstraße 76
90513 Zirndorf
0911 / 9601470
mwolf@adiumentum.com
prev parent reply other threads:[~2010-08-31 19:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-29 15:57 problem with bisecting a bug in the alsa driver Martin
2010-08-29 16:09 ` Jaroslav Kysela
2010-08-29 16:52 ` Martin
2010-08-29 17:28 ` Jaroslav Kysela
2010-08-29 17:57 ` Martin
2010-08-29 17:59 ` Martin
2010-08-31 19:09 ` Martin Wolf [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=4C7D5383.1090306@adiumentum.com \
--to=mwolf@adiumentum.com \
--cc=alsa-devel@alsa-project.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.