[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.20.1511271610500.29051@math.ut.ee>
Date: Fri, 27 Nov 2015 16:14:01 +0200 (EET)
From: Meelis Roos <mroos@...ux.ee>
To: Ilia Mirkin <imirkin@...m.mit.edu>
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
> > 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@...ux.ee)
--
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/
Powered by blists - more mailing lists