From: Takashi Iwai <tiwai@suse.de>
To: Klaus@ethgen.ch
Cc: alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] CPU hook snd_hda_intel
Date: Wed, 04 Dec 2019 17:31:48 +0100 [thread overview]
Message-ID: <s5hy2vsjbm3.wl-tiwai@suse.de> (raw)
In-Reply-To: <20191202184759.GB29478@ikki.ethgen.ch>
On Mon, 02 Dec 2019 19:47:59 +0100,
Klaus Ethgen wrote:
>
> Hello,
>
> Please keep me in Cc when you answer as I am not subscribed to the list.
>
> I use the most current kernel 5.4.1 (but I did have that problem since
> several 5.x versions) on gentoo on a X61s Lenovo laptop. What I see is
> that from time to time one CPU is constantly working and draining my
> battery with a process kworker/*-events.
>
> Today I was able to identify the source of the problem. The module
> snd-hda-intel seems to produce that load. When I unload the module, the
> CPU hook is gone. Even if I load it again, I have a good change to solve
> the problem.
>
> It also helps often to put the laptop to sleep and waking it up again.
>
> My relevant dmesg part is:
> [ 7.186766] snd_hda_intel 0000:00:1b.0: probe_mask set to 0x1 for device 17aa:20ac
> [ 7.563277] snd_hda_codec_generic hdaudioC0D0: autoconfig for Generic: line_outs=1 (0x12/0x0/0x0/0x0/0x0) type:speaker
> [ 7.563281] snd_hda_codec_generic hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
> [ 7.563284] snd_hda_codec_generic hdaudioC0D0: hp_outs=1 (0x11/0x0/0x0/0x0/0x0)
> [ 7.563286] snd_hda_codec_generic hdaudioC0D0: mono: mono_out=0x0
> [ 7.563288] snd_hda_codec_generic hdaudioC0D0: inputs:
> [ 7.563292] snd_hda_codec_generic hdaudioC0D0: Internal Mic=0x15
> [ 7.563294] snd_hda_codec_generic hdaudioC0D0: Mic=0x14
> [ 7.563297] snd_hda_codec_generic hdaudioC0D0: Dock Mic=0x1c
>
> For reference I attach my kernel config to this mail. I am not sure if
> it is needed but better give as much as informations that I have.
>
> So please, if you have any idea how to narrow that problem or even solve
> it, help would be appreciated.
I guess checking the perf output would give you more clue, e.g. which
function is hogging the CPU. Without such information, it's very hard
to diagnose...
thanks,
Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-12-04 16:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 18:47 [alsa-devel] CPU hook snd_hda_intel Klaus Ethgen
2019-12-04 16:31 ` Takashi Iwai [this message]
2019-12-07 20:06 ` Klaus Ethgen
2019-12-08 8:45 ` Takashi Iwai
2019-12-08 17:31 ` Klaus Ethgen
2019-12-09 7:10 ` Takashi Iwai
2019-12-09 8:57 ` Klaus Ethgen
2019-12-09 9:27 ` Takashi Iwai
2019-12-09 9:45 ` Klaus Ethgen
2019-12-10 14:32 ` Klaus Ethgen
2019-12-10 14:35 ` Klaus Ethgen
2019-12-10 14:43 ` Takashi Iwai
2019-12-10 15:10 ` Klaus Ethgen
2019-12-10 15:19 ` Takashi Iwai
2019-12-10 15:28 ` Klaus Ethgen
2019-12-23 17:18 ` Klaus Ethgen
2019-12-23 22:14 ` 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=s5hy2vsjbm3.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=Klaus@ethgen.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox