Fedora 35 freezes when using HDMI audio

Ask Fedora
, , ,
1

My Fedora froze completely and even tty didn’t work while using HDMI audio output. Had to forcefully switch off my system. I got the following error logs for my last boot. Has someone else also encountered such problems.

-- Boot 15d9764f5295439f8103c3f914259473 --
Dec 01 18:28:08 fedora kernel: x86/cpu: SGX disabled by BIOS.
Dec 01 12:58:18 fedora kernel: 
Dec 01 12:58:21 fedora alsactl[922]: alsa-lib parser.c:242:(error_node) UCM is not supported for this HDA model (HDA Intel PCH at 0xdf240000 irq 135)
Dec 01 12:58:21 fedora alsactl[922]: alsa-lib main.c:1405:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -6
Dec 01 12:58:21 fedora alsactl[922]: alsa-lib parser.c:242:(error_node) UCM is not supported for this HDA model (HDA NVidia at 0xdf080000 irq 17)
Dec 01 12:58:21 fedora alsactl[922]: alsa-lib main.c:1405:(snd_use_case_mgr_open) error: failed to import hw:1 use case configuration -6
Dec 01 12:59:43 fedora gdm-password][1587]: gkr-pam: unable to locate daemon control file
Dec 01 12:59:45 fedora systemd[1608]: Failed to start Application launched by gnome-session-binary.
Dec 01 12:59:47 fedora systemd[1608]: Failed to start Application launched by gnome-session-binary.
Dec 01 12:59:47 fedora systemd[1608]: Failed to start Application launched by gnome-session-binary.
Dec 01 12:59:47 fedora systemd[1608]: Failed to start Application launched by gnome-session-binary.
Dec 01 12:59:47 fedora systemd[1608]: Failed to start Application launched by gnome-session-binary.
Dec 01 12:59:50 fedora gdm-launch-environment][1141]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Dec 01 13:03:29 fedora gdm-password][5070]: gkr-pam: unable to locate daemon control file
Dec 01 13:03:31 fedora systemd[1608]: Failed to start Application launched by gnome-session-binary.
Dec 01 13:03:31 fedora systemd[1608]: Failed to start Application launched by gnome-session-binary.
Dec 01 13:03:31 fedora systemd[1608]: Failed to start Application launched by gnome-session-binary.
Dec 01 13:03:31 fedora systemd[1608]: Failed to start Application launched by gnome-session-binary.
Dec 01 13:03:33 fedora gdm-launch-environment][4652]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Dec 01 13:07:11 fedora kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 27s! [msedge:7028]
Dec 01 13:07:13 fedora abrt-notification[7465]: [🡕] System encountered a non-fatal error in ??()
Dec 01 13:07:39 fedora kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 53s! [msedge:7028]
Dec 01 13:07:40 fedora abrt-notification[7488]: [🡕] System encountered a non-fatal error in ??()
Dec 01 13:07:44 fedora kernel: rcu: INFO: rcu_sched self-detected stall on CPU
Dec 01 13:07:44 fedora kernel: rcu:         2-....: (59994 ticks this GP) idle=1aa/1/0x4000000000000000 softirq=42425/42426 fqs=14958 
Dec 01 13:07:49 fedora kernel: rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 2-... } 61384 jiffies s: 1081 root: 0x4/.
Dec 01 13:07:49 fedora kernel: rcu: blocking rcu_node structures (internal RCU debug):
Dec 01 13:08:11 fedora kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 82s! [msedge:7028]
Dec 01 13:08:12 fedora abrt-notification[7508]: [🡕] System encountered a non-fatal error in ??()
Dec 01 13:08:39 fedora kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 108s! [msedge:7028]
Dec 01 13:08:40 fedora abrt-notification[7529]: [🡕] System encountered a non-fatal error in ??()
Dec 01 13:09:07 fedora kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 135s! [msedge:7028]
Dec 01 13:09:08 fedora abrt-notification[7549]: [🡕] System encountered a non-fatal error in ??()
Dec 01 13:09:35 fedora kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 161s! [msedge:7028]
Dec 01 13:09:36 fedora abrt-notification[7569]: [🡕] System encountered a non-fatal error in ??()
Dec 01 13:10:03 fedora kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 187s! [msedge:7028]
Dec 01 13:10:04 fedora abrt-notification[7589]: [🡕] System encountered a non-fatal error in ??()
Dec 01 13:10:31 fedora kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 213s! [msedge:7028]
Dec 01 13:10:32 fedora abrt-notification[7609]: [🡕] System encountered a non-fatal error in ??()
Dec 01 13:10:44 fedora kernel: rcu: INFO: rcu_sched self-detected stall on CPU
Dec 01 13:10:44 fedora kernel: rcu:         2-....: (239978 ticks this GP) idle=1aa/1/0x4000000000000000 softirq=42425/42426 fqs=59912 
Dec 01 13:10:50 fedora kernel: rcu: INFO: rcu_sched detected expedited stalls on CPUs/tasks: { 2-... } 241608 jiffies s: 1081 root: 0x4/.
Dec 01 13:10:50 fedora kernel: rcu: blocking rcu_node structures (internal RCU debug):
Dec 01 13:11:11 fedora kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 250s! [msedge:7028]
Dec 01 13:11:12 fedora abrt-notification[7632]: [🡕] System encountered a non-fatal error in ??()
Dec 01 13:11:39 fedora kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 276s! [msedge:7028]
Dec 01 13:11:40 fedora abrt-notification[7652]: [🡕] System encountered a non-fatal error in ??()
Dec 01 13:12:07 fedora kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 302s! [msedge:7028]
Dec 01 13:12:08 fedora abrt-notification[7672]: [🡕] System encountered a non-fatal error in ??()
Dec 01 13:12:35 fedora kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 328s! [msedge:7028]
Dec 01 13:12:36 fedora abrt-notification[7692]: [🡕] System encountered a non-fatal error in ??()
-- Boot 64bad4da507e4fd395e8aebf61174788 --

