From: Efraim Flashner <efraim@flashner.co.il>
To: Declan Rixon <declan.fraser.rixon@gmail.com>
Cc: 58316-done@debbugs.gnu.org
Subject: bug#58316: 5.19.12 kernel causes issues with Intel laptops
Date: Thu, 6 Oct 2022 20:00:38 +0300 [thread overview]
Message-ID: <Yz8JtuASHJypH80q@3900XT> (raw)
In-Reply-To: <CACHWwUV4PCanUY3XvtfgQMuT2GE8xTqJuA+8u_-0k_WOOE2UUw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1191 bytes --]
On Wed, Oct 05, 2022 at 01:05:59PM +0000, Declan Rixon wrote:
> Hi all, I ran guix pull and system reconfigure today, updating my kernel to
> 5.19.12. On rebooting I was unable to get much past the bootloader before
> the screen started flashing. Aparrently there's a regression in 5.19.12
> that couses this issue in some intel laptops. Because guix is guix I just
> rolled back for now.
>
> This regression was fixed in the 5.19.13 stable release.
>
> https://www.neowin.net/news/beware-linux-kernel-51912-could-damage-your-intel-laptop-display-literally/
> shows the effect on someone elses laptop (not guix). They say that 5.19.11
> works fine and while I haven't checked that myself, I can say 5.19.9 works
> fine.
Thanks for the report. I was wondering if it was also happening with the
linux-libre kernel. The 5.19 kernel has been updated to 5.19.14, so all
should be good now.
Of course let us know if it comes back with the newer kernel version.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-10-06 17:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 13:05 bug#58316: 5.19.12 kernel causes issues with Intel laptops Declan Rixon
2022-10-06 17:00 ` Efraim Flashner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yz8JtuASHJypH80q@3900XT \
--to=efraim@flashner.co.il \
--cc=58316-done@debbugs.gnu.org \
--cc=declan.fraser.rixon@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).