White noise on shutdown/reboot

Ask Fedora
, ,
1

I have a fairly standard Fedora 44 XFCE system which I use for work and gaming, with an Asus Xonar D(S?)X which is recognised as Multimedia audio controller: C-Media Electronics Inc CMI8788 [Oxygen HD Audio].

The sound has been fine under Wine for about a month except for some rare crackling which usually corrects itself after a minute or two. A few days ago during a game, the sound cut out completely, and did not recover. After a reboot the sound returned perfectly, both inside Wine and on the desktop.

However now, when I shutdown or reboot, I get a blast of white noise just before the system powers off. It last about a third- to a half-second, and it occurs during the last 15 or so lines of the textual shutdown log. This did not happen before the incident. Besides volume, and disabling unused devices, I have made no audio configuration changes.

I… don’t know where to start diagnosing this. I don’t even fully understand the Linux sound system.

Here’s what I have installed that I think might be relevant.

$ yum list --installed | grep -i "pulse\|pipewire\|audio\|jack"
cirrus-audio-firmware.noarch                         20260622-1.fc44                     updates
intel-audio-firmware.noarch                          20260622-1.fc44                     updates
jack-mixer.x86_64                                    14-22.fc44                          fedora
mingw64-FAudio.noarch                                25.05-4.fc44                        fedora
pcaudiolib.x86_64                                    1.1-19.fc44                         fedora
pipewire.x86_64                                      1.6.8-1.fc44                        updates
pipewire-alsa.x86_64                                 1.6.8-1.fc44                        updates
pipewire-config-raop.x86_64                          1.6.8-1.fc44                        updates
pipewire-gstreamer.x86_64                            1.6.8-1.fc44                        updates
pipewire-jack-audio-connection-kit.x86_64            1.6.8-1.fc44                        updates
pipewire-jack-audio-connection-kit-libs.x86_64       1.6.8-1.fc44                        updates
pipewire-libs.x86_64                                 1.6.8-1.fc44                        updates
pipewire-plugin-libcamera.x86_64                     1.6.8-1.fc44                        updates
pipewire-pulseaudio.x86_64                           1.6.8-1.fc44                        updates
pipewire-utils.x86_64                                1.6.8-1.fc44                        updates
portaudio.x86_64                                     19.7.0-3.fc44                       fedora
pulseaudio-libs.x86_64                               17.0-9.fc44                         fedora
pulseaudio-libs-glib2.x86_64                         17.0-9.fc44                         fedora
pulseaudio-utils.x86_64                              17.0-9.fc44                         fedora
python3-audioread.noarch                             3.0.1-12.fc44                       fedora
python3-pyaudio.x86_64                               0.2.13-11.fc44                      fedora
python3-simpleaudio.x86_64                           1.0.4-21.fc44                       fedora
qjackctl.x86_64                                      1.0.6-1.fc44                        updates
webrtc-audio-processing.x86_64                       2.1-5.fc44                          fedora
wine-pulseaudio.x86_64                               11.0-3.fc44                         fedora
xfce4-pulseaudio-plugin.x86_64                       0.5.1-3.fc44                        fedora

~/.config/pulse/ contains a binary cookie file.

~/.config/jack_mixer/preferences.ini

[Preferences]
confirm_quit = False
default_meter_scale = K20
default_slider_scale = linear_30dB
midi_behavior_mode = 0
use_custom_widgets = False
vumeter_color = #ccb300
vumeter_color_scheme = default

/etc/pulse/client.conf

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = no 
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 MiB

; auto-connect-localhost = no
; auto-connect-display = no

I’ve eyeballed the last page of /var/log/messages, and I don’t see anything related to either sound, audio or PCIe. If someone could tell what to look for, that’d be a great help.

I’d really appreciate some help in fixing this. It scares the cat.

And me.

2

I would think that it is a kernel issue.
As the kernel controls what the system hardware does.

Can you try an earlier kernel?

Can you post the last 15 or so lines from your shutdown where you say the sound plays?

3

Still fairly new to this Linux lark, and that sounds like forbidden witchcraft. Last resort perhaps.

So, uh… turns out my machine reboots really fast and the entire reboot log is under two seconds. I apologise for log-dumping, but I don’t know enough to narrow it down.

There seems to be some interesting stuff regarding sound.target/start, but that’s as much as I can offer.

$ journalctl -k -b “-1” -o short-precise

Sep 26 14:08:32.527270 groovy kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Sep 26 14:08:32.528269 groovy kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7
Sep 26 14:08:35.389394 groovy kernel: kauditd_printk_skb: 26 callbacks suppressed
Sep 26 14:08:35.389425 groovy kernel: audit: type=1305 audit(1790428115.387:334): op=set audit_pid=0 old=1165 auid=4294967295 ses=4294967295 subj=system_u:system_r:auditd_t:s0 res=1
Sep 26 14:08:35.389451 groovy kernel: audit: type=1131 audit(1790428115.388:335): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=auditd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 26 14:08:35.390282 groovy kernel: audit: type=1131 audit(1790428115.388:336): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 26 14:08:35.413268 groovy kernel: audit: type=1131 audit(1790428115.411:337): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-fsck@dev-disk-by\x2duuid-E8B2\x2dB14B comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 26 14:08:35.417268 groovy kernel: EXT4-fs (sda2): unmounting filesystem 54b2f5e9-f507-4e0d-b544-47dc7d652df7.
Sep 26 14:08:35.421270 groovy kernel: audit: type=1131 audit(1790428115.419:338): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-fsck@dev-disk-by\x2duuid-54b2f5e9\x2df507\x2d4e0d\x2db544\x2d47dc7d652df7 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 26 14:08:35.422266 groovy kernel: audit: type=1131 audit(1790428115.420:339): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 26 14:08:35.422290 groovy kernel: audit: type=1131 audit(1790428115.420:340): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 26 14:08:35.423268 groovy kernel: audit: type=1131 audit(1790428115.421:341): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup-dev-early comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 26 14:08:35.434269 groovy kernel: audit: type=1131 audit(1790428115.432:342): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-zram-setup@zram0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Sep 26 14:08:35.501267 groovy kernel: audit: type=1131 audit(1790428115.499:343): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 26 14:08:35.549273 groovy kernel: watchdog: watchdog0: watchdog did not stop!
Sep 26 14:08:35.556283 groovy systemd-shutdown[1]: Using hardware watchdog /dev/watchdog0: 'SP5100 TCO timer', version 0.
Sep 26 14:08:35.581784 groovy systemd-shutdown[1]: Watchdog running with a hardware timeout of 10min.
Sep 26 14:08:35.581810 groovy systemd-shutdown[1]: Syncing filesystems and block devices.
Sep 26 14:08:35.591279 groovy systemd-shutdown[1]: Sending SIGTERM to remaining processes...
4

last two seconds of /var/log/messages
https://pastebin.com/raw/97mz35fS

5

Well i might consider a safe option here one of the reason being you arent changing the system config. So give it a try.

6

It is really easy.
Your system keeps three kernels.
On boot, press left shift, you will get a ‘Grub’ menu, select the kernel you want and press enter.

7

Uh, I don’t see that. I have Fedora, Fedora rescue, Windows and UEFI.

This is a fresh install, not an update. Unless the previous kernels are installed as part of the normal install routine, then I won’t have them. Other than removing ‘quiet’, I haven’t edited grub.cfg.

8

With a fresh install it is very important to immediately after the installation completes.

A fresh install will have older packages that have probably been updated to resolve issues others may have seen.

Please do a full update, then let us know if the problem continues after that.