linux-kernel - Re: 4.3 nouveau regression: nv04_fbcon

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAKb7Uvg77PND=Hvxgqgihw7HTDhX1WOoAL8Mpe749+e+-1-ojw@mail.gmail.com>
Date:	Thu, 26 Nov 2015 12:16:45 -0500
From:	Ilia Mirkin <imirkin@...m.mit.edu>
To:	Meelis Roos <mroos@...ux.ee>
Cc:	Linux Kernel list <linux-kernel@...r.kernel.org>,
	"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
	David Airlie <airlied@...ux.ie>,
	Ben Skeggs <bskeggs@...hat.com>
Subject: Re: 4.3 nouveau regression: nv04_fbcon_imageblit(?) deadlock

On Thu, Nov 26, 2015 at 12:10 PM, Meelis Roos <mroos@...ux.ee> wrote:
> 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?

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.

  -ilia
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/