On Sun Feb20'22 07:11:11PM, Branko Grubić wrote: > From: Branko Grubić <bitlord0xff@xxxxxxxxx> > Date: Sun, 20 Feb 2022 19:11:11 +0100 > To: Community support for Fedora users <users@xxxxxxxxxxxxxxxxxxxxxxx> > Reply-To: Community support for Fedora users <users@xxxxxxxxxxxxxxxxxxxxxxx> > 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 > Actually, another suggestion in one of those links is to take out alsa-utils and that is what i have now done with kernel 5.16.9. I will report if that has any benefit. However, the volume appears lower. Ranjan _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
