Hi Andrés,

We need a bit more information and help from you. Could you , please, send us full dmesg log  (not just a fragment) .

It looks like the problem in suspend() function in the driver connected to this particular

model of laptop. Short story is that we have tested this on Vostro 3401, Vostro-3520 and Inspiron-5415

and found no issue with suspend/resume functionality, but all these laptops are Intel's CPU,

and yours is AMD AMD PIC/DALI CPU model, and it looks like this issue is related to the specific

HW setup, in other words how system executes suspend sequence. By looking at the description

it looks like the codec driver incorrectly executes suspend sequence and cannot be waked up on resume because of this.

So, full dmesg log will be helpful.

Thanks,

Vitaly

On 27/11/2023 21:12, Andrés Pedraza wrote:

Hello my dudes.

I've been having this bug for a few months now. Sound on my laptop works just fine until the system suspends or I close the lid. If my headphones are connected when I suspend the system, then there's no sound on headphones or speakers on wake and PulseAudio claims there's never any headphones connected. If my headphones aren't connected on suspend, then speakers work just fine, but headphones are still never detected and make no sound.

Additionally, I recently found out that after waking from suspend, if I run `sudo dmesg | grep snd` I find two timeout warnings that weren't there before, and more showing up as I keep running the command. They go:

...

snd_hda_codec_cs8409 hdaudioC1D0: Timeout waiting for PDN_DONE for CS42L42

I'm on a Dell Vostro 3405 laptop, which I know has a Cirrus sound card. I recently compiled and tested this bug on the Linux 6.6.2 stable kernel. No dice. I attach the outputs of `pactl list sinks`, `sudo dmesg | grep snd` and `sudo lspci -v | grep snd -B 10`. Please do tell if the issue might be caused by some other module or BIOS configuration, or if you need more data.