Error messaages from ALSA.

I’m not sure if this is the correct forum, but I started seeing some new error log messages a few days ago. Here are the messages:


Dec 07 16:34:01 Mobile-PC pulseaudio[1794]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Dec 07 16:34:01 Mobile-PC pulseaudio[1794]: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers.
Dec 07 16:34:01 Mobile-PC pulseaudio[1794]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.

Here is the extent of how long they have been occurring:


Dec 06 13:45:48 Mobile-PC pulseaudio[1607]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Dec 07 11:05:52 Mobile-PC pulseaudio[4629]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
Dec 07 16:34:01 Mobile-PC pulseaudio[1794]: ALSA woke us up to write new data to the device, but there was actually nothing to write.

The only recent ALSA update is:


> zypp-hist | grep -i ALSA
...
2020-12-04 14:47:55 | install | alsa-ucm-conf | 1.2.4-2.1

My system is AMD, so I have no idea why the messages specify the driver ‘snd_hda_intel’. Any ideas where to look?

Thanks,
Gene

Hi Gene
Have you run rpmconfigcheck lately? I note some changes in /etc/pulse/default.pa or have you configured this at some point?

I run sudo rpmconf -at after most updates, and on the Dec. 4, the date alsa-ucm-conf was updated, a new /etc/pulse/daemon.conf showed up. I installed the new configuration file and set flat-volumes = no in the new file. I just ran rpmconfigcheck and nothing showed up:


> sudo rpmconfigcheck
Searching for unresolved configuration files

Interesting, I see that flat-volumes is already being set to no in /etc/pulse/daemon.conf.d/60-disable_flat_volumes.conf. I was unaware of the contents of this file:


> cat /etc/pulse/daemon.conf.d/60-disable_flat_volumes.conf
# Set flat-volumes to no so that no applications can abruptedly increase master volume
# Remedy for fate#310668.
flat-volumes = no

It looks like I need to figure out how to report the issue to the ALSA developers.

Gene

The 3400G has the following messages since Dec 01:

[FONT=monospace]Dec 02 18:44:19 3400G kernel: snd_hda_intel 0000:08:00.1: enabling device (0000 -> 0002) 
Dec 02 18:44:19 3400G kernel: snd_hda_intel 0000:08:00.1: Handle vga_switcheroo audio client 
Dec 02 18:44:19 3400G kernel: snd_hda_intel 0000:08:00.6: enabling device (0000 -> 0002) 
Dec 02 18:44:20 3400G kernel: snd_hda_intel 0000:08:00.1: bound 0000:08:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) 
**-- Reboot --**
Dec 03 05:55:32 3400G kernel: snd_hda_intel 0000:08:00.1: enabling device (0000 -> 0002) 
Dec 03 05:55:32 3400G kernel: snd_hda_intel 0000:08:00.1: Handle vga_switcheroo audio client 
Dec 03 05:55:32 3400G kernel: snd_hda_intel 0000:08:00.6: enabling device (0000 -> 0002) 
Dec 03 05:55:33 3400G kernel: snd_hda_intel 0000:08:00.1: bound 0000:08:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
[/FONT]

No more messages since Dec 04. There was some trouble with alsa: https://forums.opensuse.org/showthread.php/547348-Disable-optical-sound-line-on-MacBook-Pros