Bug 1776836

Summary:	Dummy Output on Kernel upgrade
Product:	[Fedora] Fedora	Reporter:	bwstevens <brettwstevens69>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	31	CC:	airlied, brettwstevens69, bskeggs, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, masami256, mchehab, mjg59, steved
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-12-06 05:45:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description bwstevens 2019-11-26 13:31:16 UTC

1. Please describe the problem:
Dummy output in the sound settings of Fedora

2. What is the Version-Release number of the kernel:
5.3.12-300.fc31.x86_64

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
This happened on an upgrade from Kernel 5.3.10 to kernel 5.3.12

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Update and restart

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:


6. Are you running any modules that not shipped with directly Fedora's kernel?:
No

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Comment 1 Hans de Goede 2019-11-26 13:44:40 UTC

On what hardware are you seeing this?

There was a bug in the recent alsa-lib-1.2.1 update which causes this issue on Bay- and Cherry-Trail based hardware.

If you are hitting that issue then this should be fixed by the alsa-lib 1.2.1.1 update which is currently in the stable updates repository now:
https://bodhi.fedoraproject.org/updates/FEDORA-2019-d70ab6e7a2

So a simple "sudo dnf update 'alsa*'" followed by a "killall pulseaudio" might fix this.

Comment 2 Fedora Update System 2019-12-03 20:35:16 UTC

FEDORA-2019-7f716645c1 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-7f716645c1

Comment 3 Fedora Update System 2019-12-04 02:20:43 UTC

alsa-lib-1.2.1.2-3.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-7f716645c1

Comment 4 Fedora Update System 2019-12-06 05:45:01 UTC

alsa-lib-1.2.1.2-3.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.