From: Marcin Slusarz <marcin.slusarz@gmail.com>
To: Valdis.Kletnieks@vt.edu
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Airlie <airlied@linux.ie>, Ben Skeggs <bskeggs@redhat.com>,
Francisco Jerez <currojerez@riseup.net>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
nouveau@lists.freedesktop.org
Subject: Re: mmotm 2010-07-27 - nouveau lockdep issues.
Date: Wed, 28 Jul 2010 08:03:51 +0200 [thread overview]
Message-ID: <20100728060334.GA2756@joi.lan> (raw)
In-Reply-To: <31845.1280295723@localhost>
On Wed, Jul 28, 2010 at 01:42:03AM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Tue, 27 Jul 2010 14:56:50 PDT, akpm@linux-foundation.org said:
> > The mm-of-the-moment snapshot 2010-07-27-14-56 has been uploaded to
> >
> > http://userweb.kernel.org/~akpm/mmotm/
>
> Hit this while the X server was on its way down during a 'shutdown -r now'. Worked fine
> in -rc5-mmotm0719. 'e16' is the Enlightenment window manager, if that matters.
>
> [ 93.181787] [drm:output_poll_execute] *ERROR* delayed enqueue failed 1
> [ 99.802836] [drm] nouveau 0000:01:00.0: Allocating FIFO number 4
> [ 99.808875] [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 4
> [ 103.262226] [drm:output_poll_execute] *ERROR* delayed enqueue failed 1
> [ 113.341948] [drm:output_poll_execute] *ERROR* delayed enqueue failed 1
> [ 123.421836] [drm:output_poll_execute] *ERROR* delayed enqueue failed 1
> [ 123.550520] [drm] nouveau 0000:01:00.0: nouveau_channel_free: freeing fifo 4
> [ 123.551253]
> [ 123.551253] ======================================================
> [ 123.551253] [ INFO: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected ]
> [ 123.551253] 2.6.35-rc6-mmotm0727 #1
> [ 123.551253] ------------------------------------------------------
> [ 123.551253] e16/3822 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:
> [ 123.551253] (&(&mm->unused_lock)->rlock){+.+...}, at: [<ffffffff812a94bc>] drm_mm_put_block+0x10e/0x142
> [ 123.551253]
> [ 123.551253] and this task is already holding:
> [ 123.551253] (&(&dev_priv->context_switch_lock)->rlock){-.....}, at: [<ffffffff812bdbab>] nouveau_channel_free+0x10f/0x233
> [ 123.551253] which would create a new lock dependency:
> [ 123.551253] (&(&dev_priv->context_switch_lock)->rlock){-.....} -> (&(&mm->unused_lock)->rlock){+.+...}
> [ 123.551253]
It's only theoritcal issue. If you want to quiet it down until it will be "fixed" properly, you can
apply patch from http://lists.freedesktop.org/archives/nouveau/2010-July/005994.html
Marcin
next prev parent reply other threads:[~2010-07-28 6:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 21:56 mmotm 2010-07-27-14-56 uploaded akpm
2010-07-28 5:30 ` mmotm 2010-07-27 - WARNING in ec_parse_io_ports() Valdis.Kletnieks
2010-07-28 11:17 ` Thomas Renninger
2010-07-28 5:42 ` mmotm 2010-07-27 - nouveau lockdep issues Valdis.Kletnieks
2010-07-28 6:03 ` Marcin Slusarz [this message]
2010-07-28 15:54 ` mmotm 2010-07-27-14-56 uploaded (staging/iio) Randy Dunlap
2010-07-28 18:32 ` Jonathan Cameron
2010-07-28 22:23 ` mmotm 2010-07-27 - hda-intel audio fails to initialize Valdis.Kletnieks
2010-07-29 5:37 ` Takashi Iwai
2010-07-29 16:05 ` Valdis.Kletnieks
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=20100728060334.GA2756@joi.lan \
--to=marcin.slusarz@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=bskeggs@redhat.com \
--cc=currojerez@riseup.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nouveau@lists.freedesktop.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