From: Martin Nyhus <martin.nyhus@gmx.com>
To: Ben Skeggs <bskeggs@redhat.com>
Cc: David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: [bisected] nouveau: "Failed to idle channel x" after resume
Date: Mon, 11 Jun 2012 23:18:42 +0200 [thread overview]
Message-ID: <20120611231842.221bd738@europa> (raw)
Hi,
after resuming from suspend nouveau starts writing Failed to idle
channel x (where x is 2 or 3) to the log and X appears to stop and then
restart only to stop again. Starting Firefox after resuming triggers the
bugs every time, and bisecting leads to 03bd6efa ("drm/nv50/fifo: use
hardware channel kickoff functionality").
$ grep -i nouveau .config
CONFIG_DRM_NOUVEAU=y
CONFIG_DRM_NOUVEAU_BACKLIGHT=y
# CONFIG_DRM_NOUVEAU_DEBUG is not set
Relevant part of the log (running v3.5-rc2-15-g4e3c8a1):
[ 79.040710] PM: resume of devices complete after 1952.375 msecs
[ 79.041735] PM: Finishing wakeup.
[ 79.064052] Restarting tasks ... done.
[ 79.064064] video LNXVIDEO:00: Restoring backlight state
[ 79.645442] tg3 0000:09:00.0: irq 47 for MSI/MSI-X
[ 79.707851] IPv6: ADDRCONF(NETDEV_UP): p3p1: link is not ready
[ 81.288510] tg3 0000:09:00.0: p3p1: Link is up at 100 Mbps, full duplex
[ 81.288510] tg3 0000:09:00.0: p3p1: Flow control is on for TX and on for RX
[ 81.289824] IPv6: ADDRCONF(NETDEV_CHANGE): p3p1: link becomes ready
[ 376.646417] [drm] nouveau 0000:01:00.0: PFIFO: channel 4 unload timeout
[ 378.649010] [sched_delayed] sched: RT throttling activated
[ 384.677024] [drm] nouveau 0000:01:00.0: Failed to idle channel 2.
[ 384.678012] [drm] nouveau 0000:01:00.0: PFIFO: channel 2 unload timeout
[ 389.685024] [drm] nouveau 0000:01:00.0: Failed to idle channel 3.
[ 389.686012] [drm] nouveau 0000:01:00.0: PFIFO: channel 3 unload timeout
[ 401.534024] [drm] nouveau 0000:01:00.0: Failed to idle channel 2.
[ 401.535012] [drm] nouveau 0000:01:00.0: PFIFO: channel 2 unload timeout
...
[ 456.688024] [drm] nouveau 0000:01:00.0: Failed to idle channel 3.
[ 456.689013] [drm] nouveau 0000:01:00.0: PFIFO: channel 3 unload timeout
[ 468.372025] [drm] nouveau 0000:01:00.0: Failed to idle channel 2.
[ 468.373013] [drm] nouveau 0000:01:00.0: PFIFO: channel 2 unload timeout
next reply other threads:[~2012-06-11 21:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 21:18 Martin Nyhus [this message]
2012-07-05 20:24 ` [bisected] nouveau: "Failed to idle channel x" after resume Martin Nyhus
2012-07-23 15:25 ` Aioanei Rares
2012-08-04 14:41 ` Maxim Levitsky
2012-08-06 20:38 ` Maxim Levitsky
2012-08-08 5:37 ` Ben Skeggs
2012-08-08 6:00 ` Sven Joachim
2012-08-08 6:08 ` Ben Skeggs
2012-08-08 6:18 ` Sven Joachim
2012-08-13 16:22 ` Sven Joachim
2012-08-13 19:49 ` Maxim Levitsky
2012-08-15 6:53 ` [Nouveau] " Maarten Maathuis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120611231842.221bd738@europa \
--to=martin.nyhus@gmx.com \
--cc=airlied@linux.ie \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox