From: "Arnd Bergmann" <arnd@arndb.de>
To: "Satadru Pramanik" <satadru@gmail.com>,
"Arnd Bergmann" <arnd@kernel.org>
Cc: "Dave Airlie" <airlied@gmail.com>,
"Dave Airlie" <airlied@redhat.com>,
"Ben Skeggs" <bskeggs@nvidia.com>,
"bskeggs@redhat.com" <bskeggs@redhat.com>,
"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>,
"open list" <linux-kernel@vger.kernel.org>,
"Lyude Paul" <lyude@redhat.com>,
"nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
"Simona Vetter" <simona@ffwll.ch>,
"Timur Tabi" <ttabi@nvidia.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>
Subject: Re: [PATCH] drm/nouveau: check ioctl command codes better
Date: Mon, 21 Jul 2025 14:37:36 +0200 [thread overview]
Message-ID: <c32114e7-a61a-4c2b-ab4b-b103d028d05f@app.fastmail.com> (raw)
In-Reply-To: <CAFrh3J85tsZRpOHQtKgNHUVnn=EG=QKBnZTRtWS8eWSc1K1xkA@mail.gmail.com>
On Mon, Jul 21, 2025, at 14:22, Satadru Pramanik wrote:
> Hello all,
>
> I suspect this commit in 6.16-rc7 has broken acceleration with Mesa's
> nouveau drivers on my machine.
>
> glxinfo -B reports that I'm using llvmpipe.
Thanks for the report! Can you run the failing command with
'strace -f -o logfile.txt -e trace=ioctl ...' to see which command
it tries?
Either I made a stupid mistake in my patch and don't catch the
intended command any more, or the command that gets sent is actually
different from the one that the kernel expects.
Arnd
next prev parent reply other threads:[~2025-07-21 12:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 12:22 [PATCH] drm/nouveau: check ioctl command codes better Satadru Pramanik
2025-07-21 12:37 ` Arnd Bergmann [this message]
[not found] ` <CAFrh3J-SpU03=Kgi8vj1XLsMfruQyF1Rew6L2+aYUgZnkTLJAw@mail.gmail.com>
2025-07-21 13:50 ` Arnd Bergmann
2025-07-21 15:23 ` Satadru Pramanik
2025-07-22 10:29 ` Chris Bainbridge
2025-07-22 10:52 ` Arnd Bergmann
2025-07-22 11:45 ` Danilo Krummrich
-- strict thread matches above, loose matches on Subject: below --
2025-07-11 7:24 Arnd Bergmann
2025-07-11 17:41 ` Danilo Krummrich
2025-07-11 18:01 ` Arnd Bergmann
2025-07-11 18:06 ` Danilo Krummrich
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=c32114e7-a61a-4c2b-ab4b-b103d028d05f@app.fastmail.com \
--to=arnd@arndb.de \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=arnd@kernel.org \
--cc=bskeggs@nvidia.com \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=nouveau@lists.freedesktop.org \
--cc=satadru@gmail.com \
--cc=simona@ffwll.ch \
--cc=ttabi@nvidia.com \
--cc=tzimmermann@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).