From: a-development@posteo.de
To: Borislav Petkov <bp@alien8.de>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
peterz@infradead.org, David.Kaplan@amd.com,
Andrew.Cooper3@citrix.com, jpoimboe@kernel.org,
gregkh@linuxfoundation.org
Subject: Re: [RFC][PATCH 00/17] Fix up the recent SRSO patches
Date: Wed, 17 Apr 2024 08:08:53 +0000 [thread overview]
Message-ID: <0065fda592b2652d1a2730ddbc81cea6@posteo.net> (raw)
In-Reply-To: <a49e7560f982f00ef1c5452483459b26@posteo.net>
Today I failed to suspend, and the spec_rstack thing was off.
https://up.tail.ws/txt/non-working-suspend-2.txt
On 16.04.2024 22:14, a-development@posteo.de wrote:
> Now that it is deactivated, the machine no longer suspends!
>
> https://up.tail.ws/txt/non-working-suspend.txt
>
>> Then, the other thing you could try is whether suspend works without
>> that proprietary crap.
>
> I refuse. I can explain. I tried lots of capture cards that stated
> they support uvcvideo and linux.
> This problem existed prior and I need it for work on this machine.
> But none of them worked reliably or would straight up glitch out.
> Thats because they do not implement it properly.
>
> It had to be a product from Magewell, who manage an array of bash
> scripts and the AUR maintainer gets updates if something breaks, too.
> Why do I use a PCIe HDMI Capture Card?
> I need to use Cameras and Displays.
>
> As for USB Cameras, unless its a product from e.g Logitech, they kept
> giving me similar headaches.
> And that included an older setup that ran a Intel i7 8700K as well.
>
> Thx.
>
>
>
> On 16.04.2024 10:45, Borislav Petkov wrote:
>> On Tue, Apr 16, 2024 at 06:48:54AM +0000, a-development@posteo.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.
next prev parent reply other threads:[~2024-04-17 8:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-27 18:58 [RFC][PATCH 00/17] Fix up the recent SRSO patches a-development
2024-01-27 19:19 ` Borislav Petkov
2024-01-27 19:27 ` a-development
2024-01-27 19:41 ` Borislav Petkov
2024-01-29 18:18 ` a-development
2024-03-26 22:21 ` Borislav Petkov
2024-04-16 6:48 ` a-development
2024-04-16 8:45 ` Borislav Petkov
2024-04-16 20:14 ` a-development
2024-04-17 8:08 ` a-development [this message]
2024-04-17 9:12 ` Borislav Petkov
2024-04-22 7:01 ` a-development
2024-01-27 19:28 ` a-development
-- strict thread matches above, loose matches on Subject: below --
2023-08-09 7:12 Peter Zijlstra
2023-08-09 9:04 ` Nikolay Borisov
2023-08-09 10:04 ` Andrew.Cooper3
2023-08-09 11:58 ` Peter Zijlstra
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0065fda592b2652d1a2730ddbc81cea6@posteo.net \
--to=a-development@posteo.de \
--cc=Andrew.Cooper3@citrix.com \
--cc=David.Kaplan@amd.com \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=x86@kernel.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox