[HP Laptop 14-ma0xxx] No sound after suspend (kernels 5.0.0 and 5.1.5 faulty, but not 5.0.1)

[Robin]

On my Laptop sound is working only after a fresh reboot. Every time I suspend the laptop, I can no longer use the internal speakers or any headphones. I tried a lot of solutions suggested online none of them working for me. Since this problem is very annoying I would really appreciate if a fix would be available.

Thanks a lot :)

Additional information:
Laptop: HP 14-ma0307ng
Ubuntu 19.04
Audio:
sudo lspci -v | grep -A7 -i "audio"
00:0e.0 Audio device: Intel Corporation Device 3198 (rev 03)
 Subsystem: Hewlett-Packard Company Device 84b6
 Flags: bus master, fast devsel, latency 0, IRQ 25
 Memory at a1310000 (64-bit, non-prefetchable) [size=16K]
 Memory at a1000000 (64-bit, non-prefetchable) [size=1M]
 Capabilities: [50] Power Management version 3
 Capabilities: [80] Vendor Specific Information: Len=14 <?>
 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: pulseaudio 1:12.2-2ubuntu3
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: harry 5835 F.... pulseaudio
 /dev/snd/pcmC0D0c: harry 5835 F...m pulseaudio
 /dev/snd/pcmC0D0p: harry 5835 F...m pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat May 18 19:12:01 2019
