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 09:40:22 -0500 [thread overview]
Message-ID: <d994dd8855c3977190b23acbe643c536deb3af71.camel@gmail.com> (raw)
In-Reply-To: <20250917013352.722151-1-kuniyu@google.com>
> Could you test it with this diff and see if 2 or 3 splats are logged
> in dmesg ? and in that case, please share the stack traces.
>
> I expect this won't trigger the black screen and you can check dmesg
> after resume.
>
> Thanks!
>
>
Good morning/afternoon. Applied this patch to the latest mainline, but
still see the black screen upon trying to resume after suspend. The
keyboard looks to be unresponsive, as trying to switch to a tty
terminal or back doesn't result in anything happening(as well as
numlock/caps not being responsive either). I also tried using the power
button, as well as closing/reopening the laptop lid to see if I could
trigger resume.
Checked the systemd journal just in case, but no splats or anything
else is recorded after the suspend. Finally, attempted following dmesg
with -Wh to a text file before suspending, but that also doesn't record
any new input after the suspend.
next prev parent reply other threads:[~2025-09-17 14:40 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 [this message]
2025-09-17 18:42 ` Kuniyuki Iwashima
2025-09-17 20:25 ` brian.scott.sampson
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=d994dd8855c3977190b23acbe643c536deb3af71.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