Feb  8 21:09:56 pbx kernel: [ INFO: hard-safe -> hard-unsafe lock order detected ]
Feb  8 21:09:56 pbx kernel: 2.6.18-53.1.6.el5debug #1
Feb  8 21:09:56 pbx kernel: ------------------------------------------------------
Feb  8 21:09:56 pbx kernel: asterisk/9721 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:
Feb  8 21:09:56 pbx kernel:  (zone_lock){--..}, at: [<f8bd2272>] set_tone_zone+0x27/0x70 [zaptel]
Feb  8 21:09:56 pbx kernel: 
Feb  8 21:09:56 pbx kernel: and this task is already holding:
Feb  8 21:09:56 pbx kernel:  (&chan->lock){++..}, at: [<f8bd2339>] zt_specchan_open+0x7e/0x4d3 [zaptel]
Feb  8 21:09:56 pbx kernel: which would create a new lock dependency:
Feb  8 21:09:56 pbx kernel:  (&chan->lock){++..} -> (zone_lock){--..}
Feb  8 21:09:56 pbx kernel: 
Feb  8 21:09:56 pbx kernel: but this new dependency connects a hard-irq-safe lock:
Feb  8 21:09:56 pbx kernel:  (&chan->lock){++..}
Feb  8 21:09:56 pbx kernel: ... which became hard-irq-safe at:
Feb  8 21:09:56 pbx kernel:   [<c043adff>] mark_lock+0x59/0x344
Feb  8 21:09:56 pbx kernel:   [<c043ba64>] __lock_acquire+0x32c/0x922
Feb  8 21:09:56 pbx kernel:   [<f8bda4cc>] zt_receive+0x35/0x742 [zaptel]
Feb  8 21:09:56 pbx kernel:   [<c0406146>] dump_trace+0x8c/0x96
Feb  8 21:09:56 pbx kernel:   [<c043ac9b>] find_usage_backwards+0x56/0x7a
Feb  8 21:09:56 pbx kernel:   [<c043c5a7>] lock_acquire+0x4b/0x68
Feb  8 21:09:56 pbx kernel:   [<f8bda4cc>] zt_receive+0x35/0x742 [zaptel]
Feb  8 21:09:56 pbx kernel:   [<c06117cf>] _spin_lock_irqsave+0x20/0x2f
Feb  8 21:09:56 pbx kernel:   [<f8bda4cc>] zt_receive+0x35/0x742 [zaptel]
Feb  8 21:09:56 pbx kernel:   [<f8bda4cc>] zt_receive+0x35/0x742 [zaptel]
Feb  8 21:09:56 pbx kernel:   [<c0426cbf>] printk+0x18/0x8e
Feb  8 21:09:56 pbx kernel:   [<f8b7c441>] t4_prep_gen2+0x119/0x148 [wct4xxp]
Feb  8 21:09:56 pbx kernel:   [<f8b7ffb5>] t4_interrupt_gen2+0x17d/0x6d28 [wct4xxp]
Feb  8 21:09:56 pbx kernel:   [<c041ff40>] task_rq_lock+0x36/0x5d
Feb  8 21:09:56 pbx kernel:   [<c043bb3a>] __lock_acquire+0x402/0x922
Feb  8 21:09:56 pbx kernel:   [<c041ff40>] task_rq_lock+0x36/0x5d
Feb  8 21:09:56 pbx kernel:   [<c04204ef>] try_to_wake_up+0x371/0x37b
Feb  8 21:09:56 pbx kernel:   [<c0439871>] clocksource_get_next+0xa/0x3f
Feb  8 21:09:56 pbx kernel:   [<c043bb3a>] __lock_acquire+0x402/0x922
Feb  8 21:09:56 pbx kernel:   [<c042e172>] do_timer+0x793/0x8a9
Feb  8 21:09:56 pbx kernel:   [<c040895f>] timer_interrupt+0x27/0x84
Feb  8 21:09:56 pbx kernel:   [<c043bb3a>] __lock_acquire+0x402/0x922
Feb  8 21:09:56 pbx kernel:   [<c0451b94>] __do_IRQ+0x3a/0xec
Feb  8 21:09:56 pbx kernel:   [<c043bb3a>] __lock_acquire+0x402/0x922
Feb  8 21:09:56 pbx kernel:   [<c0451b2f>] handle_IRQ_event+0x1c/0x47
Feb  8 21:09:56 pbx kernel:   [<c0451bee>] __do_IRQ+0x94/0xec
Feb  8 21:09:56 pbx kernel:   [<c04075fe>] do_IRQ+0x9b/0xb9
Feb  8 21:09:56 pbx kernel:   [<ffffffff>] 0xffffffff
Feb  8 21:09:56 pbx kernel: