[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240416084544.GAZh46uKW6ijAfftmI@fat_crate.local>
Date: Tue, 16 Apr 2024 10:45:44 +0200
From: Borislav Petkov <bp@...en8.de>
To: a-development@...teo.de
Cc: x86@...nel.org, linux-kernel@...r.kernel.org, peterz@...radead.org,
David.Kaplan@....com, Andrew.Cooper3@...rix.com,
jpoimboe@...nel.org, gregkh@...uxfoundation.org
Subject: Re: [RFC][PATCH 00/17] Fix up the recent SRSO patches
On Tue, Apr 16, 2024 at 06:48:54AM +0000, a-development@...teo.de wrote:
> It worked, it worked!
>
> https://up.tail.ws/txt/working-suspend.txt
>
> I've tested it now quite some time.
> But, I also had to start using 6.6.26-1-lts because my magewell capture card
> wouldn't without.
Right, that thing I guess:
[Mon Apr 15 18:37:58 2024] ProCapture: loading out-of-tree module taints kernel.
[Mon Apr 15 18:37:58 2024] ProCapture: module verification failed: signature and/or required key missing - tainting kernel
So, machines do suspend even with SRSO enabled and since your machine is
affected, you probably should try without spec_rstack_overflow=off to
see if it works with the new kernel.
Then, the other thing you could try is whether suspend works without
that proprietary crap.
And then we can see.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists