[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <181005cf4a78a4c3c5e1de77498f6c23@posteo.net>
Date: Sat, 27 Jan 2024 19:27:45 +0000
From: a-development@...teo.de
To: Borislav Petkov <bp@...en8.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
Oh that was quick :)
I can umount the FUSE mounts and it will work fine.
Previously I didn't even suspend.
Also, in the log I had provided, I was on a cachyos kernel, but it
didn't matter, even the most recent arch kernel had the same issues.
full dmesg is no problem - I can do that the next day, when I startup
the server again
full ~/.config folder I don't want to share
here is /proc/cpuinfo https://paste.cachyos.org/p/158b767
Thanks
On 27.01.2024 20:19, Borislav Petkov wrote:
> On Sat, Jan 27, 2024 at 06:58:37PM +0000, a-development@...teo.de
> wrote:
>> putting srso=off in the cmdline fixed up my FUSE related issues.
>> Basically, I could not suspend anymore.
>> kernel 6.7.1.
>>
>> This is the behavior with srso enabled...
>> https://paste.cachyos.org/p/bae7257
>
> Can you disable, if possible, whatever's doing FUSE and try suspending
> then?
>
> Also, can you share full dmesg, .config and /proc/cpuinfo from the
> machine?
>
> Thx.
Powered by blists - more mailing lists