From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753217AbbKZRLv (ORCPT ); Thu, 26 Nov 2015 12:11:51 -0500 Received: from smtp2.it.da.ut.ee ([193.40.5.67]:54665 "EHLO smtp2.it.da.ut.ee" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752246AbbKZRLt (ORCPT ); Thu, 26 Nov 2015 12:11:49 -0500 Date: Thu, 26 Nov 2015 19:10:28 +0200 (EET) From: Meelis Roos To: Linux Kernel list , dri-devel@lists.freedesktop.org, David Airlie , Ben Skeggs Subject: 4.3 nouveau regression: nv04_fbcon_imageblit(?) deadlock Message-ID: 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 Hello, this is a report about a PC with 3 nvidia cards - PCI-E NV44, AGP NV34 and PCI NV05. Only NV44 has monitor attached currently. 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? -- Meelis Roos (mroos@linux.ee)