From: Tommi Rantala <tt.rantala@gmail.com>
To: Ilia Mirkin <imirkin@alum.mit.edu>
Cc: "nouveau@lists.freedesktop.org" <nouveau@lists.freedesktop.org>,
trinity@vger.kernel.org, Ben Skeggs <bskeggs@redhat.com>,
DRI Development <dri-devel@lists.freedesktop.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: nouveau: iowrite32 oops & warning at drivers/gpu/drm/nouveau/nouveau_fence.c:198
Date: Mon, 23 Nov 2015 22:17:39 +0200 [thread overview]
Message-ID: <CA+ydwtr670rK5kAAFkJ=BEMXAMWLHwim3754rVvqZaCdhh+4-Q@mail.gmail.com> (raw)
In-Reply-To: <CAKb7Uvh+sGQJgEYb3SzVDH-YytX7WsU=EQnUEeZeWR-haHGdfA@mail.gmail.com>
2015-11-22 22:49 GMT+02:00 Ilia Mirkin <imirkin@alum.mit.edu>:
> Not sure if these apply here but there are a couple of outstanding
> locking fixes available in
> http://cgit.freedesktop.org/~darktama/nouveau/ -- specifically these
> two:
>
> http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=2f3a56ad019e378a352e9cb7a559f478826f1a87
> http://cgit.freedesktop.org/~darktama/nouveau/commit/?id=4179b15c6e9fcfb253e811e5477debe46c84c395
>
> Not sure if they affect this particular issue, but thought I'd point
> it out. Are you fuzzing with multiple threads, or just one at a time?
> Do you have a branch somewhere public with the changes to add nouveau
> ioctl support to trinity?
Hi!
I applied those two on top of v4.4-rc2, but the same warning and oops
are still easily reproducible. I can test with older kernels and/or
try to bisect when I have more time, unless anyone has better ideas.
I'm actually running unmodified trinity, and for this purpose only
fuzzing the ioctl() syscall from multiple processes, and opening only
the files from /dev/dri/:
$ ./trinity -q -loff -C20 -c ioctl -V /dev/dri/
Trinity knows about a bunch of DRM ioctl commands, but the rest of the
ioctl arguments will be garbage:
https://github.com/kernelslacker/trinity/blob/master/ioctls/drm.c
Tommi
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2015-11-23 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-22 20:30 nouveau: iowrite32 oops & warning at drivers/gpu/drm/nouveau/nouveau_fence.c:198 Tommi Rantala
2015-11-22 20:49 ` Ilia Mirkin
2015-11-23 20:17 ` Tommi Rantala [this message]
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='CA+ydwtr670rK5kAAFkJ=BEMXAMWLHwim3754rVvqZaCdhh+4-Q@mail.gmail.com' \
--to=tt.rantala@gmail.com \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=imirkin@alum.mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=trinity@vger.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).