From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Matthew Auld <matthew.william.auld@gmail.com>,
Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/ttm: replace busy placement with flags
Date: Thu, 12 Jan 2023 17:07:12 +0100 [thread overview]
Message-ID: <c5630980-283c-a1af-ecde-57433cb86a9d@gmail.com> (raw)
In-Reply-To: <CAM0jSHOEXiQj-9160deCA-AxDjbUUrwYDUit9=yzPCcdLp_Wwg@mail.gmail.com>
Am 11.01.23 um 16:18 schrieb Matthew Auld:
> [SNIP]
>> Currently "dim rebuild-tip" doesn't work for me because of a conflict in
>> i915_gem_execbuffer.c
> Seems to be working now.
Nope. When I do a fresh install with "drm setup" in a different working
directly I run into exactly this problem again.
On a different system "drm rebuild-tip" runs perfectly fine, so my
educated guess is that some conflict resolution isn't applied on some
systems.
I've seen this phenomena couple of times with drm-tip now, but can't
really make sense what's going wrong here. Daniel any idea?
Christian.
>
>> Any idea how to fix this?
>>
>> Thanks,
>> Christian.
>>
>>
>>> [1] https://patchwork.freedesktop.org/project/intel-gfx-trybot/series/?ordering=-last_updated
next prev parent reply other threads:[~2023-01-12 16:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 11:42 [PATCH 1/2] drm/ttm: prevent moving of pinned BOs Christian König
2023-01-11 11:42 ` [PATCH 2/2] drm/ttm: replace busy placement with flags Christian König
2023-01-11 13:03 ` [Intel-gfx] " Matthew Auld
2023-01-11 14:43 ` Christian König
2023-01-11 15:18 ` Matthew Auld
2023-01-12 16:07 ` Christian König [this message]
2023-01-24 9:55 ` Christian König
2023-01-11 13:17 ` [Intel-gfx] [PATCH 1/2] drm/ttm: prevent moving of pinned BOs Matthew Auld
2023-01-24 9:51 ` Christian König
2023-01-24 10:12 ` Matthew Auld
2023-01-24 10:15 ` Christian König
2023-01-11 14:09 ` kernel test robot
2023-01-15 16:14 ` kernel test robot
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=c5630980-283c-a1af-ecde-57433cb86a9d@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox