From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: intel-gfx@lists.freedesktop.org,
Patchwork <patchwork@emeril.freedesktop.org>,
Robert Beckett <bob.beckett@collabora.com>
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915: stop using swiotlb (rev6)
Date: Thu, 28 Jul 2022 15:03:32 +0100 [thread overview]
Message-ID: <23d3fdcb-fa6e-5e77-34fe-940f65530589@linux.intel.com> (raw)
In-Reply-To: <165899531215.21236.2568971216791916773@emeril.freedesktop.org>
On 28/07/2022 09:01, Patchwork wrote:
[snip]
> Possible regressions
>
> * igt@gem_mmap_offset@clear:
> o shard-iclb: PASS
> <https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11946/shard-iclb6/igt@gem_mmap_offset@clear.html>
> -> INCOMPLETE
> <https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_106589v6/shard-iclb1/igt@gem_mmap_offset@clear.html>
What was supposed to be a simple patch.. a storm of errors like:
DMAR: ERROR: DMA PTE for vPFN 0x3d00000 already set (to 2fd7ff003 not 2fd7ff003)
------------[ cut here ]------------
WARNING: CPU: 6 PID: 1254 at drivers/iommu/intel/iommu.c:2278 __domain_mapping.cold.93+0x32/0x39<>
Modules linked in: vgem drm_shmem_helper snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_cod>
CPU: 6 PID: 1254 Comm: gem_mmap_offset Not tainted 5.19.0-rc8-Patchwork_106589v6-g0e9c43d76a14+ #>
Hardware name: Intel Corporation Ice Lake Client Platform/IceLake U DDR4 SODIMM PD RVP TLC, BIOS >
RIP: 0010:__domain_mapping.cold.93+0x32/0x39
Code: fe 48 c7 c7 28 32 37 82 4c 89 5c 24 08 e8 e4 61 fd ff 8b 05 bf 8e c9 00 4c 8b 5c 24 08 85 c>
RSP: 0000:ffffc9000037f9c0 EFLAGS: 00010202
RAX: 0000000000000004 RBX: ffff8881117b4000 RCX: 0000000000000001
RDX: 0000000000000000 RSI: ffffffff82320b25 RDI: 00000000ffffffff
RBP: 0000000000000001 R08: 0000000000000000 R09: c0000000ffff7fff
R10: 0000000000000001 R11: 00000000002fd7ff R12: 00000002fd7ff003
R13: 0000000000076c01 R14: ffff8881039ee800 R15: 0000000003d00000
FS: 00007f2863c1d700(0000) GS:ffff88849fd00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2692c53000 CR3: 000000011c440006 CR4: 0000000000770ee0
PKRU: 55555554
Call Trace:
<TASK>
intel_iommu_map_pages+0xb7/0xe0
__iommu_map+0xe0/0x310
__iommu_map_sg+0xa2/0x140
iommu_dma_map_sg+0x2ef/0x4e0
__dma_map_sg_attrs+0x64/0x70
dma_map_sg_attrs+0x5/0x20
i915_gem_gtt_prepare_pages+0x56/0x70 [i915]
shmem_get_pages+0xe3/0x360 [i915]
____i915_gem_object_get_pages+0x32/0x100 [i915]
__i915_gem_object_get_pages+0x8d/0xa0 [i915]
vm_fault_gtt+0x3d0/0x940 [i915]
? ptlock_alloc+0x15/0x40
? rt_mutex_debug_task_free+0x91/0xa0
__do_fault+0x30/0x180
do_fault+0x1c4/0x4c0
__handle_mm_fault+0x615/0xbe0
handle_mm_fault+0x75/0x1c0
do_user_addr_fault+0x1e7/0x670
exc_page_fault+0x62/0x230
asm_exc_page_fault+0x22/0x30
No idea. Maybe try CI kernel config on your Tigerlake?
Regards,
Tvrtko
next prev parent reply other threads:[~2022-07-28 14:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 15:39 [Intel-gfx] [PATCH v5] drm/i915: stop using swiotlb Robert Beckett
2022-07-26 16:59 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: stop using swiotlb (rev5) Patchwork
2022-07-26 22:19 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-07-27 18:44 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: stop using swiotlb (rev6) Patchwork
2022-07-27 19:04 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-07-28 8:01 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-07-28 14:03 ` Tvrtko Ursulin [this message]
2022-07-28 15:54 ` Robert Beckett
2022-07-28 16:07 ` Tvrtko Ursulin
2022-08-08 15:48 ` [Intel-gfx] [PATCH v5] drm/i915: stop using swiotlb Hellstrom, Thomas
2022-08-09 11:36 ` Tvrtko Ursulin
2022-08-09 18:54 ` hch
2022-08-09 18:51 ` hch
2022-10-06 13:25 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: stop using swiotlb (rev7) Patchwork
2022-10-06 13:49 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
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=23d3fdcb-fa6e-5e77-34fe-940f65530589@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=bob.beckett@collabora.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=patchwork@emeril.freedesktop.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