From: brian.scott.sampson@gmail.com
To: Kuniyuki Iwashima <kuniyu@google.com>
Cc: christian@heusel.eu, davem@davemloft.net,
difrost.kernel@gmail.com, dnaim@cachyos.org,
edumazet@google.com, horms@kernel.org, kuba@kernel.org,
kuni1840@gmail.com, linux-kernel@vger.kernel.org,
mario.limonciello@amd.com, netdev@vger.kernel.org,
pabeni@redhat.com, regressions@lists.linux.dev
Subject: Re: [REGRESSION] af_unix: Introduce SO_PASSRIGHTS - break OpenGL
Date: Wed, 17 Sep 2025 15:25:07 -0500 [thread overview]
Message-ID: <caa08e5b15bc35b9f3c24f679c62ded1e8e58925.camel@gmail.com> (raw)
In-Reply-To: <20250917184307.999737-1-kuniyu@google.com>
> Thanks for testing the painful scenario.
>
> Could you apply this on top of the previous diff and give it
> another shot ?
>
> I think the application hit a race similar to one in 43fb2b30eea7.
Just tested again with latest mainline, but no change. Once suspended,
keyboard becomes inactive and no longer accepts any input, so no way to
switch to tty to view dmesg. The only way to move forward after
suspending is holding down power to hard shutdown, then power back on.
I tried enabling persistence in the systemd journal, then checking
journalctl -k -b -1, but nothing is recorded from dmesg after the
suspend.
--
Brian Sampson <brian.scott.sampson@gmail.com>
next prev parent reply other threads:[~2025-09-17 20:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 19:22 [REGRESSION] af_unix: Introduce SO_PASSRIGHTS - break OpenGL Jacek Łuczak
2025-06-11 11:46 ` Christian Heusel
2025-06-11 16:42 ` Kuniyuki Iwashima
2025-06-11 17:10 ` Christian Heusel
2025-06-11 19:24 ` André Almeida
2025-06-18 7:30 ` Matthew Schwartz
2025-09-16 22:16 ` brian.scott.sampson
2025-09-17 1:33 ` Kuniyuki Iwashima
2025-09-17 14:40 ` brian.scott.sampson
2025-09-17 18:42 ` Kuniyuki Iwashima
2025-09-17 20:25 ` brian.scott.sampson [this message]
2025-09-20 3:50 ` Kuniyuki Iwashima
2025-09-20 22:28 ` brian.scott.sampson
2025-11-09 16:07 ` brian.scott.sampson
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=caa08e5b15bc35b9f3c24f679c62ded1e8e58925.camel@gmail.com \
--to=brian.scott.sampson@gmail.com \
--cc=christian@heusel.eu \
--cc=davem@davemloft.net \
--cc=difrost.kernel@gmail.com \
--cc=dnaim@cachyos.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=regressions@lists.linux.dev \
/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