[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240127194139.GFZbVcc2RxhNtO3ZHD@fat_crate.local>
Date: Sat, 27 Jan 2024 20:41:39 +0100
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 Sat, Jan 27, 2024 at 07:27:45PM +0000, a-development@...teo.de wrote:
> I can umount the FUSE mounts and it will work fine.
Aha, so it is FUSE-related.
How do I trigger it here? What are the steps to reproduce? Suspend while
I have a FUSE mount? How do I set it up so that it is as close to yours
as possible?
> 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.
You should try an upstream kernel to confirm it reproduces there - no
distro kernels.
> 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
Not the full .config folder - just the kernel .config of the kernel
you're triggering this with so that I can try to do it here too.
> here is /proc/cpuinfo https://paste.cachyos.org/p/158b767
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists