From: Ted Percival <ted-QSfhGDxlWt8QrrorzV6ljw@public.gmane.org>
To: Maarten Lankhorst
<maarten.lankhorst-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
Cc: "nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>,
Ben Skeggs <bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
"dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: [PATCH] drm/nv84+: fix fence context seqno's
Date: Thu, 25 Sep 2014 16:28:22 -0600 [thread overview]
Message-ID: <54249706.9060803@tedp.id.au> (raw)
In-Reply-To: <542182AD.9020808-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
On 09/23/2014 08:24 AM, Maarten Lankhorst wrote:
> Op 23-09-14 om 07:35 schreef Ben Skeggs:
>>> On 09/22/2014 03:08 AM, Maarten Lankhorst wrote:
>>>> This fixes a regression introduced by "drm/nouveau: rework to new fence interface"
>>>> (commit 29ba89b2371d466).
>>
>> I'm still seeing issues with suspend, even with this patch, and the
>> one you pastebinned recently.
>>
> Annoying, and I'm out of ideas. The pastebinned patch is posted to dri-devel as:
> [PATCH 2/8] drm/nouveau: specify if interruptible wait is desired in nouveau_fence_sync.
>
> Could you bisect to where the suspend issues started? With this patch applied after
> "drm/nouveau: rework to new fence interface", and the other patch applied after
> "drm/nouveau: use shared fences for readable objects"
I started bisecting to track down the suspend issue, but X won't start
at all with today's dri-next tree @ d743ecf36063 ("drm/doc: Fixup
drm_irq kerneldoc includes") plus the two patches, so I'll have to get
that out of the way first.
prev parent reply other threads:[~2014-09-25 22:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 9:08 [PATCH] drm/nv84+: fix fence context seqno's Maarten Lankhorst
[not found] ` <541FE720.50504-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2014-09-22 16:23 ` Ted Percival
[not found] ` <54204CE7.2010502-QSfhGDxlWt8QrrorzV6ljw@public.gmane.org>
2014-09-23 5:35 ` Ben Skeggs
[not found] ` <CACAvsv4gmpN62-FZifbwcFb=dTr7mMtu7K5Ga793i6rUohs=tg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-23 14:24 ` Maarten Lankhorst
[not found] ` <542182AD.9020808-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
2014-09-25 22:28 ` Ted Percival [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=54249706.9060803@tedp.id.au \
--to=ted-qsfhgdxlwt8qrrorzv6ljw@public.gmane.org \
--cc=bskeggs-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=maarten.lankhorst-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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 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.