Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #80328 > unrolled thread

Bug#1051367: Acknowledgement (regression: powersave screen blank causes system freeze after upgrade to Debian 12)

Started byMarcin Owsiany <marcin@owsiany.pl>
First post2023-09-07 18:30 +0200
Last post2023-10-05 21:20 +0200
Articles 3 — 1 participant

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#1051367: Acknowledgement (regression: powersave screen blank causes system freeze after upgrade to Debian 12) Marcin Owsiany <marcin@owsiany.pl> - 2023-09-07 18:30 +0200
    Bug#1051367: Acknowledgement (regression: powersave screen blank causes system freeze after upgrade to Debian 12) Marcin Owsiany <marcin@owsiany.pl> - 2023-09-07 22:10 +0200
      Bug#1051367: Acknowledgement (regression: powersave screen blank causes system freeze after upgrade to Debian 12) Marcin Owsiany <marcin@owsiany.pl> - 2023-10-05 21:20 +0200

#80328 — Bug#1051367: Acknowledgement (regression: powersave screen blank causes system freeze after upgrade to Debian 12)

FromMarcin Owsiany <marcin@owsiany.pl>
Date2023-09-07 18:30 +0200
SubjectBug#1051367: Acknowledgement (regression: powersave screen blank causes system freeze after upgrade to Debian 12)
Message-ID<Hbq3f-7nAs-1@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Today I switched to an Xorg-based GNOME session, and found out that
invoking `xset dpms force off` also results in the system freezing.
Interestingly, the system was responsive via ssh for another couple seconds
or so.

So I think this regression must be related to the kernel version change
more than anything else. Reassigning the bug.

Again, I'd be more than happy to do whatever is needed to investigate this
deeper. The only idea comes to mind is to try and bisect the kernel history
between 5.10.179-2 and 6.1.38-4, but I'm not sure how feasible it is these
days (it's been almost two decades since I last built my own kernel package
and don't know what config to use between these two versions).

[toc] | [next] | [standalone]


#80333

FromMarcin Owsiany <marcin@owsiany.pl>
Date2023-09-07 22:10 +0200
Message-ID<Hbtu9-7pJl-3@gated-at.bofh.it>
In reply to#80328

[Multipart message — attachments visible in raw view] — view raw

Turns out this issue is already fixed in the 6.4.4-3~bpo12+1 version
available in bookworm-backports \o/

[toc] | [prev] | [next] | [standalone]


#80610

FromMarcin Owsiany <marcin@owsiany.pl>
Date2023-10-05 21:20 +0200
Message-ID<HlC37-dLZl-7@gated-at.bofh.it>
In reply to#80333

[Multipart message — attachments visible in raw view] — view raw

Unfortunately it's not fixed. Looks like the probability of a freeze is
just lower :-(

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web