[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180212033947.GA19049@wunner.de>
Date: Mon, 12 Feb 2018 04:39:47 +0100
From: Lukas Wunner <lukas@...ner.de>
To: Mike Lothian <mike@...eburn.co.uk>
Cc: Tejun Heo <tj@...nel.org>, Lai Jiangshan <jiangshanlai@...il.com>,
Alex Deucher <alexander.deucher@....com>,
Dave Airlie <airlied@...hat.com>,
Ben Skeggs <bskeggs@...hat.com>,
Ismo Toijala <ismo.toijala@...il.com>,
nouveau@...ts.freedesktop.org,
Intel Graphics Development <intel-gfx@...ts.freedesktop.org>,
Liviu Dudau <Liviu.Dudau@....com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Maling list - DRI developers
<dri-devel@...ts.freedesktop.org>,
Hans de Goede <hdegoede@...hat.com>,
Peter Wu <peter@...ensteyn.nl>
Subject: Re: [PATCH 0/5] Fix deadlock on runtime suspend in DRM drivers
On Mon, Feb 12, 2018 at 12:35:51AM +0000, Mike Lothian wrote:
> I've not been able to reproduce the original problem you're trying to
> solve on amdgpu thats with or without your patch set and the above
> "trigger" too
>
> Is anything else required to trigger it, I started multiple DRI_PRIME
> glxgears, in parallel, serial waiting the 12 seconds and serial within
> the 12 seconds and I couldn't reproduce it
The discrete GPU needs to runtime suspend, that's the trigger,
so no DRI_PRIME executables should be running. Just let it
autosuspend after boot. Do you see "waiting 12 sec" messages
in dmesg? If not it's not autosuspending.
Thanks,
Lukas
Powered by blists - more mailing lists