Displaying 3 results from an estimated 3 matches for "nv50_disp_data_ctor".
2013 Feb 05
0
[PATCH] drm/nouveau: fix lockdep splat in display
...nted
---------------------------------------------
modprobe/585 is trying to acquire lock:
(&subdev->mutex){+.+.+.}, at: [<ffffffffa016c323>]
nouveau_instobj_create_+0x43/0x90 [nouveau]
but task is already holding lock:
(&subdev->mutex){+.+.+.}, at: [<ffffffffa017672d>]
nv50_disp_data_ctor+0x5d/0xd0 [nouveau]
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(&subdev->mutex);
lock(&subdev->mutex);
*** DEADLOCK ***
May be due to missing lock nesting notation
4 locks held by modprobe/585:
#0: (&__lockdep_no_va...
2013 Jan 15
0
nouveau lockdep splat on init
...524 is trying to acquire lock:
[ 40.864179] (&subdev->mutex){+.+.+.}, at: [<ffffffffa0333ba3>] nouveau_instobj_create_+0x43/0x90 [nouveau]
[ 40.864179]
[ 40.864179] but task is already holding lock:
[ 40.864179] (&subdev->mutex){+.+.+.}, at: [<ffffffffa03467f4>] nv50_disp_data_ctor+0x94/0x160 [nouveau]
[ 40.864179]
[ 40.864179] other info that might help us debug this:
[ 40.864179] Possible unsafe locking scenario:
[ 40.864179]
[ 40.864179] CPU0
[ 40.864179] ----
[ 40.864179] lock(&subdev->mutex);
[ 40.864179] lock(&subdev->m...
2013 Feb 03
1
3.8-rc6: nouveau lockdep recursive lock acquisition
...nted
---------------------------------------------
modprobe/585 is trying to acquire lock:
(&subdev->mutex){+.+.+.}, at: [<ffffffffa016c323>]
nouveau_instobj_create_+0x43/0x90 [nouveau]
but task is already holding lock:
(&subdev->mutex){+.+.+.}, at: [<ffffffffa017672d>]
nv50_disp_data_ctor+0x5d/0xd0 [nouveau]
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(&subdev->mutex);
lock(&subdev->mutex);
*** DEADLOCK ***
May be due to missing lock nesting notation
4 locks held by modprobe/585:
#0: (&__lockdep_no_va...