InstallationDate: Installed on 2019-04-30 (18 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/09/2018
dmi.bios.vendor: Insyde
dmi.bios.version: F.05
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 84B6
dmi.board.vendor: HP
dmi.board.version: KBC Version 76.17
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.05:bd04/09/2018:svnHP:pnHPLaptop14-ma0xxx:pvrType1ProductConfigId:rvnHP:rn84B6:rvrKBCVersion76.17:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 14-ma0xxx
dmi.product.sku: 4DL72EA#ABD
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

[Daniel van Vugt (vanvugt)]

Please try installing some older (and newer) kernels and tell us which (if any) avoid the problem:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

[Robin (r-ehl)]

 @vanvugt Thank you for your answer.
I tried the kernel versions 5.0.0-13 and 4.3.0-04 as well. For the first one, the same problem occured (sound only after a fresh boot) and the second one couldn't be installed correctly because of missing libraries (a boot was possible, but e.g. the mouse pointer was not moving).
I have already tried to reconfigure pulseaudio, to force alsa-audio to reload (it does reload but doesn't change anything).

Here is my output of aplay:
$ aplay -L
default
    Playback/recording through the PulseAudio sound server
null
    Discard all samples (playback) or generate zero samples (capture)
jack
    JACK Audio Connection Kit
pulse
    PulseAudio Sound Server
sysdefault:CARD=PCH
    HDA Intel PCH, ALC236 Analog
    Default Audio Device
front:CARD=PCH,DEV=0
    HDA Intel PCH, ALC236 Analog
    Front speakers
surround21:CARD=PCH,DEV=0
    HDA Intel PCH, ALC236 Analog
    2.1 Surround output to Front and Subwoofer speakers
surround40:CARD=PCH,DEV=0
    HDA Intel PCH, ALC236 Analog
    4.0 Surround output to Front and Rear speakers
surround41:CARD=PCH,DEV=0
    HDA Intel PCH, ALC236 Analog
    4.1 Surround output to Front, Rear and Subwoofer speakers
surround50:CARD=PCH,DEV=0
    HDA Intel PCH, ALC236 Analog
    5.0 Surround output to Front, Center and Rear speakers
surround51:CARD=PCH,DEV=0
    HDA Intel PCH, ALC236 Analog
    5.1 Surround output to Front, Center, Rear and Subwoofer speakers
surround71:CARD=PCH,DEV=0
    HDA Intel PCH, ALC236 Analog
    7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
hdmi:CARD=PCH,DEV=0
    HDA Intel PCH, HDMI 0
    HDMI Audio Output
hdmi:CARD=PCH,DEV=1
    HDA Intel PCH, HDMI 1
    HDMI Audio Output
hdmi:CARD=PCH,DEV=2
    HDA Intel PCH, HDMI 2
    HDMI Audio Output
hdmi:CARD=PCH,DEV=3
    HDA Intel PCH, HDMI 3
    HDMI Audio Output
hdmi:CARD=PCH,DEV=4
    HDA Intel PCH, HDMI 4
    HDMI Audio Output
dmix:CARD=PCH,DEV=0
    HDA Intel PCH, ALC236 Analog
    Direct sample mixing device
dmix:CARD=PCH,DEV=3
    HDA Intel PCH, HDMI 0
    Direct sample mixing device
dmix:CARD=PCH,DEV=7
    HDA Intel PCH, HDMI 1
    Direct sample mixing device
dmix:CARD=PCH,DEV=8
    HDA Intel PCH, HDMI 2
    Direct sample mixing device
dmix:CARD=PCH,DEV=9
    HDA Intel PCH, HDMI 3
    Direct sample mixing device
dmix:CARD=PCH,DEV=10
    HDA Intel PCH, HDMI 4
    Direct sample mixing device
dsnoop:CARD=PCH,DEV=0
    HDA Intel PCH, ALC236 Analog
    Direct sample snooping device
dsnoop:CARD=PCH,DEV=3
    HDA Intel PCH, HDMI 0
    Direct sample snooping device
dsnoop:CARD=PCH,DEV=7
    HDA Intel PCH, HDMI 1
    Direct sample snooping device
dsnoop:CARD=PCH,DEV=8
    HDA Intel PCH, HDMI 2
    Direct sample snooping device
dsnoop:CARD=PCH,DEV=9
    HDA Intel PCH, HDMI 3
    Direct sample snooping device
dsnoop:CARD=PCH,DEV=10
    HDA Intel PCH, HDMI 4
    Direct sample snooping device
hw:CARD=PCH,DEV=0
    HDA Intel PCH, ALC236 Analog
    Direct hardware device without any conversions
hw:CARD=PCH,DEV=3
    HDA Intel PCH, HDMI 0
    Direct hardware device without any conversions
hw:CARD=PCH,DEV=7
    HDA Intel PCH, HDMI 1
    Direct hardware device without any conversions
hw:CARD=PCH,DEV=8
    H...

[Robin (r-ehl)]

It also affects kernel version 5.0.0-16 (installed from disco-proposed)

[Daniel van Vugt (vanvugt)]

Thanks, but we will need more data points. We need to know at least one kernel version which does not have the bug (if a version exists). And then we need to know the earliest version where the bug was introduced.

[Robin (r-ehl)]

I was now able to try a few different versions leading to the following results:
* The bug does not affect kernel version 4.18.0-15 (Tested using a Live install of 18.04.2)
* The bug does not affect kernel version 4.20.17-042017 (Tested on my install of 19.04 with a manually installed kernel)
* The bug does not affect kernel version 5.0.1-050001 (Tested on my install of 19.04 with a manually installed kernel)
* The bug does affect newly build kernel version 5.1.5-050105 (Tested on my install of 19.04 with a manually installed kernel)

So the bug must be introduced between 4.20.17 and 5.0.0-15.
I hope this can be a good starting point for troubleshooting.

[Daniel van Vugt (vanvugt)]

It sounds like you made a typo there. The points you list suggest the regression started between kernels 5.0.1 and 5.1.5:

* The bug does not affect kernel version 5.0.1-050001 (Tested on my install of 19.04 with a manually installed kernel)
* The bug does affect newly build kernel version 5.1.5-050105 (Tested on my install of 19.04 with a manually installed kernel)

Yet your original bug description suggests the bug is in version 5.0.0-15.16-generic too, as does your summary in comment #6. Those conclusions conflict with the above listed findings, so please clarify...

[Robin (r-ehl)]

Indeed my conclusion was wrong because I mixed up the versions. The bug does affect some newer versions although it seems that it was solved in the meantime before reappearing again.

To correct, I observed the following:

* The bug does NOT affect kernel version 4.18.0-15 (Tested using a Live install of 18.04.2)
* The bug does NOT affect kernel version 4.20.17-042017 (Tested on my install of 19.04 with a manually installed kernel)
* The bug DOES affect kernel version 5.0.0-13 (Tested on my install of 19.04 with a manually installed kernel)
* The bug DOES affect kernel version 5.0.0-15 (I used this version when I filed the bug report some days after I installed Ubuntu on my laptop)
* The bug DOES affect kernel version 5.0.0-16 (Tested on my install of 19.04 with an update from disco-proposed using apt-get)
* The bug does NOT affect kernel version 5.0.1-050001 (Tested on my install of 19.04 with a manually installed kernel)
* The bug DOES affect newly build kernel version 5.1.5-050105 (Tested on my install of 19.04 with a manually installed kernel)

I conclude, that the bug was introduced between 4.20.17 and 5.0.0-13, then solved between 5.0.0-16 and 5.0.1 only to be reintroduced in the most recent build (5.1.5).
As you might notice, I am only a user, so I have limited skills. The change might also come from something else but I did not purposely change any setting or behavior while I tried the different versions. I tested the sound using the button in the sound-settings of Ubuntu and Spotify (both after a fresh boot and after suspend).

[Daniel van Vugt (vanvugt)]

Thanks. That is very helpful.

[Hui Wang (hui.wang)]

@Robin,

Please do a test.

edit /etc/modprobe.d/alsa-base.conf
add "options snd-hda-intel probe_mask=0x1"
reboot
and redo the test, if the problem still can be reproduced?

[Kai-Heng Feng (kaihengfeng)]

Please test this kernel:
https://people.canonical.com/~khfeng/lp1829621/

[Robin (r-ehl)]

Thanks for your comments

@Hui Wang: The additional line worked. Following your steps the bug could no longer be reproduced with kernel 5.1.5-050105. Thanks a lot. Would it be suitable to apply these changes as default or to propose them commented out in the config file?
@Kai-Heng Feng: Your kernel worked, too. I tested it with the additional line and without: The bug could not be reproduced in both cases.

[Kai-Heng Feng (kaihengfeng)]

Ok I'll discuss with Hui about this issue.

I reverted this commit in the test kernel:
commit b5a236c175b0d984552a5f7c9d35141024c2b261
Author: Hui Wang <email address hidden>
Date: Tue Mar 19 09:28:44 2019 +0800

    ALSA: hda - Enforces runtime_resume after S3 and S4 for each codec

[Hui Wang (hui.wang)]

I backported a i915 patch, let us see if it can fix this problem on glk machines, please test this kernel:

https://drive.google.com/drive/folders/1K7OrvkUTiub7vRaicen6smXR6TiDdBTM?usp=sharing

remove the workaround of #10
sudo dpkg -i linux-modules-xxxx.deb
sudo dpkg -i linux-image-unsigned-xxx.deb
sudo dpkg -i linux-modules-extra-xxx.deb

reboot and choose this new installed kernel to boo. redo the test.

thx.

[Robin (r-ehl)]

I installed your kernel and commented out the previous manual configuration. All is working fine and the speakers are working after suspend, too. So the bug can't be reproduced.
Thanks!

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]