MIME-Version: 1.0
From: Ian Kumlien <ian.kumlien@gmail.com>
Date: Sat, 29 Nov 2014 01:51:20 +0100
Message-ID: <CAA85sZs6u08DxzV3gF3r-=LvBry0vUFMtfvG1pXRbz1FG6wnag@mail.gmail.com>
Subject: Re: 3.18-rc regression: drm/nouveau: use shared fences for readable objects
To: maarten.lankhorst@canonical.com
Cc: mike@marineau.org, tobias.johannes.klausmann@mni.thm.de,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        dri-devel@lists.freedesktop.org
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org

Hi,

Sorry to but in like this but I'm suffering from the same kind of
deadlocks with nouveau...

The really odd thing is that i could boot some -rc6+ kernel without
problems but it hung
while playing video and then it refused to start properly again.


Anyway, to quote Maarten:
Ok that most likely means the interrupt based wait is borked somehow,
so lets find \
out why..

I fear that this happens because of a race in the interface, so my
first attempt will \
rule out abuse of the nvif api by nouveau_fence.c

Can you test below patch with the default wait function?
---

I tried the patch, straight on Linus' master and it didn't change
anything for me :(
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/