<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - failed to idle channel 0xcccc0001 then crash"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90682#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - failed to idle channel 0xcccc0001 then crash"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90682">bug 90682</a>
from <span class="vcard"><a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> <span class="fn">Ilia Mirkin</span></a>
</span></b>
<pre>I think that some things are being confused here... you mention multi-stream,
presumably in reference to DP-MST, but that doesn't work on nouveau, only intel
and radeon. Are you actually using nouveau for anything? Can you attach an xorg
log and xrandr output, that should make things a bit clearer.
runpm is a very crude form of power management -- it'll turn the GPU off when
the driver decides it hasn't been used for ~5s or so (maybe 10? I forget). It
can do this using ACPI calls. It will then wake the GPU back up when it wants
to use something.
Now you have a Lenovo + GK106 combo, which is well known to have lots of
trouble bringing up acceleration. In fact, your logs show
[ 4.472623] nouveau E[ PGR][0000:01:00.0] grctx template channel unload
timeout
which means that PGRAPH doesn't come up. You could save nouveau some trouble
and just use nouveau.noaccel=1. You should still be able to use reverse-prime
in this case.
Now, none of that has to do with you seeing the crash, just trying to help you
achieve a working system. We shouldn't be crashing even when PGRAPH fails to
come up.
[ 52.772499] nouveau E[ DRM] failed to idle channel 0xcccc0000 [DRM]
[ 52.788584] pci_pm_runtime_suspend(): nouveau_pmops_runtime_suspend+0x0/0xf0
[nouveau] returns -16
OK, so it tries to suspend but it can't shut down the main DRM channel. Because
PGRAPH is dead to begin with. Although it begs the question of why it even
tries to idle the channel, that means there's an active fence on it. I'm
guessing that the remaining messages are due to improper cleanup of a failed
runtime suspend.
If the above is in the vicinity of correct, nouveau.noaccel=1 should "fix" it,
I think.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>