public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Éric Piel" <eric.piel@tremplin-utc.net>
To: Maciej Rutecki <maciej.rutecki@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	alsa-devel@alsa-project.org, perex@perex.cz,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [2.6.33-rc1] [SOUND] HDA: high cpu usage, noise
Date: Mon, 21 Dec 2009 20:08:34 +0100	[thread overview]
Message-ID: <4B2FC7B2.7000001@tremplin-utc.net> (raw)
In-Reply-To: <8db1092f0912211012mcdd6639oaaf0bddc118e7d66@mail.gmail.com>

Op 21-12-09 19:12, Maciej Rutecki schreef:
> 2009/12/21 Takashi Iwai <tiwai@suse.de>:
>> At Sun, 20 Dec 2009 18:27:45 +0100,
>> Maciej Rutecki wrote:
>>>
>>> Hi
>>>
>>> Affected kernel: 2.6.33-rc1
>>> Last known good: 2.6.32
>>
>> The only fundamental change, AFAIK, is the use of MSI as default.
>> Could you try to add enable_msi=0 option to snd-hda-intel?
>>
> 
> root@gumis:/# cat /sys/module/snd_hda_intel/parameters/enable_msi
> 0
> 
> Still the same:
> ps aux:
> 
> root      1117 27.4  0.0      0     0 ?        S    19:00   2:05 [hd-audio0]
> 
> I also notice short sound during booting system, when sound modules is
> loading.  I can try bisection, but in next week; already I don't have
> to much time.
Hello,
I've got the same problem here (high hd-audio0 usage + clicks in the
output sound).

Hardware is identical:
/proc/asound/pcm
00-00: AD198x Analog : AD198x Analog : playback 1 : capture 1

I haven't tried the enable_msi parameter but, just to give more info,
here is the log ("dmesg | grep -i hda") when the bug happens:
Dec 18 10:39:10 dutifh kernel: HDA Intel 0000:00:1b.0: power state
changed by ACPI to D0
Dec 18 10:39:10 dutifh kernel: HDA Intel 0000:00:1b.0: PCI INT A -> GSI
17 (level, low) -> IRQ 17
Dec 18 10:39:10 dutifh kernel: input: HDA Digital PCBeep as
/devices/pci0000:00/0000:00:1b.0/input/input12
Dec 18 10:39:10 dutifh kernel: hda-intel: azx_get_response timeout,
switching to polling mode: last cmd=0x006f0900

And here is with 2.6.32, working fine
Dec 18 11:46:03 dutifh kernel: HDA Intel 0000:00:1b.0: power state
changed by ACPI to D0
Dec 18 11:46:03 dutifh kernel: HDA Intel 0000:00:1b.0: PCI INT A -> GSI
17 (level, low) -> IRQ 17
Dec 18 11:46:03 dutifh kernel: input: HDA Digital PCBeep as
/devices/pci0000:00/0000:00:1b.0/input/input11

Could it be coming from this timeout?

Eric

  reply	other threads:[~2009-12-21 19:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-20 17:27 [2.6.33-rc1] [SOUND] HDA: high cpu usage, noise Maciej Rutecki
2009-12-21 10:28 ` Takashi Iwai
2009-12-21 18:12   ` Maciej Rutecki
2009-12-21 19:08     ` Éric Piel [this message]
2009-12-22  7:04       ` Takashi Iwai
2009-12-22  9:15         ` Éric Piel
2009-12-22  9:17           ` Takashi Iwai
2009-12-22 15:15             ` Éric Piel
2009-12-22 15:40               ` Takashi Iwai
2009-12-22 15:42                 ` Éric Piel
2009-12-23 14:27             ` Éric Piel
2009-12-23 15:02               ` Takashi Iwai

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=4B2FC7B2.7000001@tremplin-utc.net \
    --to=eric.piel@tremplin-utc.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maciej.rutecki@gmail.com \
    --cc=perex@perex.cz \
    --cc=rjw@sisk.pl \
    --cc=tiwai@suse.de \
    /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