[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1112643: AW: Bug#1112643: linux-image-6.12.41+deb13-amd64: Older Acer Notebooks do not wake up from suspend afer upgrade to Trixie or new install of Trixie



Title: AW: Bug#1112643: linux-image-6.12.41+deb13-amd64: Older Acer Notebooks do not wake up from suspend afer upgrade to Trixie or new install of Trixie

Dear Salvatore,


Thank you very much for providing the very useful workaround!! Without your reply, I would never have found this.


Regards,


Michael


-----Ursprüngliche Nachricht-----
Von: Salvatore Bonaccorso <carnil@debian.org>
Gesendet: Donnerstag 25 September 2025 10:59
An: Prof. Dr. Michael Schefczyk <michael@schefczyk.net>; 1112643@bugs.debian.org
Betreff: Re: Bug#1112643: linux-image-6.12.41+deb13-amd64: Older Acer Notebooks do not wake up from suspend afer upgrade to Trixie or new install of Trixie

Control: forcemerge 1106411 1112643

Hi,

On Sun, Aug 31, 2025 at 03:46:44PM +0200, Michael Schefczyk wrote:
> Package: src:linux
> Version: 6.12.41-1
> Severity: important
> X-Debbugs-Cc: michael@schefczyk.net
>
> Dear Maintainer,
>
> * What led up to the situation?
>
> Either upgrading to Trixe from Oldstable or installing fresh on older Acer
> Notebooks, such as Spin SP111-34N. Either closing the lid or running systemctl
> suspend leads to a black screen from which the Notebook will never wake up
> again (unlike with Bookworm) - no response to keys, network or USB. Finding
> from Bug 1100153 (echo 0 > /sys/power/pm_async) does not resolve this.
>
>
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
>
> As above: Upgrade to Trixie or install it fresh, close lid or run systemctl
> suspend. Afterwards, power LED does stay blue, but one can only restart after
> long pressing the power button.
>
> * What was the outcome of this action?
>
> System needs to be rebooted.
>
> * What outcome did you expect instead?
>
> System will wake up from suspend as it dit with Bookworm.

I believe this has the same root cause as #1106411.

As workaround you can mask the iio-sensor-proxy service.

Regards,
Salvatore

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature


Reply to: