Arch Linux

loqs

Member

Registered: 2014-03-06

Posts: 18,645

Re: [SOLVED] snd_hda_intel issues after kernel upgrade to 5.0.arch1-1

744c67ffeb06f2d2493f4049ba0bd19698ce0adf is queued for 5.0.5 https://git.kernel.org/pub/scm/linux/ke … 03022172d7

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,857

Re: [SOLVED] snd_hda_intel issues after kernel upgrade to 5.0.arch1-1

5.0.5 changelog definitely reads like this should be fixed, can any of the affected confirm?

MartinRi

Member

Registered: 2019-03-21

Posts: 3

Re: [SOLVED] snd_hda_intel issues after kernel upgrade to 5.0.arch1-1

wasn't able to reproduce the bug with 5.0.5 even after a dozen suspend/resume cycles - so it seems like it's fixed for me.

axel

Member

Registered: 2007-12-10

Posts: 77

Re: [SOLVED] snd_hda_intel issues after kernel upgrade to 5.0.arch1-1

It looks fixed for me as well with 5.0.5.

Matt3o

Member

From: Firenze, Italy

Registered: 2007-09-13

Posts: 177

Re: [SOLVED] snd_hda_intel issues after kernel upgrade to 5.0.arch1-1

5.0.5 seems to have fixed it

meal

Member

From: Poland

Registered: 2017-04-27

Posts: 4

Re: [SOLVED] snd_hda_intel issues after kernel upgrade to 5.0.arch1-1

5.0.5 fixed it for me as well

---

i7 7700K / 32GB / GTX 1070 / PRIME Z270-A

nachopro

Member

Registered: 2013-08-23

Posts: 91

Re: [SOLVED] snd_hda_intel issues after kernel upgrade to 5.0.arch1-1

Sorry for necrobumping this thread, but I have the same issue today with kernel 6.10.4 and I don't know how to report the issue to the kernel project.
Any advice? Thank you

PS: The Ropid is workaround works fine: https://bbs.archlinux.org/viewtopic.php … 0#p1836910

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 24,857

Re: [SOLVED] snd_hda_intel issues after kernel upgrade to 5.0.arch1-1

Chances are very, very high these are similar symptoms but completely different causes.

On a limb

snd_soc_avs

has been acting up and stealing devices from real drivers recently, try blacklisting that. If that doesn't help, please open a new thread and post

sudo journalctl -b
aplay -lL
lspci -k

while affected and not affected so we can determine the proper course of action.

Closing this old thread.