From: Brian Norris <briannorris@chromium.org>
To: Matthew Auld <matthew.william.auld@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Set PROBE_PREFER_ASYNCHRONOUS
Date: Fri, 4 Nov 2022 18:29:29 -0700 [thread overview]
Message-ID: <Y2W8eYOgcPhXW6jP@google.com> (raw)
In-Reply-To: <CAM0jSHPe6Ecyh4X4ki=xcnT24REvAPoUqwH5Kkm6rEKYCCr4kQ@mail.gmail.com>
On Fri, Nov 04, 2022 at 02:38:03PM +0000, Matthew Auld wrote:
> On Thu, 3 Nov 2022 at 00:14, Brian Norris <briannorris@chromium.org> wrote:
> > I'm still curious about the reported failures, but maybe they require
> > some particular sequence of tests? I also don't have the full
> > igt-gpu-tools set running, so maybe they do something a little
> > differently than my steps in [1]?
> >
> > Brian
> >
> > [1] I have a GLk system, if it matters. I figured I can run some of
> > these with any one of the following:
> >
> > modprobe i915 live_selftests=1
> > modprobe i915 live_selftests=1 igt__20__live_workarounds=Y
> > modprobe i915 live_selftests=1 igt__19__live_uncore=Y
> > modprobe i915 live_selftests=1 igt__18__live_sanitycheck=Y
> > ...
>
> CI should be using the IGT wrapper to run them, AFAIK. So something like:
>
> ./build/tests/i915_selftest
>
> Or to just run the live, mock or perf:
>
> ./build/tests/i915_selftest --run-subtest live
> ./build/tests/i915_selftest --run-subtest mock
> ./build/tests/i915_selftest --run-subtest perf
>
> Or if you want to run some particular selftest, like live mman tests:
>
> ./build/tests/i915_selftest --run-subtest live --dyn mman
Thanks. I'm running through those now, and it seems like I'm doing
closer to what the CI logs show [1], but I'm still not reproducing on my
GLK. (I've now managed to run it with drm-tip; still no luck.)
So far, now I've managed to just reproduced *different* known problems:
https://lore.kernel.org/all/Y2WfpLbX1SeDtk+7@google.com/
But after working around those, I run without any similar lockup
failures.
I might poke around some more next week, but I've probably spent more
time than reasonable on this already.
Anyway, thanks for the help!
Regards,
Brian
[1] For one, I've run through a test list, in order, based on this:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_110277v1/fi-glk-j4005/testlist0.txt
next prev parent reply other threads:[~2022-11-05 1:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 21:53 [Intel-gfx] [PATCH] drm/i915: Set PROBE_PREFER_ASYNCHRONOUS Brian Norris
2022-10-28 21:53 ` Brian Norris
2022-10-28 21:53 ` Brian Norris
2022-10-29 0:24 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2022-11-01 21:58 ` Brian Norris
2022-11-02 12:18 ` Matthew Auld
2022-11-03 0:14 ` Brian Norris
2022-11-04 14:38 ` Matthew Auld
2022-11-05 1:29 ` Brian Norris [this message]
2022-11-04 15:20 ` Matthew Auld
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=Y2W8eYOgcPhXW6jP@google.com \
--to=briannorris@chromium.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.william.auld@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.