All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Hans de Goede <hdegoede@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>, Ben Skeggs <bskeggs@redhat.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: 4.9-rc1 lockdep warning suggesting a deadlock between nouveau and i915 with prime video outputs active
Date: Thu, 13 Jul 2017 15:57:31 +0200	[thread overview]
Message-ID: <2007195d-6663-867a-ecc3-03d2d348fb72@gmail.com> (raw)
In-Reply-To: <20161109172600.GB9300@nuc-i3427.alporthouse.com>

Stealing this thread as an opensuse user hit that too:
https://bugzilla.suse.com/show_bug.cgi?id=1045105

On 11/09/2016, 06:26 PM, Chris Wilson wrote:
> On Wed, Nov 09, 2016 at 06:02:40PM +0100, Hans de Goede wrote:
>> Hi,
>>
>> I noticed this while testing the displayport output attached
>> to the nvidia GPU on a Thinkpad P50 while the intel GPU
>> was driving the LCD panel (and was the primary GPU according
>> to Xorg). This was while logging into gnome-3 with Xorg-1.19-rc2,
>> from gdm (also running on top of Xorg-1.19-rc2).
> 
> Worth trying
> 
> 
> 
> to test for a false positive first.

Hmm, not that easy:
[  +0.011001] BUG: key ffff8807573ed758 not in .data!
[  +0.000103] DEBUG_LOCKS_WARN_ON(1)
[  +0.000012] ------------[ cut here ]------------
[  +0.000147] WARNING: CPU: 1 PID: 282 at
../kernel/locking/lockdep.c:3156 lockdep_init_map+0x4db/0x5e0

Any other idea :)?

> -Chris
> 
> diff --git a/drivers/gpu/drm/drm_drv.c b/drivers/gpu/drm/drm_drv.c
> index 6efdba4993fc..3e4dc782812d 100644
> --- a/drivers/gpu/drm/drm_drv.c
> +++ b/drivers/gpu/drm/drm_drv.c
> @@ -505,7 +505,9 @@ int drm_dev_init(struct drm_device *dev,
>  
>         spin_lock_init(&dev->buf_lock);
>         spin_lock_init(&dev->event_lock);
> -       mutex_init(&dev->struct_mutex);
> +       __mutex_init(&dev->struct_mutex,
> +                    "struct_mutex",
> +                    &dev->struct_mutex_class);
>         mutex_init(&dev->filelist_mutex);
>         mutex_init(&dev->ctxlist_mutex);
>         mutex_init(&dev->master_mutex);
> diff --git a/include/drm/drmP.h b/include/drm/drmP.h
> index ae49c3174d24..ed2e53534c2e 100644
> --- a/include/drm/drmP.h
> +++ b/include/drm/drmP.h
> @@ -808,6 +808,7 @@ struct drm_device {
>  
>         /** \name Locks */
>         /*@{ */
> +       struct lock_class_key struct_mutex_class;
>         struct mutex struct_mutex;      /**< For others */
>         struct mutex master_mutex;      /**< For drm_minor::master and drm_file::is_master */
>         /*@} */
> 


-- 
js
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-07-13 13:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-09 17:02 4.9-rc1 lockdep warning suggesting a deadlock between nouveau and i915 with prime video outputs active Hans de Goede
2016-11-09 17:26 ` Chris Wilson
2016-11-09 18:36   ` Hans de Goede
2017-07-13 13:57   ` Jiri Slaby [this message]
2017-07-13 14:01     ` Peter Zijlstra
2017-07-13 14:04     ` Chris Wilson
2017-07-13 18:59       ` Daniel Vetter

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=2007195d-6663-867a-ecc3-03d2d348fb72@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=bskeggs@redhat.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hdegoede@redhat.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.