Kernel: 5.14.18-300.fc35.x86_64

My system details:

b6bb351057e6a4f3245057645740eb74853a8fb7.png
b6bb351057e6a4f3245057645740eb74853a8fb7.png604×603 24.1 KB

2

@nilanshu96

Welcome to the community :slight_smile: !

Was that a one time event or is the freezing still appearing?

Do you use a proprietary NVIDIA driver?

I see in the logs that you have a NVIDIA card, which is involved when you use audio with HDMI (line Dec 01 12:58:21).

If you use a proprietary driver, I suggest to deactivate it (I suggest to use nouveau to test whether the driver was the origin of the freeze) and test it some time .

If you find out that it was the NVIDIA driver, you can check whether there is another version of NVIDIA drivers that you can use for your graphics card. Maybe another version will work better. Also, when I had such an issue many years ago, it was sufficient to replace the NVIDIA driver I installed through the repo (I assume it was the rpmfusion repo) with the one provided directly by NVIDIA, even with the same version.

Also, check whether NVIDIA provides suggestions of the settings with which grub deploys the kernel (so the kernel’s grub configuration). This could also make a difference.

Personally, I have not used proprietary drivers for years, so my experiences are not up to date, but maybe proprietary drivers are still today what they were back then :wink:

3

Hi, thanks for answering my query.
This wasn’t a one time event. I do encounter the error you mentioned in every boot. I don’t know if it has anything to do with it. Normally I don’t use the hdmi audio output but I thought of giving it a test and it didn’t go well. Everything else is working fine except this issue. But I believe it is as you said most likely an Nvidia problem. I guess I’ll just have to deal with it for now. The system didn’t create better logs or I would have filed a report with Nvidia as well.

4

Does the problem also occur with Nouveau? Just to isolate the problem clearly (this would also be an important point if you file a report to NVIDIA).

You can still try another NVIDIA driver.

5

I’ll give it a try and see. Right now this issue isn’t a big deal for me. I’ll test your suggestion during the weekend and see how it goes. I use Fedora for work so I don’t want to mess anything for now.

6

To me this does not seem a GPU driver issue, but rather a potential audio driver issue.

What audio drivers/packages are installed?
Is alsa active?

The solution here seems similar to your problem.
https://discussion.fedoraproject.org/t/alsa-error-in-journalctl/67711/16

7

From what I read about alsa-ucm, the error seems to be harmless as it’s only meant for cards with ucm config available. Anyway I’ll try removing it and see if it does anything.