From: Balbir Singh <balbirs@nvidia.com>
To: Bert Karwatzki <spasswolf@web.de>
Cc: Ingo Molnar <mingo@kernel.org>, Kees Cook <kees@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Andy Lutomirski <luto@kernel.org>,
linux-kernel@vger.kernel.org, amd-gfx@lists.freedesktop.org
Subject: Re: commit 7ffb791423c7 breaks steam game
Date: Fri, 14 Mar 2025 17:14:00 +1100 [thread overview]
Message-ID: <7866593f-0322-4fb3-9729-82366940fc85@nvidia.com> (raw)
In-Reply-To: <fa8d5e76694918bdaae9faee9648776f298f78ca.camel@web.de>
On 3/14/25 09:22, Bert Karwatzki wrote:
> Am Freitag, dem 14.03.2025 um 08:54 +1100 schrieb Balbir Singh:
>> On 3/14/25 05:12, Bert Karwatzki wrote:
>>> Am Donnerstag, dem 13.03.2025 um 22:47 +1100 schrieb Balbir Singh:
>>>>
>>>>
>>>> Anyway, I think the nokaslr result is interesting, it seems like with nokaslr
>>>> even the older kernels have problems with the game
>>>>
>>>> Could you confirm if with nokaslr
>>>>
>>> Now I've tested kernel 6.8.12 with nokaslr
>>>
>>>> 1. Only one single game stellaris is not working?
>>>> 2. The entire laptop does not work?
>>>> 3. Laptop works and other games work? Just one game is not working as
>>> expected?
>>>
>>>
>>> Stellaris is showing the input lag and the entire graphical user interface shows
>>> the same input lag as long as stellaris is running.
>>> Civilization 6 shows the same input lag as stellaris, probably even worse.
>>> Magic the Gathering: Arena (with wine) works normally.
>>> Valheim also works normally.
>>> Crusader Kings 2 works normally
>>> Rogue Heroes: Ruins of Tasos (a Zelda lookalike) works normally.
>>> Baldur's Gate I & II and Icewind Dale work normally.
>>>
>>> Also the input lag is only in the GUI, if I switch to a text console (ctrl + alt
>>> + Fn), input works normally even while the affected games are running.
>>>
>>> Games aside everything else (e.g. compiling kernels) seems to work with nokaslr.
>>>
>>
>> Would it be fair to assume that anything Xorg/Wayland is working fine
>> when the game is not running, even with nokaslr?
>>
> Yes, Xorg (I'm normally using xfce4 as desktop) works fine. I also tested with
> gnome using Xwayland, here the buggy behaviour also exists, with the addtion
> that mouse position is off, i.e. to click a button in the game you have to click
> somewhat above it.
So the issue is narrowed down to just the games you've mentioned with nokaslr/patch?
>
>> +amd-gfx@lists.freedesktop.org to see if there are known issues with
>> nokaslr and the games you mentioned.
>>
>>
>> Balbir Singh
>>
>> PS: I came across an interesting link
>> https://www.alex-ionescu.com/behind-windows-x64s-44-bit-memory-addressing-limit/
>>
>> I think SLIST_HEADER is used by wine as well for user space and I am not sure
>> if in this situation the game is hitting this scenario, but surprisingly the other
>> games are not. This is assuming the game uses wine. I am not sure it's related,
>> but the 44 bits caught my attention.
>
> Stellaris is a native linux game (x86_64), the one game (MTGA) I tested with
> wine worked fine.
>
Thanks for the update! I wonder if there are any game logs. If you can look for any
warnings/errors it might be interesting to see where the difference is coming from?
> By the way, the warning
> [ T8562] WARNING: CPU: 14 PID: 8562 at mm/slub.c:5028
> __kvmalloc_node_noprof+0x2fd/0x360
> that appeared in the dmesg I sent you is caused by the upgrade of mesa from
> 25.0.0 to 25.0.1. (I'm still bisecting ...)
>
Thanks!
Balbir
next prev parent reply other threads:[~2025-03-14 6:14 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 11:22 Bert Karwatzki
2025-03-10 21:48 ` Balbir Singh
2025-03-11 7:19 ` Balbir Singh
2025-03-11 7:28 ` Ingo Molnar
2025-03-11 11:15 ` Bert Karwatzki
2025-03-11 18:24 ` Bert Karwatzki
2025-03-11 22:10 ` Balbir Singh
2025-03-11 23:09 ` Bert Karwatzki
2025-03-12 0:26 ` Bert Karwatzki
2025-03-12 2:23 ` Balbir Singh
2025-03-12 1:24 ` Balbir Singh
2025-03-13 9:22 ` Bert Karwatzki
2025-03-13 10:40 ` Balbir Singh
2025-03-13 10:53 ` Bert Karwatzki
2025-03-13 11:47 ` Balbir Singh
2025-03-13 18:12 ` Bert Karwatzki
2025-03-13 21:54 ` Balbir Singh
2025-03-13 22:22 ` Bert Karwatzki
2025-03-14 6:14 ` Balbir Singh [this message]
2025-03-14 13:34 ` Balbir Singh
2025-03-14 14:18 ` Bert Karwatzki
2025-03-15 0:16 ` Balbir Singh
2025-03-15 17:40 ` Alex Deucher
2025-03-16 13:09 ` Bert Karwatzki
2025-03-16 20:06 ` Bert Karwatzki
2025-03-17 9:13 ` Balbir Singh
2025-03-20 9:01 ` Ingo Molnar
2025-03-20 23:55 ` Balbir Singh
2025-03-21 10:24 ` Ingo Molnar
2025-03-21 11:05 ` Balbir Singh
2025-03-22 8:04 ` Ingo Molnar
2025-03-22 9:40 ` Balbir Singh
2025-03-20 23:43 ` Bert Karwatzki
2025-03-21 4:55 ` Balbir Singh
2025-03-21 12:26 ` Bert Karwatzki
2025-03-22 2:06 ` Balbir Singh
2025-03-22 12:23 Bert Karwatzki
2025-03-23 6:51 ` Balbir Singh
2025-03-24 11:23 ` Bert Karwatzki
2025-03-24 12:14 ` Christian König
2025-03-24 22:48 ` Balbir Singh
[not found] ` <938c2cbd-c47f-4925-ba82-94eef54d9ebc@amd.com>
2025-03-25 22:45 ` Balbir Singh
2025-03-25 23:21 ` Bert Karwatzki
2025-03-25 23:43 ` Balbir Singh
2025-03-26 1:50 ` Balbir Singh
2025-03-26 10:10 ` Bert Karwatzki
2025-03-26 10:36 ` Balbir Singh
2025-03-26 11:14 ` Bert Karwatzki
2025-03-27 10:53 ` Ingo Molnar
2025-03-27 22:03 ` Balbir Singh
2025-03-24 21:43 ` Balbir Singh
2025-03-24 23:07 Bert Karwatzki
[not found] ` <634e77d7-4f3c-4d1a-8aa3-1978896f9bf2@amd.com>
2025-03-25 10:25 ` Balbir Singh
2025-03-25 10:14 Bert Karwatzki
2025-03-25 12:23 ` Christian König
2025-03-26 22:00 ` Bert Karwatzki
2025-03-26 22:58 ` Linus Torvalds
2025-03-27 0:57 ` Balbir Singh
2025-03-27 0:58 ` Bert Karwatzki
2025-03-27 10:40 ` Ingo Molnar
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=7866593f-0322-4fb3-9729-82366940fc85@nvidia.com \
--to=balbirs@nvidia.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bhelgaas@google.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=spasswolf@web.de \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®