Displaying 2 results from an estimated 2 matches for "ffffffff810a5b4".
Did you mean:
ffffffff810a5b4e
2013 Aug 27
0
[PATCH 6/9] drm/nouveau: Convert event handler list to RCU
...70
[<ffffffff810f71ca>] handle_fasteoi_irq+0x5a/0x100
[<ffffffff81004512>] handle_irq+0x22/0x40
[<ffffffff817691fa>] do_IRQ+0x5a/0xd0
[<ffffffff8175f76f>] ret_from_intr+0x0/0x13
[<ffffffff8100b876>] arch_cpu_idle+0x26/0x30
[<ffffffff810a5b4e>] cpu_startup_entry+0xce/0x410
[<ffffffff81743d4e>] start_secondary+0x255/0x25c
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0 CPU1
---- ----
lock(&(&event->lock)->rlock);...
2013 Aug 27
11
[PATCH 0/9] drm/nouveau: Cleanup event/handler design
This series was originally motivated by a deadlock, introduced in
commit 1d7c71a3e2f77336df536855b0efd2dc5bdeb41b
'drm/nouveau/disp: port vblank handling to event interface',
due to inverted lock order between nouveau_drm_vblank_enable()
and nouveau_drm_vblank_handler() (the complete
lockdep report is included in the patch 4/5 changelog).
Because this series fixes the vblank event