From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754821AbbK0OP1 (ORCPT ); Fri, 27 Nov 2015 09:15:27 -0500 Received: from smtp2.it.da.ut.ee ([193.40.5.67]:45136 "EHLO smtp2.it.da.ut.ee" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754785AbbK0OPU (ORCPT ); Fri, 27 Nov 2015 09:15:20 -0500 Date: Fri, 27 Nov 2015 16:14:01 +0200 (EET) From: Meelis Roos To: Ilia Mirkin cc: Linux Kernel list , "dri-devel@lists.freedesktop.org" , David Airlie , Ben Skeggs Subject: Re: 4.3 nouveau regression: nv04_fbcon_imageblit(?) deadlock In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (LRH 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > 4.2.0 (both packaged and self-compiled) worked fine, 4.3.0 and 4.4-rc2 > > exhibit a problem: after the system has started up, I start getting > > messages like INFO: task kworker/0:2:652 blocked for more than 120 > > seconds. where nv04_fbcon_imageblit and nouveau_pmops_runtime_suspend > > show up in trace. The trace keeps reappearing, also breaking lspci and > > clean reboot (they hang). > > > > dmesg from 4.4-rc2, drm-debug=0xe > > http://kodu.ut.ee/~mroos/download/dm-nouveau-4.4-rc2 > > > > dmesg from 4.2.0, drm.debug=0xe > > http://kodu.ut.ee/~mroos/download/dm-nouveau-4.2 > > > > lspci -vvv > > http://kodu.ut.ee/~mroos/download/lspci.nouveau > > > > config: > > http://kodu.ut.ee/~mroos/download/nouveau-config > > > > Is there anything else I can provide? > > Runtime pm shouldn't be a thing for these GPUs... can you see if > booting with nouveau.runpm=0 fixes it? Sounds like we reintroduced > some problem for GPUs that don't have optimus-style acpi power off > hooks. Yes, nouveau.runpm=0 makes the hang go away, and reboot and lspci also started working without hangs. -- Meelis Roos (mroos@linux.ee)