[asterisk-dev] Zaptel issue in FC6

Aryanto Rachmad aryanto at chello.at
Fri Sep 15 16:11:21 MST 2006


Hello All,

Attached is some information which is always reported on /var/log/messages since I started
to use FC6. I have no clue at all about the impact though as everthing seems to be working
normally.

I have posted this issue on Fedora-test-list and suggested to report it here. It was said
that this is an indication of a bug in zaptel driver. Is it not?

Cheers,

Anto
----

kernel: ======================================================
kernel: [ INFO: hard-safe -> hard-unsafe lock order detected ]
kernel: 2.6.17-1.2647.fc6 #1
kernel: ------------------------------------------------------
kernel: asterisk/1374 [HC0[0]:SC0[0]:HE0:SE1] is trying to acquire:
kernel:  (zone_lock){--..}, at: [<f8a6b693>] set_tone_zone+0x43/0x90 [zaptel]
kernel:
kernel: and this task is already holding:
kernel:  (&chan->lock){++..}, at: [<f8a6e327>] initialize_channel+0x37/0x540 [zaptel]
kernel: which would create a new lock dependency:
kernel:  (&chan->lock){++..} -> (zone_lock){--..}
kernel:
kernel: but this new dependency connects a hard-irq-safe lock:
kernel:  (&chan->lock){++..}
kernel: ... which became hard-irq-safe at:
kernel:   [<c043c176>] lock_acquire+0x4b/0x6d
kernel:   [<c06156c7>] _spin_lock_irqsave+0x22/0x32
kernel:   [<f8a6beb7>] zt_ec_chunk+0x17/0x10a0 [zaptel]
kernel:   [<f89363ab>] wctdm_interrupt+0xd7b/0x17c0 [wctdm]
kernel:   [<c04511b4>] handle_IRQ_event+0x20/0x4d
kernel:   [<c0451275>] __do_IRQ+0x94/0xef
kernel:   [<c040678d>] do_IRQ+0x9e/0xbd
kernel:
kernel: to a hard-irq-unsafe lock:
kernel:  (zone_lock){--..}
kernel: ... which became hard-irq-unsafe at:
kernel: ...  [<c043c176>] lock_acquire+0x4b/0x6d
kernel:   [<c06153f0>] _write_lock+0x19/0x28
kernel:   [<f8a74d07>] zt_ioctl+0x157/0x15b0 [zaptel]
kernel:   [<c048356a>] do_ioctl+0x4e/0x67
kernel:   [<c04837db>] vfs_ioctl+0x258/0x26b
kernel:   [<c0483835>] sys_ioctl+0x47/0x62
kernel:   [<c0403faf>] syscall_call+0x7/0xb
kernel:
kernel: other info that might help us debug this:
kernel:
kernel: 1 lock held by asterisk/1374:
kernel:  #0:  (&chan->lock){++..}, at: [<f8a6e327>] initialize_channel+0x37/0x540 [zaptel]
kernel:
kernel: the hard-irq-safe lock's dependencies:
kernel: -> (&chan->lock){++..} ops: 0 {
kernel:    initial-use  at:
kernel:                         [<c043c176>] lock_acquire+0x4b/0x6d
kernel:                         [<c06156c7>] _spin_lock_irqsave+0x22/0x32
kernel:                         [<f8a6b4a2>] zt_reallocbufs+0x32/0x1e0 [zaptel]
kernel:                         [<f8a6ebe4>] close_channel+0x14/0x390 [zaptel]
kernel:                         [<f8a6f01a>] zt_chan_reg+0xba/0x160 [zaptel]
kernel:                         [<f8a6f1a8>] zt_register+0xe8/0x2b0 [zaptel]
kernel:                         [<f893717c>] wctdm_init_one+0x38c/0x1150 [wctdm]
kernel:                         [<c04f4241>] pci_device_probe+0x39/0x5b
kernel:                         [<c05552d6>] driver_probe_device+0x45/0x92
kernel:                         [<c0555403>] __driver_attach+0x68/0x93
kernel:                         [<c0554d4f>] bus_for_each_dev+0x3a/0x5f
kernel:                         [<c0555231>] driver_attach+0x14/0x17
kernel:                         [<c0554a26>] bus_add_driver+0x68/0x106
kernel:                         [<c05556ac>] driver_register+0x78/0x7d
kernel:                         [<c04f4392>] __pci_register_driver+0x4f/0x69
kernel:                         [<f8846071>] 0xf8846071
kernel:                         [<c04426ce>] sys_init_module+0x16ad/0x1856
kernel:                         [<c0403faf>] syscall_call+0x7/0xb
kernel:    in-hardirq-W at:
kernel:                         [<c043c176>] lock_acquire+0x4b/0x6d
kernel:                         [<c06156c7>] _spin_lock_irqsave+0x22/0x32
kernel:                         [<f8a6beb7>] zt_ec_chunk+0x17/0x10a0 [zaptel]
kernel:                         [<f89363ab>] wctdm_interrupt+0xd7b/0x17c0 [wctdm]
kernel:                         [<c04511b4>] handle_IRQ_event+0x20/0x4d
kernel:                         [<c0451275>] __do_IRQ+0x94/0xef
kernel:                         [<c040678d>] do_IRQ+0x9e/0xbd
kernel:    in-softirq-W at:
kernel:                         [<c043c176>] lock_acquire+0x4b/0x6d
kernel:                         [<c06156c7>] _spin_lock_irqsave+0x22/0x32
kernel:                         [<f8a6beb7>] zt_ec_chunk+0x17/0x10a0 [zaptel]
kernel:                         [<f89363ab>] wctdm_interrupt+0xd7b/0x17c0 [wctdm]
kernel:                         [<c04511b4>] handle_IRQ_event+0x20/0x4d
kernel:                         [<c0451275>] __do_IRQ+0x94/0xef
kernel:                         [<c040678d>] do_IRQ+0x9e/0xbd
kernel:  }
kernel:  ... key      at: [<f8a87f1c>] __key.18214+0x0/0xffff207b [zaptel]
kernel:
kernel: the hard-irq-unsafe lock's dependencies:
kernel: -> (zone_lock){--..} ops: 0 {
kernel:    initial-use  at:
kernel:                         [<c043c176>] lock_acquire+0x4b/0x6d
kernel:                         [<c06153f0>] _write_lock+0x19/0x28
kernel:                         [<f8a74d07>] zt_ioctl+0x157/0x15b0 [zaptel]
kernel:                         [<c048356a>] do_ioctl+0x4e/0x67
kernel:                         [<c04837db>] vfs_ioctl+0x258/0x26b
kernel:                         [<c0483835>] sys_ioctl+0x47/0x62
kernel:                         [<c0403faf>] syscall_call+0x7/0xb
kernel:    softirq-on-W at:
kernel:                         [<c043c176>] lock_acquire+0x4b/0x6d
kernel:                         [<c06153f0>] _write_lock+0x19/0x28
kernel:                         [<f8a74d07>] zt_ioctl+0x157/0x15b0 [zaptel]
kernel:                         [<c048356a>] do_ioctl+0x4e/0x67
kernel:                         [<c04837db>] vfs_ioctl+0x258/0x26b
kernel:                         [<c0483835>] sys_ioctl+0x47/0x62
kernel:                         [<c0403faf>] syscall_call+0x7/0xb
kernel:    hardirq-on-W at:
kernel:                         [<c043c176>] lock_acquire+0x4b/0x6d
kernel:                         [<c06153f0>] _write_lock+0x19/0x28
kernel:                         [<f8a74d07>] zt_ioctl+0x157/0x15b0 [zaptel]
kernel:                         [<c048356a>] do_ioctl+0x4e/0x67
kernel:                         [<c04837db>] vfs_ioctl+0x258/0x26b
kernel:                         [<c0483835>] sys_ioctl+0x47/0x62
kernel:                         [<c0403faf>] syscall_call+0x7/0xb
kernel:  }
kernel:  ... key      at: [<f8a7e3b8>] zone_lock+0x10/0xffffbbef [zaptel]
kernel:
kernel: stack backtrace:
kernel:  [<c04051ee>] show_trace_log_lvl+0x58/0x171
kernel:  [<c0405802>] show_trace+0xd/0x10
kernel:  [<c040591b>] dump_stack+0x19/0x1b
kernel:  [<c043af24>] check_usage+0x1ee/0x1fb
kernel:  [<c043ba91>] __lock_acquire+0x828/0x99c
kernel:  [<c043c176>] lock_acquire+0x4b/0x6d
kernel:  [<c06154d2>] _read_lock+0x19/0x28
kernel:  [<f8a6b693>] set_tone_zone+0x43/0x90 [zaptel]
kernel:  [<f8a6e64d>] initialize_channel+0x35d/0x540 [zaptel]
kernel:  [<f8a7587b>] zt_ioctl+0xccb/0x15b0 [zaptel]
kernel:  [<c048356a>] do_ioctl+0x4e/0x67
kernel:  [<c04837db>] vfs_ioctl+0x258/0x26b
kernel:  [<c0483835>] sys_ioctl+0x47/0x62
kernel:  [<c0403faf>] syscall_call+0x7/0xb
kernel: DWARF2 unwinder stuck at syscall_call+0x7/0xb
kernel: Leftover inexact backtrace:
kernel:  [<c0405802>] show_trace+0xd/0x10
kernel:  [<c040591b>] dump_stack+0x19/0x1b
kernel:  [<c043af24>] check_usage+0x1ee/0x1fb
kernel:  [<c043ba91>] __lock_acquire+0x828/0x99c
kernel:  [<c043c176>] lock_acquire+0x4b/0x6d
kernel:  [<c06154d2>] _read_lock+0x19/0x28
kernel:  [<f8a6b693>] set_tone_zone+0x43/0x90 [zaptel]
kernel:  [<f8a6e64d>] initialize_channel+0x35d/0x540 [zaptel]
kernel:  [<f8a7587b>] zt_ioctl+0xccb/0x15b0 [zaptel]
kernel:  [<c048356a>] do_ioctl+0x4e/0x67
kernel:  [<c04837db>] vfs_ioctl+0x258/0x26b
kernel:  [<c0483835>] sys_ioctl+0x47/0x62
kernel:  [<c0403faf>] syscall_call+0x7/0xb




More information about the asterisk-dev mailing list