From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Matt Roper <matthew.d.roper@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: "Vudum, Lakshminarayana" <lakshminarayana.vudum@intel.com>
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Second round of i915_reg.h splitting (rev3)
Date: Fri, 28 Jan 2022 17:07:47 +0100 [thread overview]
Message-ID: <ecd61984-43bf-985f-9a70-1682feda4031@linux.intel.com> (raw)
In-Reply-To: <9fb5d99e-e99d-063f-839b-3253950eec71@linux.intel.com>
Op 28-01-2022 om 16:49 schreef Tvrtko Ursulin:
>
>
> On 28/01/2022 15:21, Matt Roper wrote:
>> On Fri, Jan 28, 2022 at 08:44:17AM +0000, Patchwork wrote:
>>> == Series Details ==
>>>
>>> Series: Second round of i915_reg.h splitting (rev3)
>>> URL : https://patchwork.freedesktop.org/series/99079/
>>> State : failure
>>>
>>> == Summary ==
>>>
>>> CI Bug Log - changes from CI_DRM_11154_full -> Patchwork_22133_full
>>> ====================================================
>>>
>>> Summary
>>> -------
>>>
>>> **FAILURE**
>>>
>>> Serious unknown changes coming with Patchwork_22133_full absolutely need to be
>>> verified manually.
>>> If you think the reported changes have nothing to do with the changes
>>> introduced in Patchwork_22133_full, please notify your bug team to allow them
>>> to document this new failure mode, which will reduce false positives in CI.
>>>
>>>
>>> Participating hosts (10 -> 10)
>>> ------------------------------
>>>
>>> No changes in participating hosts
>>>
>>> Possible new issues
>>> -------------------
>>>
>>> Here are the unknown changes that may have been introduced in Patchwork_22133_full:
>>>
>>> ### IGT changes ###
>>>
>>> #### Possible regressions ####
>>>
>>> * igt@gem_softpin@softpin:
>>> - shard-snb: [PASS][1] -> [INCOMPLETE][2]
>>> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11154/shard-snb5/igt@gem_softpin@softpin.html
>>> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_22133/shard-snb6/igt@gem_softpin@softpin.html
>>
>> It's not really clear what the error was here, but it happened during
>> GTT reservation for an execbuf operation. That doesn't seem like
>> anything that could be related to the register definition shuffling in
>> this series.
>
> Yes, does not look like your problem.
>
> Ungrab_vma() points to Maarten, any idea on this oops?:
>
> <6> [54.564958] [IGT] gem_softpin: starting subtest softpin
> <4> [61.713735] stack segment: 0000 [#1] PREEMPT SMP PTI
> <4> [61.713746] CPU: 0 PID: 1363 Comm: gem_softpin Not tainted 5.17.0-rc1-CI-Patchwork_22133+ #1
> <4> [61.713753] Hardware name: Dell Inc. XPS 8300 /0Y2MRG, BIOS A06 10/17/2011
> <4> [61.713759] RIP: 0010:ungrab_vma+0x9/0x80 [i915]
> <4> [61.713909] Code: ef e8 4b 5c de e0 e8 16 90 e5 e0 8b 83 38 99 00 00 85 c0 75 e1 5b 5d 41 5c 41 5d c3 e9 4c ef 14 00 55 53 48 8b af c0 00 00 00 <8b> 45 00 85 c0 75 03 5b 5d c3 48 8b 85 a0 02 00 00 48 89 fb 48 8b
> <4> [61.713920] RSP: 0018:ffffc90000a8f880 EFLAGS: 00010246
> <4> [61.713926] RAX: 0000000000000000 RBX: ffffc90000a8f598 RCX: 0000000000000000
> <4> [61.713931] RDX: ffff88812ef1b270 RSI: ffff8881053e0880 RDI: ffff88813d6c2d40
> <4> [61.713936] RBP: 6b6b6b6b6b6b6b6b R08: ffff88812ef1b270 R09: ffff88812ef1b2c0
> <4> [61.713940] R10: 0000000000000000 R11: ffff88812ef180b0 R12: ffff88813d6c2d40
> <4> [61.713945] R13: 0000000000000000 R14: ffff88812ef18040 R15: ffff88813d6c3058
> <4> [61.713950] FS: 00007f6158f37c00(0000) GS:ffff888227600000(0000) knlGS:0000000000000000
> <4> [61.713956] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> <4> [61.713961] CR2: 000055de05dcc028 CR3: 000000010eb1a004 CR4: 00000000000606f0
> <4> [61.713966] Call Trace:
> <4> [61.713968] <TASK>
> <4> [61.713971] i915_gem_evict_for_node+0x329/0x3b0 [i915]
> <4> [61.714088] i915_gem_gtt_reserve+0x106/0x130 [i915]
> <4> [61.714202] i915_vma_pin_ww+0x8a6/0xb00 [i915]
> <4> [61.714324] eb_validate_vmas+0x688/0x860 [i915]
> <4> [61.714440] i915_gem_do_execbuffer+0xbfe/0x2530 [i915]
> <4> [61.714549] ? find_held_lock+0x2d/0x90
> <4> [61.714559] ? __lock_acquire+0x5e6/0x2580
> <4> [61.714565] ? coalesce_file_region+0x181/0x230
> <4> [61.714574] i915_gem_execbuffer2_ioctl+0x116/0x2c0 [i915]
> <4> [61.714681] ? i915_gem_do_execbuffer+0x2530/0x2530 [i915]
> <4> [61.714791] drm_ioctl_kernel+0xae/0x140
> <4> [61.714797] drm_ioctl+0x201/0x3d0
> <4> [61.714802] ? i915_gem_do_execbuffer+0x2530/0x2530 [i915]
> <4> [61.714910] __x64_sys_ioctl+0x6d/0xa0
> <4> [61.714916] do_syscall_64+0x3a/0xb0
> <4> [61.714921] entry_SYSCALL_64_after_hwframe+0x44/0xae
>
> Regards,
>
> Tvrtko
This might help:
https://patchwork.freedesktop.org/series/99418/
prev parent reply other threads:[~2022-01-28 16:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 23:43 [Intel-gfx] [CI v3 0/6] Second round of i915_reg.h splitting Matt Roper
2022-01-27 23:43 ` [Intel-gfx] [CI v3 1/6] drm/i915/perf: Move OA regs to their own header Matt Roper
2022-01-27 23:43 ` [Intel-gfx] [CI v3 2/6] drm/i915/perf: Express OA register ranges with i915_range Matt Roper
2022-01-27 23:43 ` [Intel-gfx] [CI v3 3/6] drm/i915: Parameterize R_PWR_CLK_STATE register definition Matt Roper
2022-01-27 23:43 ` [Intel-gfx] [CI v3 4/6] drm/i915: Parameterize MI_PREDICATE registers Matt Roper
2022-01-27 23:43 ` [Intel-gfx] [CI v3 5/6] drm/i915: Move GT registers to their own header file Matt Roper
2022-01-27 23:43 ` [Intel-gfx] [CI v3 6/6] drm/i915: Only include i915_reg.h from .c files Matt Roper
2022-01-28 2:15 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Second round of i915_reg.h splitting (rev3) Patchwork
2022-01-28 2:17 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-01-28 2:44 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-01-28 8:44 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-01-28 15:21 ` Matt Roper
2022-01-28 15:49 ` Tvrtko Ursulin
2022-01-28 16:07 ` Maarten Lankhorst [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=ecd61984-43bf-985f-9a70-1682feda4031@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lakshminarayana.vudum@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=tvrtko.ursulin@linux.intel.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.