search for: __lockdep_no_validate__

Displaying 5 results from an estimated 5 matches for "__lockdep_no_validate__".

2013 Mar 05
3
nouveau lockdep splat
...k); > [ 0.633628] lock(&dmac->lock); > [ 0.633628] > [ 0.633628] *** DEADLOCK *** > [ 0.633628] > [ 0.633628] May be due to missing lock nesting notation > [ 0.633628] > [ 0.633629] 10 locks held by swapper/0/1: > [ 0.633632] #0: (&__lockdep_no_validate__){......}, at: [<ffffffff8143375b>] __driver_attach+0x5b/0xb0 > [ 0.633633] #1: (&__lockdep_no_validate__){......}, at: [<ffffffff81433769>] __driver_attach+0x69/0xb0 > [ 0.633636] #2: (drm_global_mutex){+.+.+.}, at: [<ffffffff8135a8f6>] drm_get_pci_dev+0xc6/0x2...
2013 Jan 15
0
nouveau lockdep splat on init
...0.864179] lock(&subdev->mutex); [ 40.864179] lock(&subdev->mutex); [ 40.864179] [ 40.864179] *** DEADLOCK *** [ 40.864179] [ 40.864179] May be due to missing lock nesting notation [ 40.864179] [ 40.864179] 4 locks held by modprobe/524: [ 40.864179] #0: (&__lockdep_no_validate__){......}, at: [<ffffffff81410ea3>] __driver_attach+0x53/0xb0 [ 40.864179] #1: (&__lockdep_no_validate__){......}, at: [<ffffffff81410eb1>] __driver_attach+0x61/0xb0 [ 40.864179] #2: (drm_global_mutex){+.+.+.}, at: [<ffffffffa0094437>] drm_get_pci_dev+0xb7/0x2a0 [drm] [...
2013 Feb 05
0
[PATCH] drm/nouveau: fix lockdep splat in display
..._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_validate__){......}, at: [<ffffffff813075f3>] __driver_attach+0x53/0xb0 #1: (&__lockdep_no_validate__){......}, at: [<ffffffff81307601>] __driver_attach+0x61/0xb0 #2: (drm_global_mutex){+.+.+.}, at: [<ffffffff812ee59c>] drm_get_pci_dev+0xbc/0x2b0 #3: (&subdev->mutex){+.+.+.}, a...
2013 Feb 03
1
3.8-rc6: nouveau lockdep recursive lock acquisition
..._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_validate__){......}, at: [<ffffffff813075f3>] __driver_attach+0x53/0xb0 #1: (&__lockdep_no_validate__){......}, at: [<ffffffff81307601>] __driver_attach+0x61/0xb0 #2: (drm_global_mutex){+.+.+.}, at: [<ffffffff812ee59c>] drm_get_pci_dev+0xbc/0x2b0 #3: (&subdev->mutex){+.+.+.}, a...
2013 Jan 03
2
3.8-rc2: EFI framebuffer lock inversion...
On 3.8-rc2 with lockdep enabled and dual-GPU setup (Macbook Pro Retina), I see two releated lock inversion issues with the EFI framebuffer, leading to possible deadlock: when X takes over from the EFI framebuffer [1] and when nouveau releases the framebuffer when being vgaswitcherood [2]. Let me know if you'd like any testing or analysis when I can get the time. Many thanks, Daniel ---