On Sun Feb20'22 07:11:11PM, Branko Grubić wrote: > From: Branko Grubić <[email protected]> > Date: Sun, 20 Feb 2022 19:11:11 +0100 > To: Community support for Fedora users <[email protected]> > Reply-To: Community support for Fedora users <[email protected]> > Subject: Re: audio-related bug(?) on Fedora 35 > > On Sun, 2022-02-20 at 09:49 -0600, Ranjan Maitra wrote: > > Hi, > > > > I have noticed a possible bug over the past ten days that pretty soon > > makes it impossible to do anything related to sound and then > > necessitates a reboot (complete with hard power button press). Here > > is what happened the last time (an hour ago) when I was forced to > > reboot: > > > > I got: > > > > After Stopping session c1 of User "xyz" > > > > (*) A stop job is running on session c1 for user "xyz" > > > > (+) A stop job is running for Manage Sound Card State (restore & > > state) > > > > > > After Stopped Login service, I get > > > > (-) A stop job is running for User Manager for UID yyyy > > > > (+) A stop job is running for Manage Sound Card State (restore & > > state) > > > > After Stopped Authorization Manager, I get > > > > (+) A stop job is running for Manage Sound Card State (restore & > > state) > > > > After about 2 mins, (*) and (-) get done (separately), and after > > about 6 min (+) gets done. > > > > However, I get a message: > > > > Waiting for process: alsactl, wireplumber, chromium-browse (not > > browser), pipewire > > > > and after a while (because I have already wasted close to 30 minutes > > if you add the time it took me to figure out the need to do a > > reboot), I give up and do a hard reboot. > > > > I wonder what the problem is. Note that I did shut down chromium- > > browser and firefox before reboot. I rebooted into the 5.16 kernel > > ten days ago. I am on a Dell XPS13 and do nightly updates. I also > > hibernate every night and usually do not reboot for weeks: I can not > > recall why I decided to reboot 10 days ago, but it must have been > > some oddity. My guess is that I was hibernating and waking for at > > least 20 days before that. > > > > Any suggestions? Let me know what additional information I can > > provide. If it is indeed a bug, what should I file under? > > > > Many thanks and best wishes, > > Ranjan > > _______________________________________________ > > Hi, > > Not sure is it the same bug, but recently I had issues with never > kernel's breaking audio completely, wireplumber gets stuck in > Uninterruptible sleep (D state), no audio at all, only option is to > hard reboot. > > This is one of the bugs, but there are links to pipewire bug, kernel > bug ...[1] > > For me last working kernel in 5.16.x series is kernel-5.16.7- > 200.fc35.x86_64. > > Some people mention suspend2ram/sleep, but for me it is broken from > first boot, sleep is completely broken, since it's not possible to > suspend that wireplumber process. Also other people have issues with > USB audio, but in my case it's integrated audio. > > Not sure if it helps, but possibly related. > > Regards, > Branko > > [1] https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/186
I see, thank you. I think I first booted into 5.16 kernel (and indeed beyond 5.15.9 kernel) about ten days ago so this seems plausible. I have now booted into my oldest kernel (5.16.7) and will let you know if the problem persists. FWIW, I also have that Logitech H390 USB COMPUTER HEADSET plugged in. It often drops in and out in zoom calls, and I have not related it previously, but it is possible that the first time this happens, problems start from there. But hard reboot "solves" the problem. The problem with me is not no sound after suspend, but sound itself starts being unusable after a while (of using sound). Oh, I now recall what the original issue was: hibernate was not working, in the sense that it was coming back on without hibernating. But it is from a week ago and not easily reconstructed now. If I were to: sudo dnf downgrade pipewire as suggested then would that not get upgraded at the next nightly update. Perhaps I do the downgrade after every update. Btw, this one is exactly what is happening: https://ask.fedoraproject.org/t/fedora-35-not-working-well-after-wakeup/20121 but better documented than my post here. Thanks again! Ranjan _______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
