Updating to 19.04 audio keeps clicking when nothing is playing audio

Bug #1833793 reported by Avamander
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
High
Unassigned

Bug Description

My Ubuntu version: Ubuntu 19.04
My sound card: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)

What I expect to happen:
Sound is absolutely quiet when no audio is playing

What happens now:
Audio output starts clicking every second incredibly annoyingly and loud.

What previously happened on Ubuntu 18.10:
I heard the click twice during boot and then it worked properly (without clicking during the time it should have been silent)
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: a 4604 F.... pulseaudio
 /dev/snd/pcmC0D0p: a 4604 F...m pulseaudio
 /dev/snd/controlC1: a 4604 F.... pulseaudio
CurrentDesktop: KDE
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2017-08-23 (679 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
IwConfig:
 enp63s0 no wireless extensions.

 wg0 no wireless extensions.

 lo no wireless extensions.
MachineType: Hewlett-Packard HP Compaq dc5700 Microtower
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-20-generic root=/dev/mapper/vgroot-lvroot ro cryptdevice=/dev/sda2:lvm quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-20-generic N/A
 linux-backports-modules-5.0.0-20-generic N/A
 linux-firmware 1.178.2
RfKill:

Tags: disco
Uname: Linux 5.0.0-20-generic x86_64
UpgradeStatus: Upgraded to disco on 2019-06-20 (13 days ago)
UserGroups: adm cdrom dialout dip kvm libvirt lpadmin plugdev sambashare sbuild sudo
_MarkForUpload: True
dmi.bios.date: 11/10/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786E2 v02.09
dmi.board.name: 0A60h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr786E2v02.09:bd11/10/2011:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.family: 103C_53307F
dmi.product.name: HP Compaq dc5700 Microtower
dmi.product.sku: EW287AV
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1833793/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Avamander (avamander)
affects: ubuntu → alsa-driver (Ubuntu)
summary: - Updating to 19.04 audio keeps clicking when it should be silent
+ Updating to 19.04 audio keeps clicking when nothing is playing audio
description: updated
description: updated
Paul White (paulw2u)
tags: added: disco
Revision history for this message
Avamander (avamander) wrote :

This is seriously infuriating, why do I have to keep something playing at 1% volume just for stuff to stay quiet.

Revision history for this message
Avamander (avamander) wrote :

It literally doesn't go away, only reliable way is playing something 24/7 just to get Ubuntu to shut the f*** up.

Revision history for this message
Avamander (avamander) wrote :

Is this some kind of new power optimization to constantly reinitialize my sound card?

Revision history for this message
Hui Wang (hui.wang) wrote :

Yes, there is a power optimization in the 19.04.

please close that optimization by editing the /etc/modprobe.d/alsa-base.conf

add options snd-hda-intel power_save=0

then reboot.

Changed in alsa-driver (Ubuntu):
importance: Undecided → High
status: New → Incomplete
Revision history for this message
Avamander (avamander) wrote :

@hui.wang Your suggestion worked and you saved my sanity. Thank you so much.

Could Ubuntu developers please sort out the power saving, so that the sound card actually shuts down instead of continuous clicking (reinitialization?), just for the sake of others on this chipset.

Revision history for this message
Hui Wang (hui.wang) wrote :

Need you to collect some logs, then let us see if it can be fixed through kernel driver.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1833793

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

affects: alsa-driver (Ubuntu) → linux (Ubuntu)
Revision history for this message
Avamander (avamander) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Avamander (avamander) wrote : CRDA.txt

apport information

Revision history for this message
Avamander (avamander) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Avamander (avamander) wrote : Lspci.txt

apport information

Revision history for this message
Avamander (avamander) wrote : Lsusb.txt

apport information

Revision history for this message
Avamander (avamander) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Avamander (avamander) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Avamander (avamander) wrote : ProcEnviron.txt

apport information

Revision history for this message
Avamander (avamander) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Avamander (avamander) wrote : ProcModules.txt

apport information

Revision history for this message
Avamander (avamander) wrote : PulseList.txt

apport information

Revision history for this message
Avamander (avamander) wrote : UdevDb.txt

apport information

Revision history for this message
Avamander (avamander) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Avamander (avamander) wrote :

apport information

description: updated
Revision history for this message
Avamander (avamander) wrote :

apport information

Revision history for this message
Avamander (avamander) wrote :

apport information

Revision history for this message
Hui Wang (hui.wang) wrote :

So when don't set the power_save=0, does the noise come from speaker or headphone or both of them?

Revision history for this message
Avamander (avamander) wrote :

When the power save is not disabled then the noise comes from speaker port, I don't have the headphone port connected anywhere so I can't right now check that. Once https://bugs.launchpad.net/ubuntu/+source/kinit/+bug/1833880 happens again I'll have to reboot and I can power down the machine and attach a jack to it to check.

Revision history for this message
Hui Wang (hui.wang) wrote :

Please restore the power_save=1 or comment power_save=0 from alsa-base.conf

and try this dkms (don't shutup audio pins in this dkms):
sudo dpkg -i oem-audio-hda-daily-dkms_0.1_all.deb
reboot

let us see if there is still noise or not.

If there is still noise, please run alsa-info.sh and upload the genereated /tmp/alsa-info.txt.xxx

To remove this dkms
sudo dpkg -r oem-audio-hda-daily-dkms

reboot.

Revision history for this message
Avamander (avamander) wrote :

Noise comes from both outputs.

The package did not resolve the bug.

Revision history for this message
Hui Wang (hui.wang) wrote :

When you have time, please test this dkms. if it doesn't fix the issue, please also upload a alsa-info.txt.

Brad Figg (brad-figg)
tags: added: cscc
Revision history for this message
Robert Phair (rphair) wrote :

I had this problem after upgrading kernel to 5.0.0-23 and the workaround in comment #5 (turning off the Intel power optimisation) worked for me.

Revision history for this message
Tais P. Hansen (taisph) wrote :

I have this problem on 18.04.3 after upgrading to the 5.0.0 hwe kernel (5.0.0-25-generic). Reproducible by letting the device go into power save and then waking it up by running pavucontrol.

Revision history for this message
Robert Phair (rphair) wrote :

I've just tested this again after upgrading to kernel 5.0.0-31 - the problem is still here. Sound device goes into "powersave" after 6 to 7 seconds without sound output, which is audible on non-grounded speakers as a buzzing noise. As in my comment #29, turning off the power "optimisation" fixes this problem.

Revision history for this message
Avamander (avamander) wrote :

I changed my motherboard and unfortunately can't test out any changes.

Revision history for this message
Robert Phair (rphair) wrote :

Tested again after kernel jump to 5.3 (5.3.0-26-generic): still a problem. Nice "optimisation" fellas. I guess most of the world doesn't experience this because they are either have grounded speakers or a motherboard that grounds the output, so they don't hear a buzz when a signal isn't coming from the sound card? (I have cheap speakers and a 10+ year old motherboard.)

Revision history for this message
Avamander (avamander) wrote :

@rphair

Please try the package @hui.wang posted and upload the asked alsa-info.txt, that way it can be possibly fixed.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.