From: Takashi Iwai <tiwai@suse.de>
To: Jonathan McDowell <noodles@earth.li>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: Audio crackles with 4.1-rc1
Date: Tue, 28 Apr 2015 16:43:00 +0200 [thread overview]
Message-ID: <s5ha8xsuxe3.wl-tiwai@suse.de> (raw)
In-Reply-To: <s5hpp6ov1wv.wl-tiwai@suse.de>
At Tue, 28 Apr 2015 15:05:20 +0200,
Takashi Iwai wrote:
>
> At Tue, 28 Apr 2015 13:35:18 +0100,
> Jonathan McDowell wrote:
> >
> > On Tue, Apr 28, 2015 at 02:00:17PM +0200, Takashi Iwai wrote:
> > > At Tue, 28 Apr 2015 12:21:57 +0100,
> > > Jonathan McDowell wrote:
> > > >
> > > > Having upgraded to 4.1-rc1 from 4.0 I'm now hearing audio crackles at
> > > > regular intervals. I'm fairly sure this is due to the HDA power save as
> > > > once audio is playing things are fine, it's just when starting to play
> > > > audio that I hear the crackle.
> > > >
> > > > System is a Dell Latitude E7240. I haven't tried a bisect yet but will
> > > > attempt to find some time to do so in the next few days. It looks like
> > > > there have been some changes in sound/hda/ between 4.0 + 4.1-rc1 so I'll
> > > > concentrate on those first.
> > > >
> > > There are lots of code changes and enhancements wrt power saving in
> > > 4.1, and bisection won't help so much, I'm afraid.
> > >
> > > First off, check the device status while you hear crackles.
> > > Is the codec in runtime suspend (aka power save)? This can be seen in
> > > /sys/bus/hdaudio/devices/*/power/runtime_status. Then check the
> > > runtime status of the controller, too, found in
> > > /sys/class/sound/card?/device/power/runtime_status.
> >
> > The cracking is definitely happening with the transition from suspended
> > to active:
> >
> > /sys/class/sound/card0/device/power/runtime_status:suspended
> > /sys/class/sound/card1/device/power/runtime_status:active
> > /sys/bus/hdaudio/devices/hdaudioC0D0/power/runtime_status:suspended
> > /sys/bus/hdaudio/devices/hdaudioC1D0/power/runtime_status:active
> >
> > card1 + C1D0 were suspended, I hit delete in a terminal to force a
> > terminal bell, got the crackle and the state changed to active as above.
>
> Ah, so it's a click noise that happens only once per runtime PM
> transition? I thought it were constant crackling noises from your
> description ("regular intervals").
>
> In anyway, please give alsa-info.sh output on both 4.0 and 4.1.
Also, does the click noise occur only at powering up, and not at
powering down?
Takashi
next prev parent reply other threads:[~2015-04-28 14:43 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 11:21 Audio crackles with 4.1-rc1 Jonathan McDowell
2015-04-28 12:00 ` Takashi Iwai
2015-04-28 12:35 ` Jonathan McDowell
2015-04-28 13:05 ` Takashi Iwai
2015-04-28 14:43 ` Takashi Iwai [this message]
2015-04-29 11:28 ` Jonathan McDowell
2015-04-29 11:54 ` Takashi Iwai
2015-04-30 15:01 ` Jonathan McDowell
2015-04-30 17:06 ` Takashi Iwai
2015-05-02 15:05 ` Jonathan McDowell
2015-05-19 6:15 ` Takashi Iwai
2015-05-19 16:19 ` Jonathan McDowell
2015-05-19 17:09 ` Takashi Iwai
2015-05-19 21:53 ` Jonathan McDowell
2015-05-20 5:01 ` Takashi Iwai
2015-05-20 20:02 ` Jonathan McDowell
2015-06-10 10:17 ` Mihai Donțu
2015-06-10 10:22 ` Takashi Iwai
2015-06-10 10:41 ` Mihai Donțu
2015-06-10 10:50 ` Takashi Iwai
2015-06-10 11:45 ` Mihai Donțu
2015-06-10 12:33 ` Takashi Iwai
2015-06-10 12:50 ` Takashi Iwai
2015-06-10 16:22 ` Mihai Donțu
2015-06-10 16:27 ` Takashi Iwai
2015-06-10 16:43 ` Mihai Donțu
2015-06-10 18:23 ` Takashi Iwai
2015-06-10 22:12 ` Mihai Donțu
2015-06-11 5:01 ` Takashi Iwai
2015-06-11 22:23 ` Mihai Donțu
2015-06-12 7:00 ` Takashi Iwai
2015-06-12 9:45 ` Mihai Donțu
2015-06-12 10:09 ` Takashi Iwai
2015-06-12 14:13 ` Takashi Iwai
2015-06-12 17:28 ` Mihai Donțu
2015-06-14 12:24 ` Jonathan McDowell
2015-06-15 12:04 ` 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=s5ha8xsuxe3.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noodles@earth.li \
/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;
as well as URLs for NNTP newsgroup(